diff --git a/all_091625_olmo_batched_categorized.csv b/all_091625_olmo_batched_categorized.csv new file mode 100644 index 0000000..391679f --- /dev/null +++ b/all_091625_olmo_batched_categorized.csv @@ -0,0 +1,151688 @@ +id,task_title,comment_text,comment_type,cleaned_sentences,sentence_categories +56791,VisualEditor: Editing at top of page shows pawn/slug character,"pawn character editing + +seen on master branch (beta labs) as of 30 September. + +open a page on beta labs in VE + +begin editing at default location or top-left beginning of page + +pawn character appears upon entering text + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F12377}",task_description,"['VisualEditor: Editing at top of page shows pawn/slug character\n\npawn character editing\n\nseen on master branch (beta labs) as of 30 September.', 'open a page on beta labs in VE\n\nbegin editing at default location or top-left beginning of page\n\npawn character appears upon entering text\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F12377}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +269631,VisualEditor: Editing at top of page shows pawn/slug character,"Change 86685 merged by jenkins-bot: +Follow-up to 9b999622: don't slug paragraphs that contain just a text node + +https://gerrit.wikimedia.org/r/86685",task_subcomment,"[""Change 86685 merged by jenkins-bot:\nFollow-up to 9b999622: don't slug paragraphs that contain just a text node\n\nGERRIT_URL""]",['ACTION ON ISSUE'] +269628,VisualEditor: Editing at top of page shows pawn/slug character,*** Bug 54785 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54785 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +269622,VisualEditor: Editing at top of page shows pawn/slug character,"Change 86685 had a related patch set uploaded by Catrope: +Follow-up to 9b999622: don't slug paragraphs that contain just a text node + +https://gerrit.wikimedia.org/r/86685",task_subcomment,"[""Change 86685 had a related patch set uploaded by Catrope:\nFollow-up to 9b999622: don't slug paragraphs that contain just a text node\n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION'] +56737,Don't release any new VE updates for three months,"**Author:** `Wikifram` + +**Description:** +After the failure of VE (e.g. witness the opt-in at the three largest wikipedia versions), the WMF now comes with MW 1.22wmf19, which creates more errors than it solves for VE, as could be predicted by anyone remotely busy with VE. I have documented some problems I found with minimal testing, there are probably a lot more. The version doesn't do what the release notes claim (e.g. reflists can't be moved, not that they often need moving anyway; many templates can't be moved either), and doesn't solve the major problems that existed with the one thing that could somewhat be dragged, images. + +Multiplying known problems instead of solving them, when there are plenty of major problems which have turned away most of your user- and testbase, is simply stupid. + +No one is waiting for weekly updates (certainly not of this ""quality""). Please, PLEASE, stop it; get back to the bug list, solve the 50 most urgent ones, ''test them thoroughly yourselves"", and then come to us, present the improvements, and ''ask'' us whether we want to implement and test them. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"[""Don't release any new VE updates for three months\n\n**Author:** CODE\n\n**Description:**\nAfter the failure of VE (e.g."", 'witness the opt-in at the three largest wikipedia versions), the WMF now comes with MW 1.22wmf19, which creates more errors than it solves for VE, as could be predicted by anyone remotely busy with VE.', 'I have documented some problems I found with minimal testing, there are probably a lot more.', ""The version doesn't do what the release notes claim (e.g."", ""reflists can't be moved, not that they often need moving anyway; many templates can't be moved either), and doesn't solve the major problems that existed with the one thing that could somewhat be dragged, images."", 'Multiplying known problems instead of solving them, when there are plenty of major problems which have turned away most of your user- and testbase, is simply stupid.', 'No one is waiting for weekly updates (certainly not of this ""quality"").', 'Please, PLEASE, stop it; get back to the bug list, solve the 50 most urgent ones, \'\'test them thoroughly yourselves"", and then come to us, present the improvements, and \'\'ask\'\' us whether we want to implement and test them.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']" +266589,Don't release any new VE updates for three months,"**Wikifram** wrote: + +Allright, thanks to both for the reply.",task_subcomment,"['**Wikifram** wrote:\n\nAllright, thanks to both for the reply.']",['SOLUTION DISCUSSION'] +266583,Don't release any new VE updates for three months,"(In reply to comment #4) +> Is that an official policy or wishful thinking? + +VE product manager James Forrester told to Tech Ambassadors at +See also http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-September/000416.html + +""However, if there is community consensus that your wiki does not want it +yet or is not ready, it can of course be reversed to ""opt-in"" - just file a +Bugzilla request or contact your local community liaison.""",task_subcomment,"['(In reply to comment #4)\nQUOTE\n\nVE product manager James Forrester told to Tech Ambassadors at \nSee also URL\n\n""However, if there is community consensus that your wiki does not want it\nyet or is not ready, it can of course be reversed to ""opt-in"" - just file a\nBugzilla request or contact your local community liaison.""']",['FUTURE PLAN'] +266576,Don't release any new VE updates for three months,"(In reply to comment #4) +> MZMcBride, is that an official policy or wishful thinking? I can't an +> official statement that declares that the opt-in is now an automatic right of +> all Wikipedias if they want it. + +How official would you like the statement to be? I've declared this both on Bugzilla and on-wiki (on the English Wikipedia). + +Is there any Wikimedia wiki community having trouble getting VisualEditor switched from opt-out to opt-in?",task_subcomment,"['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\n\nHow official would you like the statement to be?', ""I've declared this both on Bugzilla and on-wiki (on the English Wikipedia)."", 'Is there any Wikimedia wiki community having trouble getting VisualEditor switched from opt-out to opt-in?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']" +266571,Don't release any new VE updates for three months,"**Wikifram** wrote: + +MZMcBride, is that an official policy or wishful thinking? I can't an official statement that declares that the opt-in is now an automatic right of all Wikipedias if they want it.",task_subcomment,"['**Wikifram** wrote:\n\nMZMcBride, is that an official policy or wishful thinking?', ""I can't an official statement that declares that the opt-in is now an automatic right of all Wikipedias if they want it.""]","['SOLUTION DISCUSSION', 'FUTURE PLAN']" +266567,Don't release any new VE updates for three months,"**Wikifram** wrote: + +While it is an improvement that the wikis can request an opt-in, I'm not interested in that. You (WMF) are pushing untested, deficient software to us, making things even worse when tempers are already running high; we don't have the means to stop your releases apparently (or if we did stop them, some people would again get very upset probably). I'll try to find a better location for this, but this is not about the policy, this is about the VE being one major bug that shouldn't be released at all until it is seriously improved.",task_subcomment,"[""**Wikifram** wrote:\n\nWhile it is an improvement that the wikis can request an opt-in, I'm not interested in that."", ""You (WMF) are pushing untested, deficient software to us, making things even worse when tempers are already running high; we don't have the means to stop your releases apparently (or if we did stop them, some people would again get very upset probably)."", ""I'll try to find a better location for this, but this is not about the policy, this is about the VE being one major bug that shouldn't be released at all until it is seriously improved.""]","['SOLUTION DISCUSSION', 'MOTIVATION', 'BUG REPRODUCTION']" +266563,Don't release any new VE updates for three months,"I agree with Andre here. + +Though I'll also point out that, while it's a little less than ideal, any Wikimedia wiki that currently has opt-out VisualEditor deployed can request that VisualEditor be switched to opt-in mode (similar to the setup on the German and English Wikipedias) by establishing a local community consensus. For further info, users should consult [[m:Requesting wiki configuration changes]].",task_subcomment,"['I agree with Andre here.', ""Though I'll also point out that, while it's a little less than ideal, any Wikimedia wiki that currently has opt-out VisualEditor deployed can request that VisualEditor be switched to opt-in mode (similar to the setup on the German and English Wikipedias) by establishing a local community consensus."", 'For further info, users should consult [[m:Requesting wiki configuration changes]].']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE']" +266557,Don't release any new VE updates for three months,"Discussing deployment policies is nothing that should happen in a technical bugtracker (however once a discussion *has* taken place in a better suited place, the request for changing the configuration based on that consensus can be filed as a ticket in Bugzilla). +Please take this discussion to the talk page or to the mailing list instead to *discuss* this request first, as statements here seem to be rather subjective (which does not necessarily mean ""wrong"" though). +Thanks for your understanding.",task_subcomment,"['Discussing deployment policies is nothing that should happen in a technical bugtracker (however once a discussion *has* taken place in a better suited place, the request for changing the configuration based on that consensus can be filed as a ticket in Bugzilla).', 'Please take this discussion to the talk page or to the mailing list instead to *discuss* this request first, as statements here seem to be rather subjective (which does not necessarily mean ""wrong"" though).', 'Thanks for your understanding.']","['FUTURE PLAN', 'SOLUTION USAGE', 'ACTION ON ISSUE']" +56712,VisualEditor: Snowmen appear near newly added references,"See last line of this diff: https://fr.wikipedia.org/w/index.php?title=T%C3%A9l%C3%A9com_SudParis&diff=next&oldid=97023702 . + +Steps to reproduce, as provided by user: Seudo. + +1) Go to https://fr.wikipedia.org/wiki/Cumul_des_mandats_en_France - you don't need to save later +2) Click on Modifier +3) Place the cursor after the words « exercice simultané de mandats » (5th line, I think) +4) Click ""Plus->Référence"" +5) Write something in the dialog, i.e. ""toto."" +6) Save the reference +7) Click at the left or at the right of the newly added reference +8) Watch pawns multiplyin' as you keep clicking. +Suedo adds that in his console Web he also got a Javascript error, TypeError: group.firstNodes[index2] is undefined (load.php:54) . + +I was able to reproduce this as well, but only with FF (exactly like Seudo), only in the actual article - not in my sandbox - and only clicking at the left of the word. The user reports instead that this might happen at any point in the page. + +My edits in the sandbox could not reproduce the issue but generated https://bugzilla.wikimedia.org/show_bug.cgi?id=54341 instead. + +Thanks. + +-------------------------- +**Version**: unspecified +**Severity**: critical +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=54976",task_description,"['VisualEditor: Snowmen appear near newly added references\n\nSee last line of this diff: URL .', 'Steps to reproduce, as provided by user: Seudo.', '1) Go to URL - you don\'t need to save later\n2) Click on Modifier \n3) Place the cursor after the words « exercice simultané de mandats » (5th line, I think)\n4) Click ""Plus->Référence""\n5) Write something in the dialog, i.e.', '""toto.""', ""6) Save the reference\n7) Click at the left or at the right of the newly added reference\n8) Watch pawns multiplyin' as you keep clicking."", 'Suedo adds that in his console Web he also got a Javascript error, TypeError: group.firstNodes[index2] is undefined (load.php:54) .', 'I was able to reproduce this as well, but only with FF (exactly like Seudo), only in the actual article - not in my sandbox - and only clicking at the left of the word.', 'The user reports instead that this might happen at any point in the page.', 'My edits in the sandbox could not reproduce the issue but generated URL instead.', 'Thanks.', '--------------------------\n**Version**: unspecified\n**Severity**: critical\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']" +264896,VisualEditor: Snowmen appear near newly added references,"(In reply to Elitre from comment #22) +> More examples from it.wp: +> https://it.wikipedia.org/w/index. +> php?title=Natale_Ciravolo&diff=67212907&oldid=67197341 , +> https://it.wikipedia.org/w/index.php?title=Utente:Nnvu/ +> Sandbox1&diff=prev&oldid=67108020 . + +This is bug 67992 I think.",task_subcomment,['(In reply to Elitre from comment #22)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis is bug 67992 I think.'],['OBSERVED BUG BEHAVIOR'] +264891,VisualEditor: Snowmen appear near newly added references,"More examples from it.wp: https://it.wikipedia.org/w/index.php?title=Natale_Ciravolo&diff=67212907&oldid=67197341 , https://it.wikipedia.org/w/index.php?title=Utente:Nnvu/Sandbox1&diff=prev&oldid=67108020 .",task_subcomment,"['More examples from it.wp: URL , URL .']",['SOLUTION DISCUSSION'] +264886,VisualEditor: Snowmen appear near newly added references,"I believe this is happening again at it.wp. +See https://it.wikipedia.org/w/index.php?title=AA.VV.&diff=prev&oldid=67188720 (snowmen) or https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Pagina_delle_prove_VE&diff=next&oldid=67195802 (pawn). +What you need to reproduce: just create a base reference, add the template Cita, add something as its first parameter, then hit Space/type something else in the reference before saving.",task_subcomment,"['I believe this is happening again at it.wp.', 'See URL (snowmen) or URL (pawn).', 'What you need to reproduce: just create a base reference, add the template Cita, add something as its first parameter, then hit Space/type something else in the reference before saving.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +264881,VisualEditor: Snowmen appear near newly added references,"Um, folks, this may be happening again... please see bug:61272...",task_subcomment,"['Um, folks, this may be happening again... please see bug:61272...']",['OBSERVED BUG BEHAVIOR'] +264877,VisualEditor: Snowmen appear near newly added references,*** Bug 54976 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54976 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +264873,VisualEditor: Snowmen appear near newly added references,"(In reply to comment #12) +> Change 87455 had a related patch set uploaded by Catrope: +> When cloning the InternalList, pass through properties that aren't rebuilt +> +> https://gerrit.wikimedia.org/r/87455 + +I just deployed this change, and the article linked in comment 0 now works for me on frwiki.",task_subcomment,"['(In reply to comment #12)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI just deployed this change, and the article linked in comment 0 now works for me on frwiki.']",['SOLUTION USAGE'] +264869,VisualEditor: Snowmen appear near newly added references,"Change 87459 merged by jenkins-bot: +When cloning the InternalList, pass through properties that aren't rebuilt + +https://gerrit.wikimedia.org/r/87459",task_subcomment,"[""Change 87459 merged by jenkins-bot:\nWhen cloning the InternalList, pass through properties that aren't rebuilt\n\nGERRIT_URL""]",['BUG REPRODUCTION'] +264863,VisualEditor: Snowmen appear near newly added references,"Change 87458 merged by jenkins-bot: +When cloning the InternalList, pass through properties that aren't rebuilt + +https://gerrit.wikimedia.org/r/87458",task_subcomment,"[""Change 87458 merged by jenkins-bot:\nWhen cloning the InternalList, pass through properties that aren't rebuilt\n\nGERRIT_URL""]",['BUG REPRODUCTION'] +264855,VisualEditor: Snowmen appear near newly added references,"Change 87455 merged by jenkins-bot: +When cloning the InternalList, pass through properties that aren't rebuilt + +https://gerrit.wikimedia.org/r/87455",task_subcomment,"[""Change 87455 merged by jenkins-bot:\nWhen cloning the InternalList, pass through properties that aren't rebuilt\n\nGERRIT_URL""]",['BUG REPRODUCTION'] +264849,VisualEditor: Snowmen appear near newly added references,"Change 87459 had a related patch set uploaded by Jforrester: +When cloning the InternalList, pass through properties that aren't rebuilt + +https://gerrit.wikimedia.org/r/87459",task_subcomment,"[""Change 87459 had a related patch set uploaded by Jforrester:\nWhen cloning the InternalList, pass through properties that aren't rebuilt\n\nGERRIT_URL""]",['ACTION ON ISSUE'] +264844,VisualEditor: Snowmen appear near newly added references,"Change 87458 had a related patch set uploaded by Jforrester: +When cloning the InternalList, pass through properties that aren't rebuilt + +https://gerrit.wikimedia.org/r/87458",task_subcomment,"[""Change 87458 had a related patch set uploaded by Jforrester:\nWhen cloning the InternalList, pass through properties that aren't rebuilt\n\nGERRIT_URL""]",['ACTION ON ISSUE'] +264837,VisualEditor: Snowmen appear near newly added references,"Change 87455 had a related patch set uploaded by Catrope: +When cloning the InternalList, pass through properties that aren't rebuilt + +https://gerrit.wikimedia.org/r/87455",task_subcomment,"[""Change 87455 had a related patch set uploaded by Catrope:\nWhen cloning the InternalList, pass through properties that aren't rebuilt\n\nGERRIT_URL""]",['BUG REPRODUCTION'] +264833,VisualEditor: Snowmen appear near newly added references,*** Bug 54917 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54917 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +264828,VisualEditor: Snowmen appear near newly added references,I was able to reproduce this on that frwiki article just now. I get the same error about group.firstNodes[group2] being undefined. Investigating further.,task_subcomment,"['I was able to reproduce this on that frwiki article just now.', 'I get the same error about group.firstNodes[group2] being undefined.', 'Investigating further.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +264823,VisualEditor: Snowmen appear near newly added references,Being able to add references without corrupting the article is a core requirement. Updating the severity to critical.,task_subcomment,"['Being able to add references without corrupting the article is a core requirement.', 'Updating the severity to critical.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +264817,VisualEditor: Snowmen appear near newly added references,"Same for me too, it appears literally impossible to add a reference without snowmen and a bogus reference tag (FF 24.0, Windows 7): + +https://en.wikipedia.org/w/index.php?title=X_Window_System&diff=575630218&oldid=575623976",task_subcomment,"['Same for me too, it appears literally impossible to add a reference without snowmen and a bogus reference tag (FF 24.0, Windows 7):\n\nURL']",['OBSERVED BUG BEHAVIOR'] +264811,VisualEditor: Snowmen appear near newly added references,"Could this please have a priority assigned? Other editors are finding it a blocker to editing with references: + +This bug is really annoying! Every time I add a new reference I can't do anything after it because whatever I click on my keyboard the snowmen appear! Even clicking backspace to delete them multiplies them along with already existing text! Only way to get out of there is to cancel my edit and lose the work I've done! :/ Basically, VE can't be used almost at all at this point, since every addition to an article has to have a reference too! Is there any information about when this bug will get fixed? TeamGale 04:35, 3 October 2013 (UTC)",task_subcomment,"['Could this please have a priority assigned?', 'Other editors are finding it a blocker to editing with references:\n\nThis bug is really annoying!', ""Every time I add a new reference I can't do anything after it because whatever I click on my keyboard the snowmen appear!"", 'Even clicking backspace to delete them multiplies them along with already existing text!', ""Only way to get out of there is to cancel my edit and lose the work I've done!"", "":/ Basically, VE can't be used almost at all at this point, since every addition to an article has to have a reference too!"", 'Is there any information about when this bug will get fixed?', 'TeamGale 04:35, 3 October 2013 (UTC)']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']" +264806,VisualEditor: Snowmen appear near newly added references,"My edit above to [[OpenOffice.org]] was in Firefox 24.0, Ubuntu 12.04 distro version.",task_subcomment,"['My edit above to [[OpenOffice.org]] was in Firefox 24.0, Ubuntu 12.04 distro version.']",['BUG REPRODUCTION'] +264801,VisualEditor: Snowmen appear near newly added references,"An instance of this from en.wp. David Gerard reports: + +Dig this: https://en.wikipedia.org/w/index.php?title=OpenOffice.org&diff=575290819&oldid=575267859 +What I was trying to do was add PladaoOffice and a reference link, which appeared to add correctly in the VE. Then I noticed there was a full stop after ""SunShine Office"", so I clicked on it to put the cursor there, and VE added a pile of ""☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃"", and more each time I clicked again. Note also that my carefully constructed reference is gone, leaving only """", and it's added another spurious one of those higher up",task_subcomment,"['An instance of this from en.wp.', 'David Gerard reports:\n\nDig this: URL\nWhat I was trying to do was add PladaoOffice and a reference link, which appeared to add correctly in the VE.', 'Then I noticed there was a full stop after ""SunShine Office"", so I clicked on it to put the cursor there, and VE added a pile of ""☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃☃"", and more each time I clicked again.', 'Note also that my carefully constructed reference is gone, leaving only """", and it\'s added another spurious one of those higher up']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +264796,VisualEditor: Snowmen appear near newly added references,"Please replace the word ""pawns"" with ""snowmen"". Sorry for the confusion.",task_subcomment,"['Please replace the word ""pawns"" with ""snowmen"".', 'Sorry for the confusion.']","['INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE']" +264791,VisualEditor: Snowmen appear near newly added references,"**seudeau** wrote: + +That looks like +https://bugzilla.wikimedia.org/show_bug.cgi?id=53642, which is quite old +though. + +I also tried to reproduced in a user-specific test page, but couldn't.",task_subcomment,"['**seudeau** wrote:\n\nThat looks like \nURL which is quite old\nthough.', ""I also tried to reproduced in a user-specific test page, but couldn't.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +264787,VisualEditor: Snowmen appear near newly added references,"**seudeau** wrote: + +%%%*** Bug 54708 has been marked as a duplicate of this bug. ***%%%",task_subcomment,"['**seudeau** wrote:\n\n%%%*** Bug 54708 has been marked as a duplicate of this bug.', '***%%%']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +264782,VisualEditor: Snowmen appear near newly added references,"A last comment from the user, +<<[...] Sometimes the following error appears, ""Javascript Error: Cannot open another window while another one is active"". Sometimes the text of the page breaks down completely and the browser gets stuck. +Do not try to look at what's on line 54 of load.php, you'll give up quickly :-)>>",task_subcomment,"['A last comment from the user,\n<<[...] Sometimes the following error appears, ""Javascript Error: Cannot open another window while another one is active"".', 'Sometimes the text of the page breaks down completely and the browser gets stuck.', ""Do not try to look at what's on line 54 of load.php, you'll give up quickly :-)>>""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOCIAL CONVERSATION']" +56375,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","For example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"[""VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed\n\nFor example, you can't copy/paste in the edit summary box."", '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +250036,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85784 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85784",task_subcomment,['Change 85784 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +250028,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85783 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85783",task_subcomment,['Change 85783 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +250019,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85784 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85784",task_subcomment,['Change 85784 had a related patch set uploaded by Catrope:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL'],['ACTION ON ISSUE'] +250011,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85783 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85783",task_subcomment,['Change 85783 had a related patch set uploaded by Catrope:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL'],['ACTION ON ISSUE'] +250007,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85204 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85204",task_subcomment,['Change 85204 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +250004,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85204 had a related patch set uploaded by Esanders: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85204",task_subcomment,['Change 85204 had a related patch set uploaded by Esanders:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL'],['ACTION ON ISSUE'] +250001,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Marking as a regression as this is new behaviour in the latest release (version ""false"")",task_subcomment,"['Marking as a regression as this is new behaviour in the latest release (version ""false"")']",['OBSERVED BUG BEHAVIOR'] +249997,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",task_subcomment,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +56341,VisualEditor: [Regression] Unnamed references get their names corrupted,"https://en.wikipedia.org/w/index.php?title=Matt_Chandler_%28pastor%29&curid=37214846&diff=573675359&oldid=571858677 + +For some reason, multiple different unnamed references all get name="":3"" there. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=54445",task_description,"['VisualEditor: [Regression] Unnamed references get their names corrupted\n\nURL\n\nFor some reason, multiple different unnamed references all get name="":3"" there.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +248008,VisualEditor: [Regression] Unnamed references get their names corrupted,*** Bug 54445 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54445 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +247999,VisualEditor: [Regression] Unnamed references get their names corrupted,"James, +I think it can be confusing that the name and the number of a reference do not match, although the links work. +See https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=575128343&oldid=575128003 (the reference #2 gets a ref name:3).",task_subcomment,"['James,\nI think it can be confusing that the name and the number of a reference do not match, although the links work.', 'See URL (the reference #2 gets a ref name:3).']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +247992,VisualEditor: [Regression] Unnamed references get their names corrupted,*** Bug 54654 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54654 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +247985,VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85781 merged by jenkins-bot: +Prevent naming collisions when generating unique reference names + +https://gerrit.wikimedia.org/r/85781",task_subcomment,['Change 85781 merged by jenkins-bot:\nPrevent naming collisions when generating unique reference names\n\nGERRIT_URL'],['ACTION ON ISSUE'] +247979,VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85780 merged by jenkins-bot: +Prevent naming collisions when generating unique reference names + +https://gerrit.wikimedia.org/r/85780",task_subcomment,['Change 85780 merged by jenkins-bot:\nPrevent naming collisions when generating unique reference names\n\nGERRIT_URL'],['ACTION ON ISSUE'] +247974,VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85781 had a related patch set uploaded by Catrope: +Prevent naming collisions when generating unique reference names + +https://gerrit.wikimedia.org/r/85781",task_subcomment,['Change 85781 had a related patch set uploaded by Catrope:\nPrevent naming collisions when generating unique reference names\n\nGERRIT_URL'],['ACTION ON ISSUE'] +247968,VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85780 had a related patch set uploaded by Catrope: +Prevent naming collisions when generating unique reference names + +https://gerrit.wikimedia.org/r/85780",task_subcomment,['Change 85780 had a related patch set uploaded by Catrope:\nPrevent naming collisions when generating unique reference names\n\nGERRIT_URL'],['ACTION ON ISSUE'] +247964,VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85144 merged by jenkins-bot: +Prevent naming collisions when generating unique reference names + +https://gerrit.wikimedia.org/r/85144",task_subcomment,['Change 85144 merged by jenkins-bot:\nPrevent naming collisions when generating unique reference names\n\nGERRIT_URL'],['ACTION ON ISSUE'] +247961,VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85144 had a related patch set uploaded by Catrope: +Failing test for bug + +https://gerrit.wikimedia.org/r/85144",task_subcomment,"['Change 85144 had a related patch set uploaded by Catrope:\nFailing test for bug\n\nGERRIT_URL']",['OBSERVED BUG BEHAVIOR'] +247957,VisualEditor: [Regression] Unnamed references get their names corrupted,"Isolated test case: https://en.wikipedia.org/wiki/User:Ed_g2s/Sandbox4 + +Diagnosis: + +The automatically generated names are based on the number of distinct references in the page up to that point, indexed at zero. The first unnamed tag is the 4th distinct reference on the page (it's preceded by two :1s, a :3 and a :0), so its autogenerated name is :3. However, there so happens to already be a literal on the page, so we get a naming collision and the whole thing goes to hell. + +In practice, this situation can only arise after multiple iterations of duplicating unnamed references with VE (which adds tags to the source), then removing or reordering references so the ref tags are aligned exactly right for this bug to occur.",task_subcomment,"['Isolated test case: URL\n\nDiagnosis:\n\nThe automatically generated names are based on the number of distinct references in the page up to that point, indexed at zero.', ""The first unnamed tag is the 4th distinct reference on the page (it's preceded by two :1s, a :3 and a :0), so its autogenerated name is :3."", 'However, there so happens to already be a literal on the page, so we get a naming collision and the whole thing goes to hell.', 'In practice, this situation can only arise after multiple iterations of duplicating unnamed references with VE (which adds tags to the source), then removing or reordering references so the ref tags are aligned exactly right for this bug to occur.']","['INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +56047,VisualEditor: Corruption with circumflexes,"VisualEditor seems to take particular pleasure in abusing circumflexes. + +Issue 1: VE duplicates the first character entered after a circumflexed letter at the end of a line. + +* Steps to reproduce: In VE, enter the text êtt (actually enter the characters individually, don't copy/paste) at the end of a line. +* Expected result: ""êtt"" is entered. +* Actual result: ""êttt"" is entered. + +Issue 2: At the beginning of a line, VE turns a circumflexed letter into a pawn character when removing text entered after the circumflexed letter. + +* Steps to reproduce: In VE, enter the text êtt at the beginning of a line, then delete the last 't'. +* Expected result: ""êt"" +* Actual result: ""♙t"" + +There's also some wonky behavior when dealing with circumflexed letters in the middle of a line, but I'm assuming that the descriptions above will be enough to help you investigate VE's blatant circumflexphobia. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Corruption with circumflexes\n\nVisualEditor seems to take particular pleasure in abusing circumflexes.', 'Issue 1: VE duplicates the first character entered after a circumflexed letter at the end of a line.', ""* Steps to reproduce: In VE, enter the text êtt (actually enter the characters individually, don't copy/paste) at the end of a line."", '* Expected result: ""êtt"" is entered.', '* Actual result: ""êttt"" is entered.', 'Issue 2: At the beginning of a line, VE turns a circumflexed letter into a pawn character when removing text entered after the circumflexed letter.', ""* Steps to reproduce: In VE, enter the text êtt at the beginning of a line, then delete the last 't'."", '* Expected result: ""êt""\n* Actual result: ""♙t""\n\nThere\'s also some wonky behavior when dealing with circumflexed letters in the middle of a line, but I\'m assuming that the descriptions above will be enough to help you investigate VE\'s blatant circumflexphobia.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254900,VisualEditor: Corruption with circumflexes,"Marking as a duplicate of bug 53680 which I believe is indeed the issue. + +*** This bug has been marked as a duplicate of bug 53680 ***",task_subcomment,"['Marking as a duplicate of bug 53680 which I believe is indeed the issue.', '*** This bug has been marked as a duplicate of bug 53680 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +254898,VisualEditor: Corruption with circumflexes,"This is a dupe of bug 53747, bug 53680 or both.",task_subcomment,"['This is a dupe of bug 53747, bug 53680 or both.']",['OBSERVED BUG BEHAVIOR'] +254894,VisualEditor: Corruption with circumflexes,"Also, circumflexes that are entered in VE are completely stripped on save. Instead, characters are jumping around to its location.",task_subcomment,"['Also, circumflexes that are entered in VE are completely stripped on save.', 'Instead, characters are jumping around to its location.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +55747,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"Since approx. August 30-31 VisualEditor breaks when Polish-language diacritics (ążśźęćń󳥯ŚŹĘĆŃÓŁ) are input. The characters themselves disappear and text around them gets mangled and moved around. + +They're all input using AltGr (right Alt) + diacritic-less version of the characters, with the exception of ""x"" mapping to ""ź"" (so, respectively, azsxecnol). + +I have been unable to replicate the issue myself, but it's definitely happening. + +pl.wp thread: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#VisualEditor_a_polskie_diakrytyki + +This is repeatedly breaking page text on the Polish Wikipedia, so I'm marking the bug ""highest critical"". + +-------------------------- +**Version**: unspecified +**Severity**: critical +**URL**: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#VisualEditor_a_polskie_diakrytyki +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=53680",task_description,"['VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input\n\nSince approx.', 'August 30-31 VisualEditor breaks when Polish-language diacritics (ążśźęćń󳥯ŚŹĘĆŃÓŁ) are input.', 'The characters themselves disappear and text around them gets mangled and moved around.', 'They\'re all input using AltGr (right Alt) + diacritic-less version of the characters, with the exception of ""x"" mapping to ""ź"" (so, respectively, azsxecnol).', ""I have been unable to replicate the issue myself, but it's definitely happening."", 'pl.wp thread: URL\n\nThis is repeatedly breaking page text on the Polish Wikipedia, so I\'m marking the bug ""highest critical"".', '--------------------------\n**Version**: unspecified\n**Severity**: critical\n**URL**: URL\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +237176,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"It seems like it does actually fix the issue (for me at least). Thanks. + +So that means editing will have been completely broken for only three weeks straight by the time this gets deployed :/",task_subcomment,"['It seems like it does actually fix the issue (for me at least).', 'Thanks.', 'So that means editing will have been completely broken for only three weeks straight by the time this gets deployed :/']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +237170,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",task_subcomment,"['Marking this as ""FIXED"" on the expectation that it\'s fixed - please re-open if you find that it is still occurring.']",['ACTION ON ISSUE'] +237164,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"Ok, the patch is merged, and due to go live on mediawiki.org by 13 September 2013: + +https://gerrit.wikimedia.org/r/#/c/82858/ + +Please let us know whether it fixes the bug!",task_subcomment,"['Ok, the patch is merged, and due to go live on mediawiki.org by 13 September 2013:\n\nURL\n\nPlease let us know whether it fixes the bug!']",['SOLUTION USAGE'] +237160,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"I'm optimistic that the following patch will fix this bug: + +https://gerrit.wikimedia.org/r/#/c/82858/ + +If someone can test this hypothesis, great; if not, then I will hopefully be able to do so later today.",task_subcomment,"[""I'm optimistic that the following patch will fix this bug:\n\nURL\n\nIf someone can test this hypothesis, great; if not, then I will hopefully be able to do so later today.""]",['INVESTIGATION AND EXPLORATION'] +237153,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,Is there any progress on this? Because today's the point when I'd suggest reverting the deployment to last known good version if nobody is going to fix this.,task_subcomment,"['Is there any progress on this?', ""Because today's the point when I'd suggest reverting the deployment to last known good version if nobody is going to fix this.""]","['SOLUTION DISCUSSION', 'WORKAROUNDS']" +237146,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"I've tested this on master in Firefox under Ubuntu -- I managed to replicate the behavior not just in polish, but also Spanish diacritics but only when these are ""added on"". Trying to add diacritic to an existing character produced a pawn and then some odd duplication of characters. + +That did not happen when I typed in either Hebrew or Arabic in master. + +Another thing I found is that there seems to be a difference between an already-combined diacritic (like ñ which is native to the Spanish keyboard) and an ""added"" diacritic. When I typed the native ñ nothing broke, it added it properly and the behavior was correct. + +And finally, the typing broke and the pawn appeared only when I tried to add diacritic to a latin letter. + +When I tried to add ""niqqud"" to Hebrew letters, though, like pressing ש and left-Alt+a to produce שְ the behavior was as expected (no pawn, no problem)",task_subcomment,"['I\'ve tested this on master in Firefox under Ubuntu -- I managed to replicate the behavior not just in polish, but also Spanish diacritics but only when these are ""added on"".', 'Trying to add diacritic to an existing character produced a pawn and then some odd duplication of characters.', 'That did not happen when I typed in either Hebrew or Arabic in master.', 'Another thing I found is that there seems to be a difference between an already-combined diacritic (like ñ which is native to the Spanish keyboard) and an ""added"" diacritic.', 'When I typed the native ñ nothing broke, it added it properly and the behavior was correct.', 'And finally, the typing broke and the pawn appeared only when I tried to add diacritic to a latin letter.', 'When I tried to add ""niqqud"" to Hebrew letters, though, like pressing ש and left-Alt+a to produce שְ the behavior was as expected (no pawn, no problem)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +237139,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,Bug 53680 shows this also happens on en.wp and fr.wp and is independent of keyboard layout.,task_subcomment,['Bug 53680 shows this also happens on en.wp and fr.wp and is independent of keyboard layout.'],['OBSERVED BUG BEHAVIOR'] +237130,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"https://pl.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Opinie&oldid=37428181#.C4.99 is a pretty good explanation, and makes clear it's not browser (or OS) dependent.",task_subcomment,"[""URL is a pretty good explanation, and makes clear it's not browser (or OS) dependent.""]",['OBSERVED BUG BEHAVIOR'] +237120,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"Actually, I sort of have reproduced it now. I used Opera 12, but some users at pl.wp reported it happening on Chrome – it's probably not browser-dependent. + +You'll probably need to set your system keyboard to ""Polish (programmer's)"" or similarly named one. (It's the same as standard US layout, but includes the AltGr diacritics. A ""Polish (typist's)"" layout exists on some systems, but nobody ever uses it, so forget it.) + +1. +Try inputting some text with diacritics, such as the ""Pójdź, kińże tę chmurność w głąb flaszy!"" sentence above (copying and pasting text with diacritics doesn't cause issues, you need to type it). (Strings of one character such as ""ąąąą"" tend to work correctly for some reason.) + +2. +Depending on your luck, it might look okay, or you might get parts of the sentence duplicated in the next paragraph. Regardless of that, try backspacing a little now. The cursor will likely be moved to someplace in the next paragraph and unrelated characters will be removed. + +3. +Try previewing the changes. The text will differ from the one shown in editing view.",task_subcomment,"['Actually, I sort of have reproduced it now.', ""I used Opera 12, but some users at pl.wp reported it happening on Chrome – it's probably not browser-dependent."", 'You\'ll probably need to set your system keyboard to ""Polish (programmer\'s)"" or similarly named one.', ""(It's the same as standard US layout, but includes the AltGr diacritics."", 'A ""Polish (typist\'s)"" layout exists on some systems, but nobody ever uses it, so forget it.)', '1.', 'Try inputting some text with diacritics, such as the ""Pójdź, kińże tę chmurność w głąb flaszy!""', ""sentence above (copying and pasting text with diacritics doesn't cause issues, you need to type it)."", '(Strings of one character such as ""ąąąą"" tend to work correctly for some reason.)', '2.', 'Depending on your luck, it might look okay, or you might get parts of the sentence duplicated in the next paragraph.', 'Regardless of that, try backspacing a little now.', 'The cursor will likely be moved to someplace in the next paragraph and unrelated characters will be removed.', '3.', 'Try previewing the changes.', 'The text will differ from the one shown in editing view.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +237112,VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input,"Examples of edits apparently exhibiting this issue: + +* https://pl.wikipedia.org/w/index.php?title=Rondo&curid=122034&diff=37421631&oldid=35999089 - ""Największe rondo"" -> ""Najwi kszerondo"" + +* https://pl.wikipedia.org/w/index.php?title=Euronews&diff=prev&oldid=37394282 - ""dostpna"" should be ""dostępna"", ""Midzyrnodowym"" should be ""Międzynarodowym"", etc. + +* https://pl.wikipedia.org/w/index.php?title=1967&diff=next&oldid=37422197 - ""ki rapers"" should probably be ""Amerykański raper"" (both occurences - this happened on two consecutive edits) + +Results of a user trying to type in ""Pójdź, kińże tę chmurność w głąb flaszy!"" when reproducing this bug: +* https://www.mediawiki.org/w/index.php?title=User:G%C5%BCdacz&oldid=775661 +* https://www.mediawiki.org/w/index.php?title=User:G%C5%BCdacz&oldid=775666",task_subcomment,"['Examples of edits apparently exhibiting this issue:\n\n* URL - ""Największe rondo"" -> ""Najwi kszerondo""\n\n* URL - ""dostpna"" should be ""dostępna"", ""Midzyrnodowym"" should be ""Międzynarodowym"", etc.', '* URL - ""ki rapers"" should probably be ""Amerykański raper"" (both occurences - this happened on two consecutive edits)\n\nResults of a user trying to type in ""Pójdź, kińże tę chmurność w głąb flaszy!""', 'when reproducing this bug:\n* URL\n* URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +55680,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,"I haven't worked out this out fully yet, but it seems that linking or annotating newly added text that contains accented or non-Latin characters frequently causes those characters to disappear. Re-adding them in the same word almost always results in their turning into pawns when, anywhere else on the page, the link dialog is subsequently opened or a link is inserted. + +This happens everywhere on a page including body text, tables and image captions. + +-------------------------- +**Version**: unspecified +**Severity**: critical +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=53747",task_description,"[""VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns\n\nI haven't worked out this out fully yet, but it seems that linking or annotating newly added text that contains accented or non-Latin characters frequently causes those characters to disappear."", 'Re-adding them in the same word almost always results in their turning into pawns when, anywhere else on the page, the link dialog is subsequently opened or a link is inserted.', 'This happens everywhere on a page including body text, tables and image captions.', '--------------------------\n**Version**: unspecified\n**Severity**: critical\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +257414,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,*** Bug 54047 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54047 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +257411,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",task_subcomment,"['Marking this as ""FIXED"" on the expectation that it\'s fixed - please re-open if you find that it is still occurring.']",['ACTION ON ISSUE'] +257405,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,"There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013: + +https://gerrit.wikimedia.org/r/#/c/82858/ + +Please let us know whether it fixes the bug!",task_subcomment,"[""There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:\n\nURL\n\nPlease let us know whether it fixes the bug!""]",['BUG REPRODUCTION'] +257400,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,"(In reply to comment #3) +> Same as bug 53747? + +Yes. I don't want to just merge them though as they're assigned to different people.",task_subcomment,"['(In reply to comment #3)\nQUOTE\n\nYes.', ""I don't want to just merge them though as they're assigned to different people.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +257393,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,Same as bug 53747?,task_subcomment,['Same as bug 53747?'],['MOTIVATION'] +257386,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,"K7L comments: +""I am seeing the same problems if I try to edit ordinary text such as the article intro. Pressing or even makes accented characters in newly-edited text vanish. This editor is not usable for non-English text on this browser [firefox]."" + +This needs to be fixed urgently.",task_subcomment,"['K7L comments:\n""I am seeing the same problems if I try to edit ordinary text such as the article intro.', 'Pressing or even makes accented characters in newly-edited text vanish.', 'This editor is not usable for non-English text on this browser [firefox].""', 'This needs to be fixed urgently.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +257381,VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,"Now also reported on the French Wikipedia: +[[:fr:Route 2 (Ontario)]] and its revision history, the distance chart is a table and Unicode descriptive text added with VisualEditor didn't save properly.[https://fr.wikipedia.org/w/index.php?title=Route_2_%28Ontario%29&diff=96342109&oldid=96342028] The damage was fixed using the standard MW wiki source editor but is still in history. Try inserting « La route 2 va à Montréal (Québec) » (or something/anything that isn't US ASCII) into a table cell and watch it fail to display correctly or fail to save. + + +The fr.wp reported was using an unspecified version of firefox on Vector in Ubuntu. I use Firefox 23 on monobook in Xubuntu. + +Raising this to critical as being able to use all characters in a language is essential.",task_subcomment,"[""Now also reported on the French Wikipedia:\n[[:fr:Route 2 (Ontario)]] and its revision history, the distance chart is a table and Unicode descriptive text added with VisualEditor didn't save properly."", '[URL The damage was fixed using the standard MW wiki source editor but is still in history.', ""Try inserting « La route 2 va à Montréal (Québec) » (or something/anything that isn't US ASCII) into a table cell and watch it fail to display correctly or fail to save."", 'The fr.wp reported was using an unspecified version of firefox on Vector in Ubuntu.', 'I use Firefox 23 on monobook in Xubuntu.', 'Raising this to critical as being able to use all characters in a language is essential.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +55334,Parsoid: Annotated text after a template is deleted,"When inserting any template immediately before any word that is linked or has bold or italic markup, that word is deleted but continues to be displayed in the editing surface. The deletion can only be seen in review changes or upon saving. + +To reproduce: +1. Open any page in VE. +2. Place the cursor immediately before a word (i.e. with no white space between the cursor and word) that is one or more of: + * A link + * Bold text + * Italic text + * plain text that you have just added one of the above to +3. Insert any template at the cursor position +4. Observe the word remains as expected +5. Review changes, and observe the word has been deleted. + +Examples: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=570195482&oldid=570194023 + +On en.wp PamD encountered this bug when inserting a maintenance template at the head of an article that started with a bold word. + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,"['Parsoid: Annotated text after a template is deleted\n\nWhen inserting any template immediately before any word that is linked or has bold or italic markup, that word is deleted but continues to be displayed in the editing surface.', 'The deletion can only be seen in review changes or upon saving.', 'To reproduce:\n1.', 'Open any page in VE.', '2.', 'Place the cursor immediately before a word (i.e.', 'with no white space between the cursor and word) that is one or more of:\n * A link\n * Bold text\n * Italic text\n * plain text that you have just added one of the above to\n3.', 'Insert any template at the cursor position\n4.', 'Observe the word remains as expected\n5. Review changes, and observe the word has been deleted.', 'Examples: URL\n\nOn en.wp PamD encountered this bug when inserting a maintenance template at the head of an article that started with a bold word.', '--------------------------\n**Version**: unspecified\n**Severity**: critical']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +237055,Parsoid: Annotated text after a template is deleted,This is the same Parsoid bug that affected both places where we implicitly assumed that the 'about' id is always present (without realizing/checking that it could be absent for VE-inserted transclusions).,task_subcomment,"[""This is the same Parsoid bug that affected both places where we implicitly assumed that the 'about' id is always present (without realizing/checking that it could be absent for VE-inserted transclusions).""]",['OBSERVED BUG BEHAVIOR'] +237050,Parsoid: Annotated text after a template is deleted," + +*** This bug has been marked as a duplicate of bug 53434 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 53434 ***'],['ACTION ON ISSUE'] +237046,Parsoid: Annotated text after a template is deleted,"HTML + +

barquux

+ +Expected wikitext + +{{Inline|Foo}}'''bar'''quux + +Actual wikitext + +{{Inline|Foo}}quux + +:(",task_subcomment,"['HTML\n\n

barquux

\n\nExpected wikitext\n\n{{Inline|Foo}}\'\'\'bar\'\'\'quux\n\nActual wikitext\n\n{{Inline|Foo}}quux\n\n:(']",['BUG REPRODUCTION'] +237040,Parsoid: Annotated text after a template is deleted,"This does not require pre-existing formatted or linked text. The bug also appears if you enter the template first and then add bold word(s) immediately afterwards (no space between the template and the text), starting from an empty page or in a new paragraph. + +For example, using VisualEditor with the intention of producing this, in this order: + +{{unreferenced}}'''Hello world''' from Wikipedia. + +actually results in this: + +{{unreferenced}} from Wikipedia. + +If you add a space or hit return after the template, then it works as expected.",task_subcomment,"['This does not require pre-existing formatted or linked text.', 'The bug also appears if you enter the template first and then add bold word(s) immediately afterwards (no space between the template and the text), starting from an empty page or in a new paragraph.', ""For example, using VisualEditor with the intention of producing this, in this order:\n\n{{unreferenced}}'''Hello world''' from Wikipedia."", 'actually results in this:\n\n{{unreferenced}} from Wikipedia.', 'If you add a space or hit return after the template, then it works as expected.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +55219,VisualEditor: [Regression] Link inspector prevents insertion of section links,"VE link insertion dialog when attempting to add a section link + +Since the latest update it is impossible to create links to specific sections of a page in VisualEditor: As soon as you enter the # character the link insertion dialog gives an ""Invalid title"" error. See screenshot attached and bug 50881 comment 11. + +I've reported this separately to bug 50881 as that is an enhancement to give proper handling of section links, but this is a regression that blocks all use of links to sections. + +-------------------------- +**Version**: unspecified +**Severity**: critical + +**Attached**: {F11887}",task_description,"['VisualEditor: [Regression] Link inspector prevents insertion of section links\n\nVE link insertion dialog when attempting to add a section link\n\nSince the latest update it is impossible to create links to specific sections of a page in VisualEditor: As soon as you enter the # character the link insertion dialog gives an ""Invalid title"" error.', 'See screenshot attached and bug 50881 comment 11.', ""I've reported this separately to bug 50881 as that is an enhancement to give proper handling of section links, but this is a regression that blocks all use of links to sections."", '--------------------------\n**Version**: unspecified\n**Severity**: critical\n\n**Attached**: {F11887}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']" +254794,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 112898 merged by jenkins-bot: +Include fragments in normalizedTitle + +https://gerrit.wikimedia.org/r/112898",task_subcomment,['Change 112898 merged by jenkins-bot:\nInclude fragments in normalizedTitle\n\nGERRIT_URL'],['ACTION ON ISSUE'] +254789,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 112898 had a related patch set uploaded by Esanders: +Include fragments in normalizedTitle + +https://gerrit.wikimedia.org/r/112898",task_subcomment,['Change 112898 had a related patch set uploaded by Esanders:\nInclude fragments in normalizedTitle\n\nGERRIT_URL'],['ACTION ON ISSUE'] +254783,VisualEditor: [Regression] Link inspector prevents insertion of section links,"(In reply to comment #10) +> Unless I'm missing something obvious, I can't make this work anymore on it.wp +> or Mediawiki. It will just ignore the #name_of_the_section if I add it to an +> existing wikilink and therefore, it will not recognize the link as edited and +> the Save button will stay greyed out. + +Split that issue into bug 61221.",task_subcomment,['(In reply to comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nSplit that issue into bug 61221.'],['INVESTIGATION AND EXPLORATION'] +254776,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Unless I'm missing something obvious, I can't make this work anymore on it.wp or Mediawiki. It will just ignore the #name_of_the_section if I add it to an existing wikilink and therefore, it will not recognize the link as edited and the Save button will stay greyed out.",task_subcomment,"[""Unless I'm missing something obvious, I can't make this work anymore on it.wp or Mediawiki."", 'It will just ignore the #name_of_the_section if I add it to an existing wikilink and therefore, it will not recognize the link as edited and the Save button will stay greyed out.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +254771,VisualEditor: [Regression] Link inspector prevents insertion of section links,… and now deployed.,task_subcomment,['… and now deployed.'],['SOLUTION USAGE'] +254763,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 80507 merged by Catrope: +Modify regex to allow section links as valid titles + +https://gerrit.wikimedia.org/r/80507",task_subcomment,['Change 80507 merged by Catrope:\nModify regex to allow section links as valid titles\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +254756,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 80505 merged by Catrope: +Modify regex to allow section links as valid titles + +https://gerrit.wikimedia.org/r/80505",task_subcomment,['Change 80505 merged by Catrope:\nModify regex to allow section links as valid titles\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +254749,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 80507 had a related patch set uploaded by Jforrester: +Modify regex to allow section links as valid titles + +https://gerrit.wikimedia.org/r/80507",task_subcomment,['Change 80507 had a related patch set uploaded by Jforrester:\nModify regex to allow section links as valid titles\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254743,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 80505 had a related patch set uploaded by Jforrester: +Modify regex to allow section links as valid titles + +https://gerrit.wikimedia.org/r/80505",task_subcomment,['Change 80505 had a related patch set uploaded by Jforrester:\nModify regex to allow section links as valid titles\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254736,VisualEditor: [Regression] Link inspector prevents insertion of section links,This is now fixed in master; we'll cherry-pick it and push live this afternoon. Sorry for the problem.,task_subcomment,"[""This is now fixed in master; we'll cherry-pick it and push live this afternoon."", 'Sorry for the problem.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +254726,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 80417 merged by jenkins-bot: +Modify regex to allow section links as valid titles + +https://gerrit.wikimedia.org/r/80417",task_subcomment,['Change 80417 merged by jenkins-bot:\nModify regex to allow section links as valid titles\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254717,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Change 80417 had a related patch set uploaded by Esanders: +Modify regex to allow section links as valid titles + +https://gerrit.wikimedia.org/r/80417",task_subcomment,['Change 80417 had a related patch set uploaded by Esanders:\nModify regex to allow section links as valid titles\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254708,VisualEditor: [Regression] Link inspector prevents insertion of section links,"Ah, good that someone already reported. Confirmed in mediawiki.org.",task_subcomment,"['Ah, good that someone already reported.', 'Confirmed in mediawiki.org.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +54608,VisualEditor: Template gets removed without editing it,"Steps to reproduce: +1. Go to http://en.wikipedia.org/wiki/Post_and_core +2. Edit it with VE +3. Make some minor edit, by example, add a space after ""is a type"" +4. Review your changes (or save) + +Results: +The {{Interventions infobox|(...)}} gets removed. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor: Template gets removed without editing it\n\nSteps to reproduce:\n1.', 'Go to URL\n2.', 'Edit it with VE\n3.', 'Make some minor edit, by example, add a space after ""is a type""\n4. Review your changes (or save)\n\nResults:\nThe {{Interventions infobox|(...)}} gets removed.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'BUG REPRODUCTION']" +244141,VisualEditor: Template gets removed without editing it,Moving to date we likely fixed this with the changes to DM.,task_subcomment,['Moving to date we likely fixed this with the changes to DM.'],['SOLUTION DISCUSSION'] +244134,VisualEditor: Template gets removed without editing it,"I can't reproduce it anymore either, so I'm closing it.",task_subcomment,"[""I can't reproduce it anymore either, so I'm closing it.""]",['ACTION ON ISSUE'] +244125,VisualEditor: Template gets removed without editing it,"* ""I can't reproduce"" ... the issue. :)",task_subcomment,"['* ""I can\'t reproduce"" ... the issue.', ':)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +244114,VisualEditor: Template gets removed without editing it,"I can't reproduce but the infobox invocation has some garbage in it. + +{{Interventions infobox | + Name = Post and core | + Image = |sesuiatu + Caption = |sasa + ICD10 = |sasas + ICD9 = |sasasasa + MeshID = D011176 | + OPS301 = |sasas + OtherCodes = |sasa +}}",task_subcomment,"[""I can't reproduce but the infobox invocation has some garbage in it."", '{{Interventions infobox |\n Name = Post and core |\n Image = |sesuiatu\n Caption = |sasa\n ICD10 = |sasas\n ICD9 = |sasasasa\n MeshID = D011176 |\n OPS301 = |sasas\n OtherCodes = |sasa\n}}']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +244104,VisualEditor: Template gets removed without editing it,"Roan, thoughts? Selser issue?",task_subcomment,"['Roan, thoughts?', 'Selser issue?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +54466,"VisualEditor: Fix violation of PHP strict standard (""Only variables should be passed by reference in VisualEditor/ApiVisualEditor.php on line 255"")","[error] PHP Strict Standards: Only variables should be passed by reference in /srv/phase3/extensions/VisualEditor/ApiVisualEditor.php on line 255, referer: http://server/wiki/index.php/Sandbox?veaction=edit + +-------------------------- +**Version**: unspecified +**Severity**: trivial",task_description,"['VisualEditor: Fix violation of PHP strict standard (""Only variables should be passed by reference in VisualEditor/ApiVisualEditor.php on line 255"")\n\n[error] PHP Strict Standards: Only variables should be passed by reference in /srv/phase3/extensions/VisualEditor/ApiVisualEditor.php on line 255, referer: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: trivial']",['OBSERVED BUG BEHAVIOR'] +235746,"VisualEditor: Fix violation of PHP strict standard (""Only variables should be passed by reference in VisualEditor/ApiVisualEditor.php on line 255"")",Now fixed in master. Sorry for the slip-up.,task_subcomment,"['Now fixed in master.', 'Sorry for the slip-up.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +235742,"VisualEditor: Fix violation of PHP strict standard (""Only variables should be passed by reference in VisualEditor/ApiVisualEditor.php on line 255"")","Change 77362 merged by jenkins-bot: +Fix notice caused by not passing the WebRequest object by reference + +https://gerrit.wikimedia.org/r/77362",task_subcomment,['Change 77362 merged by jenkins-bot:\nFix notice caused by not passing the WebRequest object by reference\n\nGERRIT_URL'],['ACTION ON ISSUE'] +235740,"VisualEditor: Fix violation of PHP strict standard (""Only variables should be passed by reference in VisualEditor/ApiVisualEditor.php on line 255"")","Change 77362 had a related patch set uploaded by Catrope: +Fix notice caused by not passing the WebRequest object by reference + +https://gerrit.wikimedia.org/r/77362",task_subcomment,['Change 77362 had a related patch set uploaded by Catrope:\nFix notice caused by not passing the WebRequest object by reference\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +54420,"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link","<> + +I tested this as well with Vector on both Chrome and FF, on it.wiki with the word Lettera (which is an existing page), it keeps insisting that I must link to Letteratura instead. I tried a workaround and was able to get Lettere, but it ain't the same thing. +Thanks! + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,"['VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link\n\n<>\n\nI tested this as well with Vector on both Chrome and FF, on it.wiki with the word Lettera (which is an existing page), it keeps insisting that I must link to Letteratura instead.', ""I tried a workaround and was able to get Lettere, but it ain't the same thing."", 'Thanks!', '--------------------------\n**Version**: unspecified\n**Severity**: critical']","['MOTIVATION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +233184,"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link",Fixed and will be deployed tonight.,task_subcomment,['Fixed and will be deployed tonight.'],['SOLUTION USAGE'] +233177,"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link","Change 77264 merged by jenkins-bot: +Don't override link target input value while typing + +https://gerrit.wikimedia.org/r/77264",task_subcomment,"[""Change 77264 merged by jenkins-bot:\nDon't override link target input value while typing\n\nGERRIT_URL""]",['ACTION ON ISSUE'] +233170,"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link","Change 77264 had a related patch set uploaded by Trevor Parscal: +Don't override link target input value while typing + +https://gerrit.wikimedia.org/r/77264",task_subcomment,"[""Change 77264 had a related patch set uploaded by Trevor Parscal:\nDon't override link target input value while typing\n\nGERRIT_URL""]",['ACTION ON ISSUE'] +233163,"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link","I did not know this was a competition, so more from me as well! :p +The ""workaround"" is what I mentioned earlier, but it won't always work. +With it I managed to get ""Lettere"": it autocompleted to Letteratura, then I put the ""e"" after the first ""r"" and cut the rest. But, it did not work to get to ""Lettera"", which was my intended outcome. +This also happens if I am interested in, say, ""Letteratura tedesca"": it won't appear in the drop down list, and I am not even allowed to write it. The only way to get there is writing ""letteraturatedesca"" instead, and adding the space later. This makes sense to VE! Thanks.",task_subcomment,"['I did not know this was a competition, so more from me as well!', ':p\nThe ""workaround"" is what I mentioned earlier, but it won\'t always work.', 'With it I managed to get ""Lettere"": it autocompleted to Letteratura, then I put the ""e"" after the first ""r"" and cut the rest.', 'But, it did not work to get to ""Lettera"", which was my intended outcome.', 'This also happens if I am interested in, say, ""Letteratura tedesca"": it won\'t appear in the drop down list, and I am not even allowed to write it.', 'The only way to get there is writing ""letteraturatedesca"" instead, and adding the space later.', 'This makes sense to VE!', 'Thanks.']","['SOCIAL CONVERSATION', 'WORKAROUNDS', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +233158,"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link","I was 25 seconds too slow reporting Bug 52421, but I did include steps to reproduce: +1.Load a page in VE +2.Press ctrl+k to enter a link +3.Try to enter a link to [[Portable Network Graphics]], [[Classic (album)]] or +[[Thing (assembly)]]. + +I've also found a workaround - continue typing the link you want after it's suggestion, then select and delete what it inserted that you don't want.",task_subcomment,"['I was 25 seconds too slow reporting Bug 52421, but I did include steps to reproduce:\n1.Load a page in VE\n2.Press ctrl+k to enter a link\n3.Try to enter a link to [[Portable Network Graphics]], [[Classic (album)]] or\n[[Thing (assembly)]].', ""I've also found a workaround - continue typing the link you want after it's suggestion, then select and delete what it inserted that you don't want.""]","['OBSERVED BUG BEHAVIOR', 'WORKAROUNDS']" +233154,"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link",*** Bug 52421 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52421 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +54368,VisualEditor.php attempts to register a hook handler that was removed,"VisualEditor.php attempts to register a hook handler that was removed (summary credit goes to Ori) + +stack: http://paste.tstarling.com/p/GuTJEM.html + +Tim says: + +> var_dump($wgHooks['BeforeWelcomeCreation']); +array(2) { + [0]=> + string(42) ""VisualEditorHooks::onBeforeWelcomeCreation"" + [1]=> + string(44) ""GettingStartedHooks::onBeforeWelcomeCreation"" +} + +> print is_callable($wgHooks['BeforeWelcomeCreation'][0]); + +> print is_callable($wgHooks['BeforeWelcomeCreation'][1]); +1 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor.php attempts to register a hook handler that was removed\n\nVisualEditor.php attempts to register a hook handler that was removed (summary credit goes to Ori)\n\nstack: URL\n\nTim says:\n\nQUOTE\narray(2) {\n [0]=>\n string(42) ""VisualEditorHooks::onBeforeWelcomeCreation""\n [1]=>\n string(44) ""GettingStartedHooks::onBeforeWelcomeCreation""\n}\n\nQUOTE\n\nQUOTE\n1\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR'] +254987,VisualEditor.php attempts to register a hook handler that was removed,"I removed the BeforeWelcomeCreation handler in I8be6198a6 but not the statement in VisualEditor.php that registered it. + +1.22wmf11 had not yet been updated to I8be6198a6, so it didn't need to be fixed. 1.22wmf12 did need a fix, but there was a merged change separating the deployed commit and my fix: change I1cd9e2bea. I didn't know if it was safe to deploy and no one from the VE team was around, so I created a cut a 'bug/52368' branch based on the deployed commit, cherry picked the fix on top, and synced that. + +My apologies to the VisualEditor team and to the users that were affected.",task_subcomment,"['I removed the BeforeWelcomeCreation handler in I8be6198a6 but not the statement in VisualEditor.php that registered it.', ""1.22wmf11 had not yet been updated to I8be6198a6, so it didn't need to be fixed."", '1.22wmf12 did need a fix, but there was a merged change separating the deployed commit and my fix: change I1cd9e2bea.', ""I didn't know if it was safe to deploy and no one from the VE team was around, so I created a cut a 'bug/52368' branch based on the deployed commit, cherry picked the fix on top, and synced that."", 'My apologies to the VisualEditor team and to the users that were affected.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']" +254979,VisualEditor.php attempts to register a hook handler that was removed,Ia4e2a7854b3a2a5cbbe4da,task_subcomment,['Ia4e2a7854b3a2a5cbbe4da'],['OBSERVED BUG BEHAVIOR'] +54317,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"Screenshot + +Since the VE update tonight the save dialog is half out of the screen on FF 23/Win7, but sometimes only. + +-------------------------- +**Version**: unspecified +**Severity**: critical +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=52326 + +**Attached**: {F11781}",task_description,"['VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar\n\nScreenshot\n\nSince the VE update tonight the save dialog is half out of the screen on FF 23/Win7, but sometimes only.', '--------------------------\n**Version**: unspecified\n**Severity**: critical\n**See Also**:\nURL\n\n**Attached**: {F11781}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +252313,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,*** Bug 52328 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52328 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +252309,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,This is fixed and being pushed live right now.,task_subcomment,['This is fixed and being pushed live right now.'],['ACTION ON ISSUE'] +252305,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"Change 76935 merged by jenkins-bot: +ve.ui.Toolbar: Emit position event on toolbar instead of surface + +https://gerrit.wikimedia.org/r/76935",task_subcomment,['Change 76935 merged by jenkins-bot:\nve.ui.Toolbar: Emit position event on toolbar instead of surface\n\nGERRIT_URL'],['ACTION ON ISSUE'] +252298,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,*** Bug 52346 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52346 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +252292,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"Whatamidoing's link is to the Polish Wikipedia: +[[pl:Wikipedia:VisualEditor/Opinie#b.C5.82.C4.99dnie_wy.C5.9Bwietlaj.C4.85ce_si.C4.99_okno_opisu_zmian]]",task_subcomment,"[""Whatamidoing's link is to the Polish Wikipedia:\n[[pl:Wikipedia:VisualEditor/Opinie#b.C5.82.C4.99dnie_wy.C5.9Bwietlaj.C4.85ce_si.C4.99_okno_opisu_zmian]]""]",['INVESTIGATION AND EXPLORATION'] +252288,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"I have a report of this sort of problem with a misplaced save dialog box appearing in the lower left corner. The editor is running Linux Mint 14 and Firefox 18.0.2. See http://i40.tinypic.com/2eojvh1.jpg and http://i41.tinypic.com/30wqpnb.jpg for his screenshots. + +The original problem description can be found at Wikipedia:VisualEditor/Opinie#b.C5.82.C4.99dnie_wy.C5.9Bwietlaj.C4.85ce_si.C4.99_okno_opisu_zmian",task_subcomment,"['I have a report of this sort of problem with a misplaced save dialog box appearing in the lower left corner.', 'The editor is running Linux Mint 14 and Firefox 18.0.2.', 'See URL and URL for his screenshots.', 'The original problem description can be found at Wikipedia:VisualEditor/Opinie#b.C5.82.C4.99dnie_wy.C5.9Bwietlaj.C4.85ce_si.C4.99_okno_opisu_zmian']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']" +252282,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"Basically it attaches to whichever toolbar is positioned last. So if you click on a link, and then open the save dialog, it pops up there. If you then scroll down (which updates position of platform toolbar), it moves to that one.",task_subcomment,"['Basically it attaches to whichever toolbar is positioned last.', 'So if you click on a link, and then open the save dialog, it pops up there.', 'If you then scroll down (which updates position of platform toolbar), it moves to that one.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +252274,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"Change 76935 had a related patch set uploaded by Krinkle: +ve.ui.Toolbar: Emit position event on toolbar instead of surface + +https://gerrit.wikimedia.org/r/76935",task_subcomment,['Change 76935 had a related patch set uploaded by Krinkle:\nve.ui.Toolbar: Emit position event on toolbar instead of surface\n\nGERRIT_URL'],['ACTION ON ISSUE'] +252268,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"Renamed. + +Removing the link to bug 49969 - the save dialog isn't (yet) an actual dialog, so that would have no effect. + +Adding a link to bug 52326 which is possibly caused by the same",task_subcomment,"['Renamed.', ""Removing the link to bug 49969 - the save dialog isn't (yet) an actual dialog, so that would have no effect."", 'Adding a link to bug 52326 which is possibly caused by the same']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +252263,VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,"There is a lot of discussion about this at https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Save_page_box_drops.2C_button_invisible_without_scrolling_..._but_fixes_itself_given_time including two screenshots: [[File:VE save form off screen.png]] and [[File:VE misplaced save box.jpg]] + +From my testing it seems that if an element is selected (picture, link, template) when you click save then the dialog aligns itself to the top right of that element, regardless of whether there is space on screen for it, with scroll bars if there isn't sufficient vertical space in the window to show the whole dialog. If you close the dialog, deselect the element then open the save box again it appears in the same place, only based on what that element is in the view now. If you close and select a different element then save, it relates to that element. If you have not selected any elements during your edit it appears overthe save button. + +Steps to reproduce: +1. Edit a page in VE +2. Make a change to the page (doesn't matter what) +3. Click on an element (link, image, template) near the lower left edge of the window. +4. Click the save button in the top right.",task_subcomment,"[""There is a lot of discussion about this at URL including two screenshots: [[File:VE save form off screen.png]] and [[File:VE misplaced save box.jpg]]\n\nFrom my testing it seems that if an element is selected (picture, link, template) when you click save then the dialog aligns itself to the top right of that element, regardless of whether there is space on screen for it, with scroll bars if there isn't sufficient vertical space in the window to show the whole dialog."", 'If you close the dialog, deselect the element then open the save box again it appears in the same place, only based on what that element is in the view now.', 'If you close and select a different element then save, it relates to that element.', 'If you have not selected any elements during your edit it appears overthe save button.', 'Steps to reproduce:\n1.', 'Edit a page in VE\n2.', ""Make a change to the page (doesn't matter what)\n3."", 'Click on an element (link, image, template) near the lower left edge of the window.', '4.', 'Click the save button in the top right.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']" +54232,Anonymous users getting VisualEditor on German Wikipedia and making edits,"https://de.wikipedia.org/w/index.php?title=Spezial:Letzte_%C3%84nderungen&limit=500&days=30&hideliu=1&tagfilter=visualeditor + +--- +29 July 2013 + +(diff | hist) . . Aurich‎ [pending edits]; 19:40 . . (-1)‎ . . ‎95.165.106.6 (Talk)‎ (→‎Branchen und Unternehmen) (Tag: VisualEditor) +(diff | hist) . . Djihadismus‎; 19:30 . . (-980)‎ . . ‎2a02:908:df31:8700:6861:a2d8:52b6:1392 (Talk)‎ (Tag: VisualEditor) +(diff | hist) . . Thronfolge (Vereinigtes Königreich)‎ [pending edits]; 19:30 . . (-2)‎ . . ‎84.155.202.154 (Talk)‎ (→‎Derzeitige Reihenfolge der Thronfolge) (Tag: VisualEditor) +(diff | hist) . . Lagerungskonzepte‎ [pending edits]; 19:15 . . (+73)‎ . . ‎81.217.18.166 (Talk)‎ (→‎Stützlagerung schwimmend (SLS)) (Tag: VisualEditor) +(diff | hist) . . Andreas Müller (Fußballspieler, 1962)‎; 19:13 . . (+233)‎ . . ‎2.244.238.208 (Talk)‎ (→‎als Funktionär) (Tag: VisualEditor) +(diff | hist) . . Nexus 7‎; 19:12 . . (+4)‎ . . ‎88.130.17.139 (Talk)‎ (→‎Zweite Generation (2013)) (Tag: VisualEditor) +(diff | hist) . . Räumliche Orientierung‎ [pending edits]; 19:09 . . (-55)‎ . . ‎72.89.247.161 (Talk)‎ (für emotionale Betroffenheit lassen sich in der Literatur keine Belege finden.) (Tag: VisualEditor) +(diff | hist) . . Medien (Land)‎; 19:06 . . (+226)‎ . . ‎78.53.45.165 (Talk)‎ (→‎Spekulationen über die Verwandtschaft von Kurden und Medern) (Tag: VisualEditor) +(diff | hist) . . Inka Bause‎; 19:05 . . (+42)‎ . . ‎188.194.150.121 (Talk)‎ (→‎Singles: ist das liebe 1987) (Tag: VisualEditor) +(diff | hist) . . Mississippi River‎; 19:03 . . (+1)‎ . . ‎77.6.118.157 (Talk)‎ (Tag: VisualEditor) +(diff | hist) . . Geständnisse‎ [pending edits]; 18:54 . . (+1)‎ . . ‎91.39.63.227 (Talk)‎ (→‎Handlung: Grammatik) (Tag: VisualEditor) +(diff | hist) . . Vojtech Tuka‎; 18:53 . . (-23)‎ . . ‎2003:4d:eb3c:f001:5452:a193:58c6:cc59 (Talk)‎ (→‎Flucht, Prozess und Hinrichtung) (Tag: VisualEditor) + +25 July 2013 + +(diff | hist) . . Lotta Schelin‎; 04:26 . . (+2)‎ . . ‎92.76.236.197 (Talk)‎ (→‎Nationalmannschaft) (Tag: VisualEditor) +--- + +Anons are editing the German Wikipedia with VisualEditor. + +My suspicion is that logged-in users are hitting certain pages, the pages are being cached, and then anons are receiving these cached pages (with the VE init JS loaded). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=52202",task_description,"['Anonymous users getting VisualEditor on German Wikipedia and making edits\n\nURL\n\n---\n29 July 2013\n\n(diff | hist) .', '.', 'Aurich\u200e [pending edits]; 19:40 .', '.', '(-1)\u200e .', '.', '\u200e95.165.106.6 (Talk)\u200e (→\u200eBranchen und Unternehmen) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Djihadismus\u200e; 19:30 .', '.', '(-980)\u200e .', '.', '\u200e2a02:908:df31:8700:6861:a2d8:52b6:1392 (Talk)\u200e (Tag: VisualEditor)\n(diff | hist) .', '.', 'Thronfolge (Vereinigtes Königreich)\u200e [pending edits]; 19:30 .', '.', '(-2)\u200e .', '.', '\u200e84.155.202.154 (Talk)\u200e (→\u200eDerzeitige Reihenfolge der Thronfolge) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Lagerungskonzepte\u200e [pending edits]; 19:15 .', '.', '(+73)\u200e .', '.', '\u200e81.217.18.166 (Talk)\u200e (→\u200eStützlagerung schwimmend (SLS)) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Andreas Müller (Fußballspieler, 1962)\u200e; 19:13 .', '.', '(+233)\u200e .', '.', '\u200e2.244.238.208 (Talk)\u200e (→\u200eals Funktionär) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Nexus 7\u200e; 19:12 .', '.', '(+4)\u200e .', '.', '\u200e88.130.17.139 (Talk)\u200e (→\u200eZweite Generation (2013)) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Räumliche Orientierung\u200e [pending edits]; 19:09 .', '.', '(-55)\u200e .', '.', '\u200e72.89.247.161 (Talk)\u200e (für emotionale Betroffenheit lassen sich in der Literatur keine Belege finden.)', '(Tag: VisualEditor)\n(diff | hist) .', '.', 'Medien (Land)\u200e; 19:06 .', '.', '(+226)\u200e .', '.', '\u200e78.53.45.165 (Talk)\u200e (→\u200eSpekulationen über die Verwandtschaft von Kurden und Medern) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Inka Bause\u200e; 19:05 .', '.', '(+42)\u200e .', '.', '\u200e188.194.150.121 (Talk)\u200e (→\u200eSingles: ist das liebe 1987) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Mississippi River\u200e; 19:03 .', '.', '(+1)\u200e .', '.', '\u200e77.6.118.157 (Talk)\u200e (Tag: VisualEditor)\n(diff | hist) .', '.', 'Geständnisse\u200e [pending edits]; 18:54 .', '.', '(+1)\u200e .', '.', '\u200e91.39.63.227 (Talk)\u200e (→\u200eHandlung: Grammatik) (Tag: VisualEditor)\n(diff | hist) .', '.', 'Vojtech Tuka\u200e; 18:53 .', '.', '(-23)\u200e .', '.', '\u200e2003:4d:eb3c:f001:5452:a193:58c6:cc59 (Talk)\u200e (→\u200eFlucht, Prozess und Hinrichtung) (Tag: VisualEditor)\n\n25 July 2013\n\n(diff | hist) .', '.', 'Lotta Schelin\u200e; 04:26 .', '.', '(+2)\u200e .', '.', '\u200e92.76.236.197 (Talk)\u200e (→\u200eNationalmannschaft) (Tag: VisualEditor)\n---\n\nAnons are editing the German Wikipedia with VisualEditor.', 'My suspicion is that logged-in users are hitting certain pages, the pages are being cached, and then anons are receiving these cached pages (with the VE init JS loaded).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'CONTRIBUTION AND COMMITMENT', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +247334,Anonymous users getting VisualEditor on German Wikipedia and making edits,"(In reply to comment #7) +> I'm sorry if we were dismissive earlier. When I said ""VE doesn't work the way +> you think it does"", what I meant to say was ""despite the confusing way these +> variables are named, they mean something slightly different, such that one of +> them is unused if the other one is set a certain way"". + +I wasn't annoyed with you (and you weren't the person quoted in comment 6). You're wonderful and I adore you.",task_subcomment,"[""(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI wasn't annoyed with you (and you weren't the person quoted in comment 6)."", ""You're wonderful and I adore you.""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']" +247330,Anonymous users getting VisualEditor on German Wikipedia and making edits,"(In reply to comment #6) +> I'm fairly annoyed that I was told that VisualEditor ""doesn't work the way +> you +> think it does"" this morning and my patch sets were roundly and soundly +> ignored +> (in favor of Gerrit change #76516), only to have the exact changes +> implemented a few hours later after this bug appeared. +Your patchsets weren't ignored, we worked off them. At the time we honestly believed that this was unnecessary, and the code that uses them is written in a way that leads the reader to believe that it is unnecessary: if wmgVisualEditorDefault is false, wmgVisualEditorDisableForAnons is unused. + +However, caching threw a wrench in all of this. Two wrongs made a right, if you will. + +I'm sorry if we were dismissive earlier. When I said ""VE doesn't work the way you think it does"", what I meant to say was ""despite the confusing way these variables are named, they mean something slightly different, such that one of them is unused if the other one is set a certain way"".",task_subcomment,"[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nYour patchsets weren't ignored, we worked off them."", 'At the time we honestly believed that this was unnecessary, and the code that uses them is written in a way that leads the reader to believe that it is unnecessary: if wmgVisualEditorDefault is false, wmgVisualEditorDisableForAnons is unused.', 'However, caching threw a wrench in all of this.', 'Two wrongs made a right, if you will.', ""I'm sorry if we were dismissive earlier."", 'When I said ""VE doesn\'t work the way you think it does"", what I meant to say was ""despite the confusing way these variables are named, they mean something slightly different, such that one of them is unused if the other one is set a certain way"".']","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION']" +247327,Anonymous users getting VisualEditor on German Wikipedia and making edits,"For the record, if my patch set from Gerrit changeset 76199 and Gerrit changeset 76468 had been merged and deployed, this bug never would have happened. + +I'm fairly annoyed that I was told that VisualEditor ""doesn't work the way you think it does"" this morning and my patch sets were roundly and soundly ignored (in favor of Gerrit changeset 76516), only to have the exact changes implemented a few hours later after this bug appeared.",task_subcomment,"['For the record, if my patch set from Gerrit changeset 76199 and Gerrit changeset 76468 had been merged and deployed, this bug never would have happened.', 'I\'m fairly annoyed that I was told that VisualEditor ""doesn\'t work the way you think it does"" this morning and my patch sets were roundly and soundly ignored (in favor of Gerrit changeset 76516), only to have the exact changes implemented a few hours later after this bug appeared.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']" +247323,Anonymous users getting VisualEditor on German Wikipedia and making edits,"(In reply to comment #4) +> Roan's putting this in place now. +Done. This bug should stop happening in the next ~10 minutes.",task_subcomment,"['(In reply to comment #4)\nQUOTE\nDone.', 'This bug should stop happening in the next ~10 minutes.']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']" +247318,Anonymous users getting VisualEditor on German Wikipedia and making edits,"(In reply to comment #0) +> My suspicion is that logged-in users are hitting certain pages, the pages are +> being cached, and then anons are receiving these cached pages (with the VE +> init +> JS loaded). + +We don't mix user preference cache between logged-in users and logged-out users, this is definitely not what's happening. + + +What's happening is that a while ago the 'visualeditor-enable' preference was enabled by default on de.wikipedia.org. Though it was disabled for anonymous users by other means, that preference was there and as such is cached inside the anonymous user cache that visited pages while VE was enabled by default on de.wikipedia.org. + +The 'other' means to disable for anons have been removed now that the preference is disabled again on de.wikipedia (it is now an opt-in for logged-in users). However this other means is not cached inside the page but globally from the startup module. + +So people visiting the pages generated while VE was enabled by default are now getting VE since there is no 'disableForAnons' flag in place. + +Roan's putting this in place now.",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe don't mix user preference cache between logged-in users and logged-out users, this is definitely not what's happening."", ""What's happening is that a while ago the 'visualeditor-enable' preference was enabled by default on de.wikipedia.org."", 'Though it was disabled for anonymous users by other means, that preference was there and as such is cached inside the anonymous user cache that visited pages while VE was enabled by default on de.wikipedia.org.', ""The 'other' means to disable for anons have been removed now that the preference is disabled again on de.wikipedia (it is now an opt-in for logged-in users)."", 'However this other means is not cached inside the page but globally from the startup module.', ""So people visiting the pages generated while VE was enabled by default are now getting VE since there is no 'disableForAnons' flag in place."", ""Roan's putting this in place now.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +247311,Anonymous users getting VisualEditor on German Wikipedia and making edits,"Change 76552 merged by jenkins-bot: +Explicitly disable VE for anons on dewiki + +https://gerrit.wikimedia.org/r/76552",task_subcomment,['Change 76552 merged by jenkins-bot:\nExplicitly disable VE for anons on dewiki\n\nGERRIT_URL'],['BUG REPRODUCTION'] +247303,Anonymous users getting VisualEditor on German Wikipedia and making edits,"Change 76552 had a related patch set uploaded by Catrope: +Explicitly disable VE for anons on dewiki + +https://gerrit.wikimedia.org/r/76552",task_subcomment,['Change 76552 had a related patch set uploaded by Catrope:\nExplicitly disable VE for anons on dewiki\n\nGERRIT_URL'],['ACTION ON ISSUE'] +247296,Anonymous users getting VisualEditor on German Wikipedia and making edits,"This appears to be a caching issue, yes",task_subcomment,"['This appears to be a caching issue, yes']",['OBSERVED BUG BEHAVIOR'] +54202,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","**Author:** `matthiasbecker1967` + +**Description:** +According to http://de.wikipedia.org/wiki/Wikipedia_Diskussion:Umfragen/VisualEditor_Opt-in the German Wikipedia community demands to postpone enablement of the VE for IPs until the VE is a robust and mostly bug free feature and to revert VE for registered users back to ""opt-in"". + +-------------------------- +**Version**: unspecified +**Severity**: critical +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=49998 +https://bugzilla.wikimedia.org/show_bug.cgi?id=52232",task_description,"['VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia\n\n**Author:** CODE\n\n**Description:**\nAccording to URL the German Wikipedia community demands to postpone enablement of the VE for IPs until the VE is a robust and mostly bug free feature and to revert VE for registered users back to ""opt-in"".', '--------------------------\n**Version**: unspecified\n**Severity**: critical\n**See Also**:\nURL\nURL']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']" +245474,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","**nrp** wrote: + +(In reply to comment #16) +> (In reply to comment #15) +> > So De Wikipedia holds a quick poll and their deployment is changed to opt-in, +> > but on En Wikipedia, despite weeks of complaints, we are still stuck with +> > opt-out? How does that work? +> +> If you can hold a coordinated vote on the English Wikipedia and get over 400 +> participants to agree to switch to opt-in, I imagine you can get the same +> result. :-) + +I think a quick look at the feedback and other related pages would show a consensus for a switch to opt-in, but in any event there is now an RFC: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Default_State_RFC",task_subcomment,"['**nrp** wrote:\n\n(In reply to comment #16)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI think a quick look at the feedback and other related pages would show a consensus for a switch to opt-in, but in any event there is now an RFC: URL']",['INVESTIGATION AND EXPLORATION'] +245468,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","(In reply to comment #15) +> So De Wikipedia holds a quick poll and their deployment is changed to opt-in, +> but on En Wikipedia, despite weeks of complaints, we are still stuck with +> opt-out? How does that work? + +If you can hold a coordinated vote on the English Wikipedia and get over 400 participants to agree to switch to opt-in, I imagine you can get the same result. :-)",task_subcomment,"['(In reply to comment #15)\nQUOTE\nQUOTE\nQUOTE\n\nIf you can hold a coordinated vote on the English Wikipedia and get over 400 participants to agree to switch to opt-in, I imagine you can get the same result.', ':-)']","['MOTIVATION', 'SOLUTION DISCUSSION']" +245462,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","**nrp** wrote: + +So De Wikipedia holds a quick poll and their deployment is changed to opt-in, but on En Wikipedia, despite weeks of complaints, we are still stuck with opt-out? How does that work?",task_subcomment,"['**nrp** wrote:\n\nSo De Wikipedia holds a quick poll and their deployment is changed to opt-in, but on En Wikipedia, despite weeks of complaints, we are still stuck with opt-out?', 'How does that work?']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +245456,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia",Closing this bug now as the issue in c13 should be resolved by bug 52232. The intention of this bug report is done.,task_subcomment,"['Closing this bug now as the issue in c13 should be resolved by bug 52232.', 'The intention of this bug report is done.']","['ACTION ON ISSUE', 'ISSUE CONTENT MANAGEMENT']" +245449,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","It seems that some IPs can use VE, see e.g. +http://de.wikipedia.org/w/index.php?title=Medien_%28Land%29&curid=132736&diff=121014468&oldid=120989155 +(tagged as Visual editor), see also the talk on the village pump +https://de.wikipedia.org/wiki/Wikipedia:Fragen_zur_Wikipedia#VE_f.C3.BCr_IP_funktioniert.3F",task_subcomment,"['It seems that some IPs can use VE, see e.g.', 'URL\n(tagged as Visual editor), see also the talk on the village pump\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245441,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","Change 76468 abandoned by MZMcBride: +Explicitly disable VisualEditor by default on dewiki + +Reason: +I feel like a Wikipedia user who finally makes his first edit only to have it reverted. ;-) + +https://gerrit.wikimedia.org/r/76468",task_subcomment,"['Change 76468 abandoned by MZMcBride:\nExplicitly disable VisualEditor by default on dewiki\n\nReason:\nI feel like a Wikipedia user who finally makes his first edit only to have it reverted.', ';-)\n\nGERRIT_URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +245434,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","(In reply to comment #7) +> (In reply to comment #6) +> >... VisualEditor will be temporarily switched back into opt-in mode on +> > the German Wikipedia. We don’t intend to otherwise alter the near-term +> > VisualEditor deployment schedule +> +> Does that mean opt-in for everyone or just registered users? +Opt-in for everyone, that is to say it's off unless you turn it on in your preferences. In practice, anonymous users won't be able to opt in unless they create an account, because anons can't change their preferences.",task_subcomment,"[""(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nOpt-in for everyone, that is to say it's off unless you turn it on in your preferences."", ""In practice, anonymous users won't be able to opt in unless they create an account, because anons can't change their preferences.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +245426,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia",This is now done.,task_subcomment,['This is now done.'],['SOLUTION USAGE'] +245418,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","Change 76516 merged by jenkins-bot: +Switch VisualEditor back to alpha (opt-in) mode on dewiki + +https://gerrit.wikimedia.org/r/76516",task_subcomment,['Change 76516 merged by jenkins-bot:\nSwitch VisualEditor back to alpha (opt-in) mode on dewiki\n\nGERRIT_URL'],['ACTION ON ISSUE'] +245412,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","Change 76516 had a related patch set uploaded by Jforrester: +Switch VisualEditor back to alpha (opt-in) mode on dewiki + +https://gerrit.wikimedia.org/r/76516",task_subcomment,['Change 76516 had a related patch set uploaded by Jforrester:\nSwitch VisualEditor back to alpha (opt-in) mode on dewiki\n\nGERRIT_URL'],['ACTION ON ISSUE'] +245406,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","**jsalsman** wrote: + +(In reply to comment #6) +>... VisualEditor will be temporarily switched back into opt-in mode on +> the German Wikipedia. We don’t intend to otherwise alter the near-term +> VisualEditor deployment schedule + +Does that mean opt-in for everyone or just registered users?",task_subcomment,['**jsalsman** wrote:\n\n(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nDoes that mean opt-in for everyone or just registered users?'],['INVESTIGATION AND EXPLORATION'] +245398,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","In response to community feedback, VisualEditor will be temporarily switched back into opt-in mode on the German Wikipedia. We don’t intend to otherwise alter the near-term VisualEditor deployment schedule, except in case of emergencies. + +As we did in the case of Dutch Wikipedia, for instance, which was exempted from the phase 2 rollout, we try to accommodate community concern in the process of this rollout. VisualEditor is the single largest and most disruptive change to the user experience in the history of our projects. Not only is it still beta software, it also depends on us working together in partnership to update documentation, add template metadata (which is used by VisualEditor to make templates more user-friendly), and deal with unexpected issues. We appreciate your patience and feedback, and we have no intent of taking your partnership for granted. + +We also recognize that there are still significant areas for improvement (e.g. performance, handling of tables, insertion of special characters) as well as work we can do to reduce the incidence rate of problematic markup changes. As we continue to support the beta where it is deployed, we’ll also update the German Wikipedia community on progress in these areas, and prepare for re-enabling VisualEditor later in the calendar year. + +As a reminder, VisualEditor has always been optional to use, and can now also be completely hidden from the user experience (as an individual preference) in wikis where it is enabled by default. + +-- James Forrester, Product Manager, VisualEditor team + +---- + +Als Reaktion auf die Rückmeldungen der deutschsprachigen Wikipedia-Gemeinschaft werden wir den VisualEditor dort temporär wieder nur per Opt-In verfügbar machen. Darüber hinaus beabsichtigen wir nicht, die unmittelbare Planung für andere Sprachversionen zu verändern, es sei denn, es treten schwerwiegende Probleme auf. + +Wie auch z.B. im Fall der niederländischen Wikipedia, die von Phase 2 der Beta ausgenommen wurde, versuchen wir, bei der weiteren Aktivierung des VisualEditor mit den Sprachversionen zusammen zu arbeiten und nehmen Bedenken ernst. VisualEditor ist die weitgehendste Änderung an der Benutzeroberfläche in der Geschichte unserer Projekte. VisualEditor ist aber noch Beta-Software, und der Erfolg des Projekts hängt sehr davon ab, dass wir ein einer positiven Partnerschaft zusammen arbeiten, um z.B. Vorlagen-Metadaten (TemplateData) hinzuzufügen (die von VisualEditor verwendet werden, um die Benutzeroberfläche für Vorlagen zu verbessern) und Dokumentation zu aktualisieren, und um mit Software-Problemen umzugehen. Wir schätzen die Geduld und das ehrliche Feedback der deutschsprachigen Wikipedia-Gemeinschaft, und gehen nicht davon aus, dass eine Kooperation ohne gegenseitiges Entgegenkommen funktionieren kann. + +Wir erkennen auch an, dass es im VisualEditor noch viel Raum für Verbesserungen gibt. Das beinhaltet z.B. Performance, bessere Unterstützung für Tabellen und einen Dialog für das Einfügen von Sonderzeichen. In einigen Fällen können wir auch das Verhalten des Editors optimieren, um unerwünschte Änderungen am Wikitext zu reduzieren. Auch auf der deutschsprachigen Wikipedia werden Verbesserungen selbstverständlich für Opt-In-Nutzer kontinuierlich zur Verfügung stehen, und wir werden regelmäßige Ankündigungen über Neuerungen veröffentlichen. Unser Ziel ist eine Wiederaktivierung des VisualEditor in der Beta-Konfiguration später im Kalenderjahr. + +Die Verwendung von Wikitext wird selbstverständlich auch nach der Wiederaktivierung des VisualEditor möglich sein. Der VisualEditor ist und bleibt optional, und kann während der Beta-Phase auch komplett aus der Benutzeroberfläche entfernt werden. + +-- James Forrester, Produktmanager, VisualEditor-Team",task_subcomment,"['In response to community feedback, VisualEditor will be temporarily switched back into opt-in mode on the German Wikipedia.', 'We don’t intend to otherwise alter the near-term VisualEditor deployment schedule, except in case of emergencies.', 'As we did in the case of Dutch Wikipedia, for instance, which was exempted from the phase 2 rollout, we try to accommodate community concern in the process of this rollout.', 'VisualEditor is the single largest and most disruptive change to the user experience in the history of our projects.', 'Not only is it still beta software, it also depends on us working together in partnership to update documentation, add template metadata (which is used by VisualEditor to make templates more user-friendly), and deal with unexpected issues.', 'We appreciate your patience and feedback, and we have no intent of taking your partnership for granted.', 'We also recognize that there are still significant areas for improvement (e.g.', 'performance, handling of tables, insertion of special characters) as well as work we can do to reduce the incidence rate of problematic markup changes.', 'As we continue to support the beta where it is deployed, we’ll also update the German Wikipedia community on progress in these areas, and prepare for re-enabling VisualEditor later in the calendar year.', 'As a reminder, VisualEditor has always been optional to use, and can now also be completely hidden from the user experience (as an individual preference) in wikis where it is enabled by default.', '-- James Forrester, Product Manager, VisualEditor team\n\n----\n\nAls Reaktion auf die Rückmeldungen der deutschsprachigen Wikipedia-Gemeinschaft werden wir den VisualEditor dort temporär wieder nur per Opt-In verfügbar machen.', 'Darüber hinaus beabsichtigen wir nicht, die unmittelbare Planung für andere Sprachversionen zu verändern, es sei denn, es treten schwerwiegende Probleme auf.', 'Wie auch z.B.', 'im Fall der niederländischen Wikipedia, die von Phase 2 der Beta ausgenommen wurde, versuchen wir, bei der weiteren Aktivierung des VisualEditor mit den Sprachversionen zusammen zu arbeiten und nehmen Bedenken ernst.', 'VisualEditor ist die weitgehendste Änderung an der Benutzeroberfläche in der Geschichte unserer Projekte.', 'VisualEditor ist aber noch Beta-Software, und der Erfolg des Projekts hängt sehr davon ab, dass wir ein einer positiven Partnerschaft zusammen arbeiten, um z.B.', 'Vorlagen-Metadaten (TemplateData) hinzuzufügen (die von VisualEditor verwendet werden, um die Benutzeroberfläche für Vorlagen zu verbessern) und Dokumentation zu aktualisieren, und um mit Software-Problemen umzugehen.', 'Wir schätzen die Geduld und das ehrliche Feedback der deutschsprachigen Wikipedia-Gemeinschaft, und gehen nicht davon aus, dass eine Kooperation ohne gegenseitiges Entgegenkommen funktionieren kann.', 'Wir erkennen auch an, dass es im VisualEditor noch viel Raum für Verbesserungen gibt.', 'Das beinhaltet z.B.', 'Performance, bessere Unterstützung für Tabellen und einen Dialog für das Einfügen von Sonderzeichen.', 'In einigen Fällen können wir auch das Verhalten des Editors optimieren, um unerwünschte Änderungen am Wikitext zu reduzieren.', 'Auch auf der deutschsprachigen Wikipedia werden Verbesserungen selbstverständlich für Opt-In-Nutzer kontinuierlich zur Verfügung stehen, und wir werden regelmäßige Ankündigungen über Neuerungen veröffentlichen.', 'Unser Ziel ist eine Wiederaktivierung des VisualEditor in der Beta-Konfiguration später im Kalenderjahr.', 'Die Verwendung von Wikitext wird selbstverständlich auch nach der Wiederaktivierung des VisualEditor möglich sein.', 'Der VisualEditor ist und bleibt optional, und kann während der Beta-Phase auch komplett aus der Benutzeroberfläche entfernt werden.', '-- James Forrester, Produktmanager, VisualEditor-Team']","['FUTURE PLAN', 'FUTURE PLAN', 'FUTURE PLAN', 'FUTURE PLAN', 'FUTURE PLAN', 'WORKAROUNDS', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'FUTURE PLAN', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +245392,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","Change 76468 had a related patch set uploaded by MZMcBride: +Explicitly disabled VisualEditor by default on dewiki + +https://gerrit.wikimedia.org/r/76468",task_subcomment,['Change 76468 had a related patch set uploaded by MZMcBride:\nExplicitly disabled VisualEditor by default on dewiki\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +245385,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","Change 76199 had a related patch set uploaded by MZMcBride: +Enable anonymous use of VisualEditor on es/fr/he/it/pl/ru/sv + +https://gerrit.wikimedia.org/r/76199",task_subcomment,['Change 76199 had a related patch set uploaded by MZMcBride:\nEnable anonymous use of VisualEditor on es/fr/he/it/pl/ru/sv\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +245381,"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","VisualEditor's configuration variables are a bit confusing to me, but it seems like the German Wikipedia would like to reverse part of this change: . + +wmgVisualEditorDefault would be set to false for dewiki. + +wmgVisualEditorDisableForAnons would be left as true for dewiki. + +Is this correct?",task_subcomment,"[""VisualEditor's configuration variables are a bit confusing to me, but it seems like the German Wikipedia would like to reverse part of this change: on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare"," + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']",['OBSERVED BUG BEHAVIOR'] +253214,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare",Now fixed.,task_subcomment,['Now fixed.'],['SOLUTION DISCUSSION'] +253211,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 76220 merged by jenkins-bot: +Don't compare annotations directly with ve.compare() + +https://gerrit.wikimedia.org/r/76220",task_subcomment,"[""Change 76220 merged by jenkins-bot:\nDon't compare annotations directly with ve.compare()\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR'] +253206,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 76220 had a related patch set uploaded by Jforrester: +Don't compare annotations directly with ve.compare() + +https://gerrit.wikimedia.org/r/76220",task_subcomment,"[""Change 76220 had a related patch set uploaded by Jforrester:\nDon't compare annotations directly with ve.compare()\n\nGERRIT_URL""]",['ACTION ON ISSUE'] +253199,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","(In reply to comment #4) +> https://www.mediawiki.org/w/index.php?title=Extension:MassMessage/ +> Design&oldid=745378&veaction=edit +> +> When I go to this URL in Google Chrome/OS X/Version 27.0.1453.116, I get the +> following error in my JavaScript console: +> +> Uncaught RangeError: Maximum call stack size exceeded +> oo.compare +> oo.compare +[…] + +This is now masked by some significant performance improvements we made (so it ""works""), but we think it's still an issue; keeping open.",task_subcomment,"['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n[…]\n\nThis is now masked by some significant performance improvements we made (so it ""works""), but we think it\'s still an issue; keeping open.']",['SOLUTION DISCUSSION'] +253193,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","https://www.mediawiki.org/w/index.php?title=Extension:MassMessage/Design&oldid=745378&veaction=edit + +When I go to this URL in Google Chrome/OS X/Version 27.0.1453.116, I get the following error in my JavaScript console: + +Uncaught RangeError: Maximum call stack size exceeded +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare +oo.compare",task_subcomment,"['URL\n\nWhen I go to this URL in Google Chrome/OS X/Version 27.0.1453.116, I get the following error in my JavaScript console:\n\nUncaught RangeError: Maximum call stack size exceeded\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare\noo.compare']",['BUG REPRODUCTION'] +253190,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 75636 merged by jenkins-bot: +Put edting in experimental for now + +https://gerrit.wikimedia.org/r/75636",task_subcomment,['Change 75636 merged by jenkins-bot:\nPut edting in experimental for now\n\nGERRIT_URL'],['ACTION ON ISSUE'] +253187,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 75636 had a related patch set uploaded by Jforrester: +Put edting in experimental for now + +https://gerrit.wikimedia.org/r/75636",task_subcomment,['Change 75636 had a related patch set uploaded by Jforrester:\nPut edting in experimental for now\n\nGERRIT_URL'],['ACTION ON ISSUE'] +253183,"VisualEditor: A on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","[Sorry, somehow it was created without a description.] + +On the latest master I cannot edit a page that has in it. VisualEditor appears to be loading with the ""progress bar"", but doesn't go to actual editing mode. + +Versions: +VisualEditor 393807462e9d04ec5e437cb50ef1d03e5644e9be +Parsoid be8a7dea49bd70692ef574a1bb7c7a70584d77e3 +core e617dc6c8f2ce1d867ddadcd4bc3de098a84ff07",task_subcomment,"['[Sorry, somehow it was created without a description.]', 'On the latest master I cannot edit a page that has in it.', 'VisualEditor appears to be loading with the ""progress bar"", but doesn\'t go to actual editing mode.', 'Versions:\nVisualEditor 393807462e9d04ec5e437cb50ef1d03e5644e9be\nParsoid be8a7dea49bd70692ef574a1bb7c7a70584d77e3\ncore e617dc6c8f2ce1d867ddadcd4bc3de098a84ff07']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +53689,VisualEditor: Newly-added references need a page save before being reusable,"Apologies if this is a duplicate; I haven't found a report about this. + +If you add a new reference with VisualEditor, you can't immediately reuse it with the reference editor; it doesn't show up in the list. You need to save the page and re-open the reference editor for that reference to show. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: Newly-added references need a page save before being reusable\n\nApologies if this is a duplicate; I haven't found a report about this."", ""If you add a new reference with VisualEditor, you can't immediately reuse it with the reference editor; it doesn't show up in the list."", 'You need to save the page and re-open the reference editor for that reference to show.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +462236,VisualEditor: Newly-added references need a page save before being reusable,This is still the case for references added inside a table though?,task_subcomment,['This is still the case for references added inside a table though?'],['OBSERVED BUG BEHAVIOR'] +238135,VisualEditor: Newly-added references need a page save before being reusable,"Change 81964 merged by jenkins-bot: +Re-build reference search index so they can be used mid-edit + +https://gerrit.wikimedia.org/r/81964",task_subcomment,['Change 81964 merged by jenkins-bot:\nRe-build reference search index so they can be used mid-edit\n\nGERRIT_URL'],['ACTION ON ISSUE'] +238133,VisualEditor: Newly-added references need a page save before being reusable,Now fixed in master and will be deployed next week.,task_subcomment,['Now fixed in master and will be deployed next week.'],['SOLUTION DISCUSSION'] +238131,VisualEditor: Newly-added references need a page save before being reusable,"Change 81964 had a related patch set uploaded by Trevor Parscal: +Bug 52000 - Reusing new reference groups + +https://gerrit.wikimedia.org/r/81964",task_subcomment,['Change 81964 had a related patch set uploaded by Trevor Parscal:\nBug 52000 - Reusing new reference groups\n\nGERRIT_URL'],['BUG REPRODUCTION'] +238127,VisualEditor: Newly-added references need a page save before being reusable,"So bug reports are taking 2 weeks to be assessed and assigned? That sounds like bad news. Glad to see it's now ""highest"", thanks. I'm amazed it took so long to be reported as a bug, and suspect it's because the experience of adding refs has been so dreadful that people haven't picked up on this specific aspect to report as a distinctive bug. Good luck.",task_subcomment,"['So bug reports are taking 2 weeks to be assessed and assigned?', 'That sounds like bad news.', 'Glad to see it\'s now ""highest"", thanks.', ""I'm amazed it took so long to be reported as a bug, and suspect it's because the experience of adding refs has been so dreadful that people haven't picked up on this specific aspect to report as a distinctive bug."", 'Good luck.']","['CONTRIBUTION AND COMMITMENT', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION']" +238122,VisualEditor: Newly-added references need a page save before being reusable,"(In reply to comment #2) +> I can think of possible two reasons why this bug has not been given high +> priority: + +You forgot option 3: We hadn't got to this bug report yet (aka, ""AGF""). :-) + +Now marked appropriately.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\n\nYou forgot option 3: We hadn\'t got to this bug report yet (aka, ""AGF"").', ':-)\n\nNow marked appropriately.']","['ACTION ON ISSUE', 'SOLUTION USAGE']" +238120,VisualEditor: Newly-added references need a page save before being reusable,"I can think of possible two reasons why this bug has not been given high priority: + +(1) Those unfamiliar with creating or substantially expanding Wikipedia articles don't think that this is a big deal. They are wrong - it IS a big deal. Not been able to cite the same source two or more times in an article, which is exceptionally common, causes all the problems noted by Pam, above. + +or (2) VE's fundamental architecture prevents it from adding footnotes created during an editing session to the list of footnotes that existed prior to that session, and if this were listed as a high-priority bug, that design mistake might be much more obvious. + +I really, really hope that the answer is not (2), because if so, that's a deal-breaker. The lack of such functionality is certainly, in and of itself, reason to NOW recommend that anyone writing a new article *not* do so in VE. (And, no, it's not acceptable to do everything but the footnotes in VE, then do footnotes with the wikitext editor - users absolutely should be footnoting their text additions with citations, *as they go along*, if only for efficiency.)",task_subcomment,"[""I can think of possible two reasons why this bug has not been given high priority:\n\n(1) Those unfamiliar with creating or substantially expanding Wikipedia articles don't think that this is a big deal."", 'They are wrong - it IS a big deal.', 'Not been able to cite the same source two or more times in an article, which is exceptionally common, causes all the problems noted by Pam, above.', ""or (2) VE's fundamental architecture prevents it from adding footnotes created during an editing session to the list of footnotes that existed prior to that session, and if this were listed as a high-priority bug, that design mistake might be much more obvious."", ""I really, really hope that the answer is not (2), because if so, that's a deal-breaker."", 'The lack of such functionality is certainly, in and of itself, reason to NOW recommend that anyone writing a new article *not* do so in VE.', ""(And, no, it's not acceptable to do everything but the footnotes in VE, then do footnotes with the wikitext editor - users absolutely should be footnoting their text additions with citations, *as they go along*, if only for efficiency.)""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +238115,VisualEditor: Newly-added references need a page save before being reusable,"I'd urge this to be a higher priority: how do we expect people to create good new articles, even a well-cited stub, if they can't use the same reference for more than one point? They get offered a ""reuse a reference"" button, but it doesn't work: seriously bad news. The confused editor then has several choices: (a) don't give the extra reference(s) they think are appropriate, dumbing down the article; (b) re-input the reference each time they want to use it; (c) stop editing in VE and go into Edit Source (if they're lucky enough to be an established editor who knows about it and has learned how to use it ... not for newbies according to current ideas); (d) curse and swear and givve up trying to create their article and probably abandon editing Wikipedia altogether.",task_subcomment,"[""I'd urge this to be a higher priority: how do we expect people to create good new articles, even a well-cited stub, if they can't use the same reference for more than one point?"", 'They get offered a ""reuse a reference"" button, but it doesn\'t work: seriously bad news.', ""The confused editor then has several choices: (a) don't give the extra reference(s) they think are appropriate, dumbing down the article; (b) re-input the reference each time they want to use it; (c) stop editing in VE and go into Edit Source (if they're lucky enough to be an established editor who knows about it and has learned how to use it ... not for newbies according to current ideas); (d) curse and swear and givve up trying to create their article and probably abandon editing Wikipedia altogether.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +53152,VisualEditor: Refactor references dialog to allow immediate insertion of reference content,"Currently, the ""insert reference"" dialog is a bit confusing and buggy, and it takes two or more steps to actually type the content of a reference (most common case). + +We should initialize the dialog with a micro-VE surface that immediately enables the user to type reference content. The selection of an existing reference can be pushed down into a separate section or tab. + +(Per discussion w/ James) + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Refactor references dialog to allow immediate insertion of reference content\n\nCurrently, the ""insert reference"" dialog is a bit confusing and buggy, and it takes two or more steps to actually type the content of a reference (most common case).', 'We should initialize the dialog with a micro-VE surface that immediately enables the user to type reference content.', 'The selection of an existing reference can be pushed down into a separate section or tab.', '(Per discussion w/ James)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +231609,VisualEditor: Refactor references dialog to allow immediate insertion of reference content,This was done and deployed last week.,task_subcomment,['This was done and deployed last week.'],['ACTION ON ISSUE'] +231603,VisualEditor: Refactor references dialog to allow immediate insertion of reference content,"Change 74191 merged by jenkins-bot: +Reference dialog commingling + +https://gerrit.wikimedia.org/r/74191",task_subcomment,['Change 74191 merged by jenkins-bot:\nReference dialog commingling\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +231598,VisualEditor: Refactor references dialog to allow immediate insertion of reference content,"Change 74191 had a related patch set uploaded by Jforrester: +Reference dialog commingling + +https://gerrit.wikimedia.org/r/74191",task_subcomment,['Change 74191 had a related patch set uploaded by Jforrester:\nReference dialog commingling\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +231594,VisualEditor: Refactor references dialog to allow immediate insertion of reference content,"Change 74191 had a related patch set uploaded by Trevor Parscal: +Reference dialog commingling + +https://gerrit.wikimedia.org/r/74191",task_subcomment,['Change 74191 had a related patch set uploaded by Trevor Parscal:\nReference dialog commingling\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +231591,VisualEditor: Refactor references dialog to allow immediate insertion of reference content,"James and I agreed to make this a ""stretch blocker"" for the IP release. (That means it's a blocker for now, unless other issues around content corruption or the basic edit surfacing operation become more critical.) The reason is that citations are such a crucial part of the new editing experience that we'd really like to make some basic improvements to the dialog ASAP, ahead of additional refactoring work around supporting citation templates etc.",task_subcomment,"['James and I agreed to make this a ""stretch blocker"" for the IP release.', ""(That means it's a blocker for now, unless other issues around content corruption or the basic edit surfacing operation become more critical.)"", ""The reason is that citations are such a crucial part of the new editing experience that we'd really like to make some basic improvements to the dialog ASAP, ahead of additional refactoring work around supporting citation templates etc.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +53150,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"data-mw.i seems to be dropped on edit in latest VE, which causes a loss of round-trip information for spaces etc. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"[""VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace\n\ndata-mw.i seems to be dropped on edit in latest VE, which causes a loss of round-trip information for spaces etc."", '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +343127,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"Change 180240 merged by jenkins-bot: +Remove workaround for Visual Editor bug (T53150). + +[[https://gerrit.wikimedia.org/r/180240]]",task_subcomment,"['Change 180240 merged by jenkins-bot:\nRemove workaround for Visual Editor bug (T53150).', '[[GERRIT_URL]]']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +343046,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"Change 180240 had a related patch set uploaded (by Cscott): +Remove workaround for Visual Editor bug (T53150). + +[[https://gerrit.wikimedia.org/r/180240]] + +#patch-for-review",task_subcomment,"['Change 180240 had a related patch set uploaded (by Cscott):\nRemove workaround for Visual Editor bug (T53150).', '[[GERRIT_URL]]\n\n#patch-for-review']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']" +231507,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"We've not seen this recur; it was probably caused by mis-cached code. Closing, but please re-open if it does happen again.",task_subcomment,"[""We've not seen this recur; it was probably caused by mis-cached code."", 'Closing, but please re-open if it does happen again.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']" +231502,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"**wicke** wrote: + +%%%*** Bug 51175 has been marked as a duplicate of this bug. ***%%%",task_subcomment,"['**wicke** wrote:\n\n%%%*** Bug 51175 has been marked as a duplicate of this bug.', '***%%%']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +231496,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"(In reply to comment #16) +> (In reply to comment #15) +> > I'm assuming that this is not yet deployed, as a new report was added to +> > 51161: +> > +> It is deployed. +> +> > Normally this single-transclusion content should be covered by the Parsoid +> > workaround. Did anything change in the VE handling recently that could have +> > re-added the ""i"" property with a faulty value? +> That sounds unlikely. When the user adds a new parameter, that parameter +> won't +> have an i value, but that seems reasonable to me. + +That infobox already existed. The 'i' property is per transclusion, not per parameter.",task_subcomment,"['(In reply to comment #16)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat infobox already existed.', ""The 'i' property is per transclusion, not per parameter.""]","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +231489,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"(In reply to comment #15) +> I'm assuming that this is not yet deployed, as a new report was added to +> 51161: +> +It is deployed. + +> Normally this single-transclusion content should be covered by the Parsoid +> workaround. Did anything change in the VE handling recently that could have +> re-added the ""i"" property with a faulty value? +That sounds unlikely. When the user adds a new parameter, that parameter won't have an i value, but that seems reasonable to me. + +I'll try to reproduce this later and see what's being sent back to Parsoid.",task_subcomment,"['(In reply to comment #15)\nQUOTE\nQUOTE\nQUOTE\nIt is deployed.', 'QUOTE\nQUOTE\nQUOTE\nThat sounds unlikely.', ""When the user adds a new parameter, that parameter won't have an i value, but that seems reasonable to me."", ""I'll try to reproduce this later and see what's being sent back to Parsoid.""]","['SOLUTION USAGE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +231485,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"I'm assuming that this is not yet deployed, as a new report was added to 51161: + +--------------------------------------------------- +This is what happened: +http://en.wikipedia.org/w/index.php?title=Scarborough_railway_station&diff=next&oldid=557856562 + +This is what the user intended: +http://en.wikipedia.org/w/index.php?title=Scarborough_railway_station&diff=564074475&oldid=557856562 + +If removal of newlines really is necessary, please insert a space instead. If +that is not possible, please remove the spaces from both sides of each equals. +An arrangement like + +|name = Scarborough|symbol = rail|code = SCA|image_name = +ScarboroughRailwayStation.jpg|caption = The entrance to the station + +gives the impression of associating a parameter name with the value immediately +preceding. An arrangement like + +|name=Scarborough |symbol=rail |code=SCA +|image_name=ScarboroughRailwayStation.jpg |caption=The entrance to the station + +would associate a parameter name with the value immediately following. +------------------------------------------------- + + +Normally this single-transclusion content should be covered by the Parsoid workaround. Did anything change in the VE handling recently that could have re-added the ""i"" property with a faulty value?",task_subcomment,"[""I'm assuming that this is not yet deployed, as a new report was added to 51161:\n\n---------------------------------------------------\nThis is what happened:\nURL\n\nThis is what the user intended:\nURL\n\nIf removal of newlines really is necessary, please insert a space instead."", 'If\nthat is not possible, please remove the spaces from both sides of each equals.', 'An arrangement like \n\n|name = Scarborough|symbol = rail|code = SCA|image_name =\nScarboroughRailwayStation.jpg|caption = The entrance to the station\n\ngives the impression of associating a parameter name with the value immediately\npreceding.', 'An arrangement like\n\n|name=Scarborough |symbol=rail |code=SCA\n|image_name=ScarboroughRailwayStation.jpg |caption=The entrance to the station\n\nwould associate a parameter name with the value immediately following.', '-------------------------------------------------\n\n\nNormally this single-transclusion content should be covered by the Parsoid workaround.', 'Did anything change in the VE handling recently that could have re-added the ""i"" property with a faulty value?']","['MOTIVATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +231479,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,*** Bug 51161 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51161 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +231473,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"Change 73372 merged by jenkins-bot: +Preserve unused Parsoid template properties + +https://gerrit.wikimedia.org/r/73372",task_subcomment,['Change 73372 merged by jenkins-bot:\nPreserve unused Parsoid template properties\n\nGERRIT_URL'],['ACTION ON ISSUE'] +231467,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"Change 73372 had a related patch set uploaded by Catrope: +Preserve unused Parsoid template properties + +https://gerrit.wikimedia.org/r/73372",task_subcomment,['Change 73372 had a related patch set uploaded by Catrope:\nPreserve unused Parsoid template properties\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +231460,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"The Parsoid workaround above is now deployed. If the index went missing in VE, it assumes that a single-transclusion target was not swapped out and reinserts the lost index in that case. This should avoid corruptions in the common single-template case. + +It will do nothing for multi-transclusion content (table start / row etc), and will also fail if the template was swapped out for another one. The latter case should be rare.",task_subcomment,"['The Parsoid workaround above is now deployed.', 'If the index went missing in VE, it assumes that a single-transclusion target was not swapped out and reinserts the lost index in that case.', 'This should avoid corruptions in the common single-template case.', 'It will do nothing for multi-transclusion content (table start / row etc), and will also fail if the template was swapped out for another one.', 'The latter case should be rare.']","['WORKAROUNDS', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +231453,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"Change 73187 merged by jenkins-bot: +Workaround for VE bug 51150 + +https://gerrit.wikimedia.org/r/73187",task_subcomment,['Change 73187 merged by jenkins-bot:\nWorkaround for VE bug 51150\n\nGERRIT_URL'],['WORKAROUNDS'] +231446,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"Change 73187 had a related patch set uploaded by GWicke: +Workaround for VE bug 51150 + +https://gerrit.wikimedia.org/r/73187",task_subcomment,['Change 73187 had a related patch set uploaded by GWicke:\nWorkaround for VE bug 51150\n\nGERRIT_URL'],['WORKAROUNDS'] +231438,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"Example on http://www.mediawiki.org/wiki/User:GWicke/TestDataMW?veaction=edit: + +Original data-mw: +data-mw='{""target"":{""wt"":""echo"",""href"":""../Template:Echo""},""params"":{""1"":{""wt"":""foo""}},""i"":0}' + +data-mw through VE without edit: +data-mw=""{"target":{"wt":"echo","href":"../Template:Echo"},"params":{"1":{"wt":"foo"}},"i":0}"" + +data-mw through VE after changing 'foo' to 'bar': +data-mw=""{"target":{"wt":"echo","href":"../Template:Echo"},"params":{"1":{"wt":"bar"}}}"" + +Note that the ""i"" member is gone.",task_subcomment,"['Example on URL\n\nOriginal data-mw:\ndata-mw=\'{""target"":{""wt"":""echo"",""href"":""../Template:Echo""},""params"":{""1"":{""wt"":""foo""}},""i"":0}\'\n\ndata-mw through VE without edit:\ndata-mw=""{"target":{"wt":"echo","href":"../Template:Echo"},"params":{"1":{"wt":"foo"}},"i":0}""\n\ndata-mw through VE after changing \'foo\' to \'bar\':\ndata-mw=""{"target":{"wt":"echo","href":"../Template:Echo"},"params":{"1":{"wt":"bar"}}}""\n\nNote that the ""i"" member is gone.']",['BUG REPRODUCTION'] +231433,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,Aha. Gotcha.,task_subcomment,"['Aha.', 'Gotcha.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +231428,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"(In reply to comment #4) +> https://en.wikipedia.org/w/index.php?title=Christchurch, +> _Dorset&diff=prev&oldid=563716751 +> appears to be a pre-deployment occurrence. + +This is post-Parsoid deployment.",task_subcomment,['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\n\nThis is post-Parsoid deployment.'],['OBSERVED BUG BEHAVIOR'] +231423,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"It is either data-mw.i or data-mw.parts[].i for templates. It is not new, but so far we have not used that information that heavily, so the fact that you drop the i probably fell under the radar. We use it to associate the public entry with private round-trip information such as the order of parameters and (crucially for this bug) whitespace. + +echo -e '{{echo|a = foo\n|b = c}}| node parse +

{{{1}}}

+",task_subcomment,"['It is either data-mw.i or data-mw.parts[].i for templates.', 'It is not new, but so far we have not used that information that heavily, so the fact that you drop the i probably fell under the radar.', 'We use it to associate the public entry with private round-trip information such as the order of parameters and (crucially for this bug) whitespace.', 'echo -e \'{{echo|a = foo\\n|b = c}}| node parse \n

{{{1}}}

\n']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']" +231419,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"https://en.wikipedia.org/w/index.php?title=Christchurch,_Dorset&diff=prev&oldid=563716751 appears to be a pre-deployment occurrence.",task_subcomment,['URL appears to be a pre-deployment occurrence.'],['OBSERVED BUG BEHAVIOR'] +231415,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,*** Bug 51161 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51161 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +231410,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"I can't reproduce this, even if I edit the template. VE preserves unmodified data-mw attributes always. + +Also, what is data-mw.i ? Is it new?",task_subcomment,"[""I can't reproduce this, even if I edit the template."", 'VE preserves unmodified data-mw attributes always.', 'Also, what is data-mw.i ?', 'Is it new?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +231407,VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,This then causes diffs like http://en.wikipedia.org/w/index.php?title=Bj%C3%B6rk&diff=563745216&oldid=563123196,task_subcomment,['This then causes diffs like URL'],['OBSERVED BUG BEHAVIOR'] +52848,VisualEditor/Parsoid: Beta release to en.wp IP users - blocking issues (tracking),"This is a tracking bug only for blocker-level issues before the planned release of the VisualEditor beta to IP users on English Wikipedia. Please only add blocker-level issues (e.g. content corruption); ultimately, what qualifies as ""blocker"" is at the discretion of James Forrester, VisualEditor PM. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",task_description,"['VisualEditor/Parsoid: Beta release to en.wp IP users - blocking issues (tracking)\n\nThis is a tracking bug only for blocker-level issues before the planned release of the VisualEditor beta to IP users on English Wikipedia.', 'Please only add blocker-level issues (e.g.', 'content corruption); ultimately, what qualifies as ""blocker"" is at the discretion of James Forrester, VisualEditor PM.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']","['FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']" +513031,VisualEditor/Parsoid: Beta release to en.wp IP users - blocking issues (tracking),[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],task_subcomment,['[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366]'],['INVESTIGATION AND EXPLORATION'] +238714,VisualEditor/Parsoid: Beta release to en.wp IP users - blocking issues (tracking),"The aspects of bug 50747 that were wanted have now been done; bug 51152 has not, but was a soft-blocker rather than a hard-blocker.",task_subcomment,"['The aspects of bug 50747 that were wanted have now been done; bug 51152 has not, but was a soft-blocker rather than a hard-blocker.']",['SOLUTION DISCUSSION'] +52768,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,"It is possible to have a tooltip that will tell you what a reference is when you hover over the number in edit mode, as it currently does in viewing? It is inconvenient to editors to have to go into the references mode to view the source while editing. + +(Request from En Wikipedia) + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**URL**: https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50110",task_description,"[""VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting\n\nIt is possible to have a tooltip that will tell you what a reference is when you hover over the number in edit mode, as it currently does in viewing?"", 'It is inconvenient to editors to have to go into the references mode to view the source while editing.', '(Request from En Wikipedia)\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**URL**: URL\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +233895,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,"Change 119913 merged by jenkins-bot: +Ultra-mega-hyper-citation editing on crack + +https://gerrit.wikimedia.org/r/119913",task_subcomment,['Change 119913 merged by jenkins-bot:\nUltra-mega-hyper-citation editing on crack\n\nGERRIT_URL'],['ACTION ON ISSUE'] +233890,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,"Change 119913 had a related patch set uploaded by Jforrester: +Ultra-mega-hyper-citation editing on crack + +https://gerrit.wikimedia.org/r/119913",task_subcomment,['Change 119913 had a related patch set uploaded by Jforrester:\nUltra-mega-hyper-citation editing on crack\n\nGERRIT_URL'],['ACTION ON ISSUE'] +233885,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,Yes. Hopefully this will be PTR later this week.,task_subcomment,"['Yes.', 'Hopefully this will be PTR later this week.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +233879,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,"This has been highest priority for four months now... +Does that still reflect reality?",task_subcomment,"['This has been highest priority for four months now...', 'Does that still reflect reality?']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']" +233871,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,"The bug as was written is the highest priority enhancement in VisualEditor and we've been working on it since October. + +The change in title and comment 3 reflect a further ambition for this area which will be addressed once this bug is fixed, and should be split off at some point.",task_subcomment,"[""The bug as was written is the highest priority enhancement in VisualEditor and we've been working on it since October."", 'The change in title and comment 3 reflect a further ambition for this area which will be addressed once this bug is fixed, and should be split off at some point.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +233865,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,"JamesF: This has been highest priority since 2013-11-08. +Any news or updates here?",task_subcomment,"['JamesF: This has been highest priority since 2013-11-08.', 'Any news or updates here?']","['BUG REPRODUCTION', 'SOLUTION USAGE']" +233861,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,*** Bug 51188 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51188 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +233857,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,"When cite web is used, webpage title, and access date should be filled +automatically for 1 click web citations.",task_subcomment,"['When cite web is used, webpage title, and access date should be filled\nautomatically for 1 click web citations.']",['INVESTIGATION AND EXPLORATION'] +233852,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,*** Bug 56708 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 56708 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +233845,VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting,*** Bug 56772 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 56772 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +52731,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",task_description,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)\n\nscreenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +231719,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)",Merged and will hopefully go out soon.,task_subcomment,['Merged and will hopefully go out soon.'],['SOLUTION DISCUSSION'] +231711,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Change 72069 merged by jenkins-bot: +mw.ViewPageTarget.init: Move edit section to top init + +https://gerrit.wikimedia.org/r/72069",task_subcomment,['Change 72069 merged by jenkins-bot:\nmw.ViewPageTarget.init: Move edit section to top init\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +231705,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",task_subcomment,"['Please consider fixing bug 50540 and maybe bug 50405, too.', 'They are directly dependent of this change.', 'Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth.', 'Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +231701,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Change 72069 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget.init: Move edit section to top init. + +https://gerrit.wikimedia.org/r/72069",task_subcomment,"['Change 72069 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget.init: Move edit section to top init.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +231697,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Bizarrely, the mouseover ""edit source"" links appear briefly when mousing over ""edit"" links while VE is loading a page into edit mode.",task_subcomment,"['Bizarrely, the mouseover ""edit source"" links appear briefly when mousing over ""edit"" links while VE is loading a page into edit mode.']",['OBSERVED BUG BEHAVIOR'] +231692,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Bug 48429#c35 - basically, visual section editing is a seriously hard problem, and isn't on the agenda any time soon.",task_subcomment,"[""Bug 48429#c35 - basically, visual section editing is a seriously hard problem, and isn't on the agenda any time soon.""]",['SOLUTION DISCUSSION'] +231686,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.",task_subcomment,"['Well, if that\'s the case (I haven\'t heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs.', 'Otherwise, I expect quite a bit of confusion.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +231679,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future. So we now don't have an interface that claims functionality there aren't even plans to implement.",task_subcomment,"[""I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future."", ""So we now don't have an interface that claims functionality there aren't even plans to implement.""]","['ISSUE CONTENT MANAGEMENT', 'SOLUTION DISCUSSION']" +52715,"VisualEditor: Transclusion dialog sometimes shows items in ""Add parameter"" that are already used","Screenshot of problem + +This causing: + +* The label fallback (parameter name + ucfirst) not working. +* It is still available from the ""Add parameter"" dropdown. +* The user can actually add it again, causing a logic error. + +I can currently consistently reproduce this on https://en.wikipedia.org/wiki/Taal%2C_Batangas?veaction=edit when editing the ""Population Consensus of Taal"" information box. + +See screenshot: +- ""title"" is both in the sidebar and in the selectable cloud +- ""title"" isn't transformed into ""Title"" (the templatedata has no .label for this one) + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11920}",task_description,"['VisualEditor: Transclusion dialog sometimes shows items in ""Add parameter"" that are already used\n\nScreenshot of problem\n\nThis causing:\n\n* The label fallback (parameter name + ucfirst) not working.', '* It is still available from the ""Add parameter"" dropdown.', '* The user can actually add it again, causing a logic error.', 'I can currently consistently reproduce this on URL when editing the ""Population Consensus of Taal"" information box.', 'See screenshot:\n- ""title"" is both in the sidebar and in the selectable cloud\n- ""title"" isn\'t transformed into ""Title"" (the templatedata has no .label for this one)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11920}']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +255765,"VisualEditor: Transclusion dialog sometimes shows items in ""Add parameter"" that are already used",This is now fixed in master and we will push to production very soon. Sorry for the inconvenience.,task_subcomment,"['This is now fixed in master and we will push to production very soon.', 'Sorry for the inconvenience.']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']" +255759,"VisualEditor: Transclusion dialog sometimes shows items in ""Add parameter"" that are already used","Change 73010 merged by jenkins-bot: +Retain original param names and ignore leading/trailing whitespace + +https://gerrit.wikimedia.org/r/73010",task_subcomment,['Change 73010 merged by jenkins-bot:\nRetain original param names and ignore leading/trailing whitespace\n\nGERRIT_URL'],['ACTION ON ISSUE'] +255753,"VisualEditor: Transclusion dialog sometimes shows items in ""Add parameter"" that are already used","Change 73010 had a related patch set uploaded by Trevor Parscal: +Retain original param names and ignore leading/trailing whitespace + +https://gerrit.wikimedia.org/r/73010",task_subcomment,['Change 73010 had a related patch set uploaded by Trevor Parscal:\nRetain original param names and ignore leading/trailing whitespace\n\nGERRIT_URL'],['ACTION ON ISSUE'] +52708,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),"The Edit tab for VisualEditor is sometimes not correctly initialized. Loading about 50 random pages, on one of them I will not have the ""Edit source"" tab, and the ""Edit"" tab will point to the wikitext editor instead of VisualEditor. + +Chrome/Ubuntu, logged-in. Console shows the following error when this occurs: + +Exception thrown by skins.vector.js: Object [object Object] has no method 'collapsibleTabs' + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews)\n\nThe Edit tab for VisualEditor is sometimes not correctly initialized.', 'Loading about 50 random pages, on one of them I will not have the ""Edit source"" tab, and the ""Edit"" tab will point to the wikitext editor instead of VisualEditor.', 'Chrome/Ubuntu, logged-in.', ""Console shows the following error when this occurs:\n\nException thrown by skins.vector.js: Object [object Object] has no method 'collapsibleTabs'\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +255243,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),No longer able to repro this either so closing as fixed; will reopen if I see it reappear.,task_subcomment,['No longer able to repro this either so closing as fixed; will reopen if I see it reappear.'],['BUG REPRODUCTION'] +255237,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),"(In reply to comment #5) +> I still saw it a couple days ago. I'll try with a clean (standard prefs) test +> account later today. + +Did a spot-test of 100 on Firefox and another 50 in Safari, and also didn't have any issues.",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\n\nDid a spot-test of 100 on Firefox and another 50 in Safari, and also didn't have any issues.""]",['SOLUTION DISCUSSION'] +255230,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),I still saw it a couple days ago. I'll try with a clean (standard prefs) test account later today.,task_subcomment,"['I still saw it a couple days ago.', ""I'll try with a clean (standard prefs) test account later today.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +255223,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),(Though it didn't recur for me just now on a spot-test of 100 Special:Randoms.),task_subcomment,"[""(Though it didn't recur for me just now on a spot-test of 100 Special:Randoms.)""]",['OBSERVED BUG BEHAVIOR'] +255216,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),"(In reply to comment #2) +> The collapsibleTabs thing was bug 50504, and it's supposed to be fixed now. + +Yes, but apparently that fix of Roan's didn't fix this issue.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\n\nYes, but apparently that fix of Roan's didn't fix this issue.""]",['OBSERVED BUG BEHAVIOR'] +255206,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),"The collapsibleTabs thing was bug 50504, and it's supposed to be fixed now.",task_subcomment,"[""The collapsibleTabs thing was bug 50504, and it's supposed to be fixed now.""]",['OBSERVED BUG BEHAVIOR'] +255198,VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews),"FYI Timo/Roan, still getting this, but no longer getting the collapsibleTabs error on the console. :P",task_subcomment,"['FYI Timo/Roan, still getting this, but no longer getting the collapsibleTabs error on the console.', ':P']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +52601,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"It might be nice to show a quick intro message for first-time user, could be implemented via GuidedTour. We may want to distinguish between new vs. experienced users. + +Part of the goal of the message would be to help users understand the difference between editing in wikitext and VisualEditor, and to explain that wikitext cannot be entered in VisualEditor. We're seeing a fair number of users enter wikitext in VisualEditor, and adding a first-time explanation might help reduce this issue as we roll out VisualEditor to more wikis. + +(Feel free to close this WONTFIX if we decide this issue is not significant in scale enough or the message would be too prominent. But having a first-time use message come up is not that unusual for a major feature change.) + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T51820} +{T89074}",task_description,"['VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?)', 'It might be nice to show a quick intro message for first-time user, could be implemented via GuidedTour.', 'We may want to distinguish between new vs. experienced users.', 'Part of the goal of the message would be to help users understand the difference between editing in wikitext and VisualEditor, and to explain that wikitext cannot be entered in VisualEditor.', ""We're seeing a fair number of users enter wikitext in VisualEditor, and adding a first-time explanation might help reduce this issue as we roll out VisualEditor to more wikis."", '(Feel free to close this WONTFIX if we decide this issue is not significant in scale enough or the message would be too prominent.', 'But having a first-time use message come up is not that unusual for a major feature change.)', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T51820}\n{T89074}']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'WORKAROUNDS', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +249025,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"**swalling** wrote: + +Okay, since VE implemented this in their own dialog system, instead of us doing it in GuidedTours, I'm going to go ahead and close this.",task_subcomment,"[""**swalling** wrote:\n\nOkay, since VE implemented this in their own dialog system, instead of us doing it in GuidedTours, I'm going to go ahead and close this.""]",['ACTION ON ISSUE'] +249020,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"(In reply to comment #11) +> GuidedTour support for VE is shaping up, so we're about ready to start +> building this. But before we embark on this tour you've suggested, I just +> wanted to confirm you're still thinking it's necessary in light of +> https://gerrit.wikimedia.org/r/#/c/73569/ and bug 49820? + +I think we still want a GuidedTour to highlight that the user is now in VisualEditor and not the wikitext editor; a very brief one-time message of ""hey, you're in VisualEditor now - here is the user guide"" or similar should suffice.",task_subcomment,"['(In reply to comment #11)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI think we still want a GuidedTour to highlight that the user is now in VisualEditor and not the wikitext editor; a very brief one-time message of ""hey, you\'re in VisualEditor now - here is the user guide"" or similar should suffice.']",['SOLUTION DISCUSSION'] +249015,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"James - please weigh in. My take is that we still need a first-use tour. We're changing the function of the ""Edit"" link, and just giving the user the wikitext warning isn't quite sufficient in informing them about a change of this magnitude. I don't think we'll need it indefinitely, but while VE is in Beta, doing this as part of the wider language rollout will save us and the community some additional transition pain, I think.",task_subcomment,"['James - please weigh in.', 'My take is that we still need a first-use tour.', 'We\'re changing the function of the ""Edit"" link, and just giving the user the wikitext warning isn\'t quite sufficient in informing them about a change of this magnitude.', ""I don't think we'll need it indefinitely, but while VE is in Beta, doing this as part of the wider language rollout will save us and the community some additional transition pain, I think.""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN']" +249007,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"**swalling** wrote: + +(In reply to comment #9) +> Let's strike the idea of a distinction between new and experienced users for +> now. Philippe and James make the good point that we can't really tell for +> sure +> whether a user is new, especially when editing as an IP, so in the interest +> of +> simplicity and consistency, I suggest we show the same message to everyone +> for +> a while. We can then later either turn it off completely, or show it only to +> a +> subset. + +GuidedTour support for VE is shaping up, so we're about ready to start building this. But before we embark on this tour you've suggested, I just wanted to confirm you're still thinking it's necessary in light of https://gerrit.wikimedia.org/r/#/c/73569/ and bug 49820?",task_subcomment,"[""**swalling** wrote:\n\n(In reply to comment #9)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nGuidedTour support for VE is shaping up, so we're about ready to start building this."", ""But before we embark on this tour you've suggested, I just wanted to confirm you're still thinking it's necessary in light of URL and bug 49820?""]","['WORKAROUNDS', 'INVESTIGATION AND EXPLORATION']" +249000,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"**weskaggs** wrote: + +I've had quite a bit of experience with things like this working on the GIMP project, and would like to try to convey a bit of ""wisdom"" that we learned the hard way. + +First, there are severe limits on the amount of information a new user, unfamiliar with the interface, can learn from a guided tour. A tour can give some increased sense of familiarity, but it can't give an ability to do specific tasks. Above all, a tour can't substitute for simplicity and discoverability. + +Second, a guided tour should never be forced on anybody. It can be offered if that can be done unobtrusively, but should never be required. + +Third, if a guided tour exists, it should be available on demand, and able to be repeated as often as desired. Ideally there should be some sort of ""help"" menu in the interface, offering the tour as one of the entries. + +Fourth, if you make a guided tour, you should consider making a video version and putting it on Youtube. That might seem like a bizarre idea, but many users are very comfortable with that format. + +Also I agree that there is a strong need to show a warning to users who try to enter wiki-markup directly (with a link to an extended explanation).",task_subcomment,"['**weskaggs** wrote:\n\nI\'ve had quite a bit of experience with things like this working on the GIMP project, and would like to try to convey a bit of ""wisdom"" that we learned the hard way.', 'First, there are severe limits on the amount of information a new user, unfamiliar with the interface, can learn from a guided tour.', ""A tour can give some increased sense of familiarity, but it can't give an ability to do specific tasks."", ""Above all, a tour can't substitute for simplicity and discoverability."", 'Second, a guided tour should never be forced on anybody.', 'It can be offered if that can be done unobtrusively, but should never be required.', 'Third, if a guided tour exists, it should be available on demand, and able to be repeated as often as desired.', 'Ideally there should be some sort of ""help"" menu in the interface, offering the tour as one of the entries.', 'Fourth, if you make a guided tour, you should consider making a video version and putting it on Youtube.', 'That might seem like a bizarre idea, but many users are very comfortable with that format.', 'Also I agree that there is a strong need to show a warning to users who try to enter wiki-markup directly (with a link to an extended explanation).']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +248992,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"Let's strike the idea of a distinction between new and experienced users for now. Philippe and James make the good point that we can't really tell for sure whether a user is new, especially when editing as an IP, so in the interest of simplicity and consistency, I suggest we show the same message to everyone for a while. We can then later either turn it off completely, or show it only to a subset.",task_subcomment,"[""Let's strike the idea of a distinction between new and experienced users for now."", ""Philippe and James make the good point that we can't really tell for sure whether a user is new, especially when editing as an IP, so in the interest of simplicity and consistency, I suggest we show the same message to everyone for a while."", 'We can then later either turn it off completely, or show it only to a subset.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +248987,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"We'll probably set this up so it launches when they visit a VE-eligible article, unless they have a hidden preference that shows it has launched before. The role isSinglePage plays is ensuring no cookie is stored tracking their tour progress. So even if they navigate away without closing the tour, it won't show again.",task_subcomment,"[""We'll probably set this up so it launches when they visit a VE-eligible article, unless they have a hidden preference that shows it has launched before."", 'The role isSinglePage plays is ensuring no cookie is stored tracking their tour progress.', ""So even if they navigate away without closing the tour, it won't show again.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +248981,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"**swalling** wrote: + +(In reply to comment #6) +> I'd suggest: +> +> If user account was created before July 1, 2013, display the following +> message +> exactly once: +> +> - +> You are using the VisualEditor, a new rich-text editing interface for +> {{SITENAME}} (currently in beta). Please be aware that wiki syntax (e.g. +> ""[[link to another page]]"") will not work in this editing mode. To use +> the +> old editing interface, click the 'Edit source' tab or section link. +> - +> +> For extra points, the ""exactly once"" could be managed via a ""Do not show this +> message again"" checkbox. But it shouldn't be handled as a notice that comes +> up +> every single time -- it should definitely be dismissible. +> +> The reason I'd like to finalize the language soon is to give us enough time +> to +> get translations. + +I think this is reasonable. + +Regarding showing a tour only once: I don't think we have to add an explicit checkbox to show it exactly once. Currently the default behavior is... + +If a user completes the tour or clicks the X to close we never show it again. So in this case, as a single step tour, clicking the ""Okay"" button or X would end the tour and it would never repeat. That is stored as a hidden preference, so it works across sessions, but not across wikis. + +If we really want to tie it to a single page, there is also an isSinglePage variable we can set for the tour, which means no matter what it will only appear on that one page.",task_subcomment,"['**swalling** wrote:\n\n(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI think this is reasonable.', ""Regarding showing a tour only once: I don't think we have to add an explicit checkbox to show it exactly once."", 'Currently the default behavior is...', 'If a user completes the tour or clicks the X to close we never show it again.', 'So in this case, as a single step tour, clicking the ""Okay"" button or X would end the tour and it would never repeat.', 'That is stored as a hidden preference, so it works across sessions, but not across wikis.', 'If we really want to tie it to a single page, there is also an isSinglePage variable we can set for the tour, which means no matter what it will only appear on that one page.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +248977,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"I'd suggest: + +If user account was created before July 1, 2013, display the following message exactly once: + +- +You are using the VisualEditor, a new rich-text editing interface for {{SITENAME}} (currently in beta). Please be aware that wiki syntax (e.g. ""[[link to another page]]"") will not work in this editing mode. To use the old editing interface, click the 'Edit source' tab or section link. +- + +For extra points, the ""exactly once"" could be managed via a ""Do not show this message again"" checkbox. But it shouldn't be handled as a notice that comes up every single time -- it should definitely be dismissible. + +The reason I'd like to finalize the language soon is to give us enough time to get translations.",task_subcomment,"[""I'd suggest:\n\nIf user account was created before July 1, 2013, display the following message exactly once:\n\n-\nYou are using the VisualEditor, a new rich-text editing interface for {{SITENAME}} (currently in beta)."", 'Please be aware that wiki syntax (e.g.', '""[[link to another page]]"") will not work in this editing mode. To use the old editing interface, click the \'Edit source\' tab or section link.', '-\n\nFor extra points, the ""exactly once"" could be managed via a ""Do not show this message again"" checkbox.', ""But it shouldn't be handled as a notice that comes up every single time -- it should definitely be dismissible."", ""The reason I'd like to finalize the language soon is to give us enough time to get translations.""]","['WORKAROUNDS', 'OBSERVED BUG BEHAVIOR', 'WORKAROUNDS', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN']" +248972,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"(In reply to comment #2) +> (In reply to comment #1) +> > Adding Steven in case his team wants to help/weigh in. +> +> TL;DR: +> +> Unless VE team wants to own it, I think E3 can handle any tours of basic +> editing functionality (with and without VE). What we have is 1/2 way toward +> the changes Erik requested. + +Awesome; very happy for E3 to lead on this. We'll support as needed, of course. + +> We are working on adding better VE support in GuidedTour currently, and I've +> added Matt Flaschen since he's tackling that. We are shooting for feature +> parity with our previous guided tour of editing for the first time delivered +> to GettingStarted editors, with the exception being that there is no Preview +> step to point to in VE. +> +> Also, soon we hope to test delivering a guided tour to all newly-registered +> editors, outside the GettingStarted funnel. (Docs: +> https://meta.wikimedia.org/wiki/Research:Guided_tours). Whether we run that +> test on a wiki like Spanish or French instead of English depends on l10n of +> the ""first edit"" tour and whether VE support is ready. S Page is helping +> out with this test, so I've added him as well. +> +> If we're interested in pointing out the difference between VE and wikitext to +> users right away, we could easily build that in as step for the guided tours +> delivered via GettingStarted and the general ""first edit"" tour we're +> planning. Currently with the tour that's in production, we just point to the +> Edit button and section edit buttons. +> +> I'm open to changing that, but I do think we should be cautious about +> throwing too much complexity at first time editors too soon, by pointing out +> the multiple methods of editing. I added Pau for his input. + +Yeah, I'm not convinced I know what we'd want to do. + +Maybe just a simple ""you're using VisualEditor"" on first load for experienced users? + +Maybe a set of ""add a {reference,template} by clicking here"" ones too? Maybe not? + +What do you advise?",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAwesome; very happy for E3 to lead on this.', ""We'll support as needed, of course."", ""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah, I'm not convinced I know what we'd want to do."", 'Maybe just a simple ""you\'re using VisualEditor"" on first load for experienced users?', 'Maybe a set of ""add a {reference,template} by clicking here"" ones too?', 'Maybe not?', 'What do you advise?']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +248968,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"If it's semi-experienced users who are entering the wikitext, that could be improved with a tour specific to them (and/or VE documentation). + +If it's new users (they are less likely to know wikitext, though) making this mistake, maybe the comparison is necessary.",task_subcomment,"[""If it's semi-experienced users who are entering the wikitext, that could be improved with a tour specific to them (and/or VE documentation)."", ""If it's new users (they are less likely to know wikitext, though) making this mistake, maybe the comparison is necessary.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +248964,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"(In reply to comment #2) +> If we're interested in pointing out the difference between VE and wikitext to +> users right away, we could easily build that in as step for the guided tours +> delivered via GettingStarted and the general ""first edit"" tour we're +> planning. + +I don't think that (comparing VE and wikitext) needs to be in the first tour. It's discoverable in the UI in a consistent way, plus people on-wiki will point to and explain the difference when necessary.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't think that (comparing VE and wikitext) needs to be in the first tour."", ""It's discoverable in the UI in a consistent way, plus people on-wiki will point to and explain the difference when necessary.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +248961,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),"**swalling** wrote: + +(In reply to comment #1) +> Adding Steven in case his team wants to help/weigh in. + +TL;DR: + +Unless VE team wants to own it, I think E3 can handle any tours of basic editing functionality (with and without VE). What we have is 1/2 way toward the changes Erik requested. + +Full details: + +We are working on adding better VE support in GuidedTour currently, and I've added Matt Flaschen since he's tackling that. We are shooting for feature parity with our previous guided tour of editing for the first time delivered to GettingStarted editors, with the exception being that there is no Preview step to point to in VE. + +Also, soon we hope to test delivering a guided tour to all newly-registered editors, outside the GettingStarted funnel. (Docs: https://meta.wikimedia.org/wiki/Research:Guided_tours). Whether we run that test on a wiki like Spanish or French instead of English depends on l10n of the ""first edit"" tour and whether VE support is ready. S Page is helping out with this test, so I've added him as well. + +If we're interested in pointing out the difference between VE and wikitext to users right away, we could easily build that in as step for the guided tours delivered via GettingStarted and the general ""first edit"" tour we're planning. Currently with the tour that's in production, we just point to the Edit button and section edit buttons. + +I'm open to changing that, but I do think we should be cautious about throwing too much complexity at first time editors too soon, by pointing out the multiple methods of editing. I added Pau for his input.",task_subcomment,"['**swalling** wrote:\n\n(In reply to comment #1)\nQUOTE\n\nTL;DR: \n\nUnless VE team wants to own it, I think E3 can handle any tours of basic editing functionality (with and without VE).', 'What we have is 1/2 way toward the changes Erik requested.', ""Full details: \n\nWe are working on adding better VE support in GuidedTour currently, and I've added Matt Flaschen since he's tackling that."", 'We are shooting for feature parity with our previous guided tour of editing for the first time delivered to GettingStarted editors, with the exception being that there is no Preview step to point to in VE.', 'Also, soon we hope to test delivering a guided tour to all newly-registered editors, outside the GettingStarted funnel.', '(Docs: URL Whether we run that test on a wiki like Spanish or French instead of English depends on l10n of the ""first edit"" tour and whether VE support is ready.', ""S Page is helping out with this test, so I've added him as well."", 'If we\'re interested in pointing out the difference between VE and wikitext to users right away, we could easily build that in as step for the guided tours delivered via GettingStarted and the general ""first edit"" tour we\'re planning.', ""Currently with the tour that's in production, we just point to the Edit button and section edit buttons."", ""I'm open to changing that, but I do think we should be cautious about throwing too much complexity at first time editors too soon, by pointing out the multiple methods of editing."", 'I added Pau for his input.']","['WORKAROUNDS', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +248956,VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?),Adding Steven in case his team wants to help/weigh in.,task_subcomment,['Adding Steven in case his team wants to help/weigh in.'],['ACTION ON ISSUE'] +52441,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"After save of page using VisualEditor on beta, and clicking on Edit again (I am on the current page, as the content has been updated), I don't get the latest revision, but the revision I had before (the content switches back to the old version), and getting a warning that I'm not editing the latest version + +-------------------------- +**Version**: unspecified +**Severity**: blocker +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50716",task_description,"[""VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages)\n\nAfter save of page using VisualEditor on beta, and clicking on Edit again (I am on the current page, as the content has been updated), I don't get the latest revision, but the revision I had before (the content switches back to the old version), and getting a warning that I'm not editing the latest version\n\n--------------------------\n**Version**: unspecified\n**Severity**: blocker\n**See Also**:\nURL""]",['OBSERVED BUG BEHAVIOR'] +239595,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"This is now deployed and appears to be working as expected in production, according to my testing. Marking as fixed. Please re-open if you find otherwise.",task_subcomment,"['This is now deployed and appears to be working as expected in production, according to my testing.', 'Marking as fixed.', 'Please re-open if you find otherwise.']","['SOLUTION USAGE', 'ACTION ON ISSUE', 'ACTION ON ISSUE']" +239592,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Change 72070 merged by jenkins-bot: +mw.ViewPageTarget: Fix incorrect retention of the wrong oldid + +https://gerrit.wikimedia.org/r/72070",task_subcomment,['Change 72070 merged by jenkins-bot:\nmw.ViewPageTarget: Fix incorrect retention of the wrong oldid\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +239587,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),*** Bug 50596 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50596 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +239580,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),Bug 47420 is the same thing that was reopened. One of these two should be merged as a duplicate of the other.,task_subcomment,"['Bug 47420 is the same thing that was reopened.', 'One of these two should be merged as a duplicate of the other.']","['BUG REPRODUCTION', 'BUG REPRODUCTION']" +239572,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Change 72070 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget: Only pass oldid if we have to and clear/update it on save + +https://gerrit.wikimedia.org/r/72070",task_subcomment,['Change 72070 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget: Only pass oldid if we have to and clear/update it on save\n\nGERRIT_URL'],['ACTION ON ISSUE'] +239565,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Actually, though we are indeed initialising for the version the user is reading instead of the latest version (separate bug) we do update `this.oldid` in mw.ViewPageTarget#onSave based on the data we got from the API. + +However the API isn't returning that data, there is no ""data.newrevid"" returned by ApiVisualEditor.",task_subcomment,"['Actually, though we are indeed initialising for the version the user is reading instead of the latest version (separate bug) we do update CODE in mw.ViewPageTarget#onSave based on the data we got from the API.', 'However the API isn\'t returning that data, there is no ""data.newrevid"" returned by ApiVisualEditor.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +239559,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Which makes me wonder, why are we using that in the first place. Don't we always want to be editing the latest version (except when url has oldid=) even if the latest version is more recent than the version the user is reading (either because the page is cached or because an edit was made while the user was viewing the page).",task_subcomment,"['Which makes me wonder, why are we using that in the first place.', ""Don't we always want to be editing the latest version (except when url has oldid=) even if the latest version is more recent than the version the user is reading (either because the page is cached or because an edit was made while the user was viewing the page).""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']" +239552,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Figured out the cause: + +This revision id for the page is initialised in ve.init.mw.Target from wgCurRevisionId but then never updated.",task_subcomment,['Figured out the cause:\n\nThis revision id for the page is initialised in ve.init.mw.Target from wgCurRevisionId but then never updated.'],['OBSERVED BUG BEHAVIOR'] +239546,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"(In reply to comment #8) +> If there's any likely timescale for the fixing of this bug, it might be +> useful to comment there: is ""soon"" likely to be hours, days, or weeks?! + +Days. :-) Don't want to promise ""tomorrow"" if we don't manage to fix it by then, but certainly as soon as we can get it written, tested and deployed.",task_subcomment,"['(In reply to comment #8)\nQUOTE\nQUOTE\n\nDays.', ':-) Don\'t want to promise ""tomorrow"" if we don\'t manage to fix it by then, but certainly as soon as we can get it written, tested and deployed.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +239539,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"(In reply to comment #7) +> (In reply to comment #6) +> > Pending a full solution, is there any way that the pink error box can be +> > amended to include something like: ""Please click the ""Cancel"" button, then +> > Refresh/Reload the page and try again. Apologies for this temporary problem - +> > we are working on it."" +> > +> > It's irritating for an experienced editor who has found the work-round, but +> > must be desperately confusing for a new editor who has just made an edit, had +> > an afterthought, and gets that message. +> +> The message displayed is editable by any English Wikipedia sysop; this +> doesn't +> need any code changes to alter the text, or remove the bright pinkness, but +> you +> should discuss it with the community: +> https://en.wikipedia.org/wiki/MediaWiki:Editingold +> +> We're hoping to get this regression fixed soon; sorry for the inconvenience. + +OK, have raised a suggestion at [[MediaWiki_talk:Editingold#VE_problem]]. If there's any likely timescale for the fixing of this bug, it might be useful to comment there: is ""soon"" likely to be hours, days, or weeks?!",task_subcomment,"['(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOK, have raised a suggestion at [[MediaWiki_talk:Editingold#VE_problem]].', 'If there\'s any likely timescale for the fixing of this bug, it might be useful to comment there: is ""soon"" likely to be hours, days, or weeks?', '!']","['SOLUTION DISCUSSION', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']" +239534,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"(In reply to comment #6) +> Pending a full solution, is there any way that the pink error box can be +> amended to include something like: ""Please click the ""Cancel"" button, then +> Refresh/Reload the page and try again. Apologies for this temporary problem - +> we are working on it."" +> +> It's irritating for an experienced editor who has found the work-round, but +> must be desperately confusing for a new editor who has just made an edit, had +> an afterthought, and gets that message. + +The message displayed is editable by any English Wikipedia sysop; this doesn't need any code changes to alter the text, or remove the bright pinkness, but you should discuss it with the community: https://en.wikipedia.org/wiki/MediaWiki:Editingold + +We're hoping to get this regression fixed soon; sorry for the inconvenience.",task_subcomment,"[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message displayed is editable by any English Wikipedia sysop; this doesn't need any code changes to alter the text, or remove the bright pinkness, but you should discuss it with the community: URL\n\nWe're hoping to get this regression fixed soon; sorry for the inconvenience.""]",['SOLUTION USAGE'] +239529,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Pending a full solution, is there any way that the pink error box can be amended to include something like: ""Please click the ""Cancel"" button, then Refresh/Reload the page and try again. Apologies for this temporary problem - we are working on it."" + +It's irritating for an experienced editor who has found the work-round, but must be desperately confusing for a new editor who has just made an edit, had an afterthought, and gets that message.",task_subcomment,"['Pending a full solution, is there any way that the pink error box can be amended to include something like: ""Please click the ""Cancel"" button, then Refresh/Reload the page and try again.', 'Apologies for this temporary problem - we are working on it.""', ""It's irritating for an experienced editor who has found the work-round, but must be desperately confusing for a new editor who has just made an edit, had an afterthought, and gets that message.""]","['WORKAROUNDS', 'WORKAROUNDS', 'OBSERVED BUG BEHAVIOR']" +239524,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),*** Bug 50555 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50555 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +239521,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Comment on attachment 12694 +Screen recording of the bug + +This is how the problem materialize for me, as you see, it jumps back to the previous revision on edit, and then complains it's not the latest revision.",task_subcomment,"[""Comment on attachment 12694\nScreen recording of the bug\n\nThis is how the problem materialize for me, as you see, it jumps back to the previous revision on edit, and then complains it's not the latest revision.""]",['OBSERVED BUG BEHAVIOR'] +239519,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"Screen recording of the bug + +**Attached**: {F11340}",task_subcomment,['Screen recording of the bug\n\n**Attached**: {F11340}'],['OBSERVED BUG BEHAVIOR'] +239515,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"The url is http://en.wikipedia.beta.wmflabs.org/wiki/User:AzaToth/Test2?veaction=edit + +Following is a timeline: + +http://i.imgur.com/VmbT33s.png +http://i.imgur.com/FVWEf4r.png +http://i.imgur.com/ieTdi36.png +http://i.imgur.com/DP0eDLs.png +http://i.imgur.com/fNRbqeP.png",task_subcomment,['The url is URL\n\nFollowing is a timeline:\n\nURL\nURL\nURL\nURL\nURL'],['OBSERVED BUG BEHAVIOR'] +239511,VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages),"What url do you go to initially? +After saving and reading the page, what do you see. The version from before you edited or after, and what does the url look like? + +When going into edit mode after saving, what does the url look like?",task_subcomment,"['What url do you go to initially?', 'After saving and reading the page, what do you see.', 'The version from before you edited or after, and what does the url look like?', 'When going into edit mode after saving, what does the url look like?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +52424,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","An attempt to save an article in the visual editor after a period of inactivity results in the ""Invalid token"" error message and saving fails. At this point, the user is completely stuck and their entire work is lost. + +Loss of session data can also occur in the regular source code edit window, but is easily rectified by repeated saving; this doesn't work in the visual editor. + +I would classify this as user-hostile behavior. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50402",task_description,"['VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work\n\nAn attempt to save an article in the visual editor after a period of inactivity results in the ""Invalid token"" error message and saving fails.', 'At this point, the user is completely stuck and their entire work is lost.', ""Loss of session data can also occur in the regular source code edit window, but is easily rectified by repeated saving; this doesn't work in the visual editor."", 'I would classify this as user-hostile behavior.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'BUG REPRODUCTION']" +238349,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","This is now fixed in master, which will be deployed within the hour.",task_subcomment,"['This is now fixed in master, which will be deployed within the hour.']",['SOLUTION USAGE'] +238342,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","Change 73446 merged by jenkins-bot: +mw.ViewPageTarget: Refetch token if session expired + +https://gerrit.wikimedia.org/r/73446",task_subcomment,['Change 73446 merged by jenkins-bot:\nmw.ViewPageTarget: Refetch token if session expired\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +238336,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","Please note that the reporter of Bug 51302 also points out that the session expiry clock already starts ticking once an article is opened for *reading*, i.e. potentially much earlier than when the visual editor is started on the article.",task_subcomment,"['Please note that the reporter of Bug 51302 also points out that the session expiry clock already starts ticking once an article is opened for *reading*, i.e.', 'potentially much earlier than when the visual editor is started on the article.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238331,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work",I just encountered this problem. I would call this bug a blocker as it is effectively 'dataloss' in bmo keyword terminology!,task_subcomment,"['I just encountered this problem.', ""I would call this bug a blocker as it is effectively 'dataloss' in bmo keyword terminology!""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +238326,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work",*** Bug 51302 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51302 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238319,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","Change 73446 had a related patch set uploaded by Krinkle: +(DRAFT) mw.ViewPageTarget: Refetch token if session expired + +https://gerrit.wikimedia.org/r/73446",task_subcomment,['Change 73446 had a related patch set uploaded by Krinkle:\n(DRAFT) mw.ViewPageTarget: Refetch token if session expired\n\nGERRIT_URL'],['ACTION ON ISSUE'] +238314,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","Change 73203 merged by jenkins-bot: +mw.ViewPageTarget: Improve error message for badtoken error + +https://gerrit.wikimedia.org/r/73203",task_subcomment,['Change 73203 merged by jenkins-bot:\nmw.ViewPageTarget: Improve error message for badtoken error\n\nGERRIT_URL'],['ACTION ON ISSUE'] +238309,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","Change 73189 merged by jenkins-bot: +api: Split save action into separate API module + +https://gerrit.wikimedia.org/r/73189",task_subcomment,['Change 73189 merged by jenkins-bot:\napi: Split save action into separate API module\n\nGERRIT_URL'],['ACTION ON ISSUE'] +238305,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","Change 73203 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget: Improve error message for badtoken error + +https://gerrit.wikimedia.org/r/73203",task_subcomment,['Change 73203 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget: Improve error message for badtoken error\n\nGERRIT_URL'],['ACTION ON ISSUE'] +238301,"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work","Change 73189 had a related patch set uploaded by Krinkle: +API: Split save action into separate API module + +https://gerrit.wikimedia.org/r/73189",task_subcomment,['Change 73189 had a related patch set uploaded by Krinkle:\nAPI: Split save action into separate API module\n\nGERRIT_URL'],['ACTION ON ISSUE'] +52423,"VisualEditor: ref warning appears within template that contains references, post-modification","Screenshot + +See the screenshot; I imagine the reference is being treated as existing within the template, rather than within the template within the page - it hunts for , can't find a tag in the template itself, and freaks the heck out. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51337 + +**Attached**: {F11303}",task_description,"[""VisualEditor: ref warning appears within template that contains references, post-modification\n\nScreenshot\n\nSee the screenshot; I imagine the reference is being treated as existing within the template, rather than within the template within the page - it hunts for , can't find a tag in the template itself, and freaks the heck out."", '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL\n\n**Attached**: {F11303}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +238262,"VisualEditor: ref warning appears within template that contains references, post-modification",I'm forking this off into bug 51337.,task_subcomment,"[""I'm forking this off into bug 51337.""]",['BUG REPRODUCTION'] +238260,"VisualEditor: ref warning appears within template that contains references, post-modification","Change 73614 had a related patch set uploaded by Esanders: +Use new class to detect Cite errors inside templates + +https://gerrit.wikimedia.org/r/73614",task_subcomment,['Change 73614 had a related patch set uploaded by Esanders:\nUse new class to detect Cite errors inside templates\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +238257,"VisualEditor: ref warning appears within template that contains references, post-modification",Should probably leave this open to track improvements.,task_subcomment,['Should probably leave this open to track improvements.'],['FUTURE PLAN'] +238252,"VisualEditor: ref warning appears within template that contains references, post-modification",Also: https://gerrit.wikimedia.org/r/73096,task_subcomment,['Also: GERRIT_URL'],['SOLUTION DISCUSSION'] +238247,"VisualEditor: ref warning appears within template that contains references, post-modification","These are now hidden by the above commit, which we're deploying in the next few minutes.",task_subcomment,"[""These are now hidden by the above commit, which we're deploying in the next few minutes.""]",['WORKAROUNDS'] +238241,"VisualEditor: ref warning appears within template that contains references, post-modification","Change 73092 merged by jenkins-bot: +Hide ref errors inside MW transclusions + +https://gerrit.wikimedia.org/r/73092",task_subcomment,['Change 73092 merged by jenkins-bot:\nHide ref errors inside MW transclusions\n\nGERRIT_URL'],['ACTION ON ISSUE'] +238235,"VisualEditor: ref warning appears within template that contains references, post-modification","Change 73092 had a related patch set uploaded by Esanders: +Hide ref errors inside MW transclusions + +https://gerrit.wikimedia.org/r/73092",task_subcomment,['Change 73092 had a related patch set uploaded by Esanders:\nHide ref errors inside MW transclusions\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +238227,"VisualEditor: ref warning appears within template that contains references, post-modification","The short-term fix is to just strip this comment from the returned HTML that the PHP parser gives us. + +When we switch over to using Parsoid for this, we'll need that to run in context, somehow, so the references are correctly numbered and that we know to update the relevant reference lists.",task_subcomment,"['The short-term fix is to just strip this comment from the returned HTML that the PHP parser gives us.', ""When we switch over to using Parsoid for this, we'll need that to run in context, somehow, so the references are correctly numbered and that we know to update the relevant reference lists.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +52349,VisualEditor: Reference toolbar icon missing in wmf9,"The references list one is still there; did Trevor's change break it? + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,"[""VisualEditor: Reference toolbar icon missing in wmf9\n\nThe references list one is still there; did Trevor's change break it?"", '--------------------------\n**Version**: unspecified\n**Severity**: critical']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +233797,VisualEditor: Reference toolbar icon missing in wmf9,Fixed with new pull.,task_subcomment,['Fixed with new pull.'],['SOLUTION USAGE'] +52339,VisualEditor:  s converted to space characters (32s not 160s) on round-trip,"http://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FGNoSR&diff=561873747&oldid=561873385 + +Removes non-breaking space. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor:  s converted to space characters (32s not 160s) on round-trip\n\nURL\n\nRemoves non-breaking space.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +233191,VisualEditor:  s converted to space characters (32s not 160s) on round-trip,"We cannot reproduce this on several different browsers/computers; it's most likely cause by a browser plug-in that the user has installed. Marking as ""WORKSFORME"" but if you can work out with the user what they have that is breaking VisualEditor it'd be good to know.",task_subcomment,"[""We cannot reproduce this on several different browsers/computers; it's most likely cause by a browser plug-in that the user has installed."", 'Marking as ""WORKSFORME"" but if you can work out with the user what they have that is breaking VisualEditor it\'d be good to know.']","['OBSERVED BUG BEHAVIOR', 'WORKAROUNDS']" +233185,VisualEditor:  s converted to space characters (32s not 160s) on round-trip,Chrome Version 27.0.1453.116 on Windows 7 Home Premium.,task_subcomment,['Chrome Version 27.0.1453.116 on Windows 7 Home Premium.'],['OBSERVED BUG BEHAVIOR'] +233178,VisualEditor:  s converted to space characters (32s not 160s) on round-trip,Will inquire.,task_subcomment,['Will inquire.'],['INVESTIGATION AND EXPLORATION'] +233171,VisualEditor:  s converted to space characters (32s not 160s) on round-trip,Do you know which browser was used for this edit?,task_subcomment,['Do you know which browser was used for this edit?'],['OBSERVED BUG BEHAVIOR'] +233164,VisualEditor:  s converted to space characters (32s not 160s) on round-trip,Odd. I can't reproduce this locally or on the article.,task_subcomment,"['Odd.', ""I can't reproduce this locally or on the article.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +52264,load.php error? many symptoms...,"Log in to beta labs: + +No navigation arrows exist in FF or Chrome + +Special:Preferences shows no tabs + +No links to VE exists even when Preferences are set + +In regular editor, no controls appear + +A number of pages e.g. user page show error Uncaught ReferenceError: mw is not defined load.php:1 + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,"['load.php error?', 'many symptoms...\n\nLog in to beta labs: \n\nNo navigation arrows exist in FF or Chrome\n\nSpecial:Preferences shows no tabs\n\nNo links to VE exists even when Preferences are set\n\nIn regular editor, no controls appear\n\nA number of pages e.g.', 'user page show error Uncaught ReferenceError: mw is not defined load.php:1\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254099,load.php error? many symptoms...,Ah it seems the cached load.php got cleared finally. I got AFT and VisualEdit working properly now :-],task_subcomment,"['Ah it seems the cached load.php got cleared finally.', 'I got AFT and VisualEdit working properly now :-]']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +254093,load.php error? many symptoms...,"AFT, VisualEditor are now working when passing ?debug=true to the URL (which bypass resourceloader cache). + +I have no idea how to clear the resource loader cache though :(",task_subcomment,"['AFT, VisualEditor are now working when passing ?debug=true to the URL (which bypass resourceloader cache).', 'I have no idea how to clear the resource loader cache though :(']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +254086,load.php error? many symptoms...,Changes above reverts the two patches mentionned in bug 45918.,task_subcomment,['Changes above reverts the two patches mentionned in bug 45918.'],['BUG REPRODUCTION'] +254080,load.php error? many symptoms...,Related URL: https://gerrit.wikimedia.org/r/70806 (Gerrit Change Ie373d1f407788a8e2456c3d8a34cc79ac9ed8bb6),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change Ie373d1f407788a8e2456c3d8a34cc79ac9ed8bb6)'],['OBSERVED BUG BEHAVIOR'] +254073,load.php error? many symptoms...,Related URL: https://gerrit.wikimedia.org/r/70805 (Gerrit Change I02ed22e324435e362cabdfc67e69c224ad9e2550),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I02ed22e324435e362cabdfc67e69c224ad9e2550)'],['OBSERVED BUG BEHAVIOR'] +254067,load.php error? many symptoms...,"In the exception.log I also got a bunch of: + + +2013-06-26 22:39:51 deployment-jobrunner08 aawiki: [ff75b05a] [no req] Exception from line 32 of /data/project/apache/common-local/php-master/extensions/MwEmbedSupport/MwEmbedResourceManager.php: MwEmbedResourceManager::register not given readable path: extensions/TimedMediaHandler/MwEmbedModules/EmbedPlayer + + +It seems the issue is caused by https://gerrit.wikimedia.org/r/#/c/69479/ ""Register resources with absolute path"" which is intended to fix bug 45918 ""MwEmbedSupport doesn't work with non standard layouts""",task_subcomment,"['In the exception.log I also got a bunch of:\n\n\n2013-06-26 22:39:51 deployment-jobrunner08 aawiki: [ff75b05a] [no req] Exception from line 32 of /data/project/apache/common-local/php-master/extensions/MwEmbedSupport/MwEmbedResourceManager.php: MwEmbedResourceManager::register not given readable path: extensions/TimedMediaHandler/MwEmbedModules/EmbedPlayer\n\n\nIt seems the issue is caused by URL ""Register resources with absolute path"" which is intended to fix bug 45918 ""MwEmbedSupport doesn\'t work with non standard layouts""']",['BUG REPRODUCTION'] +254061,load.php error? many symptoms...,"exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""/usr/local/apache/common-local/php-master/er/extensions/MwEmbedSupport/MwEmbedModules/MediaWikiSupport/MediaWikiSupport.loader.js""' in /data/project/apache/common-local/php-master/includes/resourceloader/ResourceLoaderFileModule.php:574",task_subcomment,"['exception \'MWException\' with message \'ResourceLoaderFileModule::readScriptFiles: script file not found: ""/usr/local/apache/common-local/php-master/er/extensions/MwEmbedSupport/MwEmbedModules/MediaWikiSupport/MediaWikiSupport.loader.js""\' in /data/project/apache/common-local/php-master/includes/resourceloader/ResourceLoaderFileModule.php:574']",['OBSERVED BUG BEHAVIOR'] +254057,load.php error? many symptoms...,"not a blocker, sorry, mw.o is a workaround",task_subcomment,"['not a blocker, sorry, mw.o is a workaround']",['WORKAROUNDS'] +254054,load.php error? many symptoms...,"This also breaks Wikilove on beta. + +In about 24 hours I will be giving a training session at WMF for 50 people about browser test automation that I had intended to do with Wikilove on beta labs. + +While I could move the demo to mw.o instead, that would be less than ideal.",task_subcomment,"['This also breaks Wikilove on beta.', 'In about 24 hours I will be giving a training session at WMF for 50 people about browser test automation that I had intended to do with Wikilove on beta labs.', 'While I could move the demo to mw.o instead, that would be less than ideal.']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION']" +52259,VisualEditor: Silent clean-up of untouched references and templates,"I made a grammar fix (one word), and did not check the differences before saving. Mistake! :) + +http://en.wikipedia.org/w/index.php?title=Abdullah_of_Saudi_Arabia&diff=prev&oldid=561571041 + +It looks like all it did was sanitize the templates, which isn't the worst thing on earth, but it's hard to verify that was all that happened (especially for a non-expert). + +No recommended fix, exactly, but perhaps something to consider. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Silent clean-up of untouched references and templates\n\nI made a grammar fix (one word), and did not check the differences before saving.', 'Mistake!', "":) \n\nURL\n\nIt looks like all it did was sanitize the templates, which isn't the worst thing on earth, but it's hard to verify that was all that happened (especially for a non-expert)."", 'No recommended fix, exactly, but perhaps something to consider.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +253805,VisualEditor: Silent clean-up of untouched references and templates,"Yeah, this is a quite bad problem to have. Thankfully, we believe that the majority of these issues have now been fixed (since that edit of yours) - so I'm going to mark this as fixed. There are no-doubt other issues we've yet to spot, but we've fixed this one. :-) Sorry for the inconvenience!",task_subcomment,"['Yeah, this is a quite bad problem to have.', ""Thankfully, we believe that the majority of these issues have now been fixed (since that edit of yours) - so I'm going to mark this as fixed."", ""There are no-doubt other issues we've yet to spot, but we've fixed this one."", ':-) Sorry for the inconvenience!']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'SOLUTION USAGE', 'ACTION ON ISSUE']" +52246,VisualEditor: Be able to have enabled for all logged-in users but not anonymous users,"For deployment purposes, we will want VisualEditor to be enabled for all logged-in users but not anonymous ones; to do this, we'll probably just fail in VisualEditor.hooks.php#onBeforePageDisplay() if they're anonymous, according to Roan. + +-------------------------- +**Version**: unspecified +**Severity**: trivial",task_description,"[""VisualEditor: Be able to have enabled for all logged-in users but not anonymous users\n\nFor deployment purposes, we will want VisualEditor to be enabled for all logged-in users but not anonymous ones; to do this, we'll probably just fail in VisualEditor.hooks.php#onBeforePageDisplay() if they're anonymous, according to Roan."", '--------------------------\n**Version**: unspecified\n**Severity**: trivial']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']" +253157,VisualEditor: Be able to have enabled for all logged-in users but not anonymous users,We achieved this. Obviously. :-),task_subcomment,"['We achieved this.', 'Obviously.', ':-)']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +52241,"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Screenshot + +See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11809}",task_description,"['VisualEditor: Dialogs, inspector menu, link inspector etc.', 'appear behind the document in Monobook\n\nScreenshot\n\nSee screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11809}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +252937,"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Change 70851 merged by jenkins-bot: +Make local overlays local to surface and remove insane z-indexes + +https://gerrit.wikimedia.org/r/70851",task_subcomment,['Change 70851 merged by jenkins-bot:\nMake local overlays local to surface and remove insane z-indexes\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +252931,"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Change 70851 had a related patch set uploaded by Robmoen: +Make local overlays local to surface and remove insane z-indexes + +https://gerrit.wikimedia.org/r/70851",task_subcomment,['Change 70851 had a related patch set uploaded by Robmoen:\nMake local overlays local to surface and remove insane z-indexes\n\nGERRIT_URL'],['ACTION ON ISSUE'] +252924,"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Appears to be now fixed; marking as resolved. Thanks, Rob! :)",task_subcomment,"['Appears to be now fixed; marking as resolved.', 'Thanks, Rob!', ':)']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']" +252916,"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook",Rob's working on re-doing our z-indexes and inheritance right now.,task_subcomment,"[""Rob's working on re-doing our z-indexes and inheritance right now.""]",['WORKAROUNDS'] +252908,"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","(Firefox 21.0, Windows 7)",task_subcomment,"['(Firefox 21.0, Windows 7)']",['OBSERVED BUG BEHAVIOR'] +52159,"VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu","Screenshot + +I am unable to click ob the icon to open the image/caption dialog, see screenshot. Instead a cross to move the image is shown. + +-------------------------- +**Version**: unspecified +**Severity**: trivial + +**Attached**: {F11665}",task_description,"['VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu\n\nScreenshot\n\nI am unable to click ob the icon to open the image/caption dialog, see screenshot.', 'Instead a cross to move the image is shown.', '--------------------------\n**Version**: unspecified\n**Severity**: trivial\n\n**Attached**: {F11665}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +248247,"VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu",Fixed and will be going out in a few minutes.,task_subcomment,['Fixed and will be going out in a few minutes.'],['SOLUTION USAGE'] +248241,"VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu","Change 70859 merged by jenkins-bot: +Local Overlay Stacks + +https://gerrit.wikimedia.org/r/70859",task_subcomment,['Change 70859 merged by jenkins-bot:\nLocal Overlay Stacks\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +248233,"VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu","Change 70859 had a related patch set uploaded by Jforrester: +Local Overlay Stacks + +https://gerrit.wikimedia.org/r/70859",task_subcomment,['Change 70859 had a related patch set uploaded by Jforrester:\nLocal Overlay Stacks\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +248226,"VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu",Also in Safari 6 for me.,task_subcomment,['Also in Safari 6 for me.'],['OBSERVED BUG BEHAVIOR'] +248219,"VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu",I confirm this in Firefox 21 on enwp.,task_subcomment,['I confirm this in Firefox 21 on enwp.'],['OBSERVED BUG BEHAVIOR'] +52140,VisualEditor: Link inspector creates the text twice if not running on a selection,"When using the control/command+k shortcut, and manually typing the text of the desired page to be linked, duplicate links are produced. See http://en.wikipedia.org/w/index.php?title=User:PEarley_%28WMF%29/sandbox&diff=prev&oldid=561424914 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Link inspector creates the text twice if not running on a selection\n\nWhen using the control/command+k shortcut, and manually typing the text of the desired page to be linked, duplicate links are produced.', 'See URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +247267,VisualEditor: Link inspector creates the text twice if not running on a selection,"(In reply to comment #5) +> Great! Thanks for the quick response, James and team! + +Our pleasure; sorry it happened in the first place.",task_subcomment,['(In reply to comment #5)\nQUOTE\n\nOur pleasure; sorry it happened in the first place.'],['ACTION ON ISSUE'] +247261,VisualEditor: Link inspector creates the text twice if not running on a selection,"Great! Thanks for the quick response, James and team!",task_subcomment,"['Great!', 'Thanks for the quick response, James and team!']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +247255,VisualEditor: Link inspector creates the text twice if not running on a selection,Fixed and being deployed right now.,task_subcomment,['Fixed and being deployed right now.'],['ACTION ON ISSUE'] +247249,VisualEditor: Link inspector creates the text twice if not running on a selection,Related URL: https://gerrit.wikimedia.org/r/70623 (Gerrit Change I8c68468a95cddbc7efb222cf3a1f9868b2949285),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I8c68468a95cddbc7efb222cf3a1f9868b2949285)'],['OBSERVED BUG BEHAVIOR'] +247242,VisualEditor: Link inspector creates the text twice if not running on a selection,*** Bug 50188 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50188 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +247238,VisualEditor: Link inspector creates the text twice if not running on a selection,Confirmed - happens whenever you use the link inspector on a non-selection (slug or otherwise). Ed?,task_subcomment,"['Confirmed - happens whenever you use the link inspector on a non-selection (slug or otherwise).', 'Ed?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +52129,VisualEditor: Transclusions not properly round-tripped,"When doing a simple test edit on https://en.wikipedia.org/wiki/Chloroplast?veaction=edit and then previewing the diff, several transclusions of the form {{expand section|..}} show up with dirty diffs. This is very likely a DOM corruption in the VE that disables selective serialization. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://en.wikipedia.org/wiki/Chloroplast?veaction=edit +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50070",task_description,"['VisualEditor: Transclusions not properly round-tripped\n\nWhen doing a simple test edit on URL and then previewing the diff, several transclusions of the form {{expand section|..}} show up with dirty diffs.', 'This is very likely a DOM corruption in the VE that disables selective serialization.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +246566,VisualEditor: Transclusions not properly round-tripped,"I don't see the Dub Jones issue any more, so that appears to be fixed. + +There was also an independent Parsoid issue that resulted in incomplete DSR on transclusions, which is now also fixed. + +If you don't see this issue any more then this bug can be closed as fixed.",task_subcomment,"[""I don't see the Dub Jones issue any more, so that appears to be fixed."", 'There was also an independent Parsoid issue that resulted in incomplete DSR on transclusions, which is now also fixed.', ""If you don't see this issue any more then this bug can be closed as fixed.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +246560,VisualEditor: Transclusions not properly round-tripped,"(In reply to comment #7) +> Another case: +> https://en.wikipedia.org/w/index. +> php?title=Dub_Jones_%28American_football%29&curid=5240085&diff=561834911&oldi +> d=561833425 +WFM when I tried to reproduce at http://en.wikipedia.org/wiki/User:Catrope/Dub_Jones?veaction=edit . VE's sanity check says the DOM is clean. I believe these failures are due to cached content or some sort of bug in Parsoid/selser.",task_subcomment,"['(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nWFM when I tried to reproduce at URL .', ""VE's sanity check says the DOM is clean."", 'I believe these failures are due to cached content or some sort of bug in Parsoid/selser.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +246552,VisualEditor: Transclusions not properly round-tripped,"Another case: +https://en.wikipedia.org/w/index.php?title=Dub_Jones_%28American_football%29&curid=5240085&diff=561834911&oldid=561833425",task_subcomment,['Another case:\nURL'],['OBSERVED BUG BEHAVIOR'] +246544,VisualEditor: Transclusions not properly round-tripped,"Another example where an unmodified template was dirtied: + +https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FGNoSR&diff=561782383&oldid=561781680 + +Since our DOM diff is so simple I have a lot of faith in it. Did you diff the template DOM fragment after making an unrelated change?",task_subcomment,"['Another example where an unmodified template was dirtied:\n\nURL\n\nSince our DOM diff is so simple I have a lot of faith in it.', 'Did you diff the template DOM fragment after making an unrelated change?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +246537,VisualEditor: Transclusions not properly round-tripped,"(In reply to comment #4) +> At least one {{expand section|..}} transclusion still dirty-diffs. +> +> This will soon not show up as a diff any more because we improved our native +> serialization, but it seems that the VE still dirties the transclusion, which +> needs to be fixed. +It doesn't seem to be dirtied by VE directly. On [[Chloroplast]], I get a clean diff if I don't make any changes, but a dirty diff if I make any change at all. This leads me to suspect a selser / DOMDiffer bug. + +Will try to produce a minimal test case and investigate from there.",task_subcomment,"[""(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nIt doesn't seem to be dirtied by VE directly."", ""On [[Chloroplast]], I get a clean diff if I don't make any changes, but a dirty diff if I make any change at all."", 'This leads me to suspect a selser / DOMDiffer bug.', 'Will try to produce a minimal test case and investigate from there.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +246529,VisualEditor: Transclusions not properly round-tripped,"At least one {{expand section|..}} transclusion still dirty-diffs. + +This will soon not show up as a diff any more because we improved our native serialization, but it seems that the VE still dirties the transclusion, which needs to be fixed.",task_subcomment,"['At least one {{expand section|..}} transclusion still dirty-diffs.', 'This will soon not show up as a diff any more because we improved our native serialization, but it seems that the VE still dirties the transclusion, which needs to be fixed.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +246522,VisualEditor: Transclusions not properly round-tripped," + +*** This bug has been marked as a duplicate of bug 50070 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50070 ***'],['ISSUE CONTENT MANAGEMENT'] +246515,VisualEditor: Transclusions not properly round-tripped,The nowiki escaping in Schuylar_Oordt is Parsoid bug 50144. It would normally be hidden with selective serialization.,task_subcomment,"['The nowiki escaping in Schuylar_Oordt is Parsoid bug 50144.', 'It would normally be hidden with selective serialization.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +246508,VisualEditor: Transclusions not properly round-tripped,"Some more examples from https://en.wikipedia.org/w/index.php?namespace=&tagfilter=visualeditor&title=Special%3ARecentChanges: + +https://en.wikipedia.org/w/index.php?title=Eugenio_Fojo&curid=33949576&diff=561434486&oldid=561304103 +https://en.wikipedia.org/w/index.php?title=Schuylar_Oordt&curid=37614262&diff=561438828&oldid=561406705",task_subcomment,['Some more examples from URL\n\nURL\nURL'],['OBSERVED BUG BEHAVIOR'] +52120,Categories/default sort sometimes duplicated to random position in DOM after edit,"https://en.wikipedia.org/w/index.php?title=Dina_bint_%27Abdu%27l-Hamid&diff=561398396&oldid=561397974 + +I added a single letter (""therafter"" --> ""thereafter""). VisualEditor duplicated the categories and the default sort. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50385 +https://bugzilla.wikimedia.org/show_bug.cgi?id=50332 +https://bugzilla.wikimedia.org/show_bug.cgi?id=54169",task_description,"['Categories/default sort sometimes duplicated to random position in DOM after edit\n\nURL\n\nI added a single letter (""therafter"" --> ""thereafter"").', 'VisualEditor duplicated the categories and the default sort.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +245935,Categories/default sort sometimes duplicated to random position in DOM after edit,"The Parsoid fix is deployed. The P-wrapping portion is verified fixed on our test case [[Tim_Gartrell]]. + +The VE newline migration should be tracked in a different bug. Closing this bug as fixed.",task_subcomment,"['The Parsoid fix is deployed.', 'The P-wrapping portion is verified fixed on our test case [[Tim_Gartrell]].', 'The VE newline migration should be tracked in a different bug.', 'Closing this bug as fixed.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'ACTION ON ISSUE']" +245932,Categories/default sort sometimes duplicated to random position in DOM after edit,"Change 73113 merged by jenkins-bot: +Bug 50120: Avoid paragraph wrapping for DOM fragments with blocks + +https://gerrit.wikimedia.org/r/73113",task_subcomment,['Change 73113 merged by jenkins-bot:\nBug 50120: Avoid paragraph wrapping for DOM fragments with blocks\n\nGERRIT_URL'],['BUG REPRODUCTION'] +245929,Categories/default sort sometimes duplicated to random position in DOM after edit,"Change 73113 had a related patch set uploaded by GWicke: +Bug 50120: Avoid paragraph wrapping for DOM fragments with blocks + +https://gerrit.wikimedia.org/r/73113",task_subcomment,['Change 73113 had a related patch set uploaded by GWicke:\nBug 50120: Avoid paragraph wrapping for DOM fragments with blocks\n\nGERRIT_URL'],['BUG REPRODUCTION'] +245926,Categories/default sort sometimes duplicated to random position in DOM after edit,"Subbu, Gabriel and I figured this out on IRC, and Subbu and Gabriel are working on a fix. Summary for the benefit of those following this bug: + +* On the first parse (either upon first VE load after the cache is purged, or upon the first edit after the purge), Parsoid parses the PERSONDATA template from scratch (because there is no cached content to reuse) and does so correctly. The output is something like \n...
+* On the second parse, (first or second edit after cache purge), Parsoid reuses the template expansion from the first parse. It notices that the first (span) and last (link) nodes are both inline, and so it assumes the entire template is inline and wraps it in a

+* The browser receives this HTML and is unhappy about the inside the

, so it moves both the

and the out of the

, leaving

\n

...
. Because the table is not a sibling of the span, VE doesn't recognize the table (or the link) as part of the template. Due to a separate bug in VE, the newline after the link is moved and ends up between the table and the link. +* VE sends this corrupted HTML back to Parsoid, which freaks out and duplicates the table as well as a bunch of categories. +* After the page is edited again (possibly by the user saving the corrupted VE output, possibly some other way), the third parse occurs, and Parsoid again tries to reuse the previous parse's expansion of the template. However, because of the

interruption, it only sees the span and doesn't see the table or the link. The table and the link disappear from the output in this and all subsequent parses, masking the bug. The user doesn't notice because the table has style=""display:none;""",task_subcomment,"['Subbu, Gabriel and I figured this out on IRC, and Subbu and Gabriel are working on a fix.', 'Summary for the benefit of those following this bug:\n\n* On the first parse (either upon first VE load after the cache is purged, or upon the first edit after the purge), Parsoid parses the PERSONDATA template from scratch (because there is no cached content to reuse) and does so correctly.', 'The output is something like \\n...
\n* On the second parse, (first or second edit after cache purge), Parsoid reuses the template expansion from the first parse.', 'It notices that the first (span) and last (link) nodes are both inline, and so it assumes the entire template is inline and wraps it in a

\n* The browser receives this HTML and is unhappy about the inside the

, so it moves both the

and the out of the

, leaving

\\n

...
.', ""Because the table is not a sibling of the span, VE doesn't recognize the table (or the link) as part of the template."", 'Due to a separate bug in VE, the newline after the link is moved and ends up between the table and the link.', '* VE sends this corrupted HTML back to Parsoid, which freaks out and duplicates the table as well as a bunch of categories.', ""* After the page is edited again (possibly by the user saving the corrupted VE output, possibly some other way), the third parse occurs, and Parsoid again tries to reuse the previous parse's expansion of the template."", ""However, because of the

interruption, it only sees the span and doesn't see the table or the link."", 'The table and the link disappear from the output in this and all subsequent parses, masking the bug.', 'The user doesn\'t notice because the table has style=""display:none;""']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245920,Categories/default sort sometimes duplicated to random position in DOM after edit,https://en.wikipedia.org/w/index.php?title=Tim_Gartrell&curid=1659124&diff=563696826&oldid=563696785,task_subcomment,['URL'],['SOLUTION DISCUSSION'] +245911,Categories/default sort sometimes duplicated to random position in DOM after edit,*** Bug 50554 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50554 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245904,Categories/default sort sometimes duplicated to random position in DOM after edit,"See also: bug 50554, bug 50385.",task_subcomment,"['See also: bug 50554, bug 50385.']",['OBSERVED BUG BEHAVIOR'] +245897,Categories/default sort sometimes duplicated to random position in DOM after edit,"Another case: +https://en.wikipedia.org/w/index.php?title=Frederick_Calvert,_6th_Baron_Baltimore&curid=884173&diff=563705563&oldid=563705411 + +Also updated the subject and moved to VE.",task_subcomment,['Another case:\nURL\n\nAlso updated the subject and moved to VE.'],['SOLUTION DISCUSSION'] +245890,Categories/default sort sometimes duplicated to random position in DOM after edit,"That's really strange. The template is one unit in the VE data model, so if tags are placed in the middle of it that must be a bug in the data model -> HTML conversion, not in the data model itself.",task_subcomment,"[""That's really strange."", 'The template is one unit in the VE data model, so if tags are placed in the middle of it that must be a bug in the data model -> HTML conversion, not in the data model itself.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245884,Categories/default sort sometimes duplicated to random position in DOM after edit,"(In reply to comment #15) +> So, there may also be a Parsoid issue here about how such templates are +> parsed. + +As long as the content (including ws-only spans) is properly encapsulated that should not be relevant for this corruption. + +I have seen VE move categories to random places in the DOM before. Apparently that bug is still alive. And hard to reproduce, sadly.",task_subcomment,"['(In reply to comment #15)\nQUOTE\nQUOTE\n\nAs long as the content (including ws-only spans) is properly encapsulated that should not be relevant for this corruption.', 'I have seen VE move categories to random places in the DOM before.', 'Apparently that bug is still alive.', 'And hard to reproduce, sadly.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245878,Categories/default sort sometimes duplicated to random position in DOM after edit,Possibly related: bug 50332.,task_subcomment,['Possibly related: bug 50332.'],['MOTIVATION'] +245873,Categories/default sort sometimes duplicated to random position in DOM after edit,"And, I misspoke. The spans from the template before/after the table are not really ""empty"" -- they have whitespace. And, the more interesting thing is that these spans do not get the display:none; css style but the table gets it from the style on the table ==> the spans are technically visible (with whitespace ignored in the browser) in VE, but the table is not. + +So, there may also be a Parsoid issue here about how such templates are parsed.",task_subcomment,"['And, I misspoke.', 'The spans from the template before/after the table are not really ""empty"" -- they have whitespace.', 'And, the more interesting thing is that these spans do not get the display:none; css style but the table gets it from the style on the table ==> the spans are technically visible (with whitespace ignored in the browser) in VE, but the table is not.', 'So, there may also be a Parsoid issue here about how such templates are parsed.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245868,Categories/default sort sometimes duplicated to random position in DOM after edit,"This may be a VE bug (unconfirmed). Here is what I did. + +I parsed mw:Jayaprakash Narayan on my local parsoid install and saved the HTML. +I then added a (a new category essentially mimicking editor behavior), but I added it between the empty span that marks the opening of the Persondata tmeplate and the that is part of the template. This effectively splits the template and duplicates the rest of the template. + +If you look at the diff in https://en.wikipedia.org/w/index.php?title=Jayaprakash_Narayan&diff=563627722&oldid=563627392, all the categories are between the end of the template and the table. The above experiment yielded something similar, except in the diff, all categories are moved up. + +So, it does seem that when a user adds categories, new/old categories are being moved/inserted between the empty span and the table breaking the atomic encapsulated template into two. + +Also note that this only seems to affect Persondata template +* in original wikitext, default sort template immediately follows the persondata template. +* it has an empty span before/after the table +* it has display:none set on it which means it doesn't show up in the editor. + +Not sure if cursor position affects where categories are inserted. Can VE folks verify this hypothesis?",task_subcomment,"['This may be a VE bug (unconfirmed).', 'Here is what I did.', 'I parsed mw:Jayaprakash Narayan on my local parsoid install and saved the HTML.', 'I then added a (a new category essentially mimicking editor behavior), but I added it between the empty span that marks the opening of the Persondata tmeplate and the
that is part of the template.', 'This effectively splits the template and duplicates the rest of the template.', 'If you look at the diff in URL all the categories are between the end of the template and the table.', 'The above experiment yielded something similar, except in the diff, all categories are moved up.', 'So, it does seem that when a user adds categories, new/old categories are being moved/inserted between the empty span and the table breaking the atomic encapsulated template into two.', 'Also note that this only seems to affect Persondata template \n* in original wikitext, default sort template immediately follows the persondata template.', ""* it has an empty span before/after the table\n* it has display:none set on it which means it doesn't show up in the editor."", 'Not sure if cursor position affects where categories are inserted.', 'Can VE folks verify this hypothesis?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245862,Categories/default sort sometimes duplicated to random position in DOM after edit,"Couple more: +https://en.wikipedia.org/w/index.php?title=Peter_Biddle&diff=563624872&oldid=563623995 +https://en.wikipedia.org/w/index.php?title=Jayaprakash_Narayan&diff=563627722&oldid=563627392 + +Based on inspection of recent diffs, I'd call this the single most prevalent and most problematic content corruption issue at this point.",task_subcomment,"[""Couple more:\nURL\nURL\n\nBased on inspection of recent diffs, I'd call this the single most prevalent and most problematic content corruption issue at this point.""]",['OBSERVED BUG BEHAVIOR'] +245856,Categories/default sort sometimes duplicated to random position in DOM after edit,Note the additional table screw-up in that one. We may need some cross-browser hammering on those revs to see if it's a browser-specific issue.,task_subcomment,"['Note the additional table screw-up in that one.', ""We may need some cross-browser hammering on those revs to see if it's a browser-specific issue.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245852,Categories/default sort sometimes duplicated to random position in DOM after edit,"Another one: +https://en.wikipedia.org/w/index.php?title=Rick_DePiro&curid=29139774&diff=563628155&oldid=560712931",task_subcomment,['Another one:\nURL'],['OBSERVED BUG BEHAVIOR'] +245847,Categories/default sort sometimes duplicated to random position in DOM after edit,"Nope, still occurring. +https://en.wikipedia.org/w/index.php?title=Ma_Huateng&curid=6152047&diff=563628488&oldid=555028382",task_subcomment,"['Nope, still occurring.', 'URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +245840,Categories/default sort sometimes duplicated to random position in DOM after edit,"https://en.wikipedia.org/w/index.php?title=Mat_Devine&curid=28997812&diff=563130933&oldid=563130533 looks like a VE bug to me. I can't reproduce it any more (similar to the case in bug 50853), so I am guessing that something in last night's VE deploy fixed this. + +Closing as fixed, please reopen if this still happens.",task_subcomment,"['URL looks like a VE bug to me.', ""I can't reproduce it any more (similar to the case in bug 50853), so I am guessing that something in last night's VE deploy fixed this."", 'Closing as fixed, please reopen if this still happens.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'ACTION ON ISSUE']" +245836,Categories/default sort sometimes duplicated to random position in DOM after edit,This may be related to bug 50853 which gabriel is going to be investigating to day.,task_subcomment,['This may be related to bug 50853 which gabriel is going to be investigating to day.'],['OBSERVED BUG BEHAVIOR'] +245830,Categories/default sort sometimes duplicated to random position in DOM after edit,"Is this a Parsoid DSR issue? Content getting repeated in this way (especially, the substituted template) is hard to see occurring in VisualEditor.",task_subcomment,"['Is this a Parsoid DSR issue?', 'Content getting repeated in this way (especially, the substituted template) is hard to see occurring in VisualEditor.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245826,Categories/default sort sometimes duplicated to random position in DOM after edit,"This is still occurring. Most recent example from a few minutes ago: + +https://en.wikipedia.org/w/index.php?title=Mat_Devine&curid=28997812&diff=563130933&oldid=563130533",task_subcomment,"['This is still occurring.', 'Most recent example from a few minutes ago:\n\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245819,Categories/default sort sometimes duplicated to random position in DOM after edit,We believe that this is now fixed (due to fixes in Parsoid). Please re-open if it recurs.,task_subcomment,"['We believe that this is now fixed (due to fixes in Parsoid).', 'Please re-open if it recurs.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +245813,Categories/default sort sometimes duplicated to random position in DOM after edit,https://en.wikipedia.org/w/index.php?title=Miloslav_Ransdorf&curid=1478506&diff=561858255&oldid=561857291 to boot.,task_subcomment,['URL to boot.'],['SOLUTION DISCUSSION'] +245807,Categories/default sort sometimes duplicated to random position in DOM after edit,"Roan, thoughts?",task_subcomment,"['Roan, thoughts?']",['SOLUTION DISCUSSION'] +245802,Categories/default sort sometimes duplicated to random position in DOM after edit,https://en.wikipedia.org/w/index.php?title=Richard_Ned_Lebow&diff=561410319&oldid=561410032,task_subcomment,['URL'],['SOLUTION DISCUSSION'] +245796,Categories/default sort sometimes duplicated to random position in DOM after edit,"Perhaps related to: + +| PLACE OF BIRTH =[Alexandria], [[Egypt]]",task_subcomment,"['Perhaps related to:\n\n| PLACE OF BIRTH =[Alexandria], [[Egypt]]']",['OBSERVED BUG BEHAVIOR'] +52115,VisualEditor: Link editor does not work in the reference editor in Firefox,"Self-explanatory; Firefox 21.0, Windows 7. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor: Link editor does not work in the reference editor in Firefox\n\nSelf-explanatory; Firefox 21.0, Windows 7.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +245554,VisualEditor: Link editor does not work in the reference editor in Firefox,Fixed and will be going out in a few minutes.,task_subcomment,['Fixed and will be going out in a few minutes.'],['SOLUTION USAGE'] +245548,VisualEditor: Link editor does not work in the reference editor in Firefox,Patched in: https://gerrit.wikimedia.org/r/#/c/70559/,task_subcomment,['Patched in: URL'],['SOLUTION DISCUSSION'] +52110,VisualEditor: Provide way for local wikis to auto-prompt reference templates,"Not sure if this is something that's been nixed and nobody has told me, but: tracking bug for adding cite template support to the VE's referencing setup. They're pretty universally useful. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50768",task_description,"[""VisualEditor: Provide way for local wikis to auto-prompt reference templates\n\nNot sure if this is something that's been nixed and nobody has told me, but: tracking bug for adding cite template support to the VE's referencing setup."", ""They're pretty universally useful."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']" +245203,VisualEditor: Provide way for local wikis to auto-prompt reference templates,"Change 119913 merged by jenkins-bot: +Ultra-mega-hyper-citation editing on crack + +https://gerrit.wikimedia.org/r/119913",task_subcomment,['Change 119913 merged by jenkins-bot:\nUltra-mega-hyper-citation editing on crack\n\nGERRIT_URL'],['ACTION ON ISSUE'] +245199,VisualEditor: Provide way for local wikis to auto-prompt reference templates,"Change 119913 had a related patch set uploaded by Jforrester: +Ultra-mega-hyper-citation editing on crack + +https://gerrit.wikimedia.org/r/119913",task_subcomment,['Change 119913 had a related patch set uploaded by Jforrester:\nUltra-mega-hyper-citation editing on crack\n\nGERRIT_URL'],['ACTION ON ISSUE'] +245195,VisualEditor: Provide way for local wikis to auto-prompt reference templates,*** Bug 51185 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51185 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245189,VisualEditor: Provide way for local wikis to auto-prompt reference templates,"(In reply to comment #2) +> For clarification: I'll assume that this is about what you put _inside_ the +> tags and not about templates that add the tags themselves. + +Correct.",task_subcomment,['(In reply to comment #2)\nQUOTE\nQUOTE\n\nCorrect.'],['SOLUTION DISCUSSION'] +245183,VisualEditor: Provide way for local wikis to auto-prompt reference templates,For clarification: I'll assume that this is about what you put _inside_ the tags and not about templates that add the tags themselves.,task_subcomment,"[""For clarification: I'll assume that this is about what you put _inside_ the tags and not about templates that add the tags themselves.""]",['INVESTIGATION AND EXPLORATION'] +245176,VisualEditor: Provide way for local wikis to auto-prompt reference templates,*** Bug 51683 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51683 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +52073,VisualEditor: Template-based references never editable from reference editor in Firefox,"Screenshot + +See screenshot. Kiiinda worrying - if this is something a group of people > me is seeing it may be a blocker. + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: https://en.wikipedia.org/wiki/Joe_Flacco?veaction=edit + +**Attached**: {F11445}",task_description,"['VisualEditor: Template-based references never editable from reference editor in Firefox\n\nScreenshot\n\nSee screenshot.', 'Kiiinda worrying - if this is something a group of people > me is seeing it may be a blocker.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**URL**: URL\n\n**Attached**: {F11445}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +242932,VisualEditor: Template-based references never editable from reference editor in Firefox,Related URL: https://gerrit.wikimedia.org/r/70119 (Gerrit Change I29e210aba9a6265d8364ff8ae49408cb4c2428b9),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I29e210aba9a6265d8364ff8ae49408cb4c2428b9)'],['OBSERVED BUG BEHAVIOR'] +242925,VisualEditor: Template-based references never editable from reference editor in Firefox,Confirmed by a second user.,task_subcomment,['Confirmed by a second user.'],['OBSERVED BUG BEHAVIOR'] +52067,"VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving"," + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]",['INVESTIGATION AND EXPLORATION'] +242549,"VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving",Written and about to be deployed.,task_subcomment,['Written and about to be deployed.'],['INVESTIGATION AND EXPLORATION'] +242544,"VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving","Change 70106 merged by jenkins-bot: +mw.ViewPageTarget: Add sanity check for DOM roundtrip + +https://gerrit.wikimedia.org/r/70106",task_subcomment,['Change 70106 merged by jenkins-bot:\nmw.ViewPageTarget: Add sanity check for DOM roundtrip\n\nGERRIT_URL'],['ACTION ON ISSUE'] +242541,"VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving",Related URL: https://gerrit.wikimedia.org/r/70106 (Gerrit Change I04f71fe8e00c6257fbc953cc9de3323e24709b0f),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I04f71fe8e00c6257fbc953cc9de3323e24709b0f)'],['OBSERVED BUG BEHAVIOR'] +52059,VisualEditor: Metadata not preserved in references,"They get stripped out when rendered back to HTML. + +e.g. + +Foo + +-> + +Foo + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Metadata not preserved in references\n\nThey get stripped out when rendered back to HTML.', 'e.g.', 'Foo\n\n->\n\nFoo\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +242101,VisualEditor: Metadata not preserved in references,Related URL: https://gerrit.wikimedia.org/r/70060 (Gerrit Change I3bbea49132ef4a720a147ba9b170c39a0c00f711),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I3bbea49132ef4a720a147ba9b170c39a0c00f711)'],['OBSERVED BUG BEHAVIOR'] +52050,VisualEditor: Inline text style annotations with different attributes should not be merged,"Moved from #48830. + +Merlijn van Deen 2013-06-23 11:20:36 UTC +---------------------------------------- +https://www.mediawiki.org/w/index.php?title=Git%2FConversion%2Fpywikipedia&diff=714194&oldid=713893 +The only real edit is at the bottom. + +Krinkle 2013-06-23 11:25:31 UTC +------------------------------- +This is due to the merging of the 2 tags. Currently it fails compare custom +attributes like ""style"" when attempting to merge equal annotation sequences. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=48830",task_description,"['VisualEditor: Inline text style annotations with different attributes should not be merged\n\nMoved from #48830.', 'Merlijn van Deen 2013-06-23 11:20:36 UTC\n----------------------------------------\nURL\nThe only real edit is at the bottom.', 'Krinkle 2013-06-23 11:25:31 UTC\n-------------------------------\nThis is due to the merging of the 2 tags.', 'Currently it fails compare custom\nattributes like ""style"" when attempting to merge equal annotation sequences.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +241658,VisualEditor: Inline text style annotations with different attributes should not be merged,"We have a work around for this - gerrit 69852 - now in production in VisualEditor, but the underlying cause is bug 48194. I've manually fixed the changes VE made - sorry about that: https://www.mediawiki.org/w/index.php?title=Git/Conversion/pywikipedia&diff=715751&oldid=715067",task_subcomment,"['We have a work around for this - gerrit 69852 - now in production in VisualEditor, but the underlying cause is bug 48194.', ""I've manually fixed the changes VE made - sorry about that: URL""]","['WORKAROUNDS', 'SOLUTION DISCUSSION']" +51993,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","This doesn't work; not quite sure why/how. Should be fixed. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow\n\nThis doesn\'t work; not quite sure why/how.', 'Should be fixed.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']" +238346,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow",Fix merged and will hopefully go out soon.,task_subcomment,['Fix merged and will hopefully go out soon.'],['ACTION ON ISSUE'] +238340,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","Change 72069 merged by jenkins-bot: +mw.ViewPageTarget.init: Move edit section to top init + +https://gerrit.wikimedia.org/r/72069",task_subcomment,['Change 72069 merged by jenkins-bot:\nmw.ViewPageTarget.init: Move edit section to top init\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +238334,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","Change 72069 had a related patch set uploaded by Jforrester: +mw.ViewPageTarget.init: Move edit section to top init. + +https://gerrit.wikimedia.org/r/72069",task_subcomment,"['Change 72069 had a related patch set uploaded by Jforrester:\nmw.ViewPageTarget.init: Move edit section to top init.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +238328,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","Gah, bad breakage related to making VE more lightweight - sorry about that. Gerrit 72069 fixes this, according to my local testing - we'll try to get this out today.",task_subcomment,"['Gah, bad breakage related to making VE more lightweight - sorry about that.', ""Gerrit 72069 fixes this, according to my local testing - we'll try to get this out today.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +238322,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","My testing shows that ctrl+click works only in VE-enabled namespaces but middle click works everywhere in Firefox 22. + +In Konqueror 4.8.5 (which is apparently not enabled for VE) both ctrl+click and middle click both work only in VE-enabled namespaces.",task_subcomment,"['My testing shows that ctrl+click works only in VE-enabled namespaces but middle click works everywhere in Firefox 22.', 'In Konqueror 4.8.5 (which is apparently not enabled for VE) both ctrl+click and middle click both work only in VE-enabled namespaces.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238317,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","I'm not sure how the fix was implemented, but it seems to have started occurring again - this time only in namespaces in which the VE isn't active.",task_subcomment,"[""I'm not sure how the fix was implemented, but it seems to have started occurring again - this time only in namespaces in which the VE isn't active.""]",['OBSERVED BUG BEHAVIOR'] +238312,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow",Related URL: https://gerrit.wikimedia.org/r/70773 (Gerrit Change I5245ab19ae16b79d2c562c05b94649a58e04a4fd),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I5245ab19ae16b79d2c562c05b94649a58e04a4fd)'],['OBSERVED BUG BEHAVIOR'] +238307,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow",Fixed in gerrit 70735 which is now merged and will get pushed later today.,task_subcomment,['Fixed in gerrit 70735 which is now merged and will get pushed later today.'],['SOLUTION USAGE'] +238303,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","Raising importance, this is quite annoying. It's just been reported on [[WP:VPT]] for the second time today.",task_subcomment,"['Raising importance, this is quite annoying.', ""It's just been reported on [[WP:VPT]] for the second time today.""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +238298,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow",*** Bug 50221 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50221 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238291,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow","**pinkampersand.wikimedia** wrote: + +I should note that I've been having this bug (well, with ctrl-click on my laptop, but think that's the same thing), and I don't have VE enabled. However, this bug's several days old, and I'm pretty sure this has only been happening to me within the past hour. Chrome on a ChromeOS netbook.",task_subcomment,"[""**pinkampersand.wikimedia** wrote:\n\nI should note that I've been having this bug (well, with ctrl-click on my laptop, but think that's the same thing), and I don't have VE enabled."", ""However, this bug's several days old, and I'm pretty sure this has only been happening to me within the past hour."", 'Chrome on a ChromeOS netbook.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238287,"VisualEditor: Opening ""Edit"" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow",Some back-of-the-envelope work by users indicates that firefox (logged in) and chromium (logged out) on linux have this problem; firefox and IE on Windows (not logged in) do not.,task_subcomment,['Some back-of-the-envelope work by users indicates that firefox (logged in) and chromium (logged out) on linux have this problem; firefox and IE on Windows (not logged in) do not.'],['OBSERVED BUG BEHAVIOR'] +51985,"VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin","Steps to reproduce: +1. Insert the cursor immediately after the first letter of a link +2. Hit delete/backspace +3. Type a new character +4. The new character isn't part of the link, so select the entire word and click the link button +5. Re-enter the link article +6. Save your changes + +Expected result: +If you started with ""[[Porcupine]]"", you should end up with ""[[porcupine]]"". + +Actual result: +If you started with ""[[Porcupine]]"", you end up with ""[[porcupine|p]][[Porcupine|orcupine]]"". + +This is just a common use case demonstrating a more general bug. Namely, if you create a new link that subsumes an existing link, the existing link is preserved within the new link instead of being replaced. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50098",task_description,"['VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin\n\nSteps to reproduce:\n1.', 'Insert the cursor immediately after the first letter of a link\n2.', 'Hit delete/backspace\n3.', 'Type a new character\n4.', ""The new character isn't part of the link, so select the entire word and click the link button\n5."", 'Re-enter the link article\n6.', 'Save your changes\n\nExpected result:\nIf you started with ""[[Porcupine]]"", you should end up with ""[[porcupine]]"".', 'Actual result:\nIf you started with ""[[Porcupine]]"", you end up with ""[[porcupine|p]][[Porcupine|orcupine]]"".', 'This is just a common use case demonstrating a more general bug.', 'Namely, if you create a new link that subsumes an existing link, the existing link is preserved within the new link instead of being replaced.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +237949,"VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin","(In reply to comment #5) +> Change 70633 merged by jenkins-bot: +> Fix comparison of MW internal links +> +> https://gerrit.wikimedia.org/r/70633 + +And with that change, this bug is fixed; closing. It will be deployed this afternoon.",task_subcomment,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAnd with that change, this bug is fixed; closing.', 'It will be deployed this afternoon.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +237941,"VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin","Change 70633 merged by jenkins-bot: +Fix comparison of MW internal links + +https://gerrit.wikimedia.org/r/70633",task_subcomment,['Change 70633 merged by jenkins-bot:\nFix comparison of MW internal links\n\nGERRIT_URL'],['ACTION ON ISSUE'] +237935,"VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin",Related URL: https://gerrit.wikimedia.org/r/70633 (Gerrit Change I5fb5bfc69c344ca4ce4803d7b6116074648a8d7e),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I5fb5bfc69c344ca4ce4803d7b6116074648a8d7e)'],['OBSERVED BUG BEHAVIOR'] +237929,"VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin","There are two issues here. + +First off, we should change getComparableObject() for MWInternalLinkAnnotation to normalize the title and possibly tweak other things to the point where links to the same title are comparable, even if they have different capitalizations or space-vs-underscore variants of that title. That will be both more semantically correct and serve as a workaround for this bug. + +Secondly, because we want to stop merging comparable but different annotations in the converter, we need Parsoid to correctly process at least things like porcupine (adjacent s with the same href) and possibly porcupine as well (adjacent s with different hrefs that normalize to the same title).",task_subcomment,"['There are two issues here.', 'First off, we should change getComparableObject() for MWInternalLinkAnnotation to normalize the title and possibly tweak other things to the point where links to the same title are comparable, even if they have different capitalizations or space-vs-underscore variants of that title.', 'That will be both more semantically correct and serve as a workaround for this bug.', 'Secondly, because we want to stop merging comparable but different annotations in the converter, we need Parsoid to correctly process at least things like porcupine (adjacent s with the same href) and possibly porcupine as well (adjacent s with different hrefs that normalize to the same title).']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +237922,"VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin","Similar but different. This case should definitely be fixed in VE, not Parsoid.",task_subcomment,"['Similar but different.', 'This case should definitely be fixed in VE, not Parsoid.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +237916,"VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin","Ed, is this due to the DM stuff around adjacent annotations?",task_subcomment,"['Ed, is this due to the DM stuff around adjacent annotations?']",['OBSERVED BUG BEHAVIOR'] +51846,mediawiki/extensions.git does not update some extensions,"http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version shows that the version of VisualEditor on beta labs is from May 28. The version of Parsoid on beta labs shows no date. + +It would be convenient to have VE/Parsoid available on beta labs as well as on test2wiki and mediawiki.org + +-------------------------- +**Version**: unspecified +**Severity**: critical +**Whiteboard**: rmqa-2013",task_description,"['mediawiki/extensions.git does not update some extensions\n\nURL shows that the version of VisualEditor on beta labs is from May 28.', 'The version of Parsoid on beta labs shows no date.', 'It would be convenient to have VE/Parsoid available on beta labs as well as on test2wiki and mediawiki.org\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical\n**Whiteboard**: rmqa-2013']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +750449,mediawiki/extensions.git does not update some extensions,"Change 317923 merged by Dzahn: +contint: remove python-requests + +[[https://gerrit.wikimedia.org/r/317923]]",task_subcomment,['Change 317923 merged by Dzahn:\ncontint: remove python-requests\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +749667,mediawiki/extensions.git does not update some extensions,"Change 317923 had a related patch set uploaded (by Hashar): +contint: remove python-requests + +[[https://gerrit.wikimedia.org/r/317923]] +",task_subcomment,['Change 317923 had a related patch set uploaded (by Hashar):\ncontint: remove python-requests\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +730051,mediawiki/extensions.git does not update some extensions,"Change 311161 merged by Dzahn: +contint: drop now unused sudo rule + +[[https://gerrit.wikimedia.org/r/311161]]",task_subcomment,['Change 311161 merged by Dzahn:\ncontint: drop now unused sudo rule\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +730024,mediawiki/extensions.git does not update some extensions,"Change 311161 had a related patch set uploaded (by Hashar): +contint: drop now unused sudo rule + +[[https://gerrit.wikimedia.org/r/311161]] +",task_subcomment,['Change 311161 had a related patch set uploaded (by Hashar):\ncontint: drop now unused sudo rule\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +725520,mediawiki/extensions.git does not update some extensions,"Change 309275 merged by Giuseppe Lavagetto: +ci::master: drop mwext-sync leftover + +[[https://gerrit.wikimedia.org/r/309275]]",task_subcomment,['Change 309275 merged by Giuseppe Lavagetto:\nci::master: drop mwext-sync leftover\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +725137,mediawiki/extensions.git does not update some extensions,"Change 309272 merged by jenkins-bot: +Remove VE script to sync the Gerrit repo + +[[https://gerrit.wikimedia.org/r/309272]]",task_subcomment,['Change 309272 merged by jenkins-bot:\nRemove VE script to sync the Gerrit repo\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +724762,mediawiki/extensions.git does not update some extensions,"This is confirmed to have been fixed when we have upgraded to Gerrit 2.12. + +The workaround script and Jenkins job have been removed end of July, the recent changes I have sent above are merely for clean up.",task_subcomment,"['This is confirmed to have been fixed when we have upgraded to Gerrit 2.12.', 'The workaround script and Jenkins job have been removed end of July, the recent changes I have sent above are merely for clean up.']","['OBSERVED BUG BEHAVIOR', 'WORKAROUNDS']" +724761,mediawiki/extensions.git does not update some extensions,"Change 309275 had a related patch set uploaded (by Hashar): +ci::master: drop mwext-sync leftover + +[[https://gerrit.wikimedia.org/r/309275]] +",task_subcomment,['Change 309275 had a related patch set uploaded (by Hashar):\nci::master: drop mwext-sync leftover\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +724760,mediawiki/extensions.git does not update some extensions,"Change 309272 had a related patch set uploaded (by Hashar): +Remove VE script to sync the Gerrit repo + +[[https://gerrit.wikimedia.org/r/309272]] +",task_subcomment,['Change 309272 had a related patch set uploaded (by Hashar):\nRemove VE script to sync the Gerrit repo\n\n[[GERRIT_URL]]'],['GERRIT_URL'] +724758,mediawiki/extensions.git does not update some extensions,"{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVcJQJLzaH8PnNb4D6OE} [2016-09-08T10:03:29Z] Delete Jenkins job https://integration.wikimedia.org/ci/job/mwext-VisualEditor-sync-gerrit/ that has been left behind. It is no more needed. T51846 T86659",task_subcomment,"['{nav icon=file, name=Mentioned in SAL, href=URL [2016-09-08T10:03:29Z] Delete Jenkins job URL that has been left behind.', 'It is no more needed.', 'T51846 T86659']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +724755,mediawiki/extensions.git does not update some extensions,"{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVcJP0y9pirJUPGy-5YX} [2016-09-08T10:02:05Z] Delete mwext-VisualEditor-sync-gerrit job, already got removed by ostriches in 139d17c8f1c4bcf2bb761e13a6501e4d85684066 . The issue in Gerrit (T51846) has been fixed. Poke T86659 , one less job on slaves. ",task_subcomment,"['{nav icon=file, name=Mentioned in SAL, href=URL [2016-09-08T10:02:05Z] Delete mwext-VisualEditor-sync-gerrit job, already got removed by ostriches in 139d17c8f1c4bcf2bb761e13a6501e4d85684066 .', 'The issue in Gerrit (T51846) has been fixed.', 'Poke T86659 , one less job on slaves.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION']" +676263,mediawiki/extensions.git does not update some extensions,"Fixed in https://gerrit-review.googlesource.com/#/c/69891/ + +Upgrading to gerrit 2.12 which will happen soon will fix the problem.",task_subcomment,['Fixed in URL\n\nUpgrading to gerrit 2.12 which will happen soon will fix the problem.'],['SOLUTION DISCUSSION'] +604483,mediawiki/extensions.git does not update some extensions,Upstream bug is https://code.google.com/p/gerrit/issues/detail?id=2393,task_subcomment,['Upstream bug is URL'],['OBSERVED BUG BEHAVIOR'] +603339,mediawiki/extensions.git does not update some extensions,Same issue with `Cards` and `mediawiki/extensions/Cards` at T125182,task_subcomment,['Same issue with CODE and CODE at T125182'],['BUG REPRODUCTION'] +254342,mediawiki/extensions.git does not update some extensions,"After much madness, this is now fixed. I had to write a bunch of shell slave scripts to let us properly push the VE update change to mediawiki/extensions.git and self merge them. + +The job is: + + https://integration.wikimedia.org/ci/job/mwext-VisualEditor-sync-gerrit/ + +It managed to merge an update a few minutes ago: + + https://gerrit.wikimedia.org/r/#/c/109113/ + + +I guess the issue is fixed now. Sorry for the long time it took to get this fixed.",task_subcomment,"['After much madness, this is now fixed.', 'I had to write a bunch of shell slave scripts to let us properly push the VE update change to mediawiki/extensions.git and self merge them.', 'The job is:\n\n URL\n\nIt managed to merge an update a few minutes ago:\n\n URL\n\n\nI guess the issue is fixed now.', 'Sorry for the long time it took to get this fixed.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +254337,mediawiki/extensions.git does not update some extensions,"Change 108837 merged by jenkins-bot: +mwext-VisualEditor-sync-gerrit on master branch only + +https://gerrit.wikimedia.org/r/108837",task_subcomment,['Change 108837 merged by jenkins-bot:\nmwext-VisualEditor-sync-gerrit on master branch only\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +254334,mediawiki/extensions.git does not update some extensions,"Change 108837 had a related patch set uploaded by Hashar: +mwext-VisualEditor-sync-gerrit on master branch only + +https://gerrit.wikimedia.org/r/108837",task_subcomment,['Change 108837 had a related patch set uploaded by Hashar:\nmwext-VisualEditor-sync-gerrit on master branch only\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254331,mediawiki/extensions.git does not update some extensions,"Change 108810 merged by jenkins-bot: +trigger mwext-VisualEditor-sync-gerrit on postmerge + +https://gerrit.wikimedia.org/r/108810",task_subcomment,['Change 108810 merged by jenkins-bot:\ntrigger mwext-VisualEditor-sync-gerrit on postmerge\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +254327,mediawiki/extensions.git does not update some extensions,"Change 108810 had a related patch set uploaded by Hashar: +trigger mwext-VisualEditor-sync-gerrit on postmerge + +https://gerrit.wikimedia.org/r/108810",task_subcomment,['Change 108810 had a related patch set uploaded by Hashar:\ntrigger mwext-VisualEditor-sync-gerrit on postmerge\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254323,mediawiki/extensions.git does not update some extensions,"The Gerrit replication got fixed last week. The bot was not able to connect because Gerrit cache accounts credential indefinitely (lowered to 7 days by Chad with https://gerrit.wikimedia.org/r/#/c/108715/ ). + +I did a few tweaks to adjust the shell script and granted jenkins-bot the ability to CR+2 and V+2 on mediawiki/extensions.git . + +The first change that self merged is https://gerrit.wikimedia.org/r/#/c/108732/ + +Gotta add triggers in Zuul.",task_subcomment,"['The Gerrit replication got fixed last week.', 'The bot was not able to connect because Gerrit cache accounts credential indefinitely (lowered to 7 days by Chad with URL ).', 'I did a few tweaks to adjust the shell script and granted jenkins-bot the ability to CR+2 and V+2 on mediawiki/extensions.git .', 'The first change that self merged is URL\n\nGotta add triggers in Zuul.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +254319,mediawiki/extensions.git does not update some extensions,"When jenkins-bot push to Gerrit, Gerrit fetch the email address of the user from the LDAP directory and compare it to the Commiter field of each commit being pushed. + +Gerrit points to LDAP server virt1000 which is no more replicated from virt1. Hence the jenkins-bot record known to virt1000 is still lacking the email field and thus Gerrit thinks jenkins-bot has no email. + + +This is thus blocked until the virt1 -> virt1000 LDAP replication is fixed.",task_subcomment,"['When jenkins-bot push to Gerrit, Gerrit fetch the email address of the user from the LDAP directory and compare it to the Commiter field of each commit being pushed.', 'Gerrit points to LDAP server virt1000 which is no more replicated from virt1.', 'Hence the jenkins-bot record known to virt1000 is still lacking the email field and thus Gerrit thinks jenkins-bot has no email.', 'This is thus blocked until the virt1 -> virt1000 LDAP replication is fixed.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254313,mediawiki/extensions.git does not update some extensions,"Still failing :( + +https://integration.wikimedia.org/ci/job/mwext-VisualEditor-sync-gerrit/9/console",task_subcomment,['Still failing :(\n\nURL'],['OBSERVED BUG BEHAVIOR'] +254306,mediawiki/extensions.git does not update some extensions,I've manually updated the database until LDAP gets back in sync. You *should* be able to push now.,task_subcomment,"[""I've manually updated the database until LDAP gets back in sync."", 'You *should* be able to push now.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +254300,mediawiki/extensions.git does not update some extensions,"Gerrit still believe that jenkins-bot user does not have any email address despite the address being shown in virt0 LDAP. + +The suspect is that the LDAP replication to virt1000 is broken and that is the server Gerrit is using as a primary. + +Whenever Gerrit learns about jenkins-bot user, the script I wrote should be able to push its change. + + +The last build I triggered ( https://integration.wikimedia.org/ci/job/mwext-VisualEditor-sync-gerrit/8/console ) yields: + +7:14:47 remote: ERROR: In commit c414977bcdbcbdf6331d9fe2e627bc0768695966 +17:14:47 remote: ERROR: committer email address jenkins-bot@wikimedia.org +17:14:47 remote: ERROR: does not match your user account. +17:14:47 remote: ERROR: +17:14:47 remote: ERROR: You have not registered any email addresses.",task_subcomment,"['Gerrit still believe that jenkins-bot user does not have any email address despite the address being shown in virt0 LDAP.', 'The suspect is that the LDAP replication to virt1000 is broken and that is the server Gerrit is using as a primary.', 'Whenever Gerrit learns about jenkins-bot user, the script I wrote should be able to push its change.', 'The last build I triggered ( URL ) yields:\n\n7:14:47 remote: ERROR: In commit c414977bcdbcbdf6331d9fe2e627bc0768695966\n17:14:47 remote: ERROR: committer email address jenkins-bot@wikimedia.org\n17:14:47 remote: ERROR: does not match your user account.', '17:14:47 remote: ERROR:\n17:14:47 remote: ERROR: You have not registered any email addresses.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254296,mediawiki/extensions.git does not update some extensions,"I have added a couple Jenkins slave scripts in integration/jenkins.git + + bin/gerrit-sync-ve.sh + bin/gerrit-sync-ve-push.sh + +That would update the VisualEditor on a local copy of mediawiki/extensions.git + +Then had to get a jenkins-bot@wikimedia.org email address registered and assigned to the jenkins-bot Gerrit user. + + +The job mwext-VisualEditor-sync-gerrit still needs to be triggered by Zuul on postmerge. That is an easy change though. Will do whenever I am sure the job is working properly.",task_subcomment,"['I have added a couple Jenkins slave scripts in integration/jenkins.git \n\n bin/gerrit-sync-ve.sh\n bin/gerrit-sync-ve-push.sh\n\nThat would update the VisualEditor on a local copy of mediawiki/extensions.git\n\nThen had to get a jenkins-bot@wikimedia.org email address registered and assigned to the jenkins-bot Gerrit user.', 'The job mwext-VisualEditor-sync-gerrit still needs to be triggered by Zuul on postmerge.', 'That is an easy change though.', 'Will do whenever I am sure the job is working properly.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'WORKAROUNDS']" +254291,mediawiki/extensions.git does not update some extensions,"Change 107862 merged by jenkins-bot: +mwext-VisualEditor-sync-gerrit + +https://gerrit.wikimedia.org/r/107862",task_subcomment,['Change 107862 merged by jenkins-bot:\nmwext-VisualEditor-sync-gerrit\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +254287,mediawiki/extensions.git does not update some extensions,"Change 107862 had a related patch set uploaded by Hashar: +mwext-VisualEditor-sync-gerrit + +https://gerrit.wikimedia.org/r/107862",task_subcomment,['Change 107862 had a related patch set uploaded by Hashar:\nmwext-VisualEditor-sync-gerrit\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254283,mediawiki/extensions.git does not update some extensions,"Change 107853 merged by Andrew Bogott: +contint: invoke gerrit-sync-ve-push.sh as jenkins + +https://gerrit.wikimedia.org/r/107853",task_subcomment,['Change 107853 merged by Andrew Bogott:\ncontint: invoke gerrit-sync-ve-push.sh as jenkins\n\nGERRIT_URL'],['ACTION ON ISSUE'] +254280,mediawiki/extensions.git does not update some extensions,"Change 107853 had a related patch set uploaded by Hashar: +contint: invoke gerrit-sync-ve-push.sh as jenkins + +https://gerrit.wikimedia.org/r/107853",task_subcomment,['Change 107853 had a related patch set uploaded by Hashar:\ncontint: invoke gerrit-sync-ve-push.sh as jenkins\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254276,mediawiki/extensions.git does not update some extensions,"Change 107841 merged by jenkins-bot: +Script to sync VisualEditor in mediawiki/extensions.git + +https://gerrit.wikimedia.org/r/107841",task_subcomment,['Change 107841 merged by jenkins-bot:\nScript to sync VisualEditor in mediawiki/extensions.git\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254271,mediawiki/extensions.git does not update some extensions,"Change 107841 had a related patch set uploaded by Hashar: +Script to sync VisualEditor in mediawiki/extensions.git + +https://gerrit.wikimedia.org/r/107841",task_subcomment,['Change 107841 had a related patch set uploaded by Hashar:\nScript to sync VisualEditor in mediawiki/extensions.git\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254264,mediawiki/extensions.git does not update some extensions,"Change 107575 abandoned by Hashar: +beta: pull VisualEditor individually + +Reason: +Per Chad, will use a Jenkins job to update mediawiki/extensions.git + +https://gerrit.wikimedia.org/r/107575",task_subcomment,"['Change 107575 abandoned by Hashar:\nbeta: pull VisualEditor individually\n\nReason:\nPer Chad, will use a Jenkins job to update mediawiki/extensions.git\n\nGERRIT_URL']",['INVESTIGATION AND EXPLORATION'] +254259,mediawiki/extensions.git does not update some extensions,"Change 107574 abandoned by Hashar: +unregister VisualEditor (replication broken in Gerrit) + +Reason: +Per Chad, will use a Jenkins job to update mediawiki/extensions.git + +https://gerrit.wikimedia.org/r/107574",task_subcomment,"['Change 107574 abandoned by Hashar:\nunregister VisualEditor (replication broken in Gerrit)\n\nReason:\nPer Chad, will use a Jenkins job to update mediawiki/extensions.git\n\nGERRIT_URL']",['OBSERVED BUG BEHAVIOR'] +254254,mediawiki/extensions.git does not update some extensions,"The patches above: + +1) unregister VisualEditor from mediawiki/extensions.git since it is broken anyway +2) make the wmf-beta-autoupdater script to use git pull to refresh the repository",task_subcomment,['The patches above:\n\n1) unregister VisualEditor from mediawiki/extensions.git since it is broken anyway\n2) make the wmf-beta-autoupdater script to use git pull to refresh the repository'],['INVESTIGATION AND EXPLORATION'] +254249,mediawiki/extensions.git does not update some extensions,"Change 107575 had a related patch set uploaded by Hashar: +beta: pull VisualEditor individually + +https://gerrit.wikimedia.org/r/107575",task_subcomment,['Change 107575 had a related patch set uploaded by Hashar:\nbeta: pull VisualEditor individually\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254247,mediawiki/extensions.git does not update some extensions,"Change 107574 had a related patch set uploaded by Hashar: +unregister VisualEditor (replication broken in Gerrit) + +https://gerrit.wikimedia.org/r/107574",task_subcomment,['Change 107574 had a related patch set uploaded by Hashar:\nunregister VisualEditor (replication broken in Gerrit)\n\nGERRIT_URL'],['ACTION ON ISSUE'] +254244,mediawiki/extensions.git does not update some extensions,"(In reply to comment #29) +> (In reply to comment #28) +> > We need to do this as a post-merge job in Jenkins for updating the meta-repo. +> > The Beta config should be able to remain as-is. +> +> I am not sure we could do a post-merge job since Zuul does not support +> triggering a job according to a project wildcard such as +> mediawiki/extensions/* +> + +We don't need to for all repos. Just VisualEditor since it's broken. So we'd adjust the VE zuul/jenkins config to update mediawiki/extensions.git after VE merges. + +> +> I thought we could adapt the 6 minutes wmf-beta-autoupdater.py script, make +> it +> fetch the list of extensions generated at: +> https://gerrit.wikimedia.org/mediawiki-extensions.txt then do a git +> submodule +> add on all of them and then update them all. + +Ew. I'd rather keep everything else as it is, keep the workaround to one place (the VE zuul/jenkins config) until the upstream fix takes place. No need to change our infrastructure.",task_subcomment,"[""(In reply to comment #29)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe don't need to for all repos."", ""Just VisualEditor since it's broken."", ""So we'd adjust the VE zuul/jenkins config to update mediawiki/extensions.git after VE merges."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nEw.', ""I'd rather keep everything else as it is, keep the workaround to one place (the VE zuul/jenkins config) until the upstream fix takes place."", 'No need to change our infrastructure.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOCIAL CONVERSATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +254241,mediawiki/extensions.git does not update some extensions,"(In reply to comment #28) +> We need to do this as a post-merge job in Jenkins for updating the meta-repo. +> The Beta config should be able to remain as-is. + +I am not sure we could do a post-merge job since Zuul does not support triggering a job according to a project wildcard such as mediawiki/extensions/* + + +I thought we could adapt the 6 minutes wmf-beta-autoupdater.py script, make it fetch the list of extensions generated at: https://gerrit.wikimedia.org/mediawiki-extensions.txt then do a git submodule add on all of them and then update them all.",task_subcomment,"['(In reply to comment #28)\nQUOTE\nQUOTE\n\nI am not sure we could do a post-merge job since Zuul does not support triggering a job according to a project wildcard such as mediawiki/extensions/*\n\n\nI thought we could adapt the 6 minutes wmf-beta-autoupdater.py script, make it fetch the list of extensions generated at: URL then do a git submodule add on all of them and then update them all.']",['SOLUTION DISCUSSION'] +254238,mediawiki/extensions.git does not update some extensions,We need to do this as a post-merge job in Jenkins for updating the meta-repo. The Beta config should be able to remain as-is.,task_subcomment,"['We need to do this as a post-merge job in Jenkins for updating the meta-repo.', 'The Beta config should be able to remain as-is.']","['WORKAROUNDS', 'SOLUTION DISCUSSION']" +254233,mediawiki/extensions.git does not update some extensions,Assigning to self and moving to CI,task_subcomment,['Assigning to self and moving to CI'],['SOLUTION DISCUSSION'] +254227,mediawiki/extensions.git does not update some extensions,"The root cause is that there are two Gerrit projects being named VisualEditor and there is a bug in Gerrit that get it confused about that and break the automatic update of mediawiki/extensions.git + +To restore automatic update, we would need to register the extensions locally by iterating over `gerrit ls-projects -p mediawiki/extensions/` and then use git `submodule update --init` as we did previously.",task_subcomment,"['The root cause is that there are two Gerrit projects being named VisualEditor and there is a bug in Gerrit that get it confused about that and break the automatic update of mediawiki/extensions.git\n\nTo restore automatic update, we would need to register the extensions locally by iterating over CODE and then use git CODE as we did previously.']",['INVESTIGATION AND EXPLORATION'] +254220,mediawiki/extensions.git does not update some extensions,Re-opening rather than having a fork in bug 59758.,task_subcomment,['Re-opening rather than having a fork in bug 59758.'],['ACTION ON ISSUE'] +254213,mediawiki/extensions.git does not update some extensions,*** Bug 59758 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 59758 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254206,mediawiki/extensions.git does not update some extensions,"happened again, see bug 59758",task_subcomment,"['happened again, see bug 59758']",['OBSERVED BUG BEHAVIOR'] +254198,mediawiki/extensions.git does not update some extensions,"(In reply to comment #21) +> Does anybody plan to investigate on this ticket? +> Or is this ""working for us"" right now? +> +> Wondering if this should still be open, and what's the way forward. + +The problem was that there was more than one git repos on gerrit called ""VisualEditor"" (namely, mediawiki/extensions/VisualEditor.git and VisualEditor.git with its subsidiaries VisualEditor/core.git, VisualEditor/plugins/.git etc.). We created the other repos to move the code out of MW and make VE properly stand-alone and shippable, but thought we have split the code, we hadn't yet moved the core of VE into the new repo). + +As a quick hack, Chad deleted the extra repos, which seems to have fixed everything, which means the issue is fixed (and has a known cause), but this isn't sustainable in the longer term as we will likely want to actually do the repo split some time soon (though we could work around the restriction on repo names)… + +Marking as ""FIXED"", but it's more like ""AVOIDED AT SOME COST"".",task_subcomment,"['(In reply to comment #21)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe problem was that there was more than one git repos on gerrit called ""VisualEditor"" (namely, mediawiki/extensions/VisualEditor.git and VisualEditor.git with its subsidiaries VisualEditor/core.git, VisualEditor/plugins/.git etc.).', ""We created the other repos to move the code out of MW and make VE properly stand-alone and shippable, but thought we have split the code, we hadn't yet moved the core of VE into the new repo)."", 'As a quick hack, Chad deleted the extra repos, which seems to have fixed everything, which means the issue is fixed (and has a known cause), but this isn\'t sustainable in the longer term as we will likely want to actually do the repo split some time soon (though we could work around the restriction on repo names)…\n\nMarking as ""FIXED"", but it\'s more like ""AVOIDED AT SOME COST"".']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +254190,mediawiki/extensions.git does not update some extensions,"Does anybody plan to investigate on this ticket? +Or is this ""working for us"" right now? + +Wondering if this should still be open, and what's the way forward.",task_subcomment,"['Does anybody plan to investigate on this ticket?', 'Or is this ""working for us"" right now?', ""Wondering if this should still be open, and what's the way forward.""]","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']" +254185,mediawiki/extensions.git does not update some extensions,VisualEditor is finally working. I hope. I pray.,task_subcomment,"['VisualEditor is finally working.', 'I hope.', 'I pray.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +254180,mediawiki/extensions.git does not update some extensions,I'm beginning to think this thing is totally broken and a waste of time to use.,task_subcomment,"[""I'm beginning to think this thing is totally broken and a waste of time to use.""]",['OBSERVED BUG BEHAVIOR'] +254175,mediawiki/extensions.git does not update some extensions,"Sorry DataTypes was dirty in my local copy. That caused git to not update the remaining extensions. It chokes currently on: + + +Cloning into 'ValueFormatters'... +remote: Counting objects: 4, done +remote: Finding sources: 100% (4/4) +remote: Getting sizes: 100% (3/3) +remote: Total 4 (delta 0), reused 4 (delta 0) +Unpacking objects: 100% (4/4), done. +Submodule path 'ValueFormatters': checked out 'b466dde64555d82fcefcdd0b1fe838de2e3acada' +fatal: Needed a single revision +Unable to find current revision in submodule path 'ValueParsers'",task_subcomment,"['Sorry DataTypes was dirty in my local copy.', 'That caused git to not update the remaining extensions.', ""It chokes currently on:\n\n\nCloning into 'ValueFormatters'...\nremote: Counting objects: 4, done\nremote: Finding sources: 100% (4/4)\nremote: Getting sizes: 100% (3/3)\nremote: Total 4 (delta 0), reused 4 (delta 0)\nUnpacking objects: 100% (4/4), done."", ""Submodule path 'ValueFormatters': checked out 'b466dde64555d82fcefcdd0b1fe838de2e3acada'\nfatal: Needed a single revision\nUnable to find current revision in submodule path 'ValueParsers'""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +254168,mediawiki/extensions.git does not update some extensions,"It is apparently totally broken right now. The check-sync.sh script reports a lot of extensions has not being up to date :/ + + +ERROR! DataTypes is lagging behind. +ERROR! DataValues is lagging behind. +ERROR! DidYouKnow is lagging behind. +ERROR! Diff is lagging behind. +ERROR! DisableAccount is lagging behind. +ERROR! Disambiguator is lagging behind. +ERROR! DonationInterface is lagging behind. +ERROR! Duplicator is lagging behind. +ERROR! EImage is lagging behind. +ERROR! Echo is lagging behind. +ERROR! EducationProgram is lagging behind. +ERROR! EventLogging is lagging behind. +ERROR! ExtensionDistributor is lagging behind. +ERROR! GettingStarted is lagging behind. +ERROR! GlobalBlocking is lagging behind. +ERROR! GuidedTour is lagging behind. +ERROR! Hovergallery is lagging behind. +ERROR! InlineCategorizer is lagging behind. +ERROR! Insider is lagging behind. +ERROR! LiquidThreads is lagging behind. +ERROR! Maps is lagging behind. +ERROR! MarkAsHelpful is lagging behind. +ERROR! Math is lagging behind. +ERROR! MobileFrontend is lagging behind. +ERROR! MoodBar is lagging behind. +ERROR! Mpdf is lagging behind. +ERROR! OAuth is lagging behind. +ERROR! Parsoid is lagging behind. +ERROR! PdfExport is lagging behind. +ERROR! PdfHandler is lagging behind. +ERROR! PerPageLicense is lagging behind. +ERROR! PronunciationRecording is lagging behind. +ERROR! RelatedArticles is lagging behind. +ERROR! RevisionCommentSupplement is lagging behind. +ERROR! SecurePoll is lagging behind. +ERROR! SemanticMediaWiki is lagging behind. +ERROR! Thanks is lagging behind. +ERROR! TimedMediaHandler is lagging behind. +ERROR! Translate is lagging behind. +ERROR! TwnMainPage is lagging behind. +ERROR! UniversalLanguageSelector is lagging behind. +ERROR! UploadWizard is lagging behind. +ERROR! ValueFormatters is lagging behind. +ERROR! ValueParsers is lagging behind. +ERROR! ValueValidators is lagging behind. +ERROR! ValueView is lagging behind. +ERROR! Vector is lagging behind. +ERROR! WikiEditor is lagging behind. +ERROR! Wikibase is lagging behind. +ERROR! WikibaseDataModel is lagging behind. +ERROR! WikibaseDatabase is lagging behind. +ERROR! WikibaseQuery is lagging behind. +ERROR! WikibaseQueryEngine is lagging behind. +ERROR! WikimediaMaintenance is lagging behind. +ERROR! WikimediaMessages is lagging behind. +ERROR! ZeroRatedMobileAccess is lagging behind.",task_subcomment,"['It is apparently totally broken right now.', 'The check-sync.sh script reports a lot of extensions has not being up to date :/\n\n\nERROR!', 'DataTypes is lagging behind.', 'ERROR!', 'DataValues is lagging behind.', 'ERROR!', 'DidYouKnow is lagging behind.', 'ERROR!', 'Diff is lagging behind.', 'ERROR!', 'DisableAccount is lagging behind.', 'ERROR!', 'Disambiguator is lagging behind.', 'ERROR!', 'DonationInterface is lagging behind.', 'ERROR!', 'Duplicator is lagging behind.', 'ERROR!', 'EImage is lagging behind.', 'ERROR!', 'Echo is lagging behind.', 'ERROR!', 'EducationProgram is lagging behind.', 'ERROR!', 'EventLogging is lagging behind.', 'ERROR!', 'ExtensionDistributor is lagging behind.', 'ERROR!', 'GettingStarted is lagging behind.', 'ERROR!', 'GlobalBlocking is lagging behind.', 'ERROR!', 'GuidedTour is lagging behind.', 'ERROR!', 'Hovergallery is lagging behind.', 'ERROR!', 'InlineCategorizer is lagging behind.', 'ERROR!', 'Insider is lagging behind.', 'ERROR!', 'LiquidThreads is lagging behind.', 'ERROR!', 'Maps is lagging behind.', 'ERROR!', 'MarkAsHelpful is lagging behind.', 'ERROR!', 'Math is lagging behind.', 'ERROR!', 'MobileFrontend is lagging behind.', 'ERROR!', 'MoodBar is lagging behind.', 'ERROR!', 'Mpdf is lagging behind.', 'ERROR!', 'OAuth is lagging behind.', 'ERROR!', 'Parsoid is lagging behind.', 'ERROR!', 'PdfExport is lagging behind.', 'ERROR!', 'PdfHandler is lagging behind.', 'ERROR!', 'PerPageLicense is lagging behind.', 'ERROR!', 'PronunciationRecording is lagging behind.', 'ERROR!', 'RelatedArticles is lagging behind.', 'ERROR!', 'RevisionCommentSupplement is lagging behind.', 'ERROR!', 'SecurePoll is lagging behind.', 'ERROR!', 'SemanticMediaWiki is lagging behind.', 'ERROR!', 'Thanks is lagging behind.', 'ERROR!', 'TimedMediaHandler is lagging behind.', 'ERROR!', 'Translate is lagging behind.', 'ERROR!', 'TwnMainPage is lagging behind.', 'ERROR!', 'UniversalLanguageSelector is lagging behind.', 'ERROR!', 'UploadWizard is lagging behind.', 'ERROR!', 'ValueFormatters is lagging behind.', 'ERROR!', 'ValueParsers is lagging behind.', 'ERROR!', 'ValueValidators is lagging behind.', 'ERROR!', 'ValueView is lagging behind.', 'ERROR!', 'Vector is lagging behind.', 'ERROR!', 'WikiEditor is lagging behind.', 'ERROR!', 'Wikibase is lagging behind.', 'ERROR!', 'WikibaseDataModel is lagging behind.', 'ERROR!', 'WikibaseDatabase is lagging behind.', 'ERROR!', 'WikibaseQuery is lagging behind.', 'ERROR!', 'WikibaseQueryEngine is lagging behind.', 'ERROR!', 'WikimediaMaintenance is lagging behind.', 'ERROR!', 'WikimediaMessages is lagging behind.', 'ERROR!', 'ZeroRatedMobileAccess is lagging behind.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +254164,mediawiki/extensions.git does not update some extensions,*** Bug 51635 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51635 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254157,mediawiki/extensions.git does not update some extensions,*** Bug 48893 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 48893 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254150,mediawiki/extensions.git does not update some extensions,"Change 73736 merged by Hashar: +update VisualEditor to latest master + +https://gerrit.wikimedia.org/r/73736",task_subcomment,['Change 73736 merged by Hashar:\nupdate VisualEditor to latest master\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR'] +254142,mediawiki/extensions.git does not update some extensions,"Change 73736 had a related patch set uploaded by Hashar: +update VisualEditor to latest master + +https://gerrit.wikimedia.org/r/73736",task_subcomment,['Change 73736 had a related patch set uploaded by Hashar:\nupdate VisualEditor to latest master\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION'] +254134,mediawiki/extensions.git does not update some extensions,I hate life.,task_subcomment,['I hate life.'],['OBSERVED BUG BEHAVIOR'] +254130,mediawiki/extensions.git does not update some extensions,"Got broken again a couple hours ago: + +* ac6c10d - (origin/master, origin/HEAD) Merge ""Bind listener to key... +|\ +| * 31104d5 - Bind listener to keyup to capture arrows & better ma... +* | 877463e - (HEAD) Merge ""Add hooks and classes, initially to s... + +which shows HEAD not pointing to the same commit as origin/HEAD :(",task_subcomment,"['Got broken again a couple hours ago:\n\n* ac6c10d - (origin/master, origin/HEAD) Merge ""Bind listener to key...\n|\\ \n| * 31104d5 - Bind listener to keyup to capture arrows & better ma...\n* | 877463e - (HEAD) Merge ""Add hooks and classes, initially to s...\n\nwhich shows HEAD not pointing to the same commit as origin/HEAD :(']",['OBSERVED BUG BEHAVIOR'] +254126,mediawiki/extensions.git does not update some extensions,"Worked around (decreasing priority), but keeping this open as it might bite us again (as bug 49906 is still open).",task_subcomment,"['Worked around (decreasing priority), but keeping this open as it might bite us again (as bug 49906 is still open).']",['WORKAROUNDS'] +254122,mediawiki/extensions.git does not update some extensions,"I fixed it before. + +Now I've fixed it once again. + +This is annoying.",task_subcomment,"['I fixed it before.', ""Now I've fixed it once again."", 'This is annoying.']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +254119,mediawiki/extensions.git does not update some extensions,"Setting Importance etc since today is ""D Day"" for Visual Editor on ENWiki. Would be great to have betalabs running up to date VE on the day we roll out to a large audience :)",task_subcomment,"['Setting Importance etc since today is ""D Day"" for Visual Editor on ENWiki.', 'Would be great to have betalabs running up to date VE on the day we roll out to a large audience :)']","['INVESTIGATION AND EXPLORATION', 'FUTURE PLAN']" +254117,mediawiki/extensions.git does not update some extensions,"VisualEditor is lagged out again: + +$ cd extensions +$ git remote update +$ git rebase +$ git submodule update --init VisualEditor +Submodule path 'VisualEditor': checked out '46c3d48ba7779254581bfad017c0804588a1983d' +$ + +Then looking at HEAD (that is the checked out version above) and origin/master: + +$ git log --oneline HEAD..origin/master +c331c19 Merge ""Minor performance optimization and cleanup in FocusableNode"" +daa83d2 Minor performance optimization and cleanup in FocusableNode +a08da9f Make node resizing happen inside onAttributeChange +f8d7314 Merge ""Simplify ve.ce.ResizableNode by removing code for 'transition' which is not used anyway"" +87667bd Merge ""Make toolbar look correct with non-standard browser font size settings"" +b0b832a Make toolbar look correct with non-standard browser font size settings +59e7a7b Simplify ve.ce.ResizableNode by removing code for 'transition' which is not used anyway +$ + + + +$ git rev-parse origin/master +c331c1980ec37a4d6926f138fd1e81879d5db299 +$ git rev-parse HEAD +46c3d48ba7779254581bfad017c0804588a1983d +$",task_subcomment,"['VisualEditor is lagged out again:\n\n$ cd extensions\n$ git remote update\n$ git rebase\n$ git submodule update --init VisualEditor\nSubmodule path \'VisualEditor\': checked out \'46c3d48ba7779254581bfad017c0804588a1983d\'\n$\n\nThen looking at HEAD (that is the checked out version above) and origin/master:\n\n$ git log --oneline HEAD..origin/master\nc331c19 Merge ""Minor performance optimization and cleanup in FocusableNode""\ndaa83d2 Minor performance optimization and cleanup in FocusableNode\na08da9f Make node resizing happen inside onAttributeChange\nf8d7314 Merge ""Simplify ve.ce.ResizableNode by removing code for \'transition\' which is not used anyway""\n87667bd Merge ""Make toolbar look correct with non-standard browser font size settings""\nb0b832a Make toolbar look correct with non-standard browser font size settings\n59e7a7b Simplify ve.ce.ResizableNode by removing code for \'transition\' which is not used anyway\n$\n\n\n\n$ git rev-parse origin/master\nc331c1980ec37a4d6926f138fd1e81879d5db299\n$ git rev-parse HEAD\n46c3d48ba7779254581bfad017c0804588a1983d\n$']",['INVESTIGATION AND EXPLORATION'] +254111,mediawiki/extensions.git does not update some extensions,"http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version + +VisualEditor (Version 0.1.0) (4b74101) +19:00, 20 June 2013 + +:-)",task_subcomment,"['URL\n\nVisualEditor (Version 0.1.0)\t(4b74101)\n19:00, 20 June 2013\n\n:-)']",['SOLUTION DISCUSSION'] +254105,mediawiki/extensions.git does not update some extensions,"I have no idea what went wrong :/ + +Filled bug 49906 to monitor such issues. + +Thank you Chad!",task_subcomment,"['I have no idea what went wrong :/\n\nFilled bug 49906 to monitor such issues.', 'Thank you Chad!']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']" +254096,mediawiki/extensions.git does not update some extensions,"Fixed. + +gerrit> select * from submodule_subscriptions where submodule_project_name like '%VisualEditor%'; + submodule_project_name | submodule_branch_name | super_project_project_name | super_project_branch_name | submodule_path + -----------------------+-----------------------+----------------------------+---------------------------+--------------- + VisualEditor | refs/heads/master | mediawiki/extensions | refs/heads/master | VisualEditor +(1 row; 2 ms) + +gerrit> update submodule_subscriptions set submodule_project_name = 'mediawiki/extensions/VisualEditor' where submodule_path = 'VisualEditor'; +UPDATE 1; 2 ms + +gerrit> select * from submodule_subscriptions where submodule_project_name like '%VisualEditor%'; + submodule_project_name | submodule_branch_name | super_project_project_name | super_project_branch_name | submodule_path + ----------------------------------+-----------------------+----------------------------+---------------------------+--------------- + mediawiki/extensions/VisualEditor | refs/heads/master | mediawiki/extensions | refs/heads/master | VisualEditor +(1 row; 1 ms) + +Was the extension at one point pointing to the wrong repository? Will file a bug upstream, since I guess this should've updated itself when the submodule changed.",task_subcomment,"['Fixed.', ""gerrit> select * from submodule_subscriptions where submodule_project_name like '%VisualEditor%';\n submodule_project_name | submodule_branch_name | super_project_project_name | super_project_branch_name | submodule_path\n -----------------------+-----------------------+----------------------------+---------------------------+---------------\n VisualEditor | refs/heads/master | mediawiki/extensions | refs/heads/master | VisualEditor\n(1 row; 2 ms)\n\ngerrit> update submodule_subscriptions set submodule_project_name = 'mediawiki/extensions/VisualEditor' where submodule_path = 'VisualEditor';\nUPDATE 1; 2 ms\n\ngerrit> select * from submodule_subscriptions where submodule_project_name like '%VisualEditor%';\n submodule_project_name | submodule_branch_name | super_project_project_name | super_project_branch_name | submodule_path\n ----------------------------------+-----------------------+----------------------------+---------------------------+---------------\n mediawiki/extensions/VisualEditor | refs/heads/master | mediawiki/extensions | refs/heads/master | VisualEditor\n(1 row; 1 ms)\n\nWas the extension at one point pointing to the wrong repository?"", ""Will file a bug upstream, since I guess this should've updated itself when the submodule changed.""]","['SOLUTION USAGE', 'BUG REPRODUCTION', 'BUG REPRODUCTION']" +254090,mediawiki/extensions.git does not update some extensions,Actually moving this bug under 'git/gerrit'.,task_subcomment,"[""Actually moving this bug under 'git/gerrit'.""]",['BUG REPRODUCTION'] +254084,mediawiki/extensions.git does not update some extensions,"On beta, origin/master points to 5add8cc4c0ea5b305525c30d8af5261406e5d355 which mean VisualEditor remote is not being fetched when running 'git pull && git submodule update --init'.",task_subcomment,"[""On beta, origin/master points to 5add8cc4c0ea5b305525c30d8af5261406e5d355 which mean VisualEditor remote is not being fetched when running 'git pull && git submodule update --init'.""]",['OBSERVED BUG BEHAVIOR'] +254076,mediawiki/extensions.git does not update some extensions,"The mediawiki/extensions.git is not updating VisualEditor extension: + + +$ git submodule update --init VisualEditor +remote: Counting objects: 3887, done +remote: Finding sources: 100% (5930/5930) +remote: Getting sizes: 100% (1370/1370) +remote: Compressing objects: 21% (288/1370) +remote: Total 5930 (delta 3846), reused 5495 (delta 3829) +Receiving objects: 100% (5930/5930), 2.95 MiB | 622 KiB/s, done. +Resolving deltas: 100% (4091/4091), completed with 275 local objects. +From https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor + 65602e1..ed1c06e master -> origin/master +Submodule path 'VisualEditor': checked out '5add8cc4c0ea5b305525c30d8af5261406e5d355' + + +$ cd VisualEditor +$ git rev-parse HEAD origin/master +5add8cc4c0ea5b305525c30d8af5261406e5d355 +ed1c06ee6b36851ba1f6e3a68d0584da4c20be46 + +HEAD should points to the same as origin/master. + + +Parsoid is updated though: + +$ git rev-parse HEAD origin/master +bf8d3dff339e5b3e10f0667850d0114f49db131c +bf8d3dff339e5b3e10f0667850d0114f49db131c + + +Moving the bug under Wikimedia > Git/Gerrit . Will poke Chad / Sam about it.",task_subcomment,"['The mediawiki/extensions.git is not updating VisualEditor extension:\n\n\n$ git submodule update --init VisualEditor\nremote: Counting objects: 3887, done\nremote: Finding sources: 100% (5930/5930)\nremote: Getting sizes: 100% (1370/1370)\nremote: Compressing objects: 21% (288/1370)\nremote: Total 5930 (delta 3846), reused 5495 (delta 3829)\nReceiving objects: 100% (5930/5930), 2.95 MiB | 622 KiB/s, done.', 'Resolving deltas: 100% (4091/4091), completed with 275 local objects.', ""From URL\n 65602e1..ed1c06e master -> origin/master\nSubmodule path 'VisualEditor': checked out '5add8cc4c0ea5b305525c30d8af5261406e5d355'\n\n\n$ cd VisualEditor\n$ git rev-parse HEAD origin/master\n5add8cc4c0ea5b305525c30d8af5261406e5d355\ned1c06ee6b36851ba1f6e3a68d0584da4c20be46\n\nHEAD should points to the same as origin/master."", 'Parsoid is updated though:\n\n$ git rev-parse HEAD origin/master\nbf8d3dff339e5b3e10f0667850d0114f49db131c\nbf8d3dff339e5b3e10f0667850d0114f49db131c\n\n\nMoving the bug under Wikimedia > Git/Gerrit .', 'Will poke Chad / Sam about it.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'ACTION ON ISSUE']" +51828,VisualEditor: Parsoid ate a reference,"In this edit: https://fr.wikipedia.org/w/index.php?diff=94100781 VisualEditor seems to have emptied a reference (the one containing ""Maxime Pargaud"" as author of the cited reference). + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Parsoid ate a reference\n\nIn this edit: URL VisualEditor seems to have emptied a reference (the one containing ""Maxime Pargaud"" as author of the cited reference).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +253136,VisualEditor: Parsoid ate a reference,This is now fixed (Parsoid selser issue); sorry!,task_subcomment,['This is now fixed (Parsoid selser issue); sorry!'],['BUG REPRODUCTION'] +253130,VisualEditor: Parsoid ate a reference,"VisualEditor kissed a girl and liked it. Oh boy, do our products grow up fast. + +Oh wait, it ate a reference? Bad bad editor. Discipline... Slacker!",task_subcomment,"['VisualEditor kissed a girl and liked it.', 'Oh boy, do our products grow up fast.', 'Oh wait, it ate a reference?', 'Bad bad editor.', 'Discipline... Slacker!']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +51763,VisualEditor: Image insertion does not work,"See https://en.wikipedia.org/wiki/User:Mdennis_%28WMF%29/sandbox for the result of four different attempts to insert images. Each one resulted in something like https://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=560491469&oldid=560491343 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Image insertion does not work\n\nSee URL for the result of four different attempts to insert images.', 'Each one resulted in something like URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +248995,VisualEditor: Image insertion does not work,Fixed. Sorry about this.,task_subcomment,"['Fixed.', 'Sorry about this.']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']" +51737,VisualEditor: Page contents replaced 'undefined' (because of an edit conflict?),"https://en.wikipedia.org/w/index.php?title=McIntosh_%28apple%29&diff=560394609&oldid=560264020 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: Page contents replaced 'undefined' (because of an edit conflict?)"", 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +247487,VisualEditor: Page contents replaced 'undefined' (because of an edit conflict?),"I'm going to speculatively mark this as fixed; we haven't seen any further issues with this and there's no steps to repeat - even when we undertake edit conflicts it still doesn't occur. + +Please re-open if you find that it does recur - and if so, any information about how to get it to trigger would be great, of course.",task_subcomment,"[""I'm going to speculatively mark this as fixed; we haven't seen any further issues with this and there's no steps to repeat - even when we undertake edit conflicts it still doesn't occur."", 'Please re-open if you find that it does recur - and if so, any information about how to get it to trigger would be great, of course.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +247481,VisualEditor: Page contents replaced 'undefined' (because of an edit conflict?),"(In reply to comment #1) +> https://en.wikipedia.org/wiki/Wikipedia: +> Village_pump_(technical)#VisualEditor_-_A.2FB_test_launch_on_18_June +> +> indicates that this might be caused by edit conflicts + +I can't replicate this, although of course it is difficult to realistically replicate edit conflicts.",task_subcomment,"[""(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI can't replicate this, although of course it is difficult to realistically replicate edit conflicts.""]",['SOLUTION DISCUSSION'] +247472,VisualEditor: Page contents replaced 'undefined' (because of an edit conflict?),"https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#VisualEditor_-_A.2FB_test_launch_on_18_June + +indicates that this might be caused by edit conflicts",task_subcomment,['URL\n\nindicates that this might be caused by edit conflicts'],['OBSERVED BUG BEHAVIOR'] +51668,VisualEditor: Page with a block and no s throws fatal error on load,"Have a page with a block but no s and you get: + +| Uncaught TypeError: Cannot call method 'connect' of null + +This is bad. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: Page with a block and no s throws fatal error on load\n\nHave a page with a block but no s and you get:\n\n| Uncaught TypeError: Cannot call method 'connect' of null \n\nThis is bad."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +243087,VisualEditor: Page with a block and no s throws fatal error on load,"This was fixed with gerrit 67924, which is now merged into master and will go out with wmf8 from Thursday.",task_subcomment,"['This was fixed with gerrit 67924, which is now merged into master and will go out with wmf8 from Thursday.']",['SOLUTION USAGE'] +51608,VisualEditor: HTML comments are dropped from transclusion calls,"https://en.wikipedia.org/w/index.php?title=Vidin&diff=559844598&oldid=559844102 shows several dirty diff issues, including spurious template bars, space changes, and corrupt links. + +However, this bug is specifically about the HTML comments that are dropped, ""the name of a location map as per http://en.wikipedia.org/wiki/Template:Location_map"" and ""the position of the pushpin label: left, right, top, bottom, none"". These comments often have important messages to other editors, so they can not be stripped. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=49603 +https://bugzilla.wikimedia.org/show_bug.cgi?id=49655",task_description,"['VisualEditor: HTML comments are dropped from transclusion calls\n\nURL shows several dirty diff issues, including spurious template bars, space changes, and corrupt links.', 'However, this bug is specifically about the HTML comments that are dropped, ""the name of a location map as per URL and ""the position of the pushpin label: left, right, top, bottom, none"".', 'These comments often have important messages to other editors, so they can not be stripped.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +335980,VisualEditor: HTML comments are dropped from transclusion calls,"verified in betalabs and test2 - HTML comments are preserved for both cases - generally and, specifically, in transclusions.",task_subcomment,"['verified in betalabs and test2 - HTML comments are preserved for both cases - generally and, specifically, in transclusions.']",['OBSERVED BUG BEHAVIOR'] +335978,VisualEditor: HTML comments are dropped from transclusion calls,"verified in betalabs - HTML comments are preserved both - generally and, specifically, in transclusions.",task_subcomment,"['verified in betalabs - HTML comments are preserved both - generally and, specifically, in transclusions.']",['OBSERVED BUG BEHAVIOR'] +239675,VisualEditor: HTML comments are dropped from transclusion calls,"That's a separate bug, will raise as such.",task_subcomment,"[""That's a separate bug, will raise as such.""]",['BUG REPRODUCTION'] +239668,VisualEditor: HTML comments are dropped from transclusion calls,"Not sure if it's the same thing, but I just did this today http://it.wikipedia.org/w/index.php?title=Google&diff=59622535&oldid=59377529 and it discarded commented text which, as noted above, should be there for a reason :)",task_subcomment,"[""Not sure if it's the same thing, but I just did this today URL and it discarded commented text which, as noted above, should be there for a reason :)""]",['INVESTIGATION AND EXPLORATION'] +239661,VisualEditor: HTML comments are dropped from transclusion calls,"This is now fixed; as an example, see https://en.wikipedia.org/w/index.php?title=Bleak_House&diff=560362551&oldid=560338958 as an edit made with VisualEditor that leaves the comments in the templates as they were.",task_subcomment,"['This is now fixed; as an example, see URL as an edit made with VisualEditor that leaves the comments in the templates as they were.']",['SOLUTION USAGE'] +239656,VisualEditor: HTML comments are dropped from transclusion calls,Can't reproduce in master. The comment appears in the template dialog and can be edited. With experimental code disabled the template is completely untouched.,task_subcomment,"[""Can't reproduce in master."", 'The comment appears in the template dialog and can be edited.', 'With experimental code disabled the template is completely untouched.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +239650,VisualEditor: HTML comments are dropped from transclusion calls,"(In reply to comment #3) +> See also bug 49655 and this (where Ssastry discusses it): +> Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox + +The place for ""see also"" bugs is the ""see also"" section at the top right of the bug - have put it there. :-) Bug 42124 is not relevant.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\n\nThe place for ""see also"" bugs is the ""see also"" section at the top right of the bug - have put it there.', ':-) Bug 42124 is not relevant.']","['WORKAROUNDS', 'MOTIVATION']" +239647,VisualEditor: HTML comments are dropped from transclusion calls,"[[Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox]] + +See also bug 42124.",task_subcomment,['[[Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox]]\n\nSee also bug 42124.'],['BUG REPRODUCTION'] +239642,VisualEditor: HTML comments are dropped from transclusion calls,"See also bug 49655 and this (where Ssastry discusses it): +Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox",task_subcomment,['See also bug 49655 and this (where Ssastry discusses it): \nWikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox'],['OBSERVED BUG BEHAVIOR'] +239637,VisualEditor: HTML comments are dropped from transclusion calls,"Confirm that these are being re-broken, but seemingly online in template calls (where we can't alienate them?). Ed, can you confirm at your end if this is a DM issue or a Parsoid one? + +I was able to edit around an HTML comment without altering it inline (as expected) in https://www.mediawiki.org/w/index.php?title=VisualEditor:TestComments&diff=712245&oldid=712244 - but changes to the HTML comment in the second template fail to be detected as a change (?). Note that the first template can't be edited as the preceding block comment it created as an mw:Placeholder (per bug 47403) and (wrongly?) merged with the following transclusion.",task_subcomment,"[""Confirm that these are being re-broken, but seemingly online in template calls (where we can't alienate them?)."", 'Ed, can you confirm at your end if this is a DM issue or a Parsoid one?', 'I was able to edit around an HTML comment without altering it inline (as expected) in URL - but changes to the HTML comment in the second template fail to be detected as a change (?).', ""Note that the first template can't be edited as the preceding block comment it created as an mw:Placeholder (per bug 47403) and (wrongly?)"", 'merged with the following transclusion.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']" +239631,VisualEditor: HTML comments are dropped from transclusion calls,"At the time of this discussion by VE developers, +[[Wikipedia:VisualEditor/Feedback/Archive 2013 05#General_observations]], hidden notes/comments were preserved. Now all hidden HTML notes on a page (or at least those in templates) are removed when the page is edited by VE. + +Page edit notices and section edit notices will not work as a replacement since hidden notes can be instructional for specific references, tables, infoboxes, navboxes, sentences, paragraphs, etc.. Page notices and edit notices are for a whole page or section. For more info: +[[Wikipedia:VisualEditor/Feedback#HTML_notes]] - or wherever it ends up later in the archives. + +If HTML notes are going to be replaced by some new hidden notation system, they still need to be preserved in the meantime. They should be treated similarly to how VE handles tables, infoboxes, and other stuff that VE can not currently edit. VE should not be doing anything within templates. Templates are too complex for VE to meddle with in the slightest way. VE should not even remove spaces in templates. + +If VE ends up with another hidden note tool, then a bot may have to go around to convert all existing hidden HTML notes to the new VE tool. But why bother? + +Why not keep the HTML notes, and use some kind of popup tooltip in VE that pops up when one puts the mouse cursor over a hidden note icon in VE edit mode? So one can read the hidden note in the popup. Kind of like how reference tooltips work.",task_subcomment,"['At the time of this discussion by VE developers, \n[[Wikipedia:VisualEditor/Feedback/Archive 2013 05#General_observations]], hidden notes/comments were preserved.', 'Now all hidden HTML notes on a page (or at least those in templates) are removed when the page is edited by VE.', 'Page edit notices and section edit notices will not work as a replacement since hidden notes can be instructional for specific references, tables, infoboxes, navboxes, sentences, paragraphs, etc..', 'Page notices and edit notices are for a whole page or section.', 'For more info: \n[[Wikipedia:VisualEditor/Feedback#HTML_notes]] - or wherever it ends up later in the archives.', 'If HTML notes are going to be replaced by some new hidden notation system, they still need to be preserved in the meantime.', 'They should be treated similarly to how VE handles tables, infoboxes, and other stuff that VE can not currently edit.', 'VE should not be doing anything within templates.', 'Templates are too complex for VE to meddle with in the slightest way.', 'VE should not even remove spaces in templates.', 'If VE ends up with another hidden note tool, then a bot may have to go around to convert all existing hidden HTML notes to the new VE tool.', 'But why bother?', 'Why not keep the HTML notes, and use some kind of popup tooltip in VE that pops up when one puts the mouse cursor over a hidden note icon in VE edit mode?', 'So one can read the hidden note in the popup.', 'Kind of like how reference tooltips work.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +51596,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"Adding a file/media fails with wrong wikicode. + +This wikicode is created, see URL: + +[[undefined|link=https://commons.wikimedia.org/wiki/File:CV.03326.jpg|right|framed|424x275px]] + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: https://test.wikipedia.org/w/index.php?title=User:Raymond/image&diff=174461&oldid=174460",task_description,"[""VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined')\n\nAdding a file/media fails with wrong wikicode."", 'This wikicode is created, see URL:\n\n[[undefined|link=URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +238648,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),*** Bug 50021 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50021 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238642,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"(In reply to comment #10) +> What about commend 5 and comment 6? + +Sorry, yes; created as bug 49849.",task_subcomment,"['(In reply to comment #10)\nQUOTE\n\nSorry, yes; created as bug 49849.']",['OBSERVED BUG BEHAVIOR'] +238635,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),What about commend 5 and comment 6?,task_subcomment,['What about commend 5 and comment 6?'],['MOTIVATION'] +238628,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"This is partially fixed in gerrit 69581 which we will deploy this afternoon. + +However, the link issue is still not fixed, thus (in the example in comment 0) we will now get: + +[[File:CV.03326.jpg|link=https://commons.wikimedia.org/wiki/File:CV.03326.jpg|right|framed|424x275px]] + +… instead of: + +[[File:CV.03326.jpg|right|framed|424x275px]] + +… which is bad, but nothing like as terrible as it was. Forking that off to a new bug, bug 49844, and marking this as fixed.",task_subcomment,"['This is partially fixed in gerrit 69581 which we will deploy this afternoon.', 'However, the link issue is still not fixed, thus (in the example in comment 0) we will now get:\n\n[[File:CV.03326.jpg|link=URL\n\n… instead of:\n\n[[File:CV.03326.jpg|right|framed|424x275px]]\n\n… which is bad, but nothing like as terrible as it was.', 'Forking that off to a new bug, bug 49844, and marking this as fixed.']","['BUG REPRODUCTION', 'SOLUTION USAGE', 'ACTION ON ISSUE']" +238619,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"From bug 49829 comment 0: + +| This is the DOM returned by the VE after inserting a new thumbnail: +|
+| +|
+| +| Note the 'undefined' in the resource attribute. The resource is the image +| target, so we notice that the link and the image named 'undefined' differ and +| serialize as +| [[undefined|link=http://commons.wikimedia.org/wiki/File:Apples.jpg|thumb]].",task_subcomment,"['From bug 49829 comment 0:\n\n| This is the DOM returned by the VE after inserting a new thumbnail:\n|
\n|
\n| \n| Note the \'undefined\' in the resource attribute.', ""The resource is the image\n| target, so we notice that the link and the image named 'undefined' differ and\n| serialize as\n| [[undefined|link=URL""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238613,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),*** Bug 49829 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49829 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238608,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"**winne2i** wrote: + +The same on plwiki: https://pl.wikipedia.org/w/index.php?diff=36790309 +(""prawo"" means ""right"" in polish, ""ramka"" means ""frame"")",task_subcomment,"['**winne2i** wrote:\n\nThe same on plwiki: URL\n(""prawo"" means ""right"" in polish, ""ramka"" means ""frame"")']",['OBSERVED BUG BEHAVIOR'] +238601,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"(In reply to comment #3) +> I get the same type of error: +> php?title=PLoS_ONE&diff=36119075&oldid=34872658> + +On this example there is also something else: I think the code ""direita,right"" should be just ""direita"" or ""right"".",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nOn this example there is also something else: I think the code ""direita,right"" should be just ""direita"" or ""right"".']",['MOTIVATION'] +238593,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),*** Bug 49795 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49795 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238587,VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),I get the same type of error: ,task_subcomment,['I get the same type of error: All events in Edit_5563071 appear to have the same value for +> event_pageViewSessionId (2147483647). + +It was simply overflowing its column type (int). I set it to 'bigint' and it's fine now. + +It's odd that we haven't run into this before! It's because we ordinarily convert timestamps to byte strings, like the rest of MediaWiki. This is the first time we've tried to save timestamps as integers. The int type is good for values between +/- 2,147,483,647, which has been adequate for all other use cases. + +> When fixing, we will want to bump the event_version value. + +Well, since this did not require a deployment, I instead moved all existing rows in the 'Edit' table to 'z_Edit_5563071'. Any events that go into the current 'Edit_5563071' will be fine.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\n\nIt was simply overflowing its column type (int).', ""I set it to 'bigint' and it's fine now."", ""It's odd that we haven't run into this before!"", ""It's because we ordinarily convert timestamps to byte strings, like the rest of MediaWiki."", ""This is the first time we've tried to save timestamps as integers."", 'The int type is good for values between +/- 2,147,483,647, which has been adequate for all other use cases.', ""QUOTE\n\nWell, since this did not require a deployment, I instead moved all existing rows in the 'Edit' table to 'z_Edit_5563071'."", ""Any events that go into the current 'Edit_5563071' will be fine.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +238081,VisualEditor: EventLogging gives the same pageViewSessionId for all edits,"All events in Edit_5563071 appear to have the same value for event_pageViewSessionId (2147483647). + +When fixing, we will want to bump the event_version value.",task_subcomment,"['All events in Edit_5563071 appear to have the same value for event_pageViewSessionId (2147483647).', 'When fixing, we will want to bump the event_version value.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +51585,VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour," + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]",['OBSERVED BUG BEHAVIOR'] +238056,VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour,Merged and we'll get this out on Monday so we can test it.,task_subcomment,"[""Merged and we'll get this out on Monday so we can test it.""]",['SOLUTION DISCUSSION'] +238049,VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour,Related URL: https://gerrit.wikimedia.org/r/68712 (Gerrit Change Iddb9eb9c64b55b25445ddf9e474d312b685978a6),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change Iddb9eb9c64b55b25445ddf9e474d312b685978a6)'],['OBSERVED BUG BEHAVIOR'] +238041,VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour,Related URL: https://gerrit.wikimedia.org/r/68712 (Gerrit Change Iddb9eb9c64b55b25445ddf9e474d312b685978a6),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change Iddb9eb9c64b55b25445ddf9e474d312b685978a6)'],['OBSERVED BUG BEHAVIOR'] +238030,VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour,"Coordination card on Trello: https://trello.com/c/xCkMEAY0 + +Reminder: anonymous editors are excluded from logging (we'll instrument the edit funnel for anons in July in preparation for the global launch).",task_subcomment,"[""Coordination card on Trello: URL\n\nReminder: anonymous editors are excluded from logging (we'll instrument the edit funnel for anons in July in preparation for the global launch).""]",['INVESTIGATION AND EXPLORATION'] +238023,VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour,"Needs also https://meta.wikimedia.org/wiki/Schema:Edit to be updated first, of course. :-)",task_subcomment,"['Needs also URL to be updated first, of course.', ':-)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +51577,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"I have edited the page w:cs:Banolo Blahnik and after saving HTML code was left at the page. See this revision: https://cs.wikipedia.org/w/index.php?title=Manolo_Blahnik&oldid=10415532 + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,"['New deployment of Parsoid leads to HTML insertion - needs deployed code reversion\n\nI have edited the page w:cs:Banolo Blahnik and after saving HTML code was left at the page.', 'See this revision: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +237552,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,*** Bug 50049 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50049 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +237549,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Yes, . It is apparently fixed.",task_subcomment,"['Yes, . Should I open a new bug?,task_subcomment,['It has the VisualEditor tag and was reported in the feedback page , but that edit was made today.",task_subcomment,['Not sure if this is related: Issue started ~ 11:37 UTC today per +> https://en.wikipedia.org/w/index. +> php?namespace=&tagfilter=visualeditor&title=Special%3ARecentChanges + +If that's really accurate *maybe* this has some relevance (posting here in case someone who knows more can do something with it): + +Jun 14 11:34:59 cerium puppet-agent[22506]: (/Stage[main]/Role::Cache::Parsoid/Varnish::Instance[parsoid-frontend]/Exec[load-new-vcl-file-frontend]) Triggered 'refresh' from 2 events +... +Jun 14 11:34:59 cerium puppet-agent[22506]: (/Stage[main]/Role::Cache::Parsoid/Varnish::Instance[parsoid-backend]/Exec[load-new-vcl-file]) Triggered 'refresh' from 2 events",task_subcomment,"[""(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nIf that's really accurate *maybe* this has some relevance (posting here in case someone who knows more can do something with it):\n\nJun 14 11:34:59 cerium puppet-agent[22506]: (/Stage[main]/Role::Cache::Parsoid/Varnish::Instance[parsoid-frontend]/Exec[load-new-vcl-file-frontend]) Triggered 'refresh' from 2 events\n...\nJun 14 11:34:59 cerium puppet-agent[22506]: (/Stage[main]/Role::Cache::Parsoid/Varnish::Instance[parsoid-backend]/Exec[load-new-vcl-file]) Triggered 'refresh' from 2 events""]",['OBSERVED BUG BEHAVIOR'] +237489,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Yes, first time I tried the new VisualEditor. My user page is live and I still left the HTML as an example. Tried a few more times to blank page with VE, it is real ugly. HTML leaks on HTML leaks on HTML leaks with each new save, http://www.mediawiki.org/w/index.php?title=User%3AHutchy68&diff=711244&oldid=711236",task_subcomment,"['Yes, first time I tried the new VisualEditor.', 'My user page is live and I still left the HTML as an example.', 'Tried a few more times to blank page with VE, it is real ugly.', 'HTML leaks on HTML leaks on HTML leaks with each new save, URL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +237483,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,This is occurring fairly widely and I have a lot of reports. Moving it up to highest priority (because frankly something being broken that is already deployed > anything we might /want/ deployed).,task_subcomment,"['This is occurring fairly widely and I have a lot of reports.', 'Moving it up to highest priority (because frankly something being broken that is already deployed > anything we might /want/ deployed).']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +237474,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,Issue started ~ 11:37 UTC today per https://en.wikipedia.org/w/index.php?namespace=&tagfilter=visualeditor&title=Special%3ARecentChanges,task_subcomment,['Issue started ~ 11:37 UTC today per URL'],['OBSERVED BUG BEHAVIOR'] +237461,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"More of this: + +https://de.wikipedia.org/w/index.php?title=Oper_K%C3%B6ln&curid=2386780&diff=119548868&oldid=118354900 + +https://test.wikipedia.org/w/index.php?title=User:Raymond/image&diff=174443&oldid=174442",task_subcomment,['More of this:\n\nURL\n\nURL'],['OBSERVED BUG BEHAVIOR'] +237449,New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,*** Bug 49573 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49573 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +51403,VisualEditor: En hard-coded as TemplateData fetch language,"Should be user interface language. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor: En hard-coded as TemplateData fetch language\n\nShould be user interface language.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +251531,VisualEditor: En hard-coded as TemplateData fetch language,"This is resolved in the latest version + +I3bcf924a3e179cb65f19e833277a39dfd3dad8bd",task_subcomment,['This is resolved in the latest version\n\nI3bcf924a3e179cb65f19e833277a39dfd3dad8bd'],['WORKAROUNDS'] +51258,"VisualEditor: Move back to ""normal"" Save dialog with optional rather than mandatory Review","This is to restore the pre-December save workflow (Save dialog triggered, with Show Changes within it). + +The ""Review and Save"" button in the toolbar will be replaced with ""Save..."" which takes you straight to the Save dialog (with the existing save box, minor edit, watch and disclaimer/legal) + +Inside the Save dialog there should also be a ""Review changes"" button that triggers the wikitext diff as a dismissible dialog; whilst we're here, remove the Parsoid ""Something looks wrong"" button entirely, and replace the ""Looks good to me"" button with a normal close one. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Move back to ""normal"" Save dialog with optional rather than mandatory Review\n\nThis is to restore the pre-December save workflow (Save dialog triggered, with Show Changes within it).', 'The ""Review and Save"" button in the toolbar will be replaced with ""Save..."" which takes you straight to the Save dialog (with the existing save box, minor edit, watch and disclaimer/legal)\n\nInside the Save dialog there should also be a ""Review changes"" button that triggers the wikitext diff as a dismissible dialog; whilst we\'re here, remove the Parsoid ""Something looks wrong"" button entirely, and replace the ""Looks good to me"" button with a normal close one.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +242592,"VisualEditor: Move back to ""normal"" Save dialog with optional rather than mandatory Review",Fixed and will go out with wmf7 from next Thursday.,task_subcomment,['Fixed and will go out with wmf7 from next Thursday.'],['SOLUTION USAGE'] +50769,VisualEditor: Link corruption oddity in production on links (Parsoid issue?)," + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://pl.wikipedia.org/w/index.php?title=Ukryta_sie%C4%87&diff=36500666&oldid=36500549 +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50720",task_description,"['VisualEditor: Link corruption oddity in production on links (Parsoid issue?)', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +218104,VisualEditor: Link corruption oddity in production on links (Parsoid issue?),I believe this is now fixed.,task_subcomment,['I believe this is now fixed.'],['BUG REPRODUCTION'] +218095,VisualEditor: Link corruption oddity in production on links (Parsoid issue?),Can't reproduce in master.,task_subcomment,"[""Can't reproduce in master.""]",['OBSERVED BUG BEHAVIOR'] +50526,VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox,"1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox\n\n1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +228977,VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox,This is not an issue anymore.,task_subcomment,['This is not an issue anymore.'],['ACTION ON ISSUE'] +50509,VisualEditor: [Regression] Link inspector button doesn't work,"1. Create a link using the link inspector button +2. Note that autocomplete feature doesn't appear +3. Hit save and note that link is stored as an external link ""[Foo Foo]"" + +Using the keyboard shortcut, however, works fine (Ctrl+K) + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: [Regression] Link inspector button doesn't work\n\n1."", 'Create a link using the link inspector button\n2.', ""Note that autocomplete feature doesn't appear\n3."", 'Hit save and note that link is stored as an external link ""[Foo Foo]""\n\nUsing the keyboard shortcut, however, works fine (Ctrl+K)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['1.', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +228003,VisualEditor: [Regression] Link inspector button doesn't work,Merged into master; will go out with wmf5.,task_subcomment,['Merged into master; will go out with wmf5.'],['SOLUTION USAGE'] +227998,VisualEditor: [Regression] Link inspector button doesn't work,Related URL: https://gerrit.wikimedia.org/r/63850 (Gerrit Change Icda3305e422bedaf0d490b8fbe51f55b8c8e79e8),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change Icda3305e422bedaf0d490b8fbe51f55b8c8e79e8)'],['OBSERVED BUG BEHAVIOR'] +227992,VisualEditor: [Regression] Link inspector button doesn't work,"Looks like the format for providing toolbar options was changed, so the MW override isn't working. As a result we're rendering a link button instead of an mwLink. Ctrl+K works because the mwLink is still registered with the command registry (should commands work without the button being rendered?)",task_subcomment,"[""Looks like the format for providing toolbar options was changed, so the MW override isn't working."", ""As a result we're rendering a link button instead of an mwLink."", 'Ctrl+K works because the mwLink is still registered with the command registry (should commands work without the button being rendered?)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +50468,VisualEditor: Pawn appears when creating new list item in Firefox,"1. Go to a page with a bullet or a numbered list. Edit with VisualEditor. + +2. Place the cursor at the end of an item of the list. Press enter to create a new item. A new item has been created and the cursor is at the beginning, ready to receive input. + +3. Type something. + +EXPECTED + +You are typing in the new line. + + +ACTUAL OUTCOME + +A pawn appears at the end of the previous line and there you can also find the text you are typing. If you press Enter again the mess continues to grow. There is no way to clean the scene of the crime. The only way is to jump to ""Edit source"". + +This happens at least at mediawiki.org with Firefox 22.0a2 (2013-05-07). + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor: Pawn appears when creating new list item in Firefox\n\n1.', 'Go to a page with a bullet or a numbered list.', 'Edit with VisualEditor.', '2.', 'Place the cursor at the end of an item of the list.', 'Press enter to create a new item.', 'A new item has been created and the cursor is at the beginning, ready to receive input.', '3.', 'Type something.', 'EXPECTED\n\nYou are typing in the new line.', 'ACTUAL OUTCOME \n\nA pawn appears at the end of the previous line and there you can also find the text you are typing.', 'If you press Enter again the mess continues to grow.', 'There is no way to clean the scene of the crime.', 'The only way is to jump to ""Edit source"".', 'This happens at least at mediawiki.org with Firefox 22.0a2 (2013-05-07).', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +225176,VisualEditor: Pawn appears when creating new list item in Firefox,"Solid like a rock! + +https://www.mediawiki.org/w/index.php?title=User%3AQgil%2FSandbox&diff=710845&oldid=710844 + +Thank you very much. The bug I filed has been fixed. Resolving accordingly.",task_subcomment,"['Solid like a rock!', 'URL\n\nThank you very much.', 'The bug I filed has been fixed.', 'Resolving accordingly.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +225170,VisualEditor: Pawn appears when creating new list item in Firefox,@Quim: Are you still able to reproduce this problem? I can't.,task_subcomment,"['SCREEN_NAME: Are you still able to reproduce this problem?', ""I can't.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +225163,VisualEditor: Pawn appears when creating new list item in Firefox,"I'm getting similar behaviour on en.wp if you use the slug at the beginning of the article, then change your mind and try to delete the text you've inserted. General behaviour with slug lines?",task_subcomment,"[""I'm getting similar behaviour on en.wp if you use the slug at the beginning of the article, then change your mind and try to delete the text you've inserted."", 'General behaviour with slug lines?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +50390,VisualEditor: Indenting & unindenting multiple list items fails,"Problems in IndentationAction that Ed it working on right now. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['VisualEditor: Indenting & unindenting multiple list items fails\n\nProblems in IndentationAction that Ed it working on right now.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +220747,VisualEditor: Indenting & unindenting multiple list items fails,Code is merged into wmf4.,task_subcomment,['Code is merged into wmf4.'],['INVESTIGATION AND EXPLORATION'] +220742,VisualEditor: Indenting & unindenting multiple list items fails,Related URL: https://gerrit.wikimedia.org/r/63485 (Gerrit Change I5ce0c385214f30c5e5c66b5b5b755c9937267cd0),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I5ce0c385214f30c5e5c66b5b5b755c9937267cd0)'],['OBSERVED BUG BEHAVIOR'] +220736,VisualEditor: Indenting & unindenting multiple list items fails,*** Bug 48069 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 48069 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +220731,VisualEditor: Indenting & unindenting multiple list items fails,"Problem here was with surface fragments and translate range in the data model. The ranges were getting out of sync, so after (un)indenting the first item, and subsequent ones would fail.",task_subcomment,"['Problem here was with surface fragments and translate range in the data model.', 'The ranges were getting out of sync, so after (un)indenting the first item, and subsequent ones would fail.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +220724,VisualEditor: Indenting & unindenting multiple list items fails,Fixed by https://gerrit.wikimedia.org/r/#/c/63394/,task_subcomment,['Fixed by URL'],['SOLUTION DISCUSSION'] +50386,VisualEditor: [Regression] Lists badly broken again," + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,['VisualEditor: [Regression] Lists badly broken again\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical'],['OBSERVED BUG BEHAVIOR'] +220417,VisualEditor: [Regression] Lists badly broken again,"verified for any page in http://en.wikipedia.beta.wmflabs.org/ +using Chrome Version 26.0.1410.65 MAC OS X 10.8.5",task_subcomment,['verified for any page in URL\nusing Chrome Version 26.0.1410.65 MAC OS X 10.8.5'],['OBSERVED BUG BEHAVIOR'] +220413,VisualEditor: [Regression] Lists badly broken again,Fixed in https://gerrit.wikimedia.org/r/63413. Will close after it gets merged.,task_subcomment,"['Fixed in GERRIT_URL.', 'Will close after it gets merged.']","['SOLUTION USAGE', 'ACTION ON ISSUE']" +220410,VisualEditor: [Regression] Lists badly broken again,Related URL: https://gerrit.wikimedia.org/r/63413 (Gerrit Change I8d7aeffc8166487806e3489b054f508c5e9418ff),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I8d7aeffc8166487806e3489b054f508c5e9418ff)'],['OBSERVED BUG BEHAVIOR'] +220407,VisualEditor: [Regression] Lists badly broken again,"By stepping back through the commit log I've isolated it down to this commit by Inez: https://gerrit.wikimedia.org/r/#/c/63223/1 + +Assigning the bug to him.",task_subcomment,"[""By stepping back through the commit log I've isolated it down to this commit by Inez: URL\n\nAssigning the bug to him.""]",['BUG REPRODUCTION'] +220404,VisualEditor: [Regression] Lists badly broken again,"1. Hitting return inside a list item cases the paragraph to split, not the listitem (that's what shift-return should do) +2. Unlisting the two line list item created in 1. causes the second line to completely disappear +3. Listing two paragraphs only lists the first one, and adds an extra paragraph between them",task_subcomment,"['1.', ""Hitting return inside a list item cases the paragraph to split, not the listitem (that's what shift-return should do)\n2."", 'Unlisting the two line list item created in 1. causes the second line to completely disappear\n3.', 'Listing two paragraphs only lists the first one, and adds an extra paragraph between them']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +50385,VisualEditor: Delete contents of slugged paragraph results in double line break visible,"* Create a page starting with a list ('* list' is sufficient) +* Enter some text into the slugged paragraph above the list, then delete it with backspaces +* The paragraph now doubles in height, inspecting the DOM you see a
has appeared from nowhere: +


+ +Also this paragraph gets sent to Parsoid resulting in an extra line break. + +Removing the text by using undo doesn't result in this bug. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: Delete contents of slugged paragraph results in double line break visible\n\n* Create a page starting with a list ('* list' is sufficient)\n* Enter some text into the slugged paragraph above the list, then delete it with backspaces\n* The paragraph now doubles in height, inspecting the DOM you see a
has appeared from nowhere:\n


\n\nAlso this paragraph gets sent to Parsoid resulting in an extra line break."", ""Removing the text by using undo doesn't result in this bug."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +220362,VisualEditor: Delete contents of slugged paragraph results in double line break visible,This is fixed with my refactor to handleDelete method.,task_subcomment,['This is fixed with my refactor to handleDelete method.'],['SOLUTION DISCUSSION'] +220359,VisualEditor: Delete contents of slugged paragraph results in double line break visible,Deeming that this is now fixed.,task_subcomment,['Deeming that this is now fixed.'],['ACTION ON ISSUE'] +220355,VisualEditor: Delete contents of slugged paragraph results in double line break visible,"(In reply to comment #1) +> We are not placing slugs around lists anymore so this bug can't be +> reproduced, however I know what was root cause of it (native handling of +> deletion) and I'm working on it now. + +Is this bug still valid? I can't reproduce now, using a thumb image (rather than a list) to create the block item.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\n\nIs this bug still valid?', ""I can't reproduce now, using a thumb image (rather than a list) to create the block item.""]","['ACTION ON ISSUE', 'BUG REPRODUCTION']" +220351,VisualEditor: Delete contents of slugged paragraph results in double line break visible,"We are not placing slugs around lists anymore so this bug can't be reproduced, however I know what was root cause of it (native handling of deletion) and I'm working on it now.",task_subcomment,"[""We are not placing slugs around lists anymore so this bug can't be reproduced, however I know what was root cause of it (native handling of deletion) and I'm working on it now.""]",['BUG REPRODUCTION'] +50346,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","Lately, I've been noticing random pawn characters at the end of paragraphs all over English Wikipedia. The source of these pawns was a mystery to me until I tried using the Visual Editor today. As soon as I started typing in the editor, it inserted a pawn at the end of the line I was editing. + +The pawn in question is the white pawn, typically the first piece to move in a game of chess. This makes me wonder if perhaps the visual editor has become sentient and is trying to initiate a friendly game with the editor. Unfortunately, playing chess on Wikipedia was banned in 2006 as a violation of WP:NOT,[1] so it's probably a good idea if we eliminate this sort of behavior. + +Actual character: ♙ +Unicode value: 2659 +UTF-8 value: E2 99 99 +Browser: Firefox + +1. https://en.wikipedia.org/wiki/Wikipedia:Miscellany_for_deletion/Wikipedia:Chess_championship + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,"[""VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption\n\nLately, I've been noticing random pawn characters at the end of paragraphs all over English Wikipedia."", 'The source of these pawns was a mystery to me until I tried using the Visual Editor today.', 'As soon as I started typing in the editor, it inserted a pawn at the end of the line I was editing.', 'The pawn in question is the white pawn, typically the first piece to move in a game of chess.', 'This makes me wonder if perhaps the visual editor has become sentient and is trying to initiate a friendly game with the editor.', ""Unfortunately, playing chess on Wikipedia was banned in 2006 as a violation of WP:NOT,[1] so it's probably a good idea if we eliminate this sort of behavior."", 'Actual character: ♙\nUnicode value: 2659\nUTF-8 value: E2 99 99\nBrowser: Firefox\n\n1.', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOCIAL CONVERSATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +218164,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","verified for any page https://test2.wikipedia.org/ + +using chrome Version 26.0.1410.65 and firefox 25.",task_subcomment,['verified for any page URL\n\nusing chrome Version 26.0.1410.65 and firefox 25.'],['OBSERVED BUG BEHAVIOR'] +218157,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption",Confirming that this is fixed in master and wmf4; deployed in the normal deployment train.,task_subcomment,['Confirming that this is fixed in master and wmf4; deployed in the normal deployment train.'],['BUG REPRODUCTION'] +218151,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","(In reply to comment #4) +> Pawn insertion from May 3: +> https://en.wikipedia.org/w/index. +> php?title=Rubik%27s_360&diff=553360286&oldid=540708795 + +These kind of issues are precisely why there's a mandatory pre-save diff for users to read and agree it's fine. If there's a pawn inserted into the article, you're not meant to press save!",task_subcomment,"[""(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\n\nThese kind of issues are precisely why there's a mandatory pre-save diff for users to read and agree it's fine."", ""If there's a pawn inserted into the article, you're not meant to press save!""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +218145,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","(In reply to comment #1) +> Steps to reproduce: +> 1. Log in and turn on the visual editor. +> 2. Go to a random article like ""Sundance Meadows Airport"" +> 3. Click the Edit tab +> 4. After the cursor appears on the page, type a character +> +> You will then see a white pawn at the end of the line of text you are +> editing. + +Thanks; have updated the bug report accordingly. + +> Interestingly, it only seems to happen on articles that insert the cursor +> into a blank line at the top of the article. I'm not sure what determines +> that behavior, but it seems to be the behavior for the vast majority of +> en.wiki articles. + +That is bug 47790. It's not really a blank line in the document; it's the ""potential"" place to insert some new content, until you click into it and insert some, at which point it's whatever you type in. But it's not really very obvious to users what it is. + +> The only article I haven't been able to reproduce the bug at so far +> is Lalage: +> https://en.wikipedia.org/wiki/Lalage + +A block-level slug only appears if the page starts with a template or other kind of generated content; any page that starts with one will get one (hence the pervasiveness). The alternative is not giving users the ability to insert content before a template if it happened to be at the start of a document, which would be even more confusing.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThanks; have updated the bug report accordingly.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat is bug 47790.', 'It\'s not really a blank line in the document; it\'s the ""potential"" place to insert some new content, until you click into it and insert some, at which point it\'s whatever you type in.', ""But it's not really very obvious to users what it is."", 'QUOTE\nQUOTE\nQUOTE\n\nA block-level slug only appears if the page starts with a template or other kind of generated content; any page that starts with one will get one (hence the pervasiveness).', 'The alternative is not giving users the ability to insert content before a template if it happened to be at the start of a document, which would be even more confusing.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +218139,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","Can't reproduce this is master. It may have already been fixed, pending release?",task_subcomment,"[""Can't reproduce this is master."", 'It may have already been fixed, pending release?']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']" +218135,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","**fran** wrote: + +Pawn ahoy: https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=modules/ve/ce/ve.ce.Surface.js;h=7ad07c54370cb585ca264f78872fee0c83bd77a5;hb=HEAD#l1009 + +""git blame"" says this section was worked on by Christian Williams, so maybe he'll know what's going on?",task_subcomment,"['**fran** wrote:\n\nPawn ahoy: URL\n\n""git blame"" says this section was worked on by Christian Williams, so maybe he\'ll know what\'s going on?']",['SOLUTION DISCUSSION'] +218130,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","Pawn insertion from May 3: +https://en.wikipedia.org/w/index.php?title=Rubik%27s_360&diff=553360286&oldid=540708795",task_subcomment,['Pawn insertion from May 3:\nURL'],['OBSERVED BUG BEHAVIOR'] +218124,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption",Confirmed in Safari and Chrome as well.,task_subcomment,['Confirmed in Safari and Chrome as well.'],['OBSERVED BUG BEHAVIOR'] +218117,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","I also can't reproduce the bug in my user sandbox: +https://en.wikipedia.org/wiki/User:Kaldari/sandbox",task_subcomment,"[""I also can't reproduce the bug in my user sandbox:\nURL""]",['BUG REPRODUCTION'] +218111,"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption","Steps to reproduce: +1. Log in and turn on the visual editor. +2. Go to a random article like ""Sundance Meadows Airport"" +3. Click the Edit tab +4. After the cursor appears on the page, type a character + +You will then see a white pawn at the end of the line of text you are editing. + +Interestingly, it only seems to happen on articles that insert the cursor into a blank line at the top of the article. I'm not sure what determines that behavior, but it seems to be the behavior for the vast majority of en.wiki articles. The only article I haven't been able to reproduce the bug at so far is Lalage: +https://en.wikipedia.org/wiki/Lalage",task_subcomment,"['Steps to reproduce:\n1.', 'Log in and turn on the visual editor.', '2.', 'Go to a random article like ""Sundance Meadows Airport""\n3.', 'Click the Edit tab\n4.', 'After the cursor appears on the page, type a character\n\nYou will then see a white pawn at the end of the line of text you are editing.', 'Interestingly, it only seems to happen on articles that insert the cursor into a blank line at the top of the article.', ""I'm not sure what determines that behavior, but it seems to be the behavior for the vast majority of en.wiki articles."", ""The only article I haven't been able to reproduce the bug at so far is Lalage:\nURL""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +50287,VisualEditor: Aborted empty list creates a pawn,"Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services +Put the cursor somewhere in the text. +Type ""Enter"" 2 times. +Type ""Up"". +Click Bullet List +Type Enter +Type Up +Type Delete + +Wild pawn appears. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Aborted empty list creates a pawn\n\nGo to URL\nPut the cursor somewhere in the text.', 'Type ""Enter"" 2 times.', 'Type ""Up"".', 'Click Bullet List\nType Enter\nType Up\nType Delete\n\nWild pawn appears.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +214464,VisualEditor: Aborted empty list creates a pawn,Merged into master; will be deployed from Monday.,task_subcomment,['Merged into master; will be deployed from Monday.'],['ACTION ON ISSUE'] +214458,VisualEditor: Aborted empty list creates a pawn,"(In reply to comment #3) +> Related URL: https://gerrit.wikimedia.org/r/63102 (Gerrit Change +> If22d9b904b8861e24d56944d791545635b2e4254) + +Merged.",task_subcomment,['(In reply to comment #3)\nQUOTE\nQUOTE\n\nMerged.'],['SOLUTION USAGE'] +214450,VisualEditor: Aborted empty list creates a pawn,Related URL: https://gerrit.wikimedia.org/r/63102 (Gerrit Change If22d9b904b8861e24d56944d791545635b2e4254),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change If22d9b904b8861e24d56944d791545635b2e4254)'],['OBSERVED BUG BEHAVIOR'] +214441,VisualEditor: Aborted empty list creates a pawn,"I can reproduce in Firefox and Chrome if you forwards-delete or insert characters. It appears that this is because when you clear out the
  • (return at the end of the list) it doesn't check that the
    • is wrapped in a . Not really WYSIWYG… + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11257}",task_description,"['VisualEditor: uneditable table lines displayed wrong\n\nThe displayed table (Firefox 22/Ubuntu)\n\nSee [[fr:Special:redirect/revision/95505705#Pr.C3.A9sidents_de_l.27universit.C3.A9]]\n\nThe lines of the table using {{ligne grise}} are uneditable because of {{ligne grise}} (which just adds bgcolor=""#F2F2F2""…).', 'But they are displayed wrong (see attachment) because the is wrapped in a .', 'Not really WYSIWYG…\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11257}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +236722,VisualEditor: uneditable table lines displayed wrong,"Yes, merging with bug 50607. + +*** This bug has been marked as a duplicate of bug 50607 ***",task_subcomment,"['Yes, merging with bug 50607.', '*** This bug has been marked as a duplicate of bug 50607 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +236716,VisualEditor: uneditable table lines displayed wrong,I think this might be a duplicate of bug 50607,task_subcomment,['I think this might be a duplicate of bug 50607'],['BUG REPRODUCTION'] +54478,References created by Singlechart cannot be accessed properly,"**Author:** `kwwilliams` + +**Description:** +http://en.wikipedia.org/wiki/User:Kww/singlechartreftest is a simple test case for accessing references created by the singlechart template. + +Singlechart directly creates references when called, using #ref (it cannot use tags because of issues involving the parsing sequence of templates and references). It will either create them with a default name that it generates algorithmically, or it will use the value of the ""refname"" parameter. + +When editing http://en.wikipedia.org/wiki/User:Kww/singlechartreftest, if the editor attempts to insert reference and chooses the option to ""use an existing reference"", three of the existing named references (sc_BillboardHot100_The Hollies, sc_Norwegian_The Hollies, and sc_Dutch100_The Hollies) aren't displayed at all. These are references that are available for the editor to use, but have not been currently reused in the article text. An examination of http://parsoid.wmflabs.org/en/User:Kww/singlechartreftest shows that Parsoid did pick up these names so VE should be able to display them. + +sc_UK_Hollies is displayed, but no text is associated with it. Similarly with germancharts. Attempting to include these references works. Both of these references should have the full reference text displayed, although the editor should not be permitted to alter it. + +{{Certification Table Entry}} and {{albumchart}} should have identical problems. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['References created by Singlechart cannot be accessed properly\n\n**Author:** CODE\n\n**Description:**\nURL is a simple test case for accessing references created by the singlechart template.', 'Singlechart directly creates references when called, using #ref (it cannot use tags because of issues involving the parsing sequence of templates and references).', 'It will either create them with a default name that it generates algorithmically, or it will use the value of the ""refname"" parameter.', 'When editing URL if the editor attempts to insert reference and chooses the option to ""use an existing reference"", three of the existing named references (sc_BillboardHot100_The Hollies, sc_Norwegian_The Hollies, and sc_Dutch100_The Hollies) aren\'t displayed at all.', 'These are references that are available for the editor to use, but have not been currently reused in the article text.', 'An examination of URL shows that Parsoid did pick up these names so VE should be able to display them.', 'sc_UK_Hollies is displayed, but no text is associated with it.', 'Similarly with germancharts.', 'Attempting to include these references works.', 'Both of these references should have the full reference text displayed, although the editor should not be permitted to alter it.', '{{Certification Table Entry}} and {{albumchart}} should have identical problems.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +236424,References created by Singlechart cannot be accessed properly,"Is {{#tag:ref}} something that is part of MediaWiki or something user-generated? If it's part of MediaWiki, presumably its creation and deployment is an indication that it's meant to work.",task_subcomment,"['Is {{#tag:ref}} something that is part of MediaWiki or something user-generated?', ""If it's part of MediaWiki, presumably its creation and deployment is an indication that it's meant to work.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +236417,References created by Singlechart cannot be accessed properly,"**kwwilliams** wrote: + +That response is beyond the pale. Please retract it, and concentrate on building an editor that functions within the environment that exists, not the environment that you wish existed.",task_subcomment,"['**kwwilliams** wrote:\n\nThat response is beyond the pale.', 'Please retract it, and concentrate on building an editor that functions within the environment that exists, not the environment that you wish existed.']","['SOCIAL CONVERSATION', 'SOLUTION DISCUSSION']" +236409,References created by Singlechart cannot be accessed properly,"This is a duplicate of bug 50474 - in general, any reference created by a template shouldn't work, deliberately. Hacks using {{#tag:ref}} which was never meant to work are a nightmare for users and VisualEditor alike. + +*** This bug has been marked as a duplicate of bug 50474 ***",task_subcomment,"[""This is a duplicate of bug 50474 - in general, any reference created by a template shouldn't work, deliberately."", 'Hacks using {{#tag:ref}} which was never meant to work are a nightmare for users and VisualEditor alike.', '*** This bug has been marked as a duplicate of bug 50474 ***']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +54467,"VisualEditor: if the title page starts with a dot, VE won't load","http://en.wikipedia.org/wiki/.tl for instance, +if you click on the Edit tab, nothing will happen. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: if the title page starts with a dot, VE won't load\n\nURL for instance,\nif you click on the Edit tab, nothing will happen."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +235784,"VisualEditor: if the title page starts with a dot, VE won't load"," + +*** This bug has been marked as a duplicate of bug 51308 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51308 ***'],['ISSUE CONTENT MANAGEMENT'] +235781,"VisualEditor: if the title page starts with a dot, VE won't load","(I believe I just duplicated https://bugzilla.wikimedia.org/show_bug.cgi?id=51308, sorry about that).",task_subcomment,['(I believe I just duplicated URL sorry about that).'],['SOLUTION DISCUSSION'] +54433,VisualEditor: Toolbar not returning under the tabs,"Toolbar mixed with #p-personal + +See the image. And I got the opposite, the toolbar staying at top of the article. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=52504 +https://bugzilla.wikimedia.org/show_bug.cgi?id=52326 + +**Attached**: {F11123}",task_description,"['VisualEditor: Toolbar not returning under the tabs\n\nToolbar mixed with #p-personal\n\nSee the image.', 'And I got the opposite, the toolbar staying at top of the article.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\n\n**Attached**: {F11123}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +233850,VisualEditor: Toolbar not returning under the tabs,"This is a duplicate of Bug 52441 which is fixed but not yet deployed + +*** This bug has been marked as a duplicate of bug 52441 ***",task_subcomment,['This is a duplicate of Bug 52441 which is fixed but not yet deployed\n\n*** This bug has been marked as a duplicate of bug 52441 ***'],['ACTION ON ISSUE'] +54431,VisualEditor: {{clr}} prevents user from editing content,"1. Got to [[fr:Disjonction logique]] +2. Edit it with VisualEditor +3. Try to modify the table. You will get a big blue rectangle allowing to edit {{clr}}, but you can’t edit directly (clicking on headings and using ↓ works) the at their end display it, confusing users\n\nSee URL - the first three (but strangely, not the last) discography tables.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +244543,"VisualEditor: Tables with a faulty at their end display it, confusing users","(In reply to comment #5) +> (In reply to comment #4) +> > This is a Parsoid bug. The PHP parser does not generate a for this +> > wikitext, and Parsoid does. +> +> Does the PHP parser create it but it then gets tidied away? +That's possible, I haven't checked what happens when Tidy is disabled.",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nThat's possible, I haven't checked what happens when Tidy is disabled.""]",['INVESTIGATION AND EXPLORATION'] +244534,"VisualEditor: Tables with a faulty at their end display it, confusing users","(In reply to comment #4) +> This is a Parsoid bug. The PHP parser does not generate a for this +> wikitext, and Parsoid does. + +Does the PHP parser create it but it then gets tidied away?",task_subcomment,['(In reply to comment #4)\nQUOTE\nQUOTE\n\nDoes the PHP parser create it but it then gets tidied away?'],['INVESTIGATION AND EXPLORATION'] +244526,"VisualEditor: Tables with a faulty at their end display it, confusing users","This is a Parsoid bug. The PHP parser does not generate a for this wikitext, and Parsoid does.",task_subcomment,"['This is a Parsoid bug.', 'The PHP parser does not generate a for this wikitext, and Parsoid does.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +244519,"VisualEditor: Tables with a faulty at their end display it, confusing users","(In reply to comment #2) +> Makes sense. Alternately would it be possible to add it in as a rule to +> Parsoid's voodo wikimarkup-fixing stuff? If a |- is followed by nothing and +> then a |}... + +But some gadgets might rely on that meaning something special for some users. Everything we change or ""fix"" potentially breaks things for some (other) users. :-(",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nBut some gadgets might rely on that meaning something special for some users.', 'Everything we change or ""fix"" potentially breaks things for some (other) users.', ':-(']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +244513,"VisualEditor: Tables with a faulty at their end display it, confusing users",Makes sense. Alternately would it be possible to add it in as a rule to Parsoid's voodo wikimarkup-fixing stuff? If a |- is followed by nothing and then a |}...,task_subcomment,"['Makes sense.', ""Alternately would it be possible to add it in as a rule to Parsoid's voodo wikimarkup-fixing stuff?"", 'If a |- is followed by nothing and then a |}...']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +244508,"VisualEditor: Tables with a faulty at their end display it, confusing users","This is not a bug (well, it's not a bug with VE :-)) - the three ""broken"" tables all have + + |- + | + |- + |} + +… at the end, which is not the case for the third ""working"" one. What you see is the result of broken wikitext. + +VE is good, but it can't be psychic about what you wanted to do with that that extra table row (maybe you wanted to expand the table and were half-way through?) so behaviour is ""as intended"". Marking as INVALID; in general broken wikitext like this can't be trivially fixed by a bot, due to wikitext's complexities, but it might be worth exploring.",task_subcomment,"['This is not a bug (well, it\'s not a bug with VE :-)) - the three ""broken"" tables all have \n\n |-\n | \n |-\n |}\n\n… at the end, which is not the case for the third ""working"" one.', 'What you see is the result of broken wikitext.', ""VE is good, but it can't be psychic about what you wanted to do with that that extra table row (maybe you wanted to expand the table and were half-way through?)"", 'so behaviour is ""as intended"".', ""Marking as INVALID; in general broken wikitext like this can't be trivially fixed by a bot, due to wikitext's complexities, but it might be worth exploring.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +51687,VisualEditor: Template displaying in the incorrect language,"See the bottom of https://en.wikipedia.org/wiki/Chad_Griffin for example - it also occurs at https://en.wikipedia.org/wiki/3rd_Brahmans and https://en.wikipedia.org/wiki/In_re_Estate_of_Gardiner (each time in a different language; Russian, Vietnamese and French respectively). + +I have no idea what's going on, but this seems pretty important to solve for. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Template displaying in the incorrect language\n\nSee the bottom of URL for example - it also occurs at URL and URL (each time in a different language; Russian, Vietnamese and French respectively).', ""I have no idea what's going on, but this seems pretty important to solve for."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +244274,VisualEditor: Template displaying in the incorrect language,"This is previously reported (and also they think fixed). + +*** This bug has been marked as a duplicate of bug 49411 ***",task_subcomment,"['This is previously reported (and also they think fixed).', '*** This bug has been marked as a duplicate of bug 49411 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +51684,VisualEditor: nowiki tags added to references (and references split up (and content dropped)),"An example is https://en.wikipedia.org/w/index.php?title=Valotte&diff=559961373&oldid=559939306 - another is https://en.wikipedia.org/w/index.php?title=The_Day_the_World_Gets_%27Round&diff=559962523&oldid=559851975 where the VisualEditor seems to have taken it upon itself to drop content and convert templates into pure reference tags + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,['VisualEditor: nowiki tags added to references (and references split up (and content dropped))\n\nAn example is URL - another is URL where the VisualEditor seems to have taken it upon itself to drop content and convert templates into pure reference tags\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR'] +243906,VisualEditor: nowiki tags added to references (and references split up (and content dropped)),[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +243902,VisualEditor: nowiki tags added to references (and references split up (and content dropped)),"The {{#tag:ref|…}} issues should now be fixed in production. + +The specific issues of adding s around wiki-able elements of tables is also, I believe, fixed in production. + +s around wikitext are, of course, intentional.",task_subcomment,"['The {{#tag:ref|…}} issues should now be fixed in production.', 'The specific issues of adding s around wiki-able elements of tables is also, I believe, fixed in production.', 's around wikitext are, of course, intentional.']","['SOLUTION USAGE', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']" +243898,VisualEditor: nowiki tags added to references (and references split up (and content dropped)),Nowiki tags are also being entered around elements of tables - see https://en.wikipedia.org/w/index.php?title=Guy_McKenna&curid=1748898&diff=560026334&oldid=560026013,task_subcomment,['Nowiki tags are also being entered around elements of tables - see URL'],['OBSERVED BUG BEHAVIOR'] +51683,VisualEditor: Unexpected padding,"See the tabs on https://en.wikipedia.org/wiki/User:Panpog1 for example. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Unexpected padding\n\nSee the tabs on URL for example.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +243852,VisualEditor: Unexpected padding,Fixed.,task_subcomment,['Fixed.'],['SOLUTION USAGE'] +51643,UniversalLanguageSelector Does not work with VisualEditor,"**Author:** `bellayet` + +**Description:** +At bn Wikipedia ULS does not working with recently added VisualEditor beta. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['UniversalLanguageSelector Does not work with VisualEditor\n\n**Author:** CODE\n\n**Description:**\nAt bn Wikipedia ULS does not working with recently added VisualEditor beta.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +241617,UniversalLanguageSelector Does not work with VisualEditor,"True, thanks for reporting. Despite the mysterious bug summary, this is known as bug 49569 :) and is being actively worked on as GSoC project. + +*** This bug has been marked as a duplicate of bug 49569 ***",task_subcomment,"['True, thanks for reporting.', 'Despite the mysterious bug summary, this is known as bug 49569 :) and is being actively worked on as GSoC project.', '*** This bug has been marked as a duplicate of bug 49569 ***']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +241610,UniversalLanguageSelector Does not work with VisualEditor,"**bellayet** wrote: + +ULS Input tool is not supporting VisualEditor.",task_subcomment,['**bellayet** wrote:\n\nULS Input tool is not supporting VisualEditor.'],['OBSERVED BUG BEHAVIOR'] +51637,VisualEditor bugzilla component should be under MediaWiki extensions,"I failed to find it under extensions where I was expecting it to be. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor bugzilla component should be under MediaWiki extensions\n\nI failed to find it under extensions where I was expecting it to be.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +241253,VisualEditor bugzilla component should be under MediaWiki extensions,"(In reply to comment #6) +> To be fair the bug summary is rather generic. It would make sense to have a +> placeholder under ""MediaWiki extensions"", or maybe a mention of the product +> somewhere. + +The plan is to split the codebase after the beta deployment in a few weeks' time into ""VisualEditor core"" and ""a MediaWiki plug-in that uses this foreign library called VisualEditor"". + +At that point, it might make sense to re-activate ""MediaWiki extensions > VisualEditor"", if only because that's where people might look for it; I'm happy to triage bugs in two places. In practice you'd likely have most bugs for MW-VE be dependent on VE-core bugs, but that's still manageable. + +@Andre, thoughts on this?",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nThe plan is to split the codebase after the beta deployment in a few weeks\' time into ""VisualEditor core"" and ""a MediaWiki plug-in that uses this foreign library called VisualEditor"".', 'At that point, it might make sense to re-activate ""MediaWiki extensions > VisualEditor"", if only because that\'s where people might look for it; I\'m happy to triage bugs in two places.', ""In practice you'd likely have most bugs for MW-VE be dependent on VE-core bugs, but that's still manageable."", 'SCREEN_NAME, thoughts on this?']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +241243,VisualEditor bugzilla component should be under MediaWiki extensions,"To be fair the bug summary is rather generic. It would make sense to have a placeholder under ""MediaWiki extensions"", or maybe a mention of the product somewhere.",task_subcomment,"['To be fair the bug summary is rather generic.', 'It would make sense to have a placeholder under ""MediaWiki extensions"", or maybe a mention of the product somewhere.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +241237,VisualEditor bugzilla component should be under MediaWiki extensions,"The visual editor backend for MediaWiki, once split out, will actually be a MediaWiki extension, and for that one a component will be created under ""MediaWiki extensions"" in Bugzilla. +The VisualEditor product itself will be MW-independent and hence a product on its own. Like now. + +> I don't see why VisualEditor can't have an entry in MediaWiki extensions. + +Because the VE product has components in Bugzilla, and Bugzilla does not allow subcomponents (components that are part of a component). +If I make the VE product a component under the ""MediaWiki extensions"" product in Bugzilla, VE will have to lose all its components. And we don't want that because it's complex enough to have components.",task_subcomment,"['The visual editor backend for MediaWiki, once split out, will actually be a MediaWiki extension, and for that one a component will be created under ""MediaWiki extensions"" in Bugzilla.', 'The VisualEditor product itself will be MW-independent and hence a product on its own.', 'Like now.', 'QUOTE\n\nBecause the VE product has components in Bugzilla, and Bugzilla does not allow subcomponents (components that are part of a component).', 'If I make the VE product a component under the ""MediaWiki extensions"" product in Bugzilla, VE will have to lose all its components.', ""And we don't want that because it's complex enough to have components.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +241232,VisualEditor bugzilla component should be under MediaWiki extensions,"I don't see why VisualEditor can't have an entry in MediaWiki extensions. It's a MediaWiki extension. This is a reasonable place to look for it. You can add a note in the description about filing the bugs under a different product, but we certainly don't to lose bugs because people can't figure out where to file them.",task_subcomment,"[""I don't see why VisualEditor can't have an entry in MediaWiki extensions."", ""It's a MediaWiki extension."", 'This is a reasonable place to look for it.', ""You can add a note in the description about filing the bugs under a different product, but we certainly don't to lose bugs because people can't figure out where to file them.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +241226,VisualEditor bugzilla component should be under MediaWiki extensions,I doubt many will understand the difference between VE and VE backend (the extension?) .I don't. They shouldn't be called the same.,task_subcomment,"['I doubt many will understand the difference between VE and VE backend (the extension?)', "".I don't."", ""They shouldn't be called the same.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +241220,VisualEditor bugzilla component should be under MediaWiki extensions,...and Bugzilla bugs should be filed under Bugzilla. Moving.,task_subcomment,"['...and Bugzilla bugs should be filed under Bugzilla.', 'Moving.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +241215,VisualEditor bugzilla component should be under MediaWiki extensions,"The VE backend for MediaWiki, once split out, is expected to become an extension on its own (also codewise) soon, but VE itself will stay as a toplevel product. + +Plus Bugzilla's three levels (classification, product, component) do not allow having subcomponents under components hence not feasible.",task_subcomment,"['The VE backend for MediaWiki, once split out, is expected to become an extension on its own (also codewise) soon, but VE itself will stay as a toplevel product.', ""Plus Bugzilla's three levels (classification, product, component) do not allow having subcomponents under components hence not feasible.""]","['FUTURE PLAN', 'INVESTIGATION AND EXPLORATION']" +51621,"""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be default","The preference ""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be enabled by default. + +More generally, users have the option to use or not to use the VisualEditor at the top of the page, but not at the section level. Some users in the Hebrew Wikipedia complained that it's disruptive, and I agree with them. + +Another possibility is to have two section edit links, like it is at the top of the page. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=49666",task_description,"['""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be default\n\nThe preference ""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be enabled by default.', 'More generally, users have the option to use or not to use the VisualEditor at the top of the page, but not at the section level.', ""Some users in the Hebrew Wikipedia complained that it's disruptive, and I agree with them."", 'Another possibility is to have two section edit links, like it is at the top of the page.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +240344,"""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be default",Thanks. I like the chosen solution.,task_subcomment,"['Thanks.', 'I like the chosen solution.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +240338,"""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be default","In the end we've gone with a solution to have both links, as requested, so closing this option on the default as INVALID (the option itself doesn't make any sense given the change in the product design).",task_subcomment,"[""In the end we've gone with a solution to have both links, as requested, so closing this option on the default as INVALID (the option itself doesn't make any sense given the change in the product design).""]",['ACTION ON ISSUE'] +240332,"""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be default","**brassratgirl** wrote: + +Agreed that having two links would be super. Visual editor for section-editing by default is driving me crazy on the English Wikipedia.",task_subcomment,"['**brassratgirl** wrote:\n\nAgreed that having two links would be super.', 'Visual editor for section-editing by default is driving me crazy on the English Wikipedia.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +51587,Implement the same EventLogging of page edits in wikitext editor as in VisualEditor for comparison purposes," + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,['Implement the same EventLogging of page edits in wikitext editor as in VisualEditor for comparison purposes\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['INVESTIGATION AND EXPLORATION'] +238129,Implement the same EventLogging of page edits in wikitext editor as in VisualEditor for comparison purposes,"This was done by Ori in gerrit 69161 for VisualEditor only; if we want to put this into core, we'll want to do that later, but for now marking this as closed.",task_subcomment,"[""This was done by Ori in gerrit 69161 for VisualEditor only; if we want to put this into core, we'll want to do that later, but for now marking this as closed.""]",['ACTION ON ISSUE'] +238124,Implement the same EventLogging of page edits in wikitext editor as in VisualEditor for comparison purposes,"Coordination card on Trello: https://trello.com/c/xCkMEAY0 + +Reminder: anonymous editors are excluded from logging (we'll instrument the edit funnel for anons in July in preparation for the global launch).",task_subcomment,"[""Coordination card on Trello: URL\n\nReminder: anonymous editors are excluded from logging (we'll instrument the edit funnel for anons in July in preparation for the global launch).""]",['INVESTIGATION AND EXPLORATION'] +51547,Configure VisualEditor for section edit links to go to VisualEditor by default," + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,['Configure VisualEditor for section edit links to go to VisualEditor by default\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR'] +235597,Configure VisualEditor for section edit links to go to VisualEditor by default,Roan implemented this in code rather than as a config of $wgVisualEditorEnableSectionEditLinks; INVLAIDing.,task_subcomment,['Roan implemented this in code rather than as a config of $wgVisualEditorEnableSectionEditLinks; INVLAIDing.'],['INVESTIGATION AND EXPLORATION'] +51545,VisualEditor: Switch over to handle mw:WikiLink/Interwiki,"Currently links with mw:WikiLink/Interwiki get alienated + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,['VisualEditor: Switch over to handle mw:WikiLink/Interwiki\n\nCurrently links with mw:WikiLink/Interwiki get alienated\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR'] +235513,VisualEditor: Switch over to handle mw:WikiLink/Interwiki,"I'm a fool to myself. + +*** This bug has been marked as a duplicate of bug 49316 ***",task_subcomment,"[""I'm a fool to myself."", '*** This bug has been marked as a duplicate of bug 49316 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +51540,VisualEditor: valid links are redlinked in the link inspector,"The link inspector shows valid links as red in the autocomplete function. This is potentially very disruptive and confusing for editors, new and old alike, who pattern-match 'red' to 'this page does not exist'. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: valid links are redlinked in the link inspector\n\nThe link inspector shows valid links as red in the autocomplete function.', ""This is potentially very disruptive and confusing for editors, new and old alike, who pattern-match 'red' to 'this page does not exist'."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +235220,VisualEditor: valid links are redlinked in the link inspector,"Yes, this is specifically that it's filtering out redirects in its suggestions (good) but then assuming that if it's not a non-redirect, it doesn't exist (bad). We'll get this fixed. + +*** This bug has been marked as a duplicate of bug 49502 ***",task_subcomment,"[""Yes, this is specifically that it's filtering out redirects in its suggestions (good) but then assuming that if it's not a non-redirect, it doesn't exist (bad)."", ""We'll get this fixed."", '*** This bug has been marked as a duplicate of bug 49502 ***']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +51525,Extension tags starting with a capital () seem to confuse the parser,"https://en.wikipedia.org/w/index.php?title=User:TheDJ/sandbox&oldid=559712952 + +Try adding a gallery that was made using + +Anything following the opening tag seems to be enclosed inside it. Also when saving, the following might apparently occur: https://en.wikipedia.org/w/index.php?title=British_Rail_Class_50&diff=prev&oldid=559199747 + + +Discussion: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=559712784#Spurious_gallery_tags + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Extension tags starting with a capital () seem to confuse the parser\n\nURL\n\nTry adding a gallery that was made using \n\nAnything following the opening tag seems to be enclosed inside it.', 'Also when saving, the following might apparently occur: URL\n\n\nDiscussion: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +234452,Extension tags starting with a capital () seem to confuse the parser,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +234447,Extension tags starting with a capital () seem to confuse the parser,https://gerrit.wikimedia.org/r/68727 (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af) | change APPROVED and MERGED [by jenkins-bot],task_subcomment,['GERRIT_URL (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af) | change APPROVED and MERGED [by jenkins-bot]'],['OBSERVED BUG BEHAVIOR'] +234438,Extension tags starting with a capital () seem to confuse the parser,Related URL: https://gerrit.wikimedia.org/r/68727 (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af)'],['OBSERVED BUG BEHAVIOR'] +234429,Extension tags starting with a capital () seem to confuse the parser,*** Bug 49579 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49579 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +234423,Extension tags starting with a capital () seem to confuse the parser,"Argh, yes, this looks like a Parsoid issue. (I would have thought that all wikitext syntax should be case insensitive?)",task_subcomment,"['Argh, yes, this looks like a Parsoid issue.', '(I would have thought that all wikitext syntax should be case insensitive?)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +51522,VisualEditor: Mass of extraneous quot and amp marks,"See https://en.wikipedia.org/w/index.php?title=Breast_cancer&diff=558696523&oldid=558695500 and https://en.wikipedia.org/w/index.php?title=Downward_causation&diff=prev&oldid=558735268 for example; I have...no idea what's happening. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: Mass of extraneous quot and amp marks\n\nSee URL and URL for example; I have...no idea what's happening."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +234178,VisualEditor: Mass of extraneous quot and amp marks,"I think that we've fixed this bug, but if it recurs please re-open.",task_subcomment,"[""I think that we've fixed this bug, but if it recurs please re-open.""]",['BUG REPRODUCTION'] +51486,VisualEditor: Add the ability to drag highlighted text around with the mouse,"As requested at https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=559578396&oldid=559577689 + +Whether this is something there will be a generalised use case for, I can't say, but it's kinda a nifty idea in theory. I'd stick it on the ""we'll consider it when everything else works"" list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",task_description,"[""VisualEditor: Add the ability to drag highlighted text around with the mouse\n\nAs requested at URL\n\nWhether this is something there will be a generalised use case for, I can't say, but it's kinda a nifty idea in theory."", 'I\'d stick it on the ""we\'ll consider it when everything else works"" list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +231896,VisualEditor: Add the ability to drag highlighted text around with the mouse,"bug 41150 was changed to be media objects only; text drag and drop is yet to come. + +*** This bug has been marked as a duplicate of bug 49981 ***",task_subcomment,"['bug 41150 was changed to be media objects only; text drag and drop is yet to come.', '*** This bug has been marked as a duplicate of bug 49981 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +231890,VisualEditor: Add the ability to drag highlighted text around with the mouse,Neat! Thanks :),task_subcomment,"['Neat!', 'Thanks :)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +231886,VisualEditor: Add the ability to drag highlighted text around with the mouse,"Good news - we've already got this planned as part of the beta - see bug 41150. Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 41150 ***",task_subcomment,"[""Good news - we've already got this planned as part of the beta - see bug 41150."", 'Marking as a dupe.', '*** This bug has been marked as a duplicate of bug 41150 ***']","['FUTURE PLAN', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +51475,Red links show as blue links in VisualEditor,"When editing for example http://pt.wikipedia.org/wiki/Rana with the VisualEditor, all the red links are shown as blue links. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Red links show as blue links in VisualEditor\n\nWhen editing for example URL with the VisualEditor, all the red links are shown as blue links.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +231186,Red links show as blue links in VisualEditor,"Hey, this is a duplicate of bug 37901 - unfortunately, this depends on hinting in Parsoid (bug 37902) which is not yet done. + +*** This bug has been marked as a duplicate of bug 37901 ***",task_subcomment,"['Hey, this is a duplicate of bug 37901 - unfortunately, this depends on hinting in Parsoid (bug 37902) which is not yet done.', '*** This bug has been marked as a duplicate of bug 37901 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +51418,new schedule for Jenkins jobs,"The number of browser tests and the number of browser test builds have both increased to the point that our original idea of a mid-day build and a late-day build (Pacific time) no longer serves us well. The builds take long enough that they run essentially back-to-back all afternoon every day. + +I suggest we run all the builds at 11:00 Pacific time to have timely build information available around deployment time during the US working day. + +Then I suggest that we run all the builds once at 19:00 Pacific time (GMT-8) so that the results will be available for analysis in the morning Croation time (GMT-1) + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",task_description,"['new schedule for Jenkins jobs\n\nThe number of browser tests and the number of browser test builds have both increased to the point that our original idea of a mid-day build and a late-day build (Pacific time) no longer serves us well.', 'The builds take long enough that they run essentially back-to-back all afternoon every day.', 'I suggest we run all the builds at 11:00 Pacific time to have timely build information available around deployment time during the US working day.', 'Then I suggest that we run all the builds once at 19:00 Pacific time (GMT-8) so that the results will be available for analysis in the morning Croation time (GMT-1)\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'WORKAROUNDS']" +252487,new schedule for Jenkins jobs,"Fixed in https://gerrit.wikimedia.org/r/#/c/69865/ + +If there is still something to be done here, reopen the bug.",task_subcomment,"['Fixed in URL\n\nIf there is still something to be done here, reopen the bug.']",['ACTION ON ISSUE'] +252482,new schedule for Jenkins jobs,"Actually, upon reflection, I think we can support the weekly releases better, and move toward even faster release cycles perhaps by something like this: + + +Builds for beta labs to run several times per day. Possibly run Chrome/FF builds more often than IE builds for speed. + +Builds for test2 to match deployments to test2/mw.o depending on features tested e.g. VisualEditor. + +Builds for production to match deployments to prod. ""Sufficiently advanced testing is indistinguishable from monitoring."" + +Builds for mobile TBD.",task_subcomment,"['Actually, upon reflection, I think we can support the weekly releases better, and move toward even faster release cycles perhaps by something like this: \n\n\nBuilds for beta labs to run several times per day.', 'Possibly run Chrome/FF builds more often than IE builds for speed.', 'Builds for test2 to match deployments to test2/mw.o depending on features tested e.g.', 'VisualEditor.', 'Builds for production to match deployments to prod.', '""Sufficiently advanced testing is indistinguishable from monitoring.""', 'Builds for mobile TBD.']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +51384,VisualEditor: Linking to an image results in the image being loaded,"The image is loaded + +editing article [[:zh:港鐵都城嘉慕電動列車_(直流電)]] + +if there exists a wikilink to a file, then the file will be loaded which should not happen. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11725}",task_description,"['VisualEditor: Linking to an image results in the image being loaded\n\nThe image is loaded\n\nediting article [[:zh:港鐵都城嘉慕電動列車_(直流電)]]\n\nif there exists a wikilink to a file, then the file will be loaded which should not happen.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11725}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +250172,VisualEditor: Linking to an image results in the image being loaded," + +*** This bug has been marked as a duplicate of bug 48387 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 48387 ***'],['ACTION ON ISSUE'] +51336,Inconsistency in the URL (veaction=edit disappears),"To edit an article using the VE, the URL is ""...?veaction=edit"". + +But, by loading the page with the VE, the URL is changed and becomes the same than the one to display the article. + +There is consequently an inconsistency between the URL and the page content. + +""?veaction=edit"" and all other URL parameters should not be changed/removed. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Inconsistency in the URL (veaction=edit disappears)\n\nTo edit an article using the VE, the URL is ""...?veaction=edit"".', 'But, by loading the page with the VE, the URL is changed and becomes the same than the one to display the article.', 'There is consequently an inconsistency between the URL and the page content.', '""?veaction=edit"" and all other URL parameters should not be changed/removed.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +247540,Inconsistency in the URL (veaction=edit disappears),"This is being done as part of bug 43844. + +Instead of letting it stay, we're going to enforce it even when not there. + +veaction=edit was originally (and still is) only used to start VisualEditor by url. + +When starting it from within MediaWiki by clicking ""Edit"" when reading an article, it never used veaction=edit. + +Bug 43844 asks for consistent url reflection of state in both directions. + +*** This bug has been marked as a duplicate of bug 43844 ***",task_subcomment,"['This is being done as part of bug 43844.', ""Instead of letting it stay, we're going to enforce it even when not there."", 'veaction=edit was originally (and still is) only used to start VisualEditor by url.', 'When starting it from within MediaWiki by clicking ""Edit"" when reading an article, it never used veaction=edit.', 'Bug 43844 asks for consistent url reflection of state in both directions.', '*** This bug has been marked as a duplicate of bug 43844 ***']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +51084,Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,"VisualEditor's new features should be exposed for testing outside of our local development environments. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;\n\nVisualEditor's new features should be exposed for testing outside of our local development environments."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']" +232785,Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,Done on 2013-06-06.,task_subcomment,['Done on 2013-06-06.'],['SOLUTION DISCUSSION'] +232781,Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,"(In reply to comment #1) +> And the test and MW.org wikis. + +Per Timo's comments, only on MW.org not test.",task_subcomment,"[""(In reply to comment #1)\nQUOTE\n\nPer Timo's comments, only on MW.org not test.""]",['ACTION ON ISSUE'] +232776,Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,And the test and MW.org wikis.,task_subcomment,['And the test and MW.org wikis.'],['OBSERVED BUG BEHAVIOR'] +50893,Various submodules in mediawiki/extensions are not being automatically updated,"I updated the translations of several VisualEditor messages in translatewiki.net. The changes were committed to Gerrit, and it looks like LocalisationUpdate ran several times since then, but I still don't see them on the Hebrew Wikipedia. + +For example, let's take the message Visualeditor-linkinspector-suggest-matching-page: + +1. Update in transatewiki.net: https://translatewiki.net/w/i.php?title=MediaWiki%3AVisualeditor-linkinspector-suggest-matching-page%2Fhe&diff=4721642&oldid=4682586 + +2. Commit to Gerrit: https://gerrit.wikimedia.org/r/#/c/63552/1/VisualEditor.i18n.php (line 1661) + +3. Still not updated in he.wikipedia: https://he.wikipedia.org/w/index.php?title=Special:AllMessages&prefix=visu&filter=modified&lang=he&limit=5000 + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",task_description,"['Various submodules in mediawiki/extensions are not being automatically updated\n\nI updated the translations of several VisualEditor messages in translatewiki.net.', ""The changes were committed to Gerrit, and it looks like LocalisationUpdate ran several times since then, but I still don't see them on the Hebrew Wikipedia."", ""For example, let's take the message Visualeditor-linkinspector-suggest-matching-page:\n\n1."", 'Update in transatewiki.net: URL\n\n2.', 'Commit to Gerrit: URL (line 1661)\n\n3.', 'Still not updated in he.wikipedia: URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +226321,Various submodules in mediawiki/extensions are not being automatically updated,"The issue is on Gerrit side. The check-sync.sh of mediawiki/extensions.git let us detect such issue. + +Follow up on bug 49846 mediawiki/extensions.git does not update some extensions + +*** This bug has been marked as a duplicate of bug 49846 ***",task_subcomment,"['The issue is on Gerrit side.', 'The check-sync.sh of mediawiki/extensions.git let us detect such issue.', 'Follow up on bug 49846 mediawiki/extensions.git does not update some extensions\n\n*** This bug has been marked as a duplicate of bug 49846 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']" +226316,Various submodules in mediawiki/extensions are not being automatically updated,"So VisualEditor was fixed with some manual database poking, and a number of the others seem to have been fixed too. Thanks ^demon! + +On the other hand, a number of others seem to be newly broken. The current list is: AutoCreateCategoryPages Bootstrap Campaigns CirrusSearch CommunityTwitter CoreEvents EImage Less OpenStreetMapSlippyMap PerPageLicense QuickResponse TimelineTable WikibaseDataModel WikibaseQueryEngine + + +If you have a fully checked-out version of mediawiki/extensions (git pull && git submodule update --init --recursive), this bash script should tell you the submodules that aren't at master: + + for m in `sed -n 's/\[submodule ""\(.*\)""\]/\1/p' .gitmodules | sort`; do ( + cd $m; + A=`git log -1 --format=""%h %ci %s""`; + B=`git log -1 --format=""%h %ci %s"" origin/master`; + [ ""$A"" = ""$B"" ] || echo $m + ); done + +Of course, that won't catch anything that hasn't had a commit since being broken, if such a state is possible. If you want to see info on the actual commits, BTW, you can change 'echo $m' in there to something like 'echo -e ""$m\n $A\n $B""'.",task_subcomment,"['So VisualEditor was fixed with some manual database poking, and a number of the others seem to have been fixed too.', 'Thanks ^demon!', 'On the other hand, a number of others seem to be newly broken.', 'The current list is: AutoCreateCategoryPages Bootstrap Campaigns CirrusSearch CommunityTwitter CoreEvents EImage Less OpenStreetMapSlippyMap PerPageLicense QuickResponse TimelineTable WikibaseDataModel WikibaseQueryEngine\n\n\nIf you have a fully checked-out version of mediawiki/extensions (git pull && git submodule update --init --recursive), this bash script should tell you the submodules that aren\'t at master:\n\n for m in CODE; do (\n cd $m;\n A=CODE;\n B=CODE;\n [ ""$A"" = ""$B"" ] || echo $m\n ); done\n\nOf course, that won\'t catch anything that hasn\'t had a commit since being broken, if such a state is possible.', 'If you want to see info on the actual commits, BTW, you can change \'echo $m\' in there to something like \'echo -e ""$m\\n $A\\n $B""\'.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']" +226310,Various submodules in mediawiki/extensions are not being automatically updated,"(In reply to comment #0) +> For example, let's take the message +> Visualeditor-linkinspector-suggest-matching-page: + +That one arrived. + +(In reply to comment #2) +> Also, I did some further checking and found some other submodules also +> affected. The full list is: EImage MagicNoCache MyVariables +> NamespaceRelations +> OpenStreetMapSlippyMap PHPExcel PerPageLicense TimelineTable VisualEditor + +I don't know if it's related, but the most obvious place where I saw recent changes being unreported is https://github.com/wikimedia/mediawiki-extensions which at some point reported a bunch of extensions as last edited ""6 months ago"" when they obviously weren't.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\n\nThat one arrived.', '(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don\'t know if it\'s related, but the most obvious place where I saw recent changes being unreported is URL which at some point reported a bunch of extensions as last edited ""6 months ago"" when they obviously weren\'t.']","['SOLUTION DISCUSSION', 'MOTIVATION']" +226304,Various submodules in mediawiki/extensions are not being automatically updated,"(In reply to comment #1) +> +> We'll see if Gerrit change #65818 (manually updating the submodule to master) +> will convince the automatic updating to start working again. + +It didn't. + +Also, I did some further checking and found some other submodules also affected. The full list is: EImage MagicNoCache MyVariables NamespaceRelations OpenStreetMapSlippyMap PHPExcel PerPageLicense TimelineTable VisualEditor + +It'll probably take someone either checking Gerrit's logs or digging through Gerrit's code to find out what exactly is making it not update these modules.",task_subcomment,"[""(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\n\nIt didn't."", 'Also, I did some further checking and found some other submodules also affected.', ""The full list is: EImage MagicNoCache MyVariables NamespaceRelations OpenStreetMapSlippyMap PHPExcel PerPageLicense TimelineTable VisualEditor\n\nIt'll probably take someone either checking Gerrit's logs or digging through Gerrit's code to find out what exactly is making it not update these modules.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +226296,Various submodules in mediawiki/extensions are not being automatically updated,"The problem seems to be that the VisualEditor submodule in mediawiki/extensions hasn't been being automatically updated for some reason. + +We'll see if gerrit change 65818 (manually updating the submodule to master) will convince the automatic updating to start working again.",task_subcomment,"[""The problem seems to be that the VisualEditor submodule in mediawiki/extensions hasn't been being automatically updated for some reason."", ""We'll see if gerrit change 65818 (manually updating the submodule to master) will convince the automatic updating to start working again.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +50669,"VisualEditor misrepresents linked files as embedded inline, when editing","**Author:** `swalling` + +**Description:** +Placing a colon before a File: link in MediaWiki should link to the file, without displaying it in the page. While VisualEditor correctly represents this text in read-mode, when it editing it displays thumbnails for the linked images instead of the link and text. (Screenshots of the error and associated markup to be attached.) + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor misrepresents linked files as embedded inline, when editing\n\n**Author:** CODE\n\n**Description:**\nPlacing a colon before a File: link in MediaWiki should link to the file, without displaying it in the page.', 'While VisualEditor correctly represents this text in read-mode, when it editing it displays thumbnails for the linked images instead of the link and text.', '(Screenshots of the error and associated markup to be attached.)', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +212529,"VisualEditor misrepresents linked files as embedded inline, when editing"," + +*** This bug has been marked as a duplicate of bug 48387 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 48387 ***'],['ACTION ON ISSUE'] +212525,"VisualEditor misrepresents linked files as embedded inline, when editing","**swalling** wrote: + +Screenshot of markup + +**Attached**: {F10438}",task_subcomment,['**swalling** wrote:\n\nScreenshot of markup\n\n**Attached**: {F10438}'],['OBSERVED BUG BEHAVIOR'] +212519,"VisualEditor misrepresents linked files as embedded inline, when editing","**swalling** wrote: + +Edit mode, with incorrect thumbnails + +**Attached**: {F10437}",task_subcomment,"['**swalling** wrote:\n\nEdit mode, with incorrect thumbnails\n\n**Attached**: {F10437}']",['OBSERVED BUG BEHAVIOR'] +50658,Enable section-editing on 'beta' profile of VisualEditor deployments,"(This is only for action in the immediate run-up to VisualEditor deployment as beta.) + +The section edit links should point to VE rather than the wikitext editor as part of the 'being the default editor' schtick. This should only apply to wikis with VE on 'beta' rather than remaining on 'alpha'. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""Enable section-editing on 'beta' profile of VisualEditor deployments\n\n(This is only for action in the immediate run-up to VisualEditor deployment as beta.)"", ""The section edit links should point to VE rather than the wikitext editor as part of the 'being the default editor' schtick."", ""This should only apply to wikis with VE on 'beta' rather than remaining on 'alpha'."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['WORKAROUNDS', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +211833,Enable section-editing on 'beta' profile of VisualEditor deployments,Done today.,task_subcomment,['Done today.'],['INVESTIGATION AND EXPLORATION'] +50645,MediaWiki:Visualeditor-feedback-link doesn't use wiki language,"Feedback gets submitted to a page given by the message MediaWiki:Visualeditor-feedback-link. The link can differ from language to language. +But feedback gets submitted to the link for the user-chosen interface language, not the wiki/content language and so hitting different pages. + +ex.: +german interface: https://de.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/R%C3%BCckmeldungen&diff=prev&oldid=118691535 +english interface: https://de.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=prev&oldid=118691557 + +This may apply to other messages as well + +-------------------------- +**Version**: unspecified +**Severity**: minor",task_description,"[""MediaWiki:Visualeditor-feedback-link doesn't use wiki language\n\nFeedback gets submitted to a page given by the message MediaWiki:Visualeditor-feedback-link."", 'The link can differ from language to language.', 'But feedback gets submitted to the link for the user-chosen interface language, not the wiki/content language and so hitting different pages.', 'ex.', ':\ngerman interface: URL\nenglish interface: URL\n\nThis may apply to other messages as well\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +211099,MediaWiki:Visualeditor-feedback-link doesn't use wiki language," + +*** This bug has been marked as a duplicate of bug 47730 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 47730 ***'],['ISSUE CONTENT MANAGEMENT'] +50596,VisualEditor expanding image links,"Screenshot of the English Wikipedia using VisualEditor, 2013-05-18 + +VisualEditor seems to be expanding certain image links. Screenshot attached. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11087}",task_description,"['VisualEditor expanding image links\n\nScreenshot of the English Wikipedia using VisualEditor, 2013-05-18\n\nVisualEditor seems to be expanding certain image links.', 'Screenshot attached.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11087}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +233284,VisualEditor expanding image links," + +*** This bug has been marked as a duplicate of bug 48387 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 48387 ***'],['ACTION ON ISSUE'] +50558,"VisualEditor: API doesn't suggest thinks for string length <= 2, so don't show the suggestions box for links/categories/etc.?","Not sure how to proceed on this one. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",task_description,"[""VisualEditor: API doesn't suggest thinks for string length <= 2, so don't show the suggestions box for links/categories/etc.?"", 'Not sure how to proceed on this one.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +230862,"VisualEditor: API doesn't suggest thinks for string length <= 2, so don't show the suggestions box for links/categories/etc.?",Apparently it does and MW was just being unhelpful. Ignore.,task_subcomment,"['Apparently it does and MW was just being unhelpful.', 'Ignore.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +50527,List looks like it has extra empty lines,"1. Edit http://en.wikipedia.org/wiki/Refrigerator +2. Look at the list in paragraph ""Production by country"" + +The list has extra empty lines, some with a bullet, some without. + +The saved wikicode is OK, though. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['List looks like it has extra empty lines\n\n1.', 'Edit URL\n2.', 'Look at the list in paragraph ""Production by country""\n\nThe list has extra empty lines, some with a bullet, some without.', 'The saved wikicode is OK, though.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +229016,List looks like it has extra empty lines,"Oh, I see, my bad, I should have checked the wikicode! :-)",task_subcomment,"['Oh, I see, my bad, I should have checked the wikicode!', ':-)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +229011,List looks like it has extra empty lines,"This is not a bug; the actual wikitext of the article has multiple lists with (admittedly hard-to-notice) gaps between them: + +> […] +> *20 South Africa 711,000 (2003) +> *21 Sweden 639,000 (2004) +> +> *22 Ukraine 562,000 (1995) +> *23 France 544,000 (2003) +> *24 Australia 423,000 (1995) +> +> *25 Portugal 399,000 (2004) +> *26 Bulgaria 353,000 (2005) +> […] + +In VisualEditor these gaps between lists are much more prominent because we need to give the user somewhere obvious to insert their cursor, but this is ""behaviour as expected"". Closing as INVALID. + +(BTW, I just went and fixed the wikitext in a personal capacity, because it was so awful. :-))",task_subcomment,"['This is not a bug; the actual wikitext of the article has multiple lists with (admittedly hard-to-notice) gaps between them:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIn VisualEditor these gaps between lists are much more prominent because we need to give the user somewhere obvious to insert their cursor, but this is ""behaviour as expected"".', 'Closing as INVALID.', '(BTW, I just went and fixed the wikitext in a personal capacity, because it was so awful.', ':-))']","['MOTIVATION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +50523,Parsoid: Expose order of template parameters call,"VisualEditor is currently unable to display the parameters in the template editor in the same order as the wikitext because they are provided as a plain object. + +And per the JSON specification (and as proven by inconsistent behaviour in different browsers), objects are ""an unordered set of name/value pairs""[1]. + +And even if JSON would support it, once in javascript, we have the for-in statement and Object.keys() which do not have a reliable cross-browser logic for the order of the keys. + +Though Parsoid is able to roundtrip the order (since it has the original wikitext and can put them in the right order), we can't. + +I'd recommend the output is updated to output an array of some kind. + +So instead of : + { foo: bar, bar: quux } + +It'd be something like this: + + [ { foo: bar }, { bar: quux } ] + +or (Trevor's idea): + + { keys: ['foo', 'bar'], values: ['bar', 'quux' ] } + + +[1] http://json.org/ + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Parsoid: Expose order of template parameters call\n\nVisualEditor is currently unable to display the parameters in the template editor in the same order as the wikitext because they are provided as a plain object.', 'And per the JSON specification (and as proven by inconsistent behaviour in different browsers), objects are ""an unordered set of name/value pairs""[1].', 'And even if JSON would support it, once in javascript, we have the for-in statement and Object.keys() which do not have a reliable cross-browser logic for the order of the keys.', ""Though Parsoid is able to roundtrip the order (since it has the original wikitext and can put them in the right order), we can't."", ""I'd recommend the output is updated to output an array of some kind."", ""So instead of :\n { foo: bar, bar: quux }\n\nIt'd be something like this:\n\n [ { foo: bar }, { bar: quux } ]\n\nor (Trevor's idea):\n\n { keys: ['foo', 'bar'], values: ['bar', 'quux' ] }\n\n\n[1] URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +228822,Parsoid: Expose order of template parameters call,"Only the name of parameters is significant, the order is a syntactic detail. You can do a numeric sort on numeric parameter names for UI purposes, but generally our API only talks about named parameters.",task_subcomment,"['Only the name of parameters is significant, the order is a syntactic detail.', 'You can do a numeric sort on numeric parameter names for UI purposes, but generally our API only talks about named parameters.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +50489,VisualEditor: Can not paste new link anchor,"If you try to change a link anchor by pasting plain text over the old anchor (or part of the old one), it won't work. The new text will just stay plain. + +You can't use the link dialog for this either, since there is no anchor field. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",task_description,"[""VisualEditor: Can not paste new link anchor\n\nIf you try to change a link anchor by pasting plain text over the old anchor (or part of the old one), it won't work."", 'The new text will just stay plain.', ""You can't use the link dialog for this either, since there is no anchor field."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +226420,VisualEditor: Can not paste new link anchor,"**jiabao.foss** wrote: + +That's very nice of you! I would love to investigate this bug.",task_subcomment,"[""**jiabao.foss** wrote:\n\nThat's very nice of you!"", 'I would love to investigate this bug.']","['SOCIAL CONVERSATION', 'INVESTIGATION AND EXPLORATION']" +226411,VisualEditor: Can not paste new link anchor,"(In reply to comment #4) +> Sorry that I did not know the link inspector could be rich text. Now looking +> forward to the new deployment of VE. It will be nice to read the solution, on +> the problem which I have worked on but did not get a good solution. Thank you +> for the reviews and explanations. I learned a lot from this attempt. :) + +Thank you for trying! If you want to get your teeth into something in VisualEditor relatively self-contained, but still touching on a considerable amount of the codebase (and which would be really great to have done), bug 47328 could be a good challenge. Will leave a comment there suggesting an approach.",task_subcomment,"['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThank you for trying!', 'If you want to get your teeth into something in VisualEditor relatively self-contained, but still touching on a considerable amount of the codebase (and which would be really great to have done), bug 47328 could be a good challenge.', 'Will leave a comment there suggesting an approach.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +226402,VisualEditor: Can not paste new link anchor,"**jiabao.foss** wrote: + +Sorry that I did not know the link inspector could be rich text. Now looking forward to the new deployment of VE. It will be nice to read the solution, on the problem which I have worked on but did not get a good solution. Thank you for the reviews and explanations. I learned a lot from this attempt. :)",task_subcomment,"['**jiabao.foss** wrote:\n\nSorry that I did not know the link inspector could be rich text.', 'Now looking forward to the new deployment of VE.', 'It will be nice to read the solution, on the problem which I have worked on but did not get a good solution.', 'Thank you for the reviews and explanations.', 'I learned a lot from this attempt.', ':)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +226394,VisualEditor: Can not paste new link anchor,"Yeah, sorry about this; I was behind in triaging bugs and didn't get to this in time. It's in fact actually a duplicate of an already-fixed bug that went out in wmf4 (but isn't yet deployed on enwiki - that will happen on Monday 20 May). + +*** This bug has been marked as a duplicate of bug 48195 ***",task_subcomment,"[""Yeah, sorry about this; I was behind in triaging bugs and didn't get to this in time."", ""It's in fact actually a duplicate of an already-fixed bug that went out in wmf4 (but isn't yet deployed on enwiki - that will happen on Monday 20 May)."", '*** This bug has been marked as a duplicate of bug 48195 ***']","['ACTION ON ISSUE', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +226383,VisualEditor: Can not paste new link anchor,"Unfortunately this bug didn't get triaged in time, and I worry that you may have spent a lot of time working on a solution for a no-longer-existing problem. + +The bug here has to do with pasting into the middle of a link not taking on the proper annotations. This appears to be fixed in master, and production is somewhat behind that. + +The solution being offered here ( I9ae4aeed6099cbe9affdc2aa83045121bc0b8669 ) adds a ""display text"" input to the inspector - but I think this patch overlooks some important UX and technical issues. + +We deliberately do not want to have a text field in the inspector for the display text, for a couple of reasons. + +1. The ""display text"" isn't just plain text, it could include formatting, templates, images, etc. This isn't going to work in a single line text input. + +2. Users already have a way to change the display text (or non-text) content, and if there are bugs there, we should resolve them there.",task_subcomment,"[""Unfortunately this bug didn't get triaged in time, and I worry that you may have spent a lot of time working on a solution for a no-longer-existing problem."", 'The bug here has to do with pasting into the middle of a link not taking on the proper annotations.', 'This appears to be fixed in master, and production is somewhat behind that.', 'The solution being offered here ( I9ae4aeed6099cbe9affdc2aa83045121bc0b8669 ) adds a ""display text"" input to the inspector - but I think this patch overlooks some important UX and technical issues.', 'We deliberately do not want to have a text field in the inspector for the display text, for a couple of reasons.', '1.', 'The ""display text"" isn\'t just plain text, it could include formatting, templates, images, etc.', ""This isn't going to work in a single line text input."", '2.', 'Users already have a way to change the display text (or non-text) content, and if there are bugs there, we should resolve them there.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +226378,VisualEditor: Can not paste new link anchor,"**jiabao.foss** wrote: + +I have investigated this bug. When looking at the use case for pasting text as you insert it into the hyperlink you need to also consider other formatting being pasted in. In other editors you can see that the link also splits leaving the text plain. This is because if you pasted for example a table or a section into the center of a link it cant accept this as part of the link itself and must be split. + +The solution I will work on is add a way to edit the displayed hyperlink text while the linkinspector dialog is open. this will allow users to paste box complex links and displayed text when using visualeditor.",task_subcomment,"['**jiabao.foss** wrote:\n\nI have investigated this bug.', 'When looking at the use case for pasting text as you insert it into the hyperlink you need to also consider other formatting being pasted in.', 'In other editors you can see that the link also splits leaving the text plain.', 'This is because if you pasted for example a table or a section into the center of a link it cant accept this as part of the link itself and must be split.', 'The solution I will work on is add a way to edit the displayed hyperlink text while the linkinspector dialog is open.', 'this will allow users to paste box complex links and displayed text when using visualeditor.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +50471,VisualEditor adds ↵ when editing user .js and .css pages,"**Author:** `the.anonymouse.wikimedia` + +**Description:** +screenshot of editing my .js file with VisualEditor + +When editing user skin .js and .css page ([[Special:MyPage/skin.js]] and [[Special:MyPage/skin.js]]), line returns are replaced with ↵ symbols. I attached a screenshot to this bug report of editing my .js page with VisualEditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F10832}",task_description,"['VisualEditor adds ↵ when editing user .js and .css pages\n\n**Author:** CODE\n\n**Description:**\nscreenshot of editing my .js file with VisualEditor\n\nWhen editing user skin .js and .css page ([[Special:MyPage/skin.js]] and [[Special:MyPage/skin.js]]), line returns are replaced with ↵ symbols.', 'I attached a screenshot to this bug report of editing my .js page with VisualEditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F10832}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +225367,VisualEditor adds ↵ when editing user .js and .css pages,"Happily, we've just last week disabled editing of JS and CSS pages (the code will be deployed to enwiki on Monday 20 May). + +*** This bug has been marked as a duplicate of bug 47456 ***",task_subcomment,"[""Happily, we've just last week disabled editing of JS and CSS pages (the code will be deployed to enwiki on Monday 20 May)."", '*** This bug has been marked as a duplicate of bug 47456 ***']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +50433,VisualEditor link tool incorrectly shows a red link,"VisualEditor link dialog box incorrectly showing red text, 2013-05-13 + +Go to . Click ""edit"". Highlight the word ""wiki"" and click the link icon in the toolbar. A dialog box pops up incorrectly showing ""wiki"" in red text (indicating that the article does not exist). Screenshot attached. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F10762}",task_description,"['VisualEditor link tool incorrectly shows a red link\n\nVisualEditor link dialog box incorrectly showing red text, 2013-05-13\n\nGo to + +Error: see attached screenshot + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F10756}",task_description,"['""visualeditor-diff-nochanges"" exposed on mediawiki.org\n\nVisualEditor message key exposed on mediawiki.org, 2013-05-13\n\nURL: is not in MW.org's message file; need to do a message purge?,task_subcomment,"[""Looks like is not in MW.org's message file; need to do a message purge?""]",['OBSERVED BUG BEHAVIOR'] +50316,"VisualEditor: When the edit tab is replaced it breaks active/selected states and doesn't replace ""Create"" tabs properly.","When the VisualEditor replaces the normal ""Edit"" tab with ""Edit source"" it deletes any selected/active state on the tab. This results in an active edit tab becoming non-active when you are on &action=edit. + +Additionally on a non existent page ""Create"" gets replaced with ""Edit source"" instead of something like ""Create source"". + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: When the edit tab is replaced it breaks active/selected states and doesn\'t replace ""Create"" tabs properly.', 'When the VisualEditor replaces the normal ""Edit"" tab with ""Edit source"" it deletes any selected/active state on the tab.', 'This results in an active edit tab becoming non-active when you are on &action=edit.', 'Additionally on a non existent page ""Create"" gets replaced with ""Edit source"" instead of something like ""Create source"".', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +216336,"VisualEditor: When the edit tab is replaced it breaks active/selected states and doesn't replace ""Create"" tabs properly.","This is a dupe of three different bugs, but I'll settle for the obvious one. :-) + +(A prior search when you're reporting a bug does help avoid this! :-)) + +*** This bug has been marked as a duplicate of bug 47452 ***",task_subcomment,"[""This is a dupe of three different bugs, but I'll settle for the obvious one."", "":-)\n\n(A prior search when you're reporting a bug does help avoid this!"", ':-))\n\n*** This bug has been marked as a duplicate of bug 47452 ***']","['OBSERVED BUG BEHAVIOR', 'WORKAROUNDS', 'ISSUE CONTENT MANAGEMENT']" +50179,Parsoid: HTML comment with immediately following table has newline split removed,"As per Subbu's report. (The corrupted table is going to be a different bug.) + +-------------------------- +**Version**: unspecified +**Severity**: trivial +**URL**: http://parsoid.wmflabs.org/_rt/en/BMW_801",task_description,"[""Parsoid: HTML comment with immediately following table has newline split removed\n\nAs per Subbu's report."", '(The corrupted table is going to be a different bug.)', '--------------------------\n**Version**: unspecified\n**Severity**: trivial\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +208134,Parsoid: HTML comment with immediately following table has newline split removed,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +208127,Parsoid: HTML comment with immediately following table has newline split removed,Fixed in production.,task_subcomment,['Fixed in production.'],['ACTION ON ISSUE'] +208120,Parsoid: HTML comment with immediately following table has newline split removed,Related URL: https://gerrit.wikimedia.org/r/62546 (Gerrit Change If16dda01058715acee8df347b2b9c4da84609113),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change If16dda01058715acee8df347b2b9c4da84609113)'],['OBSERVED BUG BEHAVIOR'] +208111,Parsoid: HTML comment with immediately following table has newline split removed,I am still getting a clean diff with Chromium (and &debug=true to work around current VE breakage). Can you point out any pages that have a dirty diff both in FF and Chrome?,task_subcomment,"['I am still getting a clean diff with Chromium (and &debug=true to work around current VE breakage).', 'Can you point out any pages that have a dirty diff both in FF and Chrome?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +208101,Parsoid: HTML comment with immediately following table has newline split removed,"(In reply to comment #5) +> Those were FF-specific, which points to client-side issues. Are they now an +> issue independent of the browser? + +Actually, that bit wasn't FF-specific, it was happening in Chrome as well (and I can confirm that it still does).",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\n\nActually, that bit wasn't FF-specific, it was happening in Chrome as well (and I can confirm that it still does).""]",['OBSERVED BUG BEHAVIOR'] +208094,Parsoid: HTML comment with immediately following table has newline split removed,"Those were FF-specific, which points to client-side issues. Are they now an issue independent of the browser?",task_subcomment,"['Those were FF-specific, which points to client-side issues.', 'Are they now an issue independent of the browser?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +208087,Parsoid: HTML comment with immediately following table has newline split removed,"(In reply to comment #3) +> Can you link to the original report? + +The midden of bug 47712.",task_subcomment,['(In reply to comment #3)\nQUOTE\n\nThe midden of bug 47712.'],['BUG REPRODUCTION'] +208081,Parsoid: HTML comment with immediately following table has newline split removed,Can you link to the original report?,task_subcomment,['Can you link to the original report?'],['ACTION ON ISSUE'] +208074,Parsoid: HTML comment with immediately following table has newline split removed,"(In reply to comment #1) +> I get a JS error when trying to preview the diff in that page using FF: +> [13:44:04.016] Error: toDomElements() failed to return an array when +> converting +> element of type alienBlock @ +> http://bits.wikimedia.org/en.wikipedia.org/load. +> php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext. +> visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs. +> wordbreak&skin=vector&version=20130506T190432Z&*:130 + +Bug 48181.",task_subcomment,['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBug 48181.'],['OBSERVED BUG BEHAVIOR'] +208068,Parsoid: HTML comment with immediately following table has newline split removed,"I get a JS error when trying to preview the diff in that page using FF: +[13:44:04.016] Error: toDomElements() failed to return an array when converting element of type alienBlock @ http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs.wordbreak&skin=vector&version=20130506T190432Z&*:130",task_subcomment,['I get a JS error when trying to preview the diff in that page using FF:\n[13:44:04.016] Error: toDomElements() failed to return an array when converting element of type alienBlock @ URL'],['OBSERVED BUG BEHAVIOR'] +50110,VisualEditor: Adjacent annotations which are equal by name but not reference do not serialise correctly.,"In MW, annotations loaded from the document will have data-parsoid attributes, and so will have difference store indexes to new annotations. If two words with differently indexed bold annotations are placed side-by-side they converter will close the first one before opening the second, e.g.: + +Bold on load textadded text + +Which Parsoid converts to + +'''Bold on load text''''''added text''' + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Adjacent annotations which are equal by name but not reference do not serialise correctly.', 'In MW, annotations loaded from the document will have data-parsoid attributes, and so will have difference store indexes to new annotations.', 'If two words with differently indexed bold annotations are placed side-by-side they converter will close the first one before opening the second, e.g.', "":\n\nBold on load textadded text\n\nWhich Parsoid converts to\n\n'''Bold on load text''''''added text'''\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +229423,VisualEditor: Adjacent annotations which are equal by name but not reference do not serialise correctly.,Merged into master.,task_subcomment,['Merged into master.'],['SOLUTION USAGE'] +229419,VisualEditor: Adjacent annotations which are equal by name but not reference do not serialise correctly.,Related URL: https://gerrit.wikimedia.org/r/62352 (Gerrit Change I93586919002c78732228e08b134e67e1a94f8ad7),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I93586919002c78732228e08b134e67e1a94f8ad7)'],['OBSERVED BUG BEHAVIOR'] +49860,VisualEditor: Extra tags got inserted causing infobox layout to be broken,"https://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and
    . + +Of course, there is no reason why this article uses float & {{clr}}, but I know some similar cases where it is useful to have floating tables + {{clr}}. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: {{clr}} prevents user from editing content\n\n1.', 'Got to [[fr:Disjonction logique]]\n2.', 'Edit it with VisualEditor\n3.', 'Try to modify the table.', 'You will get a big blue rectangle allowing to edit {{clr}}, but you can’t edit directly (clicking on headings and using ↓ works) the .', 'Of course, there is no reason why this article uses float & {{clr}}, but I know some similar cases where it is useful to have floating tables + {{clr}}.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +233774,VisualEditor: {{clr}} prevents user from editing content," + +*** This bug has been marked as a duplicate of bug 50551 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50551 ***'],['ACTION ON ISSUE'] +233769,VisualEditor: {{clr}} prevents user from editing content,"This is related to bug 51933 - an excessively large transclusion box prevents accessing an item it overlaps. It's not identical though as that bug relates to other templates and this to tables, so I'll leave the decision whether to merge up to someone more knowledgeable.",task_subcomment,"['This is related to bug 51933 - an excessively large transclusion box prevents accessing an item it overlaps.', ""It's not identical though as that bug relates to other templates and this to tables, so I'll leave the decision whether to merge up to someone more knowledgeable.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +54421,"VisualEditor: Link suggestions sometimes too foreceful, can't select the target you want.","Sometimes when entering a link in the link input widget the first suggested target is automatically inserted, even before you finish typing, making it very difficult to choose a different target. + +Steps to reproduce: +1.Load a page in VE +2.Press ctrl+k to enter a link +3.Try to enter a link to [[Portable Document Format]], [[Classic (album)]] or [[Thing (assembly)]]. + +-------------------------- +**Version**: unspecified +**Severity**: critical",task_description,"[""VisualEditor: Link suggestions sometimes too foreceful, can't select the target you want."", 'Sometimes when entering a link in the link input widget the first suggested target is automatically inserted, even before you finish typing, making it very difficult to choose a different target.', 'Steps to reproduce:\n1.Load a page in VE\n2.Press ctrl+k to enter a link\n3.Try to enter a link to [[Portable Document Format]], [[Classic (album)]] or [[Thing (assembly)]].', '--------------------------\n**Version**: unspecified\n**Severity**: critical']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +233233,"VisualEditor: Link suggestions sometimes too foreceful, can't select the target you want.","Elitre was 25 seconds faster than you ;) + +*** This bug has been marked as a duplicate of bug 52420 ***",task_subcomment,['Elitre was 25 seconds faster than you ;)\n\n*** This bug has been marked as a duplicate of bug 52420 ***'],['ACTION ON ISSUE'] +54410,VisualEditor: Undoing a larger cut restores selection incorrectly,"- Chrome 30 (canary) +- https://en.wikipedia.org/w/index.php?title=Narayana_Gosain_Temple&oldid=565414421&veaction=edit + + +When selecting the following: + +> +> h2.Transport +> p.It is situated within 20km from NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar. +> h2.References +> references. +> \n +> +> \n +> h2.External links + +.. and cutting it, and then ctrl-Z. It restores both content and selection properly + + + +When selecting the following: + +> +> h2.Transport +> p.It is situated within 20km from NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar. +> h2.References +> references. +> \n +> \n +> h2.External links + +.. and cutting it and then ctrl-Z. It restores the content properly, but the selection is restored only within the first paragraph: + +> +> h2.Transport +> p.It is situated within 20km from NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar. +> h2.References +> references. +> \n +> \n +> h2.External links + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Undoing a larger cut restores selection incorrectly\n\n- Chrome 30 (canary)\n- URL\n\n\nWhen selecting the following:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n.. and cutting it, and then ctrl-Z.', 'It restores both content and selection properly \n\n\n\nWhen selecting the following:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n.. and cutting it and then ctrl-Z.', 'It restores the content properly, but the selection is restored only within the first paragraph:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +257652,VisualEditor: Undoing a larger cut restores selection incorrectly,This was fixed in the selection re-writes.,task_subcomment,['This was fixed in the selection re-writes.'],['SOLUTION DISCUSSION'] +54374,Stray bullet points around template and strange editing around them,"Screenshot: 2 extra bullet points & template content edited + +Browser: Firefox 24 + +When editing this page[1] on sv-wp two weird things happen: + +1) The bullet point on the bottom of the page duplicates into three bullet points + +I expect it to show one bullet point, like when viewing the article. + + +2) I can edit the text of the template used in the list[2], though when I check the diff, it hasn't detected that I edited the template text + +I expect the text of the template to show a blue background when clicking on it and *not* be editable. + + +[1] https://sv.wikipedia.org/w/index.php?title=Byrackorna&oldid=22981861 +[2] https://sv.wikipedia.org/wiki/Mall:IMDb-titel + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/User:Skalman/bullet_point_test + +**Attached**: {F11912}",task_description,"['Stray bullet points around template and strange editing around them\n\nScreenshot: 2 extra bullet points & template content edited\n\nBrowser: Firefox 24\n\nWhen editing this page[1] on sv-wp two weird things happen:\n\n1) The bullet point on the bottom of the page duplicates into three bullet points\n\nI expect it to show one bullet point, like when viewing the article.', ""2) I can edit the text of the template used in the list[2], though when I check the diff, it hasn't detected that I edited the template text\n\nI expect the text of the template to show a blue background when clicking on it and *not* be editable."", '[1] URL\n[2] URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n\n**Attached**: {F11912}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +255600,Stray bullet points around template and strange editing around them,"This is a known tidy issue, so marking as a duplicate. + +*** This bug has been marked as a duplicate of bug 47673 ***",task_subcomment,"['This is a known tidy issue, so marking as a duplicate.', '*** This bug has been marked as a duplicate of bug 47673 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +255598,Stray bullet points around template and strange editing around them,"This is a duplicate of a Parsoid bug that has been WONTFIX'ed, I believe (but I can't find right now) - Gabriel, can you remember which one? + +(In reply to comment #4) +> FWIW, even Special:ExpandTemplates seems to be affected by this bug! + +… which is a sign that you're abusing wikitext, and should stop trying to get this to work. :-) Special:ExpandTemplates has nothing to do with VisualEditor or Parsoid.",task_subcomment,"[""This is a duplicate of a Parsoid bug that has been WONTFIX'ed, I believe (but I can't find right now) - Gabriel, can you remember which one?"", ""(In reply to comment #4)\nQUOTE\n\n… which is a sign that you're abusing wikitext, and should stop trying to get this to work."", ':-) Special:ExpandTemplates has nothing to do with VisualEditor or Parsoid.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +255595,Stray bullet points around template and strange editing around them,"I believe I found the root cause - demonstrated by a minimal test case: https://www.mediawiki.org/wiki/User:Skalman/bullet_point_test + +Wikitext of template: +* {{{1}}} + +Wikitext of page: +* {{template|Hello there}} + +Expected output (the way the traditional parser handles it): +* Hello there + +Note that a naive wikitext template expander would produce: +* * Hello there + +To me, this now seems to be a problem with the data model. + + +FWIW, even Special:ExpandTemplates seems to be affected by this bug!",task_subcomment,"['I believe I found the root cause - demonstrated by a minimal test case: URL\n\nWikitext of template:\n* {{{1}}}\n\nWikitext of page:\n* {{template|Hello there}}\n\nExpected output (the way the traditional parser handles it):\n* Hello there\n\nNote that a naive wikitext template expander would produce:\n* * Hello there\n\nTo me, this now seems to be a problem with the data model.', 'FWIW, even Special:ExpandTemplates seems to be affected by this bug!']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +255589,Stray bullet points around template and strange editing around them,Reproduced in Chrome 28 and Opera 12.16.,task_subcomment,['Reproduced in Chrome 28 and Opera 12.16.'],['OBSERVED BUG BEHAVIOR'] +255583,Stray bullet points around template and strange editing around them,"And further weirdness: + +When I add the text 'ABC' to the first of the now three bullet points I get the following wikitext: + +* {{IMDb-titel|id=0105928}}ABC +* ''[ackorna''' (originaltitel ''2 Stupid Byrackorna]'' på [[Internet Movie Database]] (engelska) +*",task_subcomment,"['And further weirdness:\n\nWhen I add the text \'ABC\' to the first of the now three bullet points I get the following wikitext:\n\n* {{IMDb-titel|id=0105928}}ABC\n* \'\'[ackorna\'\'\' (originaltitel \'\'2 Stupid Byrackorna]\'\' på [[Internet Movie Database]] (engelska)\n*']",['SOLUTION DISCUSSION'] +255577,Stray bullet points around template and strange editing around them,This is probably a ContentEditable problem.,task_subcomment,['This is probably a ContentEditable problem.'],['OBSERVED BUG BEHAVIOR'] +54364,drag and drop for text,"Request to introduce drag and drop for text passages; there are also bugs for images around (obviously). + +Report: + +http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121095343#Drag_.26_Drop_von_Textabschnitten + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",task_description,"['drag and drop for text\n\nRequest to introduce drag and drop for text passages; there are also bugs for images around (obviously).', 'Report:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['REQUEST', 'BUG REPORT']" +254818,drag and drop for text,"There's already bug 49981 for drag-and-drop of content in general; I don't think this is sufficiently different (drag-and-drop of text is not sufficiently distinct from drag-and-drop of non-text to be worth splitting out), so merging. + +*** This bug has been marked as a duplicate of bug 49981 ***",task_subcomment,"[""There's already bug 49981 for drag-and-drop of content in general; I don't think this is sufficiently different (drag-and-drop of text is not sufficiently distinct from drag-and-drop of non-text to be worth splitting out), so merging."", '*** This bug has been marked as a duplicate of bug 49981 ***']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +54307,Contents of pre-existing transclusion saved to article adjacent to transclusion,"https://pl.wikipedia.org/w/index.php?title=Octan_etylu&curid=217010&diff=37144425&oldid=37144363 + +This may be a template that got subst'd in VisualEditor. It produces this text: + +
    + +
    + +Something sensible ought to be done with this, but I'm not sure what the right answer is. (Yes, that's in English, even though it's not an English-language project.) + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""Contents of pre-existing transclusion saved to article adjacent to transclusion\n\nURL\n\nThis\xa0may be a template that got subst'd in VisualEditor."", 'It produces this text:\n\n
    \n \n
    \n\nSomething sensible ought to be done with this, but I\'m not sure what the right answer is.', ""(Yes, that's in English, even though it's not an English-language project.)"", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +251756,Contents of pre-existing transclusion saved to article adjacent to transclusion,I believe all these issues were fixed months ago (sorry for very slow triage).,task_subcomment,['I believe all these issues were fixed months ago (sorry for very slow triage).'],['OBSERVED BUG BEHAVIOR'] +251750,Contents of pre-existing transclusion saved to article adjacent to transclusion,"That's the contents of the {{Przypisy}} template. It looks like they ""spilled out"". Parsoid issue?",task_subcomment,"[""That's the contents of the {{Przypisy}} template."", 'It looks like they ""spilled out"".', 'Parsoid issue?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +54291,VisualEditor: Editing surface displays non-existent spaces after bullet points in Thai Wikipedia,"Image of issue + +Upon loading VE in Thai wikipedia in an article with a bulleted list, spaces are added after bullets in the edit view. Attempts to remove the spaces remove the preceding bullet. Spaces are not added upon Save, but will lead to confusion for editors. + +Duplicated in FF, Chrome. Ubuntu, OS 10.6.8 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11736}",task_description,"['VisualEditor: Editing surface displays non-existent spaces after bullet points in Thai Wikipedia\n\nImage of issue\n\nUpon loading VE in Thai wikipedia in an article with a bulleted list, spaces are added after bullets in the edit view.', 'Attempts to remove the spaces remove the preceding bullet.', 'Spaces are not added upon Save, but will lead to confusion for editors.', 'Duplicated in FF, Chrome.', 'Ubuntu, OS 10.6.8\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11736}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +250586,VisualEditor: Editing surface displays non-existent spaces after bullet points in Thai Wikipedia,"This is because the Thai Wikipedia has this CSS in its Common.css: + +| /* A request by octahedron80 19:13, 7 ธันวาคม 2554 (ICT) */ +| .mw-content-ltr dd, .mw-content-rtl .mw-content-ltr dd { +| margin-left: 2.5em; +| } +| .mw-content-ltr ul, .mw-content-rtl .mw-content-ltr ul { +| margin-left: 2.5em; +| } +| .mw-content-ltr ol, .mw-content-rtl .mw-content-ltr ol { +| margin-left: 2.5em; +| } + +There's no justification for it beyond who requested it, so I can't judge whether the purpose it serves is sufficient, but it's deliberate. + +As this is based on local wiki configuration, marking as INVALID.",task_subcomment,"[""This is because the Thai Wikipedia has this CSS in its Common.css:\n\n| /* A request by octahedron80 19:13, 7 ธันวาคม 2554 (ICT) */\n| .mw-content-ltr dd, .mw-content-rtl .mw-content-ltr dd {\n| margin-left: 2.5em;\n| }\n| .mw-content-ltr ul, .mw-content-rtl .mw-content-ltr ul {\n| margin-left: 2.5em;\n| }\n| .mw-content-ltr ol, .mw-content-rtl .mw-content-ltr ol {\n| margin-left: 2.5em;\n| }\n\nThere's no justification for it beyond who requested it, so I can't judge whether the purpose it serves is sufficient, but it's deliberate."", 'As this is based on local wiki configuration, marking as INVALID.']","['MOTIVATION', 'BUG REPRODUCTION']" +250577,VisualEditor: Editing surface displays non-existent spaces after bullet points in Thai Wikipedia,"**KaewWiki** wrote: + +(In reply to comment #0) +> Created attachment 13022 [details] +> Image of issue +> +> Upon loading VE in Thai wikipedia in an article with a bulleted list, spaces +> are added after bullets in the edit view. Attempts to remove the spaces +> remove +> the preceding bullet. Spaces are not added upon Save, but will lead to +> confusion for editors. +> +> Duplicated in FF, Chrome. Ubuntu, OS 10.6.8 + +Also in the same image, at the end of reference section +(in Thai {{รายการอ้างอิง}}) and immediately before {{stub}} (in Thai +{{โครงกฎหมาย}}), VE displayed additional blank line where it should +not do so. + +**Attached**: {F11736}",task_subcomment,"['**KaewWiki** wrote:\n\n(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAlso in the same image, at the end of reference section\n(in Thai {{รายการอ้างอิง}}) and immediately before {{stub}} (in Thai\n{{โครงกฎหมาย}}), VE displayed additional blank line where it should\nnot do so.', '**Attached**: {F11736}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +250569,VisualEditor: Editing surface displays non-existent spaces after bullet points in Thai Wikipedia,"Example page on th.wp: +https://th.wikipedia.org/wiki/กฎหมายปิดปาก?veaction=edit + +I can't reproduce this with Thai text on en.wp. See for example https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575310209&veaction=edit",task_subcomment,"[""Example page on th.wp:\nURL\n\nI can't reproduce this with Thai text on en.wp."", 'See for example URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +54285,VisualEditor: Following links in image captions that have a large value takes over media settings dialog which can't then be closed,"link target takes over media settings dialog + +If text has a size specified, e.g , then you cannot edit it in VE at present. The bar that notifies you of this is fixed to standard line height so you can click on links that extend above or beyond this, e.g. text with a [[link]]. + +If such a link appears in body text, then clicking it takes you to the link target in the same window (i.e. exactly the same as if you clicked on it in read mode). If you ctrl+click to open in a new window/tab then you get the same behaviour as described for section links in bug 51122. + +If such a link appears in an image caption, then ctrl+clicking has the same effect as in the paragraph above/bug 51122. Left clicking does take you to the linked page, but instead of using the main window it uses the media settings dialog's frame (see screenshot). You cannot close this frame - the close button has been replaced by the link target and it doesn't respond to escape. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11727}",task_description,"[""VisualEditor: Following links in image captions that have a large value takes over media settings dialog which can't then be closed\n\nlink target takes over media settings dialog\n\nIf text has a size specified, e.g , then you cannot edit it in VE at present."", 'The bar that notifies you of this is fixed to standard line height so you can click on links that extend above or beyond this, e.g.', 'text with a [[link]].', 'If such a link appears in body text, then clicking it takes you to the link target in the same window (i.e.', 'exactly the same as if you clicked on it in read mode).', 'If you ctrl+click to open in a new window/tab then you get the same behaviour as described for section links in bug 51122.', 'If such a link appears in an image caption, then ctrl+clicking has the same effect as in the paragraph above/bug 51122.', ""Left clicking does take you to the linked page, but instead of using the main window it uses the media settings dialog's frame (see screenshot)."", ""You cannot close this frame - the close button has been replaced by the link target and it doesn't respond to escape."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11727}']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +250209,VisualEditor: Following links in image captions that have a large value takes over media settings dialog which can't then be closed,"This has the same root cause as bug 51778, despite the names; merging. + +*** This bug has been marked as a duplicate of bug 51778 ***",task_subcomment,"['This has the same root cause as bug 51778, despite the names; merging.', '*** This bug has been marked as a duplicate of bug 51778 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +250200,VisualEditor: Following links in image captions that have a large value takes over media settings dialog which can't then be closed,Cryptic C62 and en.wp has noted that he can replicate this in Firefox 22 and Chrome 28 running on Windows Vista. Both they and I use the monobook skin.,task_subcomment,"['Cryptic C62 and en.wp has noted that he can replicate this in Firefox 22 and Chrome 28 running on Windows Vista.', 'Both they and I use the monobook skin.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +250194,VisualEditor: Following links in image captions that have a large value takes over media settings dialog which can't then be closed,"Steps to reproduce: + +1. Edit https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=566460073#New_section in VE +2. Click on the last image and open the media settings dialog +3. Left click the link above the ""can only edit in source"" bar. + +This happens in Firefox 22 on Linux, I can't test in other browsers/OSes.",task_subcomment,"['Steps to reproduce:\n\n1.', 'Edit URL in VE\n2.', 'Click on the last image and open the media settings dialog\n3.', 'Left click the link above the ""can only edit in source"" bar.', ""This happens in Firefox 22 on Linux, I can't test in other browsers/OSes.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']" +54270,VisualEditor should be themeable by the user with custom CSS,"A user at en.wp comments that VisualEditor looks best in the Vector skin, but that it would be better if ""manual CSS theming"" were supported. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",task_description,"['VisualEditor should be themeable by the user with custom CSS\n\nA user at en.wp comments that VisualEditor looks best in the Vector skin, but that it would be better if ""manual CSS theming"" were supported.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +249376,VisualEditor should be themeable by the user with custom CSS,"**gryllida** wrote: + +I understand you expect folks to either 1) look into having existing themes change the VisualEditor appearance to fit their style, or 2) to look into using CSS. As the latter is not user-friendly for non-technical users I will look into the former. Thank you.",task_subcomment,"['**gryllida** wrote:\n\nI understand you expect folks to either 1) look into having existing themes change the VisualEditor appearance to fit their style, or 2) to look into using CSS.', 'As the latter is not user-friendly for non-technical users I will look into the former.', 'Thank you.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +249373,VisualEditor should be themeable by the user with custom CSS,"(In reply to comment #8) +> [...] when the rest of MediaWiki is designed to be consistent. + +:-)",task_subcomment,['(In reply to comment #8)\nQUOTE\n\n:-)'],['SOLUTION DISCUSSION'] +249371,VisualEditor should be themeable by the user with custom CSS,"(In reply to comment #5) +> My original query was in making different styles available for an average +> user, who has no CSS experience. + +Then that's a question for MediaWiki core, not VisualEditor; VisualEditor just inherits its styling from MediaWiki. + +Certainly, we are not going to build a custom-styling tool just for VisualEditor when the rest of MediaWiki is designed to be consistent.",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\n\nThen that's a question for MediaWiki core, not VisualEditor; VisualEditor just inherits its styling from MediaWiki."", 'Certainly, we are not going to build a custom-styling tool just for VisualEditor when the rest of MediaWiki is designed to be consistent.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']" +249368,VisualEditor should be themeable by the user with custom CSS,"Hey James, +I am reopening this to understand whether Gryllida's concerns can/should be addressed, and because the user understands, from the logs of a recent office hour, that you welcome feedback from users about this topic. Gryllida is asking for a set of themes for the Toolbar from which the user can choose the one he/she wants (and provided examples in comment #2). + +Other users instead were hoping that graphic solutions that are now possible by changing one's CSS are made more easily accessible in VE itself. I for one am not really good at editing my CSS page, but I could easily check a box that lets me choose a different background color that makes it more obvious when I'm VEditing (and would gladly do so). + +So there are probably 2 different requests here, and I can split them if one of them can be worked on. +Thanks :)",task_subcomment,"[""Hey James,\nI am reopening this to understand whether Gryllida's concerns can/should be addressed, and because the user understands, from the logs of a recent office hour, that you welcome feedback from users about this topic."", 'Gryllida is asking for a set of themes for the Toolbar from which the user can choose the one he/she wants (and provided examples in comment #2).', ""Other users instead were hoping that graphic solutions that are now possible by changing one's CSS are made more easily accessible in VE itself."", ""I for one am not really good at editing my CSS page, but I could easily check a box that lets me choose a different background color that makes it more obvious when I'm VEditing (and would gladly do so)."", 'So there are probably 2 different requests here, and I can split them if one of them can be worked on.', 'Thanks :)']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +249365,VisualEditor should be themeable by the user with custom CSS,"**gryllida** wrote: + +Elitre, please file a new bug, my query you pasted does not belong here.",task_subcomment,"['**gryllida** wrote:\n\nElitre, please file a new bug, my query you pasted does not belong here.']",['INVESTIGATION AND EXPLORATION'] +249360,VisualEditor should be themeable by the user with custom CSS,"**gryllida** wrote: + +My original query was in making different styles available for an average user, who has no CSS experience.",task_subcomment,"['**gryllida** wrote:\n\nMy original query was in making different styles available for an average user, who has no CSS experience.']",['INVESTIGATION AND EXPLORATION'] +249355,VisualEditor should be themeable by the user with custom CSS,"I'm entirely unsure what this is asking for. VE already inherits users' CSS, which lets people change the CSS as they see fit - as John Broughton's script shows. + +Marking as ""INVALID"", but happy to re-open if people can explain what different from the above this is asking for.",task_subcomment,"[""I'm entirely unsure what this is asking for."", ""VE already inherits users' CSS, which lets people change the CSS as they see fit - as John Broughton's script shows."", 'Marking as ""INVALID"", but happy to re-open if people can explain what different from the above this is asking for.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE']" +249352,VisualEditor should be themeable by the user with custom CSS,"An example of how users might want to change the way they see VE: +https://en.wikipedia.org/wiki/User:John_Broughton/common.css +(an easier way to set a background color for VE is being requested).",task_subcomment,['An example of how users might want to change the way they see VE:\nURL\n(an easier way to set a background color for VE is being requested).'],['INVESTIGATION AND EXPLORATION'] +249348,VisualEditor should be themeable by the user with custom CSS,"**gryllida** wrote: + +( Illustrations: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=570246873#Toolbar_icons_style )",task_subcomment,['**gryllida** wrote:\n\n( Illustrations: URL )'],['OBSERVED BUG BEHAVIOR'] +249344,VisualEditor should be themeable by the user with custom CSS,"Gryllida adds, +<>",task_subcomment,"['Gryllida adds,\n<>']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +54269,VisualEditor: References not saved,"References 5-8 were not saved + +At https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=566402676&oldid=566401436 only four of the 8 references I added were saved. + +The second references for each statement had the same title as the first but were a different URL. They appeared in the editor as being there (see attachment) but were silently not saved. + +-------------------------- +**Version**: unspecified +**Severity**: critical + +**Attached**: {F11698}",task_description,"['VisualEditor: References not saved\n\nReferences 5-8 were not saved\n\nAt URL only four of the 8 references I added were saved.', 'The second references for each statement had the same title as the first but were a different URL.', 'They appeared in the editor as being there (see attachment) but were silently not saved.', '--------------------------\n**Version**: unspecified\n**Severity**: critical\n\n**Attached**: {F11698}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +249314,VisualEditor: References not saved,"I can't reproduce this now, so it seems likely this was a duplicate of now-fixed Bug 52228 + +*** This bug has been marked as a duplicate of bug 52228 ***",task_subcomment,"[""I can't reproduce this now, so it seems likely this was a duplicate of now-fixed Bug 52228\n\n*** This bug has been marked as a duplicate of bug 52228 ***""]",['BUG REPRODUCTION'] +54266,Parsoid or VisualEditor: nowiki added around space following HTML comment,"At line 138 of https://en.wikipedia.org/w/index.php?title=Wikipedia&diff=566045928&oldid=566042453 parsoid (presumably) has added nowikis around around a space following a HTML comment. I don't know whether the comment containing references is relevant or not. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Parsoid or VisualEditor: nowiki added around space following HTML comment\n\nAt line 138 of URL parsoid (presumably) has added nowikis around around a space following a HTML comment.', ""I don't know whether the comment containing references is relevant or not."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +249210,Parsoid or VisualEditor: nowiki added around space following HTML comment," + +*** This bug has been marked as a duplicate of bug 50758 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50758 ***'],['ISSUE CONTENT MANAGEMENT'] +54264,VisualEditor: Wikitext insertion warning needs to be more visible,"The wikitext insertion warning now works, and is visible regardless of the position of the user on the page. + +However, its color scheme is the same as other regular, confirmation-type notifications like ""you've added this page to your watchlist"". + +Wikitext insertion is an actual problem, rather than ""just"" a confirmation or feedback notification. We need it to be more visible, possibly by using a different color scheme. Maybe not a big red blinking bubble, but something more noticeable than a white bubble with a light blue border. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Wikitext insertion warning needs to be more visible\n\nThe wikitext insertion warning now works, and is visible regardless of the position of the user on the page.', 'However, its color scheme is the same as other regular, confirmation-type notifications like ""you\'ve added this page to your watchlist"".', 'Wikitext insertion is an actual problem, rather than ""just"" a confirmation or feedback notification.', 'We need it to be more visible, possibly by using a different color scheme.', 'Maybe not a big red blinking bubble, but something more noticeable than a white bubble with a light blue border.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +249118,VisualEditor: Wikitext insertion warning needs to be more visible,"WONTFIX. It's currently blocking save, doesn't disappear until clicked, and in the standard place for interactive notifications in MediaWiki; moving these around for the mouse (or cursor) could get very ugly and confusing, and the advantage isn't so significant that it's worth doing.",task_subcomment,"['WONTFIX.', ""It's currently blocking save, doesn't disappear until clicked, and in the standard place for interactive notifications in MediaWiki; moving these around for the mouse (or cursor) could get very ugly and confusing, and the advantage isn't so significant that it's worth doing.""]","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION']" +249111,VisualEditor: Wikitext insertion warning needs to be more visible,"Maybe closest to the mouse would be better. If someone edits at the bottom of the displayed content with a large screen, I’m not sure he will see the warning, too far.",task_subcomment,"['Maybe closest to the mouse would be better.', 'If someone edits at the bottom of the displayed content with a large screen, I’m not sure he will see the warning, too far.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +54252,Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"Labeled Section Transclusion (
    Text here
    ) is not supported. This is used for status reports on MediaWiki.org. The first step is to alienate it. Currently it is treated as raw text. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid\n\nLabeled Section Transclusion (
    Text here
    ) is not supported.', 'This is used for status reports on MediaWiki.org.', 'The first step is to alienate it.', 'Currently it is treated as raw text.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +248314,Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"LST is heavily used in wikisource, where most parts of pages are wrapped in section tags. Alienation and / or an extension-like visual edit experience would not be ideal there, which is why we are considering supporting
    natively as the HTML5 element it is. + +Closing as duplicated of bug 47936 for that reason. Please respond there if you feel that this is the wrong approach. + +*** This bug has been marked as a duplicate of bug 47936 ***",task_subcomment,"['LST is heavily used in wikisource, where most parts of pages are wrapped in section tags.', 'Alienation and / or an extension-like visual edit experience would not be ideal there, which is why we are considering supporting
    natively as the HTML5 element it is.', 'Closing as duplicated of bug 47936 for that reason.', 'Please respond there if you feel that this is the wrong approach.', '*** This bug has been marked as a duplicate of bug 47936 ***']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'ISSUE CONTENT MANAGEMENT', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +248309,Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"Related: bug 51562 +Related: bug 47936 + +We probably need a single bug that merges all these three.",task_subcomment,['Related: bug 51562\nRelated: bug 47936\n\nWe probably need a single bug that merges all these three.'],['BUG REPRODUCTION'] +248302,Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,whoops. misfire.,task_subcomment,"['whoops.', 'misfire.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +248299,Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid," + +*** This bug has been marked as a duplicate of bug 51462 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51462 ***'],['ISSUE CONTENT MANAGEMENT'] +248296,Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"For VisualEditor to alienate something, all that is required is for Parsoid to mark it up as something VisualEditor doesn't recognise; right now, Parsoid and VisualEditor are both entirely dumb to the issue. :-)",task_subcomment,"[""For VisualEditor to alienate something, all that is required is for Parsoid to mark it up as something VisualEditor doesn't recognise; right now, Parsoid and VisualEditor are both entirely dumb to the issue."", ':-)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +248295,Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,An example is https://www.mediawiki.org/w/index.php?title=Editor_engagement_experiments/status&oldid=750533,task_subcomment,['An example is URL'],['OBSERVED BUG BEHAVIOR'] +54251,"VisualEditor: Link input widget should not show ""New: (redlink)"" when a redirect exists by that name","Screenshot of problem + +See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11666}",task_description,"['VisualEditor: Link input widget should not show ""New: (redlink)"" when a redirect exists by that name\n\nScreenshot of problem\n\nSee screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11666}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +248262,"VisualEditor: Link input widget should not show ""New: (redlink)"" when a redirect exists by that name"," + +*** This bug has been marked as a duplicate of bug 50898 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50898 ***'],['ISSUE CONTENT MANAGEMENT'] +54250,VisualEditor: Add guidance message into the reference dialog to tell a user what to put there,"One of the biggest interface issue is the new reference dialog. The use is presented with a window and no real guidance on what to do. + +Some brief instructions guiding the user to choose an appropriate citation template would be good. This obviously needs to be customisable on a wiki basis. For en.wikipedia you could have something like + +""To add a reference please choose a citation template like {{cite web}}, {{cite journal}}, {{cite book}} or {{cite news}}. Click the jigsaw icon to insert one of these templates."" + +The message could be specified by a page in the MediaWiki: namespace. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",task_description,"['VisualEditor: Add guidance message into the reference dialog to tell a user what to put there\n\nOne of the biggest interface issue is the new reference dialog.', 'The use is presented with a window and no real guidance on what to do.', 'Some brief instructions guiding the user to choose an appropriate citation template would be good.', 'This obviously needs to be customisable on a wiki basis.', 'For en.wikipedia you could have something like\n\n""To add a reference please choose a citation template like {{cite web}}, {{cite journal}}, {{cite book}} or {{cite news}}.', 'Click the jigsaw icon to insert one of these templates.""', 'The message could be specified by a page in the MediaWiki: namespace.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +248201,VisualEditor: Add guidance message into the reference dialog to tell a user what to put there,"This feels like the wrong approach. In general, if you have to prompt a user with text telling them what to do, your interface has failed. + +Bug 50110 (which we want to work on soon) would give users some buttons (or something similar) for a few, recommended templates for the context - and yes, that would be wiki-localised. + +Consequently, I'm marking this as WONTFIX so we can focus on bug 50110.",task_subcomment,"['This feels like the wrong approach.', 'In general, if you have to prompt a user with text telling them what to do, your interface has failed.', 'Bug 50110 (which we want to work on soon) would give users some buttons (or something similar) for a few, recommended templates for the context - and yes, that would be wiki-localised.', ""Consequently, I'm marking this as WONTFIX so we can focus on bug 50110.""]","['SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +54248,Provide a way for the Behavior switches magic words to be inserted.,"The Behavior switches like __TOC__, __NOTOC__ are occasionally useful in the article space and __NOINDEX__ is a useful in the user namespace. Some way to insert these in visual editor would be handy. + +Bug 49996 and Bug 50855 also address magic words, but don't seem to cover the Behavior switches. + +This was discussed at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Some_ideas_for_29_July + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Provide a way for the Behavior switches magic words to be inserted.', 'The Behavior switches like __TOC__, __NOTOC__ are occasionally useful in the article space and __NOINDEX__ is a useful in the user namespace.', 'Some way to insert these in visual editor would be handy.', ""Bug 49996 and Bug 50855 also address magic words, but don't seem to cover the Behavior switches."", 'This was discussed at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +248120,Provide a way for the Behavior switches magic words to be inserted.,"This was later created as bug 56865, but I'm only just triaging this now. Up-merging (unusually) given the history on that one - sorry! + +*** This bug has been marked as a duplicate of bug 56865 ***",task_subcomment,"[""This was later created as bug 56865, but I'm only just triaging this now."", 'Up-merging (unusually) given the history on that one - sorry!', '*** This bug has been marked as a duplicate of bug 56865 ***']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +54242,VisualEditor: template substituted in,"See https://en.wikipedia.org/w/index.php?title=Cruz_Azul&diff=564888460&oldid=564725284 - very strange. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: template substituted in\n\nSee URL - very strange.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +247748,VisualEditor: template substituted in,This was a recurring Parsoid bug which is now fixed; closing. Sorry for slow triage.,task_subcomment,"['This was a recurring Parsoid bug which is now fixed; closing.', 'Sorry for slow triage.']","['ACTION ON ISSUE', 'ACTION ON ISSUE']" +54218,inserting media into tables,"Inserting media, namely images, into complext tables leads to problems. A user tried to put an image into a table listing Intel CPU sockets on De.WP and the search function went back and forth in being able to find the image he knew was on Commons and how it is labeled. + +Table: + +http://de.wikipedia.org/wiki/Prozessorsockel#Intel + +Image: + +http://commons.wikimedia.org/wiki/File:Intel_Socket_1150_IMGP8593_smial_wp.jpg + +The file fails to show up, if you put its name in manually once you reach ""5"" + +Report: + +http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121004381#Bildeinbindung + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['inserting media into tables\n\nInserting media, namely images, into complext tables leads to problems.', 'A user tried to put an image into a table listing Intel CPU sockets on De.WP and the search function went back and forth in being able to find the image he knew was on Commons and how it is labeled.', 'Table:\n\nURL\n\nImage:\n\nURL\n\nThe file fails to show up, if you put its name in manually once you reach ""5""\n\nReport:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +246556,inserting media into tables,"This is actually a duplicate of bug 52782, which has been marked as WONTFIX as the Wikimedia search system is being replaced. Sorry for the slow response. + +*** This bug has been marked as a duplicate of bug 52782 ***",task_subcomment,"['This is actually a duplicate of bug 52782, which has been marked as WONTFIX as the Wikimedia search system is being replaced.', 'Sorry for the slow response.', '*** This bug has been marked as a duplicate of bug 52782 ***']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +246548,inserting media into tables,"Confirmed. +Typing 'Intel Socket 11' gives a list of images, but not this image. +Typing 'Intel Socket 115' gives zero results. + +The image description is 'Intel core socket 1150, open.' + +Typing in 'Intel core socket 1150' does show this, and other images, so it doesnt appear to be bug 50018.",task_subcomment,"['Confirmed.', ""Typing 'Intel Socket 11' gives a list of images, but not this image."", ""Typing 'Intel Socket 115' gives zero results."", ""The image description is 'Intel core socket 1150, open.'"", ""Typing in 'Intel core socket 1150' does show this, and other images, so it doesnt appear to be bug 50018.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +54212,reference clipboard errors,"If one tries to move a reference using Ctrl + X to pick it out, Ctrl + V doesn't work, i.e. the reference doesn't seem to be stored in the clipboard. + +If one selects the sign to the left of the reference as well, Ctrl + V provides the reference number but not the content, which gets lost. + +If one selects the sign to the right of the reference as well, Ctrl + V provides the sign to the right but the reference gets lost. + +If one selects a sign to the right and to the left of the reference, it works. + +Report: http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=120995561#Einzelnachweise_in_der_Zwischenablage + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""reference clipboard errors\n\nIf one tries to move a reference using Ctrl + X to pick it out, Ctrl + V doesn't work, i.e."", ""the reference doesn't seem to be stored in the clipboard."", 'If one selects the sign to the left of the reference as well, Ctrl + V provides the reference number but not the content, which gets lost.', 'If one selects the sign to the right of the reference as well, Ctrl + V provides the sign to the right but the reference gets lost.', 'If one selects a sign to the right and to the left of the reference, it works.', 'Report: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +246229,reference clipboard errors," + +*** This bug has been marked as a duplicate of bug 49396 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49396 ***'],['ACTION ON ISSUE'] +54205,VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general),"Screenshot of VE on an iPad (3rd gen, iOS 6, en.wikipedia.org) + +Dimensions Dim.. without OS menu bar +iPhone / iPod 320 x 480 320 x 460 +iPh?o.. Retina 640 x 960 640 x 920 +iPad (portait) 768 x 1024 768 x 1004 +iPa.. (landscape) 1024 x 768 1024 x 748 + + +So that means at least under 1024px (not accounting for MediaWiki sidebar, that is to be subtracted from that) + +Measuring on my MacBook Pro in latest Chrome I measure exactly 1281px as the minimum window width to have the toolbar be one line. 1331px to account for vector-hd mode and allow a bit of breathing room between the left and right half of the toolbar. + +When at 1281px, the width of just the toolbar (subtracted the mw sidebar) is 1103px. + +So, a lot to cut down on. Any ideas? + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11563}",task_description,"['VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general)\n\nScreenshot of VE on an iPad (3rd gen, iOS 6, en.wikipedia.org)\n\nDimensions Dim.. without OS menu bar\niPhone / iPod 320 x 480 320 x 460\niPh?o.. Retina 640 x 960 640 x 920\niPad (portait) 768 x 1024 768 x 1004\niPa.. (landscape) 1024 x 768 1024 x 748\n\n\nSo that means at least under 1024px (not accounting for MediaWiki sidebar, that is to be subtracted from that)\n\nMeasuring on my MacBook Pro in latest Chrome I measure exactly 1281px as the minimum window width to have the toolbar be one line.', '1331px to account for vector-hd mode and allow a bit of breathing room between the left and right half of the toolbar.', 'When at 1281px, the width of just the toolbar (subtracted the mw sidebar) is 1103px.', 'So, a lot to cut down on.', 'Any ideas?', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11563}']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +245709,VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general),"Yes, this is; merging. + +*** This bug has been marked as a duplicate of bug 51000 ***",task_subcomment,"['Yes, this is; merging.', '*** This bug has been marked as a duplicate of bug 51000 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +245700,VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general),Same as bug 51000?,task_subcomment,['Same as bug 51000?'],['MOTIVATION'] +245693,VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general),"Created attachment 13387 +Screenshot of two side-by-side VE windows on 1080p screen + +I see the exact same problem when sizing a window to half of a 1080p HD screen -- circa 960px window width is not uncommon... + +**Attached**: {F11565}",task_subcomment,['Created attachment 13387\nScreenshot of two side-by-side VE windows on 1080p screen\n\nI see the exact same problem when sizing a window to half of a 1080p HD screen -- circa 960px window width is not uncommon...\n\n**Attached**: {F11565}'],['BUG REPRODUCTION'] +54198,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","Per http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Content_transclusion_causes_WTF_mode + +If trying to add a template, only adding content (empty) and click apply, following error is thrown: + +TypeError: content is undefined +http://bits.wikimedia.org/static-1.22wmf11/extensions/VisualEditor/modules/ve-mw/dm/nodes/ve.dm.MWTransclusionNode.js +Line 192 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Fix ""Uncaught TypeError: Cannot read property \'params\' of undefined \'content\'""\n\nPer URL\n\nIf trying to add a template, only adding content (empty) and click apply, following error is thrown:\n\nTypeError: content is undefined\nURL\nLine 192\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['BUG REPRODUCTION'] +245098,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","(In reply to comment #5) +> Doesn't give a error anymore, but API is returning: +> +> {""warnings"":{""main"":{""*"":""Unrecognized parameter: +> 'token'""}},""visualeditor"":{""result"":""success"",""content"":""

    x

    \n\n""}} + +That warning is unrelated. We're passively passing the authentication token to API requests, even though some API requests don't require a token. This is technical debt we should clean up. + +Closing bug as fixed/worksforme.",task_subcomment,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat warning is unrelated.', ""We're passively passing the authentication token to API requests, even though some API requests don't require a token."", 'This is technical debt we should clean up.', 'Closing bug as fixed/worksforme.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +245094,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","(In reply to comment #1) +> 1. Insert Transclusion +> 2. Ignore ""New template"" panel in the dialog and go to ""+ [] Add content"" +> 3. Type ""x"" +> 4. Apply changes + +5. Show changes +6. Review your changes + + Foo ++ x + Bar + +All works as expected on latest master, and no errors.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n5.', 'Show changes\n6. Review your changes\n\n Foo\n+ x\n Bar\n\nAll works as expected on latest master, and no errors.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']" +245091,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","Doesn't give a error anymore, but API is returning: + + {""warnings"":{""main"":{""*"":""Unrecognized parameter: 'token'""}},""visualeditor"":{""result"":""success"",""content"":""

    x

    \n\n""}}",task_subcomment,"['Doesn\'t give a error anymore, but API is returning: \n\n {""warnings"":{""main"":{""*"":""Unrecognized parameter: \'token\'""}},""visualeditor"":{""result"":""success"",""content"":""

    x

    \\n\\n""}}']",['OBSERVED BUG BEHAVIOR'] +245088,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","(In reply to comment #3) +> (In reply to comment #2) +> > > > > if (content.params) { +> > +> > If we had used coffescript instead of plain JS, it would be so simple to +> > write +> > that as: +> > if content?.params +> > ... +> > +> > Now I assume we'll need to do it manually as +> > if (typeof content !== ""undefined"" && content !== null && content.params) { +> > ... +> > } +> It's much easier than that, you can just do if ( content && content.params ) +> . +> No need to use typeof and string comparisons and all that :) +> +> Really, though, content shouldn't be undefined in the first place. + +Indeed, guarding it with an if statement for content? itself is undesirable because the error is elsewhere.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIndeed, guarding it with an if statement for content?', 'itself is undesirable because the error is elsewhere.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +245083,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","(In reply to comment #2) +> > > > if (content.params) { +> +> If we had used coffescript instead of plain JS, it would be so simple to +> write +> that as: +> if content?.params +> ... +> +> Now I assume we'll need to do it manually as +> if (typeof content !== ""undefined"" && content !== null && content.params) { +> ... +> } +It's much easier than that, you can just do if ( content && content.params ) . No need to use typeof and string comparisons and all that :) + +Really, though, content shouldn't be undefined in the first place.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nIt's much easier than that, you can just do if ( content && content.params ) ."", ""No need to use typeof and string comparisons and all that :)\n\nReally, though, content shouldn't be undefined in the first place.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +245080,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","> > > if (content.params) { + +If we had used coffescript instead of plain JS, it would be so simple to write that as: + if content?.params + ... + +Now I assume we'll need to do it manually as + if (typeof content !== ""undefined"" && content !== null && content.params) { + ... + }",task_subcomment,"['QUOTE\n\nIf we had used coffescript instead of plain JS, it would be so simple to write that as:\n if content?.params\n ...\n\nNow I assume we\'ll need to do it manually as\n if (typeof content !== ""undefined"" && content !== null && content.params) {\n ...\n }']",['INVESTIGATION AND EXPLORATION'] +245075,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'params' of undefined 'content'""","1. Insert Transclusion +2. Ignore ""New template"" panel in the dialog and go to ""+ [] Add content"" +3. Type ""x"" +4. Apply changes +5. > Uncaught TypeError: content is undefined +http://bits.wikimedia.org/static-1.22wmf11/extensions/VisualEditor/modules/ve-mw/dm/nodes/ve.dm.MWTransclusionNode.js:192 + +> ve.dm.MWTransclusionNode.prototype.getWikitext = function() { +> var i, len, part, template, param, content = this.getAttribute('mw'), wikitext = ''; +> > if (content.params) { +> content = {'parts': [{'template': content}]}; +> } + +Uncaught TypeError: Cannot read property 'params' of undefined +ve.dm.MWTransclusionNode.getWikitext +ve.ce.MWTransclusionNode.generateContents +ve.ce.GeneratedContentNode.onUpdate +VeCeGeneratedContentNode +VeCeMWTransclusionNode +VeCeMWTransclusionInlineNode +ve.Factory.create +ve.ce.BranchNode.onSplice +ve.ce.ContentBranchNode.onSplice +oo.EventEmitter.emit +ve.dm.BranchNode.splice +ve.insertIntoArray +ve.dm.Document.rebuildNodes +ve.dm.DocumentSynchronizer.synchronizers.rebuild +ve.dm.DocumentSynchronizer.synchronize +ve.dm.TransactionProcessor.process +ve.dm.Document.commit +ve.dm.Surface.change +ve.dm.SurfaceFragment.insertContent +ve.ui.MWTransclusionDialog.onClose +ve.ui.Window.close +(anonymous function) +proxy",task_subcomment,"['1.', 'Insert Transclusion\n2.', 'Ignore ""New template"" panel in the dialog and go to ""+ [] Add content""\n3.', 'Type ""x""\n4.', 'Apply changes\n5.', ""> Uncaught TypeError: content is undefined\nURL\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nUncaught TypeError: Cannot read property 'params' of undefined\nve.dm.MWTransclusionNode.getWikitext\nve.ce.MWTransclusionNode.generateContents\nve.ce.GeneratedContentNode.onUpdate\nVeCeGeneratedContentNode\nVeCeMWTransclusionNode\nVeCeMWTransclusionInlineNode\nve.Factory.create\nve.ce.BranchNode.onSplice\nve.ce.ContentBranchNode.onSplice\noo.EventEmitter.emit\nve.dm.BranchNode.splice\nve.insertIntoArray\nve.dm.Document.rebuildNodes\nve.dm.DocumentSynchronizer.synchronizers.rebuild\nve.dm.DocumentSynchronizer.synchronize\nve.dm.TransactionProcessor.process\nve.dm.Document.commit\nve.dm.Surface.change\nve.dm.SurfaceFragment.insertContent\nve.ui.MWTransclusionDialog.onClose\nve.ui.Window.close\n(anonymous function)\nproxy""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']" +54169,VisualEditor doesn't confirm closing window,"Unlike the standard source editing windows, VE doesn't confirm closing the page if you have made changes, making it very easy to accidentally close a tab and lose all of your edits. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor doesn't confirm closing window\n\nUnlike the standard source editing windows, VE doesn't confirm closing the page if you have made changes, making it very easy to accidentally close a tab and lose all of your edits."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +243401,VisualEditor doesn't confirm closing window,Yeah I can confirm as well. Not sure when it started working again.,task_subcomment,"['Yeah I can confirm as well.', 'Not sure when it started working again.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +243398,VisualEditor doesn't confirm closing window,"For the record: going to +https://en.wikipedia.org/wiki/Mykola_Labovskyy?veaction=edit +and typing anithing, and then closing the browser tab causes the warning ""Are you sure you want to go back to view mode without saving first?""",task_subcomment,"['For the record: going to\nURL\nand typing anithing, and then closing the browser tab causes the warning ""Are you sure you want to go back to view mode without saving first?""']",['OBSERVED BUG BEHAVIOR'] +243394,VisualEditor doesn't confirm closing window,"I'm going to close this as WORKSFORME because it does (and always has), and the bug report gives no details of how to reproduce. Please re-open if you have steps to reproduce. + +Sorry for very slow triage.",task_subcomment,"[""I'm going to close this as WORKSFORME because it does (and always has), and the bug report gives no details of how to reproduce."", 'Please re-open if you have steps to reproduce.', 'Sorry for very slow triage.']","['ACTION ON ISSUE', 'BUG REPRODUCTION', 'ACTION ON ISSUE']" +54155,"VisualEditor: ""Wikitext markup detected"" message should disappear automatically when there's no more wikitext","""Wikitext markup detected"" message should disappear automatically when there's no more wikitext. Now the user must click it to make it go away. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: ""Wikitext markup detected"" message should disappear automatically when there\'s no more wikitext\n\n""Wikitext markup detected"" message should disappear automatically when there\'s no more wikitext.', 'Now the user must click it to make it go away.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +242535,"VisualEditor: ""Wikitext markup detected"" message should disappear automatically when there's no more wikitext"," + +%%%*** This bug has been marked as a duplicate of bug 51701 ***%%%",task_subcomment,['\n\n%%%*** This bug has been marked as a duplicate of bug 51701 ***%%%'],['ACTION ON ISSUE'] +54125,"VisualEditor - Using ""Select all"" (Ctrl+a) and deleting the selected content afterwards leaves the document uneditable.","Tested on Firefox 22, Monobook and Vector skin. DOES NOT seem to affect Chrome 28 on Vector. + +Steps to reproduce: +- Open the [[Olive Branch High School]] in the visual editor. +- Press CTRL+A to select everything on the page. +- Press Delete. + +The result will be that the entire document becomes uneditable since there is no editable section anymore that the user can click. The console will report the error: +- ""TypeError: node is null"" + +If you don't click anywhere else after pressing delete and start typing the visual editor will behave extremely wonkey. I have seen behavior that ranged from adding an unending steam of pawns to cursor focus jumping all over the page. Additionally, the console will fill with a hailstorm of errors (Below is just a small sample). +- Error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds +- TypeError: parent is null +- Error: Unbalanced set of replace operations found +- Error: Unbalanced input passed to document +- Error: Invalid retain length, cannot retain backwards + +The above is likely just a consequence of the deletion . If i look at firebug's output it seems that Ctrl+A will delete these lines: + +

    +

    + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor - Using ""Select all"" (Ctrl+a) and deleting the selected content afterwards leaves the document uneditable.', 'Tested on Firefox 22, Monobook and Vector skin.', 'DOES NOT seem to affect Chrome 28 on Vector.', 'Steps to reproduce:\n- Open the [[Olive Branch High School]] in the visual editor.', '- Press CTRL+A to select everything on the page.', '- Press Delete.', 'The result will be that the entire document becomes uneditable since there is no editable section anymore that the user can click.', 'The console will report the error:\n- ""TypeError: node is null""\n\nIf you don\'t click anywhere else after pressing delete and start typing the visual editor will behave extremely wonkey.', 'I have seen behavior that ranged from adding an unending steam of pawns to cursor focus jumping all over the page.', 'Additionally, the console will fill with a hailstorm of errors (Below is just a small sample).', '- Error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds \n- TypeError: parent is null \n- Error: Unbalanced set of replace operations found \n- Error: Unbalanced input passed to document\n- Error: Invalid retain length, cannot retain backwards\n\nThe above is likely just a consequence of the deletion .', 'If i look at firebug\'s output it seems that Ctrl+A will delete these lines:\n\n

    \n

    \n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +240932,"VisualEditor - Using ""Select all"" (Ctrl+a) and deleting the selected content afterwards leaves the document uneditable.","This is a duplicate of bug 50947 - merging. + +*** This bug has been marked as a duplicate of bug 50947 ***",task_subcomment,"['This is a duplicate of bug 50947 - merging.', '*** This bug has been marked as a duplicate of bug 50947 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +240925,"VisualEditor - Using ""Select all"" (Ctrl+a) and deleting the selected content afterwards leaves the document uneditable.","On Firefox I can get pawns too, or keypresses causing the character to appear twice, if I do +1. Control-A +2. Delete +3. type 'a' + +But the page becomes unusable if I follow these steps: +1. Control-A +2. Delete +3. Click on the link icon, or anything else +4. type a- doesnt work",task_subcomment,"['On Firefox I can get pawns too, or keypresses causing the character to appear twice, if I do\n1.', 'Control-A\n2.', ""Delete\n3. type 'a'\n\nBut the page becomes unusable if I follow these steps:\n1."", 'Control-A\n2.', 'Delete\n3.', 'Click on the link icon, or anything else\n4. type a- doesnt work']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +240917,"VisualEditor - Using ""Select all"" (Ctrl+a) and deleting the selected content afterwards leaves the document uneditable.","Slight alteration: Chrome 28 does seem to be affected after all, though the problem is less severe. + +(Chrome) +- Open the [[Nodeulseom]] in the visual editor. +- Press CTRL+A to select everything on the page. +- Press Delete. + +Chrome will place a pawn (♙) in the article as soon as one starts typing after the deletion. Often this pawn is also a hyperlink. Firefox will behave in a similar fashion on this specific page. + +Both Chrome and Firefox report a single error in the console: +""Error: Offset could not be translated to a DOM element and offset: 3"" + +This is probably because the article in this instance isn't blanked entirely. Ctrl+a followed by delete doesn't seem to delete the categories present in the article.",task_subcomment,"['Slight alteration: Chrome 28 does seem to be affected after all, though the problem is less severe.', '(Chrome)\n- Open the [[Nodeulseom]] in the visual editor.', '- Press CTRL+A to select everything on the page.', '- Press Delete.', 'Chrome will place a pawn (♙) in the article as soon as one starts typing after the deletion.', 'Often this pawn is also a hyperlink.', 'Firefox will behave in a similar fashion on this specific page.', 'Both Chrome and Firefox report a single error in the console:\n""Error: Offset could not be translated to a DOM element and offset: 3""\n\nThis is probably because the article in this instance isn\'t blanked entirely.', ""Ctrl+a followed by delete doesn't seem to delete the categories present in the article.""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +54124,VisualEditor or Parsoid: Breaks and partially duplicates html tag,"en.wp editor DragonsFlight reports a strange diff at https://en.wikipedia.org/w/index.php?title=Axial_precession&diff=next&oldid=565790907 where a
    was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor or Parsoid: Breaks and partially duplicates html tag\n\nen.wp editor DragonsFlight reports a strange diff at URL where a
    was duplicated minus the leading <\n\nPossibly related to bug 51304?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +240895,VisualEditor or Parsoid: Breaks and partially duplicates html tag,"Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue. Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.",task_subcomment,"[""Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue."", 'Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']" +240890,VisualEditor or Parsoid: Breaks and partially duplicates html tag,"Given the proximity of the image, im guessing this is bug 52107.",task_subcomment,"['Given the proximity of the image, im guessing this is bug 52107.']",['OBSERVED BUG BEHAVIOR'] +54116,VisualEditor - EditIntro is incorrectly linked in the monobook skin.,"(Tested on Firefox 22) + +It seems that the ""&editintro=Template:BLP_editintro"" URL is accidentally reversed on Monobook. + +Steps to reproduce: +(Vector - Working correctly) +- Navigate to [[Martin J. Silverstein]]. +-- The ""Edit"" link will be: https://en.wikipedia.org/wiki/Martin_J._Silverstein?veaction=edit +-- The ""Edit Source"" link will be: https://en.wikipedia.org/w/index.php?title=Martin_J._Silverstein&action=edit&editintro=Template:BLP_editintro + +(Monobook - Working incorrectly) +- Navigate to [[Martin J. Silverstein]]. +-- The ""Edit"" link will be: https://en.wikipedia.org/wiki/Martin_J._Silverstein?veaction=edit&editintro=Template:BLP_editintro +-- The ""Edit Source"" link will be: https://en.wikipedia.org/w/index.php?title=Martin_J._Silverstein&action=edit + +As far as i can see only the source editor can load a template when using the ""EditIntro"" parameter in the URL. In monobook, it seems that the EditIntro parameter is accidentally added to the Visual Editor link instead of the Edit Source link. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor - EditIntro is incorrectly linked in the monobook skin.', '(Tested on Firefox 22)\n\nIt seems that the ""&editintro=Template:BLP_editintro"" URL is accidentally reversed on Monobook.', 'Steps to reproduce:\n(Vector - Working correctly)\n- Navigate to [[Martin J. Silverstein]].', '-- The ""Edit"" link will be: URL\n-- The ""Edit Source"" link will be: URL\n\n(Monobook - Working incorrectly)\n- Navigate to [[Martin J. Silverstein]].', '-- The ""Edit"" link will be: URL\n-- The ""Edit Source"" link will be: URL\n\nAs far as i can see only the source editor can load a template when using the ""EditIntro"" parameter in the URL.', 'In monobook, it seems that the EditIntro parameter is accidentally added to the Visual Editor link instead of the Edit Source link.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +240385,VisualEditor - EditIntro is incorrectly linked in the monobook skin.,"Marking as INVALID, as per standard practice for issues with on-wiki code. (Has this been fixed?)",task_subcomment,"['Marking as INVALID, as per standard practice for issues with on-wiki code.', '(Has this been fixed?)']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +240378,VisualEditor - EditIntro is incorrectly linked in the monobook skin.,Confirming problem exists. The fix probably needs to be made at [[MediaWiki:Common.js]],task_subcomment,"['Confirming problem exists.', 'The fix probably needs to be made at [[MediaWiki:Common.js]]']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +54107,VisualEditor: image followed immediately with wikilink causes dirty diff,"See https://en.wikipedia.org/w/index.php?title=Karma_in_Hinduism&diff=564615505&oldid=564615290 and https://en.wikipedia.org/w/index.php?title=Karma_in_Hinduism&diff=565801063&oldid=565800169 + +Reproduced at https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&diff=565853026&oldid=565852620, https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&diff=565853312&oldid=565853264 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,['VisualEditor: image followed immediately with wikilink causes dirty diff\n\nSee URL and URL\n\nReproduced at URL URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR'] +239940,VisualEditor: image followed immediately with wikilink causes dirty diff,"Sorry for getting to this bug so late. + +I can't reproduce this bug at all. However, I have a number of confusions and questions about the bug report such that I don't know if that's because the bug has been fixed, was never present, or I just can't understand it… :-( + +""In VE, the image is not editable."" + +What does ""not editable"" mean? You can't move? Can't resize? Can't add a caption? Can't delete? Doesn't appear? + +""(note the diff is a mess)"" + +Is it? What kind of mess? Details help a lot in a complex system so we can tell whether we can reproduce or not. Is the VE still the same VE that you had open in step 2 (with the changes made to the text line into ""abc def gh"", and the WT changes made in step 3 also made but in parallel to the edit)? + +See https://www.mediawiki.org/wiki/VisualEditor:Bug_52107 for my testing page. + +Am provisionally marking this as ""WORKSFORME"", which is very unsatisfactory. :-( Happy to review if we can have further information.",task_subcomment,"['Sorry for getting to this bug so late.', ""I can't reproduce this bug at all."", 'However, I have a number of confusions and questions about the bug report such that I don\'t know if that\'s because the bug has been fixed, was never present, or I just can\'t understand it… :-(\n\n""In VE, the image is not editable.""', 'What does ""not editable"" mean?', ""You can't move?"", ""Can't resize?"", ""Can't add a caption?"", ""Can't delete?"", ""Doesn't appear?"", '""(note the diff is a mess)""\n\nIs it?', 'What kind of mess?', 'Details help a lot in a complex system so we can tell whether we can reproduce or not.', 'Is the VE still the same VE that you had open in step 2 (with the changes made to the text line into ""abc def gh"", and the WT changes made in step 3 also made but in parallel to the edit)?', 'See URL for my testing page.', 'Am provisionally marking this as ""WORKSFORME"", which is very unsatisfactory.', ':-( Happy to review if we can have further information.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'WORKAROUNDS', 'ACTION ON ISSUE']" +239930,VisualEditor: image followed immediately with wikilink causes dirty diff,"Here is another case that looks similar: +https://en.wikipedia.org/w/index.php?title=Persian_language&diff=prev&oldid=566108307",task_subcomment,['Here is another case that looks similar:\nURL'],['OBSERVED BUG BEHAVIOR'] +239921,VisualEditor: image followed immediately with wikilink causes dirty diff,"Steps to reproduce: +1. Create a page with + +"" +abc + +def gh + +[[File:Andrew-W.K.-The-Party-All-Goddamn-Night-EP-2011.jpg|thumb|right]][[Sambanthar|Thirugnana Sambanthar]] of the [[Shaiva Siddhanta]] school. +"" + +2. In VE, the image is not editable. Place the cursor at 'c', press space and then delete: converting the first line to ""abc def gh"" - press save, review changes. + +(note that the diff looks good. Do not save.) + +3. In Source Editor, after gh add ' ij' and save + +4. In VE, repeat step 2 + +(note the diff is a mess) + +Confirmed any image does this; and tested in Chrome and Firefox.",task_subcomment,"['Steps to reproduce:\n1.', 'Create a page with\n\n""\nabc\n\ndef gh\n\n[[File:Andrew-W.K.-The-Party-All-Goddamn-Night-EP-2011.jpg|thumb|right]][[Sambanthar|Thirugnana Sambanthar]] of the [[Shaiva Siddhanta]] school.\n""', '2.', 'In VE, the image is not editable.', 'Place the cursor at \'c\', press space and then delete: converting the first line to ""abc def gh"" - press save, review changes.', '(note that the diff looks good.', 'Do not save.)', '3.', ""In Source Editor, after gh add ' ij' and save\n\n4."", 'In VE, repeat step 2\n\n(note the diff is a mess)\n\nConfirmed any image does this; and tested in Chrome and Firefox.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +239917,VisualEditor: image followed immediately with wikilink causes dirty diff,"This looks like a string buffer problem, as it inserts different pieces of text into the same spot. And it appears to only happen every second edit. + +https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&action=history&offset=20130727021955&limit=4 + +The testcase is fairly small now +https://en.wikipedia.org/wiki/User:John_Vandenberg/test + +My process for reproducing the bug is to open the page in VE, merge the first two paragraphs (i.e. bring 'other Hindu views' up to the 'and'). Review. +If that doesnt trigger it, edit source, remove a word further down in the page, save, and remove the process in VE.",task_subcomment,"['This looks like a string buffer problem, as it inserts different pieces of text into the same spot.', 'And it appears to only happen every second edit.', 'URL\n\nThe testcase is fairly small now\nURL\n\nMy process for reproducing the bug is to open the page in VE, merge the first two paragraphs (i.e.', ""bring 'other Hindu views' up to the 'and')."", 'Review.', 'If that doesnt trigger it, edit source, remove a word further down in the page, save, and remove the process in VE.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +54103,Missing nowiki escaping when single quotes wrap new i/b tags,"Reported at: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Link_formatting_trick + +Simplified test cases here: + +[subbu@earth lib] echo ""[[Foo|'foo']]"" | node parse | sed ""s/foo/foo<\/i>/g;"" | node parse --html2wt +[[Foo|'''foo''']] + +[subbu@earth lib] echo ""[[Foo|'foo']]"" | node parse | sed ""s/foo/foo<\/b>/g;"" | node parse --html2wt +[[Foo|''''foo'''']] + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Missing nowiki escaping when single quotes wrap new i/b tags\n\nReported at: URL\n\nSimplified test cases here:\n\n[subbu@earth lib] echo ""[[Foo|\'foo\']]"" | node parse | sed ""s/foo/foo<\\/i>/g;"" | node parse --html2wt\n[[Foo|\'\'\'foo\'\'\']]\n\n[subbu@earth lib] echo ""[[Foo|\'foo\']]"" | node parse | sed ""s/foo/foo<\\/b>/g;"" | node parse --html2wt\n[[Foo|\'\'\'\'foo\'\'\'\']]\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['BUG REPRODUCTION'] +239734,Missing nowiki escaping when single quotes wrap new i/b tags,Deployed and tested in production.,task_subcomment,['Deployed and tested in production.'],['SOLUTION USAGE'] +239730,Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76467 merged by jenkins-bot: +Take #2: (Bug 52103) nowiki escaping when quotes surround i/b tags + +https://gerrit.wikimedia.org/r/76467",task_subcomment,['Change 76467 merged by jenkins-bot:\nTake #2: (Bug 52103) nowiki escaping when quotes surround i/b tags\n\nGERRIT_URL'],['ACTION ON ISSUE'] +239726,Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76467 had a related patch set uploaded by Subramanya Sastry: +Take #2: (Bug 52103) nowiki escaping when quotes surround i/b tags + +https://gerrit.wikimedia.org/r/76467",task_subcomment,['Change 76467 had a related patch set uploaded by Subramanya Sastry:\nTake #2: (Bug 52103) nowiki escaping when quotes surround i/b tags\n\nGERRIT_URL'],['ACTION ON ISSUE'] +239719,Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76162 merged by jenkins-bot: +(Bug 52103) escape when single quotes wrap new i/b tags + +https://gerrit.wikimedia.org/r/76162",task_subcomment,['Change 76162 merged by jenkins-bot:\n(Bug 52103) escape when single quotes wrap new i/b tags\n\nGERRIT_URL'],['BUG REPRODUCTION'] +239713,Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76162 had a related patch set uploaded by Subramanya Sastry: +(Bug 52103) escape when single quotes wrap new i/b tags + +https://gerrit.wikimedia.org/r/76162",task_subcomment,['Change 76162 had a related patch set uploaded by Subramanya Sastry:\n(Bug 52103) escape when single quotes wrap new i/b tags\n\nGERRIT_URL'],['BUG REPRODUCTION'] +54086,User preference to disable VisualEditor (VE product),"This bug is about the generalisation of the solution deployed in bug #50929 in the Wikimedia environment. Having in mind the medium term of the deployment of the VisualEditor in many/most of the MediaWiki wikis, it could be a good idea to give the sysadmins the choice of enabling or disabling the VisualEditor by default for registrated users, with a LocalSettings parameter wgVisualEditorDefault. + +This would give the choice to the sysadmins to enable by default or not the VE for registrated users (for anons there is already the preference wgVisualEditorDisableForAnons), and this could be directly used in the Wikimedia environment to replace the parameter $wmgVisualEditorDefault. + +To resolve this bug, the patch https://gerrit.wikimedia.org/r/#/c/75541/ could be generalised by renaming the new preference ""visualeditor-betatempdisable"" into ""visualeditor-preference-disable"", and depending of the variable wgVisualEditorDefault either the positive preference (for alpha/beta environments, ""Enable the VE"") or the negative preference (for production environments, ""Disable the VE"") would be used, the other preference being hidden with wgHiddenPrefs. + +In the normal scenario the wiki change from beta to production environment, it would be easy for the sysadmin to change the wgVisualEditorDefault value from false to true and this would automatically activate the VE during the change, so that the users are aware of the new setting and have the possibility of seeing the new editor (some welcoming message could be displayed then) and if users don’t like it they are given the possibility to disable it (or not if the relevant preference is hidden, but this is a sysadmin/community choice). + +I point out the default messages visualeditor-preference-enable/disable should have a general-wiki phrasing, and any Wikimedia customisation (about namespaces where it is enabled, about the time the parameter is available before possibly hide the preference) should be customised in the WikimediaMessages extension (see my comment https://bugzilla.wikimedia.org/show_bug.cgi?id=50929#c34 ). + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50929",task_description,"['User preference to disable VisualEditor (VE product)\n\nThis bug is about the generalisation of the solution deployed in bug #50929 in the Wikimedia environment.', 'Having in mind the medium term of the deployment of the VisualEditor in many/most of the MediaWiki wikis, it could be a good idea to give the sysadmins the choice of enabling or disabling the VisualEditor by default for registrated users, with a LocalSettings parameter wgVisualEditorDefault.', 'This would give the choice to the sysadmins to enable by default or not the VE for registrated users (for anons there is already the preference wgVisualEditorDisableForAnons), and this could be directly used in the Wikimedia environment to replace the parameter $wmgVisualEditorDefault.', 'To resolve this bug, the patch URL could be generalised by renaming the new preference ""visualeditor-betatempdisable"" into ""visualeditor-preference-disable"", and depending of the variable wgVisualEditorDefault either the positive preference (for alpha/beta environments, ""Enable the VE"") or the negative preference (for production environments, ""Disable the VE"") would be used, the other preference being hidden with wgHiddenPrefs.', 'In the normal scenario the wiki change from beta to production environment, it would be easy for the sysadmin to change the wgVisualEditorDefault value from false to true and this would automatically activate the VE during the change, so that the users are aware of the new setting and have the possibility of seeing the new editor (some welcoming message could be displayed then) and if users don’t like it they are given the possibility to disable it (or not if the relevant preference is hidden, but this is a sysadmin/community choice).', 'I point out the default messages visualeditor-preference-enable/disable should have a general-wiki phrasing, and any Wikimedia customisation (about namespaces where it is enabled, about the time the parameter is available before possibly hide the preference) should be customised in the WikimediaMessages extension (see my comment URL ).', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['BUG REPRODUCTION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE']" +238867,User preference to disable VisualEditor (VE product),"I am a bit disappointed by this closing, although it was only a suggestion of generalisation of the Wikimedia configuration for progressive deployment on third-party wikis. But it’s not very important.",task_subcomment,"['I am a bit disappointed by this closing, although it was only a suggestion of generalisation of the Wikimedia configuration for progressive deployment on third-party wikis.', 'But it’s not very important.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']" +238859,User preference to disable VisualEditor (VE product),"On-wiki configuration management is a much bigger piece than just for VisualEditor; I think it's probably marking this as WONTFIX within the context of VE, but instead suggest that the RfCs for this (as a piecemeal approach seems worse than nothing).",task_subcomment,"[""On-wiki configuration management is a much bigger piece than just for VisualEditor; I think it's probably marking this as WONTFIX within the context of VE, but instead suggest that the RfCs for this (as a piecemeal approach seems worse than nothing).""]",['SOLUTION DISCUSSION'] +238853,User preference to disable VisualEditor (VE product),"(In reply to comment #0) +... +> I point out the default messages visualeditor-preference-enable/disable +> should +> have a general-wiki phrasing, and any Wikimedia customisation (about +> namespaces +> where it is enabled, about the time the parameter is available before +> possibly +> hide the preference) should be customised in the WikimediaMessages extension +> (see my comment https://bugzilla.wikimedia.org/show_bug.cgi?id=50929#c34 ). + +About this, see also bug 52188.",task_subcomment,"['(In reply to comment #0)\n...\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAbout this, see also bug 52188.']",['MOTIVATION'] +238849,User preference to disable VisualEditor (VE product),"In the proposed scenario the default values of the two preferences visualeditor-enable and visualeditor-disable would be false: in a beta environment the default is ""not enabled by default=false"", and in the production environment the default is ""not disabled by default=false"".",task_subcomment,"['In the proposed scenario the default values of the two preferences visualeditor-enable and visualeditor-disable would be false: in a beta environment the default is ""not enabled by default=false"", and in the production environment the default is ""not disabled by default=false"".']",['SOLUTION DISCUSSION'] +54083,VisualEditor: References that are added by templates are not recognized by the references tool,"I saw bugs that are similar to this one, for example Bug 51289, but nothing exactly like this one. + +References that are added by templates are not recognized by the references tool. I am not talking about templates like the English Wikipedia's {{cite web}}, which go inside the tag, but about template that add the tag itself (with {{#tag:ref}}). + +This can be in infoboxes (Bug 51289) or in any other template. The Hebrew Wikipedia, for example, uses such a template, {{הערה}} very extensively, because mixing right-to-left text with left-to-right XML tags like is very hard to edit. This means that most of the references there are not usable for reusing in the ""Use an existing reference"". + +(This also means a bunch of other things, but I'll report them separately.) + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: References that are added by templates are not recognized by the references tool\n\nI saw bugs that are similar to this one, for example Bug 51289, but nothing exactly like this one.', 'References that are added by templates are not recognized by the references tool.', ""I am not talking about templates like the English Wikipedia's {{cite web}}, which go inside the tag, but about template that add the tag itself (with {{#tag:ref}})."", 'This can be in infoboxes (Bug 51289) or in any other template.', 'The Hebrew Wikipedia, for example, uses such a template, {{הערה}} very extensively, because mixing right-to-left text with left-to-right XML tags like is very hard to edit.', 'This means that most of the references there are not usable for reusing in the ""Use an existing reference"".', ""(This also means a bunch of other things, but I'll report them separately.)"", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +238669,VisualEditor: References that are added by templates are not recognized by the references tool,"The problems with references created by templates are numerous, and possibly impossible to fix ({{#tag:ref}} was never meant to work and this is an example of it not working). :-( + +In general they are part of bug 50474, but I'll expand that to be clearer. + +*** This bug has been marked as a duplicate of bug 50474 ***",task_subcomment,"['The problems with references created by templates are numerous, and possibly impossible to fix ({{#tag:ref}} was never meant to work and this is an example of it not working).', "":-(\n\nIn general they are part of bug 50474, but I'll expand that to be clearer."", '*** This bug has been marked as a duplicate of bug 50474 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +54080,"Wrong tab-order on the ""Edit summary"" window","A5b writes: + +Edit page, then click save to get ""Edit summary"" Window. Don't touch mouse, put some description, using the keyboard. Then we want to change checkboxes ""minor edit"" or ""watch page"", without using the mouse. Press key, and you will be directed to the link ""minor edit"" not to the checkbox. second Tab - is ""Save Page"" button. Next - ""review changes"". Next three tabs - for links in the footer of this windows. + +Is it possible to change tab order to this (e.g. using tabindex argument or via rearranging divs and other elements): +*1. ""description"" +*2. ""minor edit checkbox"" +*3. ""watch page checkbox"" +*4. ""Save page"" +*5. ""review changes"" +*6. anything else +Or even move ""save page"" and ""review"" to be just after ""description"". + +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback#Wrong tab-order on the ""Edit summary"" window + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Wrong tab-order on the ""Edit summary"" window\n\nA5b writes:\n\nEdit page, then click save to get ""Edit summary"" Window.', ""Don't touch mouse, put some description, using the keyboard."", 'Then we want to change checkboxes ""minor edit"" or ""watch page"", without using the mouse.', 'Press key, and you will be directed to the link ""minor edit"" not to the checkbox.', 'second Tab - is ""Save Page"" button.', 'Next - ""review changes"".', 'Next three tabs - for links in the footer of this windows.', 'Is it possible to change tab order to this (e.g.', 'using tabindex argument or via rearranging divs and other elements): \n*1.', '""description""\n*2.', '""minor edit checkbox""\n*3.', '""watch page checkbox""\n*4.', '""Save page""\n*5.', '""review changes""\n*6. anything else\nOr even move ""save page"" and ""review"" to be just after ""description"".', 'URL tab-order on the ""Edit summary"" window\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +238544,"Wrong tab-order on the ""Edit summary"" window"," + +*** This bug has been marked as a duplicate of bug 51918 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51918 ***'],['ACTION ON ISSUE'] +238536,"Wrong tab-order on the ""Edit summary"" window"," + +*** This bug has been marked as a duplicate of bug 50047 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50047 ***'],['ISSUE CONTENT MANAGEMENT'] +54044,VisualEditor: only a part of word is linked and is added,"When I select text that ends in the middle of the word and add a link, only the selected part is linked. Also, is added after the link. + +For example, in https://en.wikipedia.org/w/index.php?title=Ramat_Yohanan&diff=565789129&oldid=553919950 I selected ""South Africa"" and added the link. I saw an AbuseFilter warning when I was saving, but saved anyway to report the bug :) + +Being a seasoned Wikipedian, I expect the whole word to be linked, although now that I think of it, I can imagine that linking a part of the word can be useful, too. So I'm not completely sure whether it's a bug or a feature. + +This may be related to Bug 50127, though the description is not the same. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: only a part of word is linked and is added\n\nWhen I select text that ends in the middle of the word and add a link, only the selected part is linked.', 'Also, is added after the link.', 'For example, in URL I selected ""South Africa"" and added the link.', 'I saw an AbuseFilter warning when I was saving, but saved anyway to report the bug :)\n\nBeing a seasoned Wikipedian, I expect the whole word to be linked, although now that I think of it, I can imagine that linking a part of the word can be useful, too.', ""So I'm not completely sure whether it's a bug or a feature."", 'This may be related to Bug 50127, though the description is not the same.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +235865,VisualEditor: only a part of word is linked and is added,"This is not a 'bug', but intentional behaviour. + +If you actually want to produce [[Foo]]ian as opposed to [[Foo|Fooian]], VisualEditor/Parsoid doesn't have a way to guarantee that (right now Parsoid creates piped links even when it could do link trails/heads, but this could change in the future), because it's irrelevant to the reader and to editors. + +Consequently I'm marking this as ""WONTFIX"", but see bug 37939 for a wider discussion of the usability issue.",task_subcomment,"[""This is not a 'bug', but intentional behaviour."", ""If you actually want to produce [[Foo]]ian as opposed to [[Foo|Fooian]], VisualEditor/Parsoid doesn't have a way to guarantee that (right now Parsoid creates piped links even when it could do link trails/heads, but this could change in the future), because it's irrelevant to the reader and to editors."", 'Consequently I\'m marking this as ""WONTFIX"", but see bug 37939 for a wider discussion of the usability issue.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +54036,VisualEditor: blanking a page doesn't remove comments,"See https://en.wikipedia.org/w/index.php?title=User:Octalpuss/sandbox&oldid=565273394, which, blanked, turns into https://en.wikipedia.org/w/index.php?title=User:Octalpuss/sandbox&oldid=565667534 + +I appreciate with the lack of comment-editing (or comment viewing) preserving these is usually A Good Thing, but we do need a better way of handling them. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60830",task_description,"[""VisualEditor: blanking a page doesn't remove comments\n\nSee URL which, blanked, turns into URL\n\nI appreciate with the lack of comment-editing (or comment viewing) preserving these is usually A Good Thing, but we do need a better way of handling them."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +235456,VisualEditor: blanking a page doesn't remove comments," + +*** This bug has been marked as a duplicate of bug 49603 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49603 ***'],['ISSUE CONTENT MANAGEMENT'] +235450,VisualEditor: blanking a page doesn't remove comments,"Providing new link since that user's sandbox is gone: +https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=63959567&oldid=63959556 .",task_subcomment,"[""Providing new link since that user's sandbox is gone:\nURL .""]",['INVESTIGATION AND EXPLORATION'] +54032,VisualEditor: No easy way to add content before a template at the start of a line,"PamD at the English Wikipedia reports that there is no easy way to add new content between a reflist and a template that follows it before you save the page. + +This is a problem if your workflow is to add the stub template before adding the external links, which is entirely reasonable. + +Steps to reproduce (option 1): +1. create page with references and a reflist. +2. add a template (e.g. a stub template) after the reflist +3. add content between the references list and the template (e.g. an external links section). + +Steps to reproduce (option 2): +1. Go to a page with no content between a reflist block and a template (e.g. https://en.wikipedia.org/w/index.php?title=Tyson_R._Roberts&oldid=565739822&veaction=edit ) +2. Delete all content after the reflist: +3. Add a template (e.g. a stub template) +4. Add content between the references list and the template (e.g. an external links section). + +There is a workaround: select the reflist, press the right cursor key once, press enter. This gets you a blank line with which to work from. + +Desired behaviour: +There should be somewhere to click between the reflist and the stub template, just as there is after the page has been saved and reopened in VE. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=52620",task_description,"['VisualEditor: No easy way to add content before a template at the start of a line\n\nPamD at the English Wikipedia reports that there is no easy way to add new content between a reflist and a template that follows it before you save the page.', 'This is a problem if your workflow is to add the stub template before adding the external links, which is entirely reasonable.', 'Steps to reproduce (option 1): \n1. create page with references and a reflist.', '2. add a template (e.g.', 'a stub template) after the reflist\n3. add content between the references list and the template (e.g.', 'an external links section).', 'Steps to reproduce (option 2):\n1.', 'Go to a page with no content between a reflist block and a template (e.g.', 'URL )\n2.', 'Delete all content after the reflist:\n3.', 'Add a template (e.g.', 'a stub template)\n4.', 'Add content between the references list and the template (e.g.', 'an external links section).', 'There is a workaround: select the reflist, press the right cursor key once, press enter.', 'This gets you a blank line with which to work from.', 'Desired behaviour: \nThere should be somewhere to click between the reflist and the stub template, just as there is after the page has been saved and reopened in VE.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'WORKAROUNDS', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +235138,VisualEditor: No easy way to add content before a template at the start of a line,"This is caused by bug 49784; if we knew that the template you'd just added was a block, we would insert a slug above the template (which exists precisely for this reason). Merging. + +*** This bug has been marked as a duplicate of bug 49784 ***",task_subcomment,"[""This is caused by bug 49784; if we knew that the template you'd just added was a block, we would insert a slug above the template (which exists precisely for this reason)."", 'Merging.', '*** This bug has been marked as a duplicate of bug 49784 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +235130,VisualEditor: No easy way to add content before a template at the start of a line,"Whatamidoing comments that the issue is that there is no way easy to select a line starting with a template: + +So someone added a book to a ==Further reading== section. Book #1 used a citation template. Book #2 did not. Neither had bullet list formatting. + +Selecting them was hard. I ended up selecting the header, the template, and the plain-text citation. Then I clicked the 'list' button. Then I went back and repaired the formatting for the section heading. This isn't necessary, but it was easier than trying to figure out the exact stop to place the cursor. + +[...] + +[The] problem is that it's hard to select just the line that contains the template. You have to find the magic spot in the middle of ""==Heading=={{template}}"" to select the template without picking up the entire section heading. I managed it later in testing, but only if I'm selecting text with arrow keys. With the trackpad, it's still beyond me.",task_subcomment,"['Whatamidoing comments that the issue is that there is no way easy to select a line starting with a template:\n\nSo someone added a book to a ==Further reading== section.', 'Book #1 used a citation template.', 'Book #2 did not.', 'Neither had bullet list formatting.', 'Selecting them was hard.', 'I ended up selecting the header, the template, and the plain-text citation.', ""Then I clicked the 'list' button."", 'Then I went back and repaired the formatting for the section heading.', ""This isn't necessary, but it was easier than trying to figure out the exact stop to place the cursor."", ""[...]\n\n[The] problem is that it's hard to select just the line that contains the template."", 'You have to find the magic spot in the middle of ""==Heading=={{template}}"" to select the template without picking up the entire section heading.', ""I managed it later in testing, but only if I'm selecting text with arrow keys."", ""With the trackpad, it's still beyond me.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +54028,TemplateData should allow specifying default values for parameters,"TemplateData should allow some parameters to have default values which are prefilled when using the VisualEditor transclusion manager. + +An example would be the current date for accessdate in citation templates. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['TemplateData should allow specifying default values for parameters\n\nTemplateData should allow some parameters to have default values which are prefilled when using the VisualEditor transclusion manager.', 'An example would be the current date for accessdate in citation templates.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +234901,TemplateData should allow specifying default values for parameters," + +*** This bug has been marked as a duplicate of bug 51428 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51428 ***'],['ACTION ON ISSUE'] +53998,"When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position","**Author:** `lovefilms` + +**Description:** +The screen shot of the missing Production section trying to edit + +When click on Edit to edit a section of an article, for example, +https://en.wikipedia.org/wiki/Blue_Jasmine#Production +the result page https://en.wikipedia.org/wiki/Blue_Jasmine?veaction=edit#Production appears to be a huge toolbar on top, and the section of ""Production"" is almost invisible - see attached screen shot. + +Also, the toolbar should be clearly marked with visible borders to distinguished from the contents of an article. Now it's almost blurred into the article and very confusing. + +-------------------------- +**Version**: unspecified +**Severity**: major +**OS**: Windows 7 +**Platform**: PC + +**Attached**: {F11047}",task_description,"['When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position\n\n**Author:** CODE\n\n**Description:**\nThe screen shot of the missing Production section trying to edit\n\nWhen click on Edit to edit a section of an article, for example, \nURL\nthe result page URL appears to be a huge toolbar on top, and the section of ""Production"" is almost invisible - see attached screen shot.', 'Also, the toolbar should be clearly marked with visible borders to distinguished from the contents of an article.', ""Now it's almost blurred into the article and very confusing."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**OS**: Windows 7\n**Platform**: PC\n\n**Attached**: {F11047}']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +232237,"When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position","**lovefilms** wrote: + +I am in FF23.0.1 and the VisualEditor is working as intended now. I go ahead to mark it as Resolved - since people can always use the new version of FF.",task_subcomment,"['**lovefilms** wrote:\n\nI am in FF23.0.1 and the VisualEditor is working as intended now.', 'I go ahead to mark it as Resolved - since people can always use the new version of FF.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE']" +232234,"When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position","Firefox 23.0 for Ubuntu: + +Everything works fine when clicking the ""Edit (beta)"" link at https://en.wikipedia.org/wiki/Blue_Jasmine#Production - fullscreen window as well as small window. + + +Chromium 28.0.1500.71 for Ubuntu + +Same thing a above. It just works.",task_subcomment,"['Firefox 23.0 for Ubuntu:\n\nEverything works fine when clicking the ""Edit (beta)"" link at URL - fullscreen window as well as small window.', 'Chromium 28.0.1500.71 for Ubuntu \n\nSame thing a above.', 'It just works.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +232230,"When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position","**lovefilms** wrote: + +I am using Firefox 22 as well (on Windows 7). + +The IE9 doesn't seem to have the VisualEditor, the edit link will simply goes to https://en.wikipedia.org/w/index.php?title=Blue_Jasmine&action=edit§ion=3",task_subcomment,"['**lovefilms** wrote:\n\nI am using Firefox 22 as well (on Windows 7).', ""The IE9 doesn't seem to have the VisualEditor, the edit link will simply goes to URL""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +232225,"When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position","(e/c) I can reproduce on Firefox 22/Linux and Windows, and on Chrome/Windows to a lesser degree when using https://en.wikipedia.org/wiki/Blue_Jasmine?veaction=edit#Production or when loading https://en.wikipedia.org/wiki/Blue_Jasmine?veaction=edit and click the 'edit' link beside 'Production' (the bug doesnt occur if middle-clicked, as that open the url with 'vesection=3' added). + +Most times I do this, it is possible to see the viewport position itself correctly at the anchor, but then then toolbar appears covering the section heading and a half of the first line of text.",task_subcomment,"[""(e/c) I can reproduce on Firefox 22/Linux and Windows, and on Chrome/Windows to a lesser degree when using URL or when loading URL and click the 'edit' link beside 'Production' (the bug doesnt occur if middle-clicked, as that open the url with 'vesection=3' added)."", 'Most times I do this, it is possible to see the viewport position itself correctly at the anchor, but then then toolbar appears covering the section heading and a half of the first line of text.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +232218,"When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position","I think is is related to screen resolution \ the size of the browser window. If you have a low resolution (Or resize the browser window to be small enough) Firefox 22 and Chrome 28 will place the ""ve-ui-toolbar-actions"" element on a second line in the edit toolbar. + +If you edit a section in the small-size browser it will scroll to the section as it normally would, but doesn't take the twice-as-high-as-usual edit toolbar into account when determining where to stop. As a result the section header is actually positioned under the second toolbar line. If you resize the browser afterwards to a size that allows for a single-line edit toolbar the section header will be correctly positioned.",task_subcomment,"['I think is is related to screen resolution \\ the size of the browser window.', 'If you have a low resolution (Or resize the browser window to be small enough) Firefox 22 and Chrome 28 will place the ""ve-ui-toolbar-actions"" element on a second line in the edit toolbar.', ""If you edit a section in the small-size browser it will scroll to the section as it normally would, but doesn't take the twice-as-high-as-usual edit toolbar into account when determining where to stop."", 'As a result the section header is actually positioned under the second toolbar line.', 'If you resize the browser afterwards to a size that allows for a single-line edit toolbar the section header will be correctly positioned.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +232210,"When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position","Which Firefox version is this about? +Can you reproduce the problem with other browsers?",task_subcomment,"['Which Firefox version is this about?', 'Can you reproduce the problem with other browsers?']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +53989,"VisualEditor: ""add template"" should have the same functionality as return in the template dialog","If you type, say, 'cite w' into the template selector, it drops down a list of possible templates. Hitting return inserts the one that was selected from that dropdown. Great! + +Hitting 'add template', however, does not; it returns 'cite w', a non-existent template. It would be good if 'add template''s behaviour could mimic that of the return key. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: ""add template"" should have the same functionality as return in the template dialog\n\nIf you type, say, \'cite w\' into the template selector, it drops down a list of possible templates.', 'Hitting return inserts the one that was selected from that dropdown.', 'Great!', ""Hitting 'add template', however, does not; it returns 'cite w', a non-existent template."", ""It would be good if 'add template''s behaviour could mimic that of the return key."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +255208,"VisualEditor: ""add template"" should have the same functionality as return in the template dialog",This was done some time ago as part of the tweaks to the input box.,task_subcomment,['This was done some time ago as part of the tweaks to the input box.'],['OBSERVED BUG BEHAVIOR'] +53976,"Impossible to edit a specific section when switching from VisualEditor to ""legacy mode"" (due to reference to QuickEdit gadget in vector.js?)","**Author:** `l736ewiki` + +**Description:** +I'm an user on it.wiki, where VisualEditor is now enabled by default on the whole ns0. + +I was trying to modify a long article, on a specific section, and needed to introduce wikicode (namely {{...}} for a paragraph replaced by an empty section). + + +VisualEditor forced me to switch to legacy mode, but whenever I try to edit the specific section, through the local ""Edit"" command at section level, the legacy editor always opens in the basic editor the whole article and not just the selected section. + +This is heavily annoying when dealing with very long articles, with plenty of sections. + +-------------------------- +**Version**: unspecified +**Severity**: major +**OS**: Mac OS X 10.8 +**Platform**: Macintosh",task_description,"['Impossible to edit a specific section when switching from VisualEditor to ""legacy mode"" (due to reference to QuickEdit gadget in vector.js?)', ""**Author:** CODE\n\n**Description:**\nI'm an user on it.wiki, where VisualEditor is now enabled by default on the whole ns0."", 'I was trying to modify a long article, on a specific section, and needed to introduce wikicode (namely {{...}} for a paragraph replaced by an empty section).', 'VisualEditor forced me to switch to legacy mode, but whenever I try to edit the specific section, through the local ""Edit"" command at section level, the legacy editor always opens in the basic editor the whole article and not just the selected section.', 'This is heavily annoying when dealing with very long articles, with plenty of sections.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**OS**: Mac OS X 10.8\n**Platform**: Macintosh']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +254477,"Impossible to edit a specific section when switching from VisualEditor to ""legacy mode"" (due to reference to QuickEdit gadget in vector.js?)","**l736ewiki** wrote: + +I'm using vector. The issue appeared both on Safari/OS X (Mountain Lion, 10.8) and on Firefox/Windows XP Pro. + + +However, I was apparently able to overcome the issue. I read in the FAQ that it's recommended to disable the QuickEdit extension to avoid undesired effects with VE, so I checked in my preference pane that this extension was actually disabled (and it was). + + +However, in my vector.js fiel, inside the ""toLoad"" variable, there was a reference to QuickEdit gadget (qed). Looks like the presence of that string inside vector.js actually caused the extension to be loaded anyway. Removing that string from the vector.js and refreshing the browser's cache overcame the issue. Now I'm able to open VE directly over single individual sections. + +So the results are: +* it's not enough to verify in the preference pane that the QuickEdit extension is disabled +* any reference to QuickEdit shall be removed also from the local vector.js (or monobook.js, I assume then)",task_subcomment,"[""**l736ewiki** wrote:\n\nI'm using vector."", 'The issue appeared both on Safari/OS X (Mountain Lion, 10.8) and on Firefox/Windows XP Pro.', 'However, I was apparently able to overcome the issue.', ""I read in the FAQ that it's recommended to disable the QuickEdit extension to avoid undesired effects with VE, so I checked in my preference pane that this extension was actually disabled (and it was)."", 'However, in my vector.js fiel, inside the ""toLoad"" variable, there was a reference to QuickEdit gadget (qed).', 'Looks like the presence of that string inside vector.js actually caused the extension to be loaded anyway.', ""Removing that string from the vector.js and refreshing the browser's cache overcame the issue."", ""Now I'm able to open VE directly over single individual sections."", ""So the results are:\n* it's not enough to verify in the preference pane that the QuickEdit extension is disabled\n* any reference to QuickEdit shall be removed also from the local vector.js (or monobook.js, I assume then)""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION']" +254470,"Impossible to edit a specific section when switching from VisualEditor to ""legacy mode"" (due to reference to QuickEdit gadget in vector.js?)","I can't reproduce this on it.wiki, using vector skin and Firefox/Linux. + +Does this happen on every article for you? Which skin are you using?",task_subcomment,"[""I can't reproduce this on it.wiki, using vector skin and Firefox/Linux."", 'Does this happen on every article for you?', 'Which skin are you using?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +53968,VisualEditor: can't remove missing image,"http://it.wikipedia.org/w/index.php?title=Pieve_di_San_Giovanni_Battista_%28Pieve_Fosciana%29&oldid=60196986 + +If you tried to edit with VE, the missing image link would just disappear. +Thanks. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: can't remove missing image\n\nURL\n\nIf you tried to edit with VE, the missing image link would just disappear."", 'Thanks.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +254194,VisualEditor: can't remove missing image," + +*** This bug has been marked as a duplicate of bug 50788 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50788 ***'],['ACTION ON ISSUE'] +254188,VisualEditor: can't remove missing image,"Confirming. To make the description more clear: even if in view mode you can see the name in red of the missing image and the caption, with VisualEditor you won't see a thing, and therefore it's impossible to edit or delete the image object. + +There is a test page at + +http://test2.wikipedia.org/wiki/MissingImageVEtest + +I found about this while trying to remove the captions in an article of two images that had been deleted at Commons: + +http://ca.wikipedia.org/w/index.php?title=Remedios_Varo&oldid=11208969 + +The only way to do this is editing source the old way.",task_subcomment,"['Confirming.', ""To make the description more clear: even if in view mode you can see the name in red of the missing image and the caption, with VisualEditor you won't see a thing, and therefore it's impossible to edit or delete the image object."", 'There is a test page at\n\nURL\n\nI found about this while trying to remove the captions in an article of two images that had been deleted at Commons: \n\nURL\n\nThe only way to do this is editing source the old way.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +254183,VisualEditor: can't remove missing image,I actually moved the above comment to https://bugzilla.wikimedia.org/show_bug.cgi?id=52575 . Thanks.,task_subcomment,"['I actually moved the above comment to URL .', 'Thanks.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +254178,VisualEditor: can't remove missing image,http://en.wikipedia.org/w/index.php?title=Walton_%28company%29&diff=567155604&oldid=565055473 This might be related (not sure how they managed to remove the bracket!),task_subcomment,['URL This might be related (not sure how they managed to remove the bracket!)'],['OBSERVED BUG BEHAVIOR'] +254171,VisualEditor: can't remove missing image,"It disappears in VE for me too. + +1. modify the page (add a ' ' anywhere) +2. 'Save page' and 'review your changes' + +The diff 'inserts' + +[[File:Pieve San Giovanni.jpg|thumb|200px|San Giovanni Battista]]",task_subcomment,"['It disappears in VE for me too.', ""1. modify the page (add a ' ' anywhere) \n2."", ""'Save page' and 'review your changes'\n\nThe diff 'inserts'\n\n[[File:Pieve San Giovanni.jpg|thumb|200px|San Giovanni Battista]]""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR']" +53959,VisualEditor or Parsoid tried to convert slash-separate numbers into and refused to save,"An anonymous editor at en.wp reports: +""I was attempting to correct a minor error at [[Class 455]]. Although I was only attempting to change one word, the editor changed, + +:...in common with the Classes 313 / 314 / 315 / 507 / 508 units."" + +into + +:...in common with the Classes 313 / 314 / 315 / 507 / 508 units. + +and then complains of a formatting error and refuses to allow the change to be saved. The editor seems to be interpreting the list of class numbers as a telephone number."" + +I have been unable to reproduce this using Firefox 22 on Linux, including editing the article in question. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=53315",task_description,"['VisualEditor or Parsoid tried to convert slash-separate numbers into and refused to save\n\nAn anonymous editor at en.wp reports:\n""I was attempting to correct a minor error at [[Class 455]].', 'Although I was only attempting to change one word, the editor changed, \n\n:...in common with the Classes 313 / 314 / 315 / 507 / 508 units.""', 'into \n\n:...in common with the Classes 313 / 314 / 315 / 507 / 508 units.\n\nand then complains of a formatting error and refuses to allow the change to be saved.', 'The editor seems to be interpreting the list of class numbers as a telephone number.""', 'I have been unable to reproduce this using Firefox 22 on Linux, including editing the article in question.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +253777,VisualEditor or Parsoid tried to convert slash-separate numbers into and refused to save,This might be default behavior in the Safari iOS contenteditable. In that case we probably need to file a bugreport upstream.,task_subcomment,"['This might be default behavior in the Safari iOS contenteditable.', 'In that case we probably need to file a bugreport upstream.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +253771,VisualEditor or Parsoid tried to convert slash-separate numbers into and refused to save,"Just for reference, the original reporter subsequently noted that they use Ipad IOS6 with Safari",task_subcomment,"['Just for reference, the original reporter subsequently noted that they use Ipad IOS6 with Safari']",['OBSERVED BUG BEHAVIOR'] +253763,VisualEditor or Parsoid tried to convert slash-separate numbers into and refused to save,"This is almost certainly due to a browser plugin that thinks it's being ""helpful"". Certainly, nothing in VisualEditor or Parsoid understand href=tel: links, so it's not going to come from us. I also can't reproduce locally in Firefox, Safari or Chrome. + +Marking as INVALID (but we are seeing a small number of these consistent due to people having broken plugins; we're investigating whether there's a way to stop them).",task_subcomment,"['This is almost certainly due to a browser plugin that thinks it\'s being ""helpful"".', ""Certainly, nothing in VisualEditor or Parsoid understand href=tel: links, so it's not going to come from us."", ""I also can't reproduce locally in Firefox, Safari or Chrome."", ""Marking as INVALID (but we are seeing a small number of these consistent due to people having broken plugins; we're investigating whether there's a way to stop them).""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +253753,VisualEditor or Parsoid tried to convert slash-separate numbers into and refused to save,This may be a VE issue if you are seeing a-href showing up in wikitext on serialization.,task_subcomment,['This may be a VE issue if you are seeing a-href showing up in wikitext on serialization.'],['OBSERVED BUG BEHAVIOR'] +53950,VisualEditor: tags not deleted when surrounding element or text is deleted,"User Atethnekos at en.wp reports: +""If in the source code there is <blockquote>, and in VE I select ""
    "" and delete it, when I save the is left behind in the source code."" + +See https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=565596201&oldid=565596137 for an example in by sandbox. Further testing shows that it also happens with other tags and even with plain text: +https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=565596772&oldid=565596703 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: tags not deleted when surrounding element or text is deleted\n\nUser Atethnekos at en.wp reports:\n""If in the source code there is <blockquote>, and in VE I select ""
    "" and delete it, when I save the is left behind in the source code.""', 'See URL for an example in by sandbox.', 'Further testing shows that it also happens with other tags and even with plain text:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +253282,VisualEditor: tags not deleted when surrounding element or text is deleted,"This is the same as bug 47678, which now fixed in some code we created this week, but unfortunately that has an issue, bug 51948 which is preventing wider deployment. Hopefully we'll get that fixed next week. + +*** This bug has been marked as a duplicate of bug 47678 ***",task_subcomment,"['This is the same as bug 47678, which now fixed in some code we created this week, but unfortunately that has an issue, bug 51948 which is preventing wider deployment.', ""Hopefully we'll get that fixed next week."", '*** This bug has been marked as a duplicate of bug 47678 ***']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +53938,VisualEditor: Deleting last use of reference should remove the entry from ..,"This is related to Bug 51741, which is about adding support for ... + +If the page already has .., and the last use of a named reference is removed, the entry inside .. needs to be removed otherwise an error is generated after save. + +Steps to reproduce: +1. https://de.wikipedia.org/wiki/This_Is_War?veaction=edit +2. Delete one of the named references, e.g. [16] at present +3. Save & Review your changes. + +Expected results: +The reference is removed from the content and the references list. + +Actual results: +The reference is removed from the content, but it remains in the references list, and if saved the error is: +""Cite error: tag with name ""rockspot_1"" defined in is not used in prior text."" + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Deleting last use of reference should remove the entry from ..\n\nThis is related to Bug 51741, which is about adding support for ...\n\nIf the page already has .., and the last use of a named reference is removed, the entry inside .. needs to be removed otherwise an error is generated after save.', 'Steps to reproduce:\n1.', 'URL\n2.', 'Delete one of the named references, e.g.', '[16] at present\n3.', 'Save & Review your changes.', 'Expected results:\nThe reference is removed from the content and the references list.', 'Actual results:\nThe reference is removed from the content, but it remains in the references list, and if saved the error is:\n""Cite error: tag with name ""rockspot_1"" defined in is not used in prior text.""', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +252743,VisualEditor: Deleting last use of reference should remove the entry from ..,This was done some time ago; sorry for the slow triage.,task_subcomment,['This was done some time ago; sorry for the slow triage.'],['ACTION ON ISSUE'] +53925,VisualEditor: Retain newlines between parameters in transclusion invocations,"Steps to reproduce: +1. https://nl.wikipedia.org/wiki/Dolichognatha_petiti?veaction=edit +2. Click on infobox and edit translusion +3. In the first parameter (afbeelding), add 'blah', and apply changes +4. 'Save' & 'Review your changes' + +Result: + | afbeelding = +-| afbeeldingtekst = ++| afbeelding = ++blah| afbeeldingtekst = + +Expected results: +-| afbeelding = ++| afbeelding = blah + +p.s. [[nl:Dolichognatha petiti]] is currently on the parsoid topfail list +http://parsoid.wmflabs.org:8001/topfails/15 + +Regarding the actual bug, I saw a similar diff ~20 hrs ago: +https://en.wikipedia.org/w/index.php?title=List_of_Sam_%26_Cat_episodes&curid=39469556&diff=565437324&oldid=565416618 + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Retain newlines between parameters in transclusion invocations\n\nSteps to reproduce:\n1.', 'URL\n2.', 'Click on infobox and edit translusion\n3.', ""In the first parameter (afbeelding), add 'blah', and apply changes\n4."", ""'Save' & 'Review your changes'\n\nResult:\n | afbeelding = \n-| afbeeldingtekst = \n+| afbeelding = \n+blah| afbeeldingtekst = \n\nExpected results:\n-| afbeelding = \n+| afbeelding = blah\n\np.s."", '[[nl:Dolichognatha petiti]] is currently on the parsoid topfail list\nURL\n\nRegarding the actual bug, I saw a similar diff ~20 hrs ago:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'BUG REPRODUCTION']" +251794,VisualEditor: Retain newlines between parameters in transclusion invocations,This was fixed some time ago; sorry for the slow triage.,task_subcomment,['This was fixed some time ago; sorry for the slow triage.'],['ACTION ON ISSUE'] +251786,VisualEditor: Retain newlines between parameters in transclusion invocations,"And another one reported on en:VEF in case it helps +https://en.wikipedia.org/w/index.php?title=Rebel_Beat_%28Goo_Goo_Dolls_song%29&diff=566058910&oldid=565340967",task_subcomment,['And another one reported on en:VEF in case it helps\nURL'],['OBSERVED BUG BEHAVIOR'] +53907,VisualEditor: DEFAULTSORT suggestions should use/not use diacritics on based on wiki policy,"English Wikipedia user PamD comments: +""Editing [[Pikku-Vesijärvi]] I noticed that VE's suggested DEFAULTSORT was exactly the title. VE should be set to drop the diacriticals when suggesting DEFAULTSORT - should have been ""Pikku-Vesijarvi"" with a plain ""a""."" + +Looking at some other wikis it seems some do use diacritics in DEFAULTSORT (at least the Czech and Estonian ones do at [[cs:Édith Piaf]] and [[et:Édith Piaf]) so this seems like something that should be configurable based on each wiki's policy. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: DEFAULTSORT suggestions should use/not use diacritics on based on wiki policy\n\nEnglish Wikipedia user PamD comments:\n""Editing [[Pikku-Vesijärvi]] I noticed that VE\'s suggested DEFAULTSORT was exactly the title.', 'VE should be set to drop the diacriticals when suggesting DEFAULTSORT - should have been ""Pikku-Vesijarvi"" with a plain ""a"".""', ""Looking at some other wikis it seems some do use diacritics in DEFAULTSORT (at least the Czech and Estonian ones do at [[cs:Édith Piaf]] and [[et:Édith Piaf]) so this seems like something that should be configurable based on each wiki's policy."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +250417,VisualEditor: DEFAULTSORT suggestions should use/not use diacritics on based on wiki policy,"VisualEditor is not ""suggesting"" a default page sort - the placeholder text informs the user what the page is currently sorted as (i.e., the page's name). + +Marking as INVALID.",task_subcomment,"['VisualEditor is not ""suggesting"" a default page sort - the placeholder text informs the user what the page is currently sorted as (i.e., the page\'s name).', 'Marking as INVALID.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +53905,VisualEditor: Inserting media dialog has no confirmation button,"**Author:** `jduranboger` + +**Description:** +screenshot of the bug + +Does not appear ""insertar multimedia"" button (insert multimedia), and can't inser image selecting from the dialoge box in the spanish version. This problem happen in firefox 22. + +Attached:Screenshot + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Windows 7 +**Platform**: PC + +**Attached**: {F11730}",task_description,"['VisualEditor: Inserting media dialog has no confirmation button\n\n**Author:** CODE\n\n**Description:**\nscreenshot of the bug\n\nDoes not appear ""insertar multimedia"" button (insert multimedia), and can\'t inser image selecting from the dialoge box in the spanish version.', 'This problem happen in firefox 22.', 'Attached:Screenshot\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Windows 7\n**Platform**: PC\n\n**Attached**: {F11730}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +250356,VisualEditor: Inserting media dialog has no confirmation button,Closing this as no confirmation of report as written. Bug 51911 gets the gist of the issue.,task_subcomment,"['Closing this as no confirmation of report as written.', 'Bug 51911 gets the gist of the issue.']","['ACTION ON ISSUE', 'MOTIVATION']" +250351,VisualEditor: Inserting media dialog has no confirmation button,Sorry for confirming; the UI design should be a separate bug.,task_subcomment,['Sorry for confirming; the UI design should be a separate bug.'],['SOLUTION DISCUSSION'] +250345,VisualEditor: Inserting media dialog has no confirmation button,"It does look very bare, and many users will be thinking ""do I need to double click""? (we have MS to thank for that) + +I would prefer to select an image, be prompted for a caption (an overlay appears), and then apply changes. That would partially solve bug 51911, as the user would feel more confident that they had inserted the image, and they would go looking for it.",task_subcomment,"['It does look very bare, and many users will be thinking ""do I need to double click""?', '(we have MS to thank for that)\n\nI would prefer to select an image, be prompted for a caption (an overlay appears), and then apply changes.', 'That would partially solve bug 51911, as the user would feel more confident that they had inserted the image, and they would go looking for it.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']" +250339,VisualEditor: Inserting media dialog has no confirmation button,Bug/enhancement reported as bug 51911.,task_subcomment,['Bug/enhancement reported as bug 51911.'],['OBSERVED BUG BEHAVIOR'] +250334,VisualEditor: Inserting media dialog has no confirmation button,"Maybe you are inserting the image somewhere out of your field of view? For example if there is an infobox in the article, or many pictures aligned to the right, the image you are inserting may be inserted BELOW all this, where you cannot see it. + +Regardless of whether this is the actual problem in this particular case, I think that it is a potential problem for others. I tried inserting an image in an article with an infobox, and indeed the image was inserted below it, out of my field of view. This could lead to puzzled users and even unintended bad edits, and I think that the solution is fairly simple: making the VisualEditor scroll the screen down to wherever the image is inserted. I'll report this to the VisualEditor team.",task_subcomment,"['Maybe you are inserting the image somewhere out of your field of view?', 'For example if there is an infobox in the article, or many pictures aligned to the right, the image you are inserting may be inserted BELOW all this, where you cannot see it.', 'Regardless of whether this is the actual problem in this particular case, I think that it is a potential problem for others.', 'I tried inserting an image in an article with an infobox, and indeed the image was inserted below it, out of my field of view.', 'This could lead to puzzled users and even unintended bad edits, and I think that the solution is fairly simple: making the VisualEditor scroll the screen down to wherever the image is inserted.', ""I'll report this to the VisualEditor team.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +250328,VisualEditor: Inserting media dialog has no confirmation button,That button was removed on purpose. You should be able to insert an image by simply clicking on the image.,task_subcomment,"['That button was removed on purpose.', 'You should be able to insert an image by simply clicking on the image.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +53880,VisualEditor: Dragging cursor through multi-part template responds unpredictably in Firefox,"A user - Cryptic C62 - reports on English language Wikipedia: +** +If I click directly on a collapse box (created with {{collapse top}} and {{collapse bottom}}), the transclusion button appears and works correctly. If I highlight a collapse box by clicking and dragging my cursor through it, one of two things happens: + +A: A transclusion button does not appear +B: A transclusion button does appear. Clicking on it opens a new template window, rather than editing the existing collapse box. + +Occurs in Firefox v21.0, cannot replicate in Chrome v28.0 +** + +I attempted to replicate this myself and found that I sometimes got result A and sometimes a transclusion button that *did* edit the existing collapse box. I could not get his result B. + +I tested it on other templates, and it did not seem that dragging through other templates ever brought up the transclusion button, but never say never. :) + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Dragging cursor through multi-part template responds unpredictably in Firefox\n\nA user - Cryptic C62 - reports on English language Wikipedia:\n**\nIf I click directly on a collapse box (created with {{collapse top}} and {{collapse bottom}}), the transclusion button appears and works correctly.', 'If I highlight a collapse box by clicking and dragging my cursor through it, one of two things happens:\n\nA: A transclusion button does not appear\nB: A transclusion button does appear.', 'Clicking on it opens a new template window, rather than editing the existing collapse box.', 'Occurs in Firefox v21.0, cannot replicate in Chrome v28.0\n**\n\nI attempted to replicate this myself and found that I sometimes got result A and sometimes a transclusion button that *did* edit the existing collapse box.', 'I could not get his result B.\n\nI tested it on other templates, and it did not seem that dragging through other templates ever brought up the transclusion button, but never say never.', ':)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +249074,VisualEditor: Dragging cursor through multi-part template responds unpredictably in Firefox,"AFAICT this is now fixed, I believe due to the changes in selection handling in Firefox. Sorry for the slow triage.",task_subcomment,"['AFAICT this is now fixed, I believe due to the changes in selection handling in Firefox.', 'Sorry for the slow triage.']","['BUG REPRODUCTION', 'ACTION ON ISSUE']" +53875,General non VE feedback goes to the VE feedback page.,"I've noticed quite a few edits going to the VE feedback page http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback page which don't really seem to be VE feedback. If you follow through the new editor experience its quite obvious why they are being directed there: +1)New editor finds a page, they want to edit and clicks ""Edit"" +2) They have a question, they see the big ? in the top bar and click it +3) There are two options: ""user guide"" and ""Leave feadback"", the second is obviously the one for questions so they click that +4) There is some complicate text which is tldr and a nice box to ask your question. The user types in that and +5)Bingo, a new section on the feedback page + +This senario probably explains why we are getting a few simple signature with no comments. As the ? is much more prominent than the Help in the left sidebar its grabbing the users attention so diverting users away from our main help system. This showing up to be a continuing problem with about one such post a day. A way needs to be found to direct users to the right place. + +-------------------------- +**Version**: unspecified +**Severity**: minor",task_description,"['General non VE feedback goes to the VE feedback page.', ""I've noticed quite a few edits going to the VE feedback page URL page which don't really seem to be VE feedback."", 'If you follow through the new editor experience its quite obvious why they are being directed there:\n1)New editor finds a page, they want to edit and clicks ""Edit""\n2) They have a question, they see the big ?', 'in the top bar and click it\n3) There are two options: ""user guide"" and ""Leave feadback"", the second is obviously the one for questions so they click that\n4) There is some complicate text which is tldr and a nice box to ask your question.', 'The user types in that and\n5)Bingo, a new section on the feedback page\n\nThis senario probably explains why we are getting a few simple signature with no comments.', 'As the ?', 'is much more prominent than the Help in the left sidebar its grabbing the users attention so diverting users away from our main help system.', 'This showing up to be a continuing problem with about one such post a day.', 'A way needs to be found to direct users to the right place.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']" +248668,General non VE feedback goes to the VE feedback page.,"Marking this as ""WORKSFORME"", though really we should consider the broader ramifications for us and think about adding a prominent help button for users who clearly want it.",task_subcomment,"['Marking this as ""WORKSFORME"", though really we should consider the broader ramifications for us and think about adding a prominent help button for users who clearly want it.']",['SOLUTION DISCUSSION'] +248660,General non VE feedback goes to the VE feedback page.,"Presumably the solution is to provide a proper help link for users for general concerns, rather than burying it where they never see it?",task_subcomment,"['Presumably the solution is to provide a proper help link for users for general concerns, rather than burying it where they never see it?']",['SOLUTION DISCUSSION'] +53858,Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs,"Both MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). + +This is a proof of concept for doing this more broadly. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=54160",task_description,"['Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs\n\nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired.', 'Vagrant currently has this, but Labs does not.', 'We should find a way to factor it out so the two environments can share it (possibly with a git submodule).', 'This is a proof of concept for doing this more broadly.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']" +247738,Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs,"Yeah. It's not integrated with the normal Wikitech interface, but my understanding is it gets the job done (I haven't really used Labs-Vagrant, but I have a general understanding how it works).",task_subcomment,"['Yeah.', ""It's not integrated with the normal Wikitech interface, but my understanding is it gets the job done (I haven't really used Labs-Vagrant, but I have a general understanding how it works).""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +247732,Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs,Does ::role::labs::vagrant satisfy this request? Applying it via the wikitech interface provisions the labs host with a copy of MediaWiki-Vagrant and then the `labs-vagrant` command can be used to manipulate roles and run puppet.,task_subcomment,"['Does ::role::labs::vagrant satisfy this request?', 'Applying it via the wikitech interface provisions the labs host with a copy of MediaWiki-Vagrant and then the CODE command can be used to manipulate roles and run puppet.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']" +247727,Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],task_subcomment,"['[mass-moving from Tools>MediaWiki-Vagrant to separate product.', 'See bug 54041.', 'Filter bugmail on this comment.]']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']" +53835,VisualEditor: Changing login status / losing session data during edit causes VE to break silently,"Edits that would trigger this error silently break VE: +""Sorry! We could not process your edit due to a loss of session data."" + +On save, it shows animation indicating it is saving, but then does not save, leaving you in the editing screen. It doesn't refresh to update your session data, so the edit will never succeed; and it doesn't show you the error message. + +To reproduce: start an edit, then logout, and try to complete; or v-v (and more common) start one as an anon, then log in. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Changing login status / losing session data during edit causes VE to break silently\n\nEdits that would trigger this error silently break VE:\n""Sorry!', 'We could not process your edit due to a loss of session data.""', 'On save, it shows animation indicating it is saving, but then does not save, leaving you in the editing screen.', ""It doesn't refresh to update your session data, so the edit will never succeed; and it doesn't show you the error message."", 'To reproduce: start an edit, then logout, and try to complete; or v-v (and more common) start one as an anon, then log in.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +246479,VisualEditor: Changing login status / losing session data during edit causes VE to break silently,This was fixed some while ago as part of the save dialog re-write; sorry for the slow triage.,task_subcomment,['This was fixed some while ago as part of the save dialog re-write; sorry for the slow triage.'],['OBSERVED BUG BEHAVIOR'] +53833,FlaggedRevs/PendingChanges notices not appearing at pl.wikipedia.org,"From https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Krytyczne_zaniedbanie_interfejsu:_wersje_przejrzane + +The Polish Wikipedia uses FlaggedRevisions or PendingChanges and has deployed both notices upon opening a page and a different text on the ""Save"" button to reduce confusion by new editors. These notices are not appearing in VisualEditor. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['FlaggedRevs/PendingChanges notices not appearing at pl.wikipedia.org\n\nFrom URL\n\nThe Polish Wikipedia uses FlaggedRevisions or PendingChanges and has deployed both notices upon opening a page and a different text on the ""Save"" button to reduce confusion by new editors.', 'These notices are not appearing in VisualEditor.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +246378,FlaggedRevs/PendingChanges notices not appearing at pl.wikipedia.org,"Yeah, this isn't good; we've actually just-about fixed it and will deploy it the morning (San Francisco time). + +*** This bug has been marked as a duplicate of bug 49699 ***",task_subcomment,"[""Yeah, this isn't good; we've actually just-about fixed it and will deploy it the morning (San Francisco time)."", '*** This bug has been marked as a duplicate of bug 49699 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +246369,FlaggedRevs/PendingChanges notices not appearing at pl.wikipedia.org,"That's not the real issue. + +FlaggedRevs are enabled globally, for all pages, and *all non-autoreviewed edits require review before they are shown*; the only groups exempt from review are reviewers themselves and bots. (You can choose to view the so-called 'unstable' versions of pages instead of 'stable' ones in preferences.) + +Information about this is shown to viewers before, during and after editing (using the messages pointed out in the issue report WhatamIdoing linked) – but VE shows it in none of these contexts. + +I would consider this a blocker to deployment to anonymous users at least.",task_subcomment,"[""That's not the real issue."", 'FlaggedRevs are enabled globally, for all pages, and *all non-autoreviewed edits require review before they are shown*; the only groups exempt from review are reviewers themselves and bots.', ""(You can choose to view the so-called 'unstable' versions of pages instead of 'stable' ones in preferences.)"", 'Information about this is shown to viewers before, during and after editing (using the messages pointed out in the issue report WhatamIdoing linked) – but VE shows it in none of these contexts.', 'I would consider this a blocker to deployment to anonymous users at least.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +53831,Long lines in 
     blocks don't cause page formatting to extend right. The html page is extended massively further than needed,"Long 
     blocks rendered in Firefox 22 on Xubuntu Linux. Monobook skin.
+
+When 
     blocks contain lines longer than the width of the page, the 
     block formatting finishes at the right edge of the page but the text continues. Shortly afterwards the page background finishes and the text continues onto a plain grey background. The html page though is rendered much wider than is needed to show all the text though (very approximately double the required width).
+
+Example page: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=565361164#save_page
+
+Firefox 22, Xubuntu Linux, Monobook skin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11594}",task_description,"[""Long lines in 
     blocks don't cause page formatting to extend right."", 'The html page is extended massively further than needed\n\nLong 
     blocks rendered in Firefox 22 on Xubuntu Linux.', 'Monobook skin.', 'When 
     blocks contain lines longer than the width of the page, the 
     block formatting finishes at the right edge of the page but the text continues.', 'Shortly afterwards the page background finishes and the text continues onto a plain grey background.', 'The html page though is rendered much wider than is needed to show all the text though (very approximately double the required width).', 'Example page: URL\n\nFirefox 22, Xubuntu Linux, Monobook skin.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11594}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246287,Long lines in 
     blocks don't cause page formatting to extend right. The html page is extended massively further than needed,"
+
+*** This bug has been marked as a duplicate of bug 260 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 260 ***'],['ACTION ON ISSUE']
+246282,Long lines in 
     blocks don't cause page formatting to extend right. The html page is extended massively further than needed,"That really wouldn't surprise me, but I couldn't find anything when searching and nothing relevant popped up when I entered the summary. If it is a dupe then the other bug describes it using completely different words, probably describing the cause rather than the symptom.",task_subcomment,"[""That really wouldn't surprise me, but I couldn't find anything when searching and nothing relevant popped up when I entered the summary."", 'If it is a dupe then the other bug describes it using completely different words, probably describing the cause rather than the symptom.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246276,Long lines in 
     blocks don't cause page formatting to extend right. The html page is extended massively further than needed,This is surely a dupe of something.,task_subcomment,['This is surely a dupe of something.'],['OBSERVED BUG BEHAVIOR']
+53829,"Removing a heading is hard, leaving ==== or turning the next paragraph into a heading","1. Visit any page on Wikipedia today.
+2. Click ""Edit"" to enter VisualEditor.
+3. Find a section heading and highlight it.
+4. Press the DEL key on your keyboard to delete it.
+5. Click ""Save Page"" then ""Review your changes.""
+
+The heading text has been removed, but the following wikitext has been left in its place.
+
+====
+
+Cancel the save, go back to the empty heading, and place your cursor in it. Press DEL in an attempt to delete the empty heading. As a result, the entire paragraph below the old heading turns into a heading.
+
+So how on earth do you delete a heading? I canceled my edit, re-edited, and this time, I highlighted the heading AND the first line of the paragraph beneath it, and pressed DEL. Regardless, the whole paragraph turned into a heading again.
+
+I finally managed to delete a heading by placing the cursor at the end of the preceding paragraph (after the last character of the paragraph) and dragging all the way to the end of the heading, then pressing DEL. Now, the heading was gone and nothing else turned into a heading.
+
+In short, you must delete some kind of invisible character on the LINE ABOVE the heading, in order to delete the heading. This is not expected behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Removing a heading is hard, leaving ==== or turning the next paragraph into a heading\n\n1.', 'Visit any page on Wikipedia today.', '2.', 'Click ""Edit"" to enter VisualEditor.', '3.', 'Find a section heading and highlight it.', '4.', 'Press the DEL key on your keyboard to delete it.', '5.', 'Click ""Save Page"" then ""Review your changes.""', 'The heading text has been removed, but the following wikitext has been left in its place.', '====\n\nCancel the save, go back to the empty heading, and place your cursor in it.', 'Press DEL in an attempt to delete the empty heading.', 'As a result, the entire paragraph below the old heading turns into a heading.', 'So how on earth do you delete a heading?', 'I canceled my edit, re-edited, and this time, I highlighted the heading AND the first line of the paragraph beneath it, and pressed DEL.', 'Regardless, the whole paragraph turned into a heading again.', 'I finally managed to delete a heading by placing the cursor at the end of the preceding paragraph (after the last character of the paragraph) and dragging all the way to the end of the heading, then pressing DEL.', 'Now, the heading was gone and nothing else turned into a heading.', 'In short, you must delete some kind of invisible character on the LINE ABOVE the heading, in order to delete the heading.', 'This is not expected behavior.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246183,"Removing a heading is hard, leaving ==== or turning the next paragraph into a heading","
+
+*** This bug has been marked as a duplicate of bug 50100 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50100 ***'],['ISSUE CONTENT MANAGEMENT']
+53827,VisualEditor: Tooltip shown when hovering over a link should also appear when link inspector icon is shown,"At the English Wikipedia, a user requests that the tooltip which is shown when hovering over a link (shows the link target) also be shown when the link inspector icon is shown (i.e. when the cursor is in the middle of the link).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51824",task_description,"['VisualEditor: Tooltip shown when hovering over a link should also appear when link inspector icon is shown\n\nAt the English Wikipedia, a user requests that the tooltip which is shown when hovering over a link (shows the link target) also be shown when the link inspector icon is shown (i.e.', 'when the cursor is in the middle of the link).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+246062,VisualEditor: Tooltip shown when hovering over a link should also appear when link inspector icon is shown,"WONTFIX. Display of tooltips is native behaviour, and though we *can* over-ride the browser and do it instead when we think we know better, we shouldn't (because we'll always miss something).",task_subcomment,"['WONTFIX.', ""Display of tooltips is native behaviour, and though we *can* over-ride the browser and do it instead when we think we know better, we shouldn't (because we'll always miss something).""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+53826,VisualEditor renderizes the image a lot bigger than it should,"Screenshot from [[pt:TV TEM]]
+
+In the page
+https://pt.wikipedia.org/wiki/User:Helder.wiki/Testes?veaction=edit
+the image is a lot bigger than it is on view mode
+https://pt.wikipedia.org/wiki/User:Helder.wiki/Testes?action=edit&oldid=36476193&preview=yes
+
+
+This is a minimal example for the problem reported at
+https://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia%3AEditor_Visual%2FComent%C3%A1rios&diff=36476052&oldid=36474378#Logo_desproporcional
+which can be seen on this article:
+https://pt.wikipedia.org/wiki/TV_TEM?veaction=edit#footer
+The screenshot provided was this:
+http://s22.postimg.org/owzuay0jl/image.jpg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://pt.wikipedia.org/wiki/?oldid=36476128&veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51628
+
+**Attached**: {F11577}",task_description,['VisualEditor renderizes the image a lot bigger than it should\n\nScreenshot from [[pt:TV TEM]]\n\nIn the page\nURL\nthe image is a lot bigger than it is on view mode\nURL\n\n\nThis is a minimal example for the problem reported at\nURL\nwhich can be seen on this article:\nURL\nThe screenshot provided was this:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n**See Also**:\nURL\n\n**Attached**: {F11577}'],['BUG REPRODUCTION']
+246016,VisualEditor renderizes the image a lot bigger than it should,"
+
+*** This bug has been marked as a duplicate of bug 51628 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51628 ***'],['ACTION ON ISSUE']
+246010,VisualEditor renderizes the image a lot bigger than it should,"Parsoid keeps the code as is:
+http://parsoid.wmflabs.org/_rt/pt/?oldid=36476193",task_subcomment,['Parsoid keeps the code as is:\nURL'],['OBSERVED BUG BEHAVIOR']
+246005,VisualEditor renderizes the image a lot bigger than it should,"It seems to be caused by the extra ""px"" in the wikicode:
+[[Image:Globo TV logo.svg|25pxpx]]",task_subcomment,"['It seems to be caused by the extra ""px"" in the wikicode:\n[[Image:Globo TV logo.svg|25pxpx]]']",['OBSERVED BUG BEHAVIOR']
+53820,"VisualEditor: When window is narrowed, article title can display over the top of the toolbar","From English Wikipedia:
+
+I've noticed in several articles today that the article title has displayed, in VE, on top of the lower border of the editing header bar. I've not noticed it before. I prefer to edit in a window less wide than my laptop screen, as reading long lines of text is a pain.
+
+On investigation: if I reduce the editing window to the point where the Question mark in a circle to the left of BETA is underneath the greyed-out ""Decrease paragraph indentation"" icon, there's a critical point where reducing the window width a little more moves that Question-mark back slightly to the right and jumps the article title up to display on top of the lower border of the editing bar.
+
+And a second problem: if I reduce the width even more, then the article title is displayed in a very narrow column. Look at Sengattuppatti, reduce the width, and at a point where the lines of text are still perfectly workable (perhaps you're working from a text open in another window on the screen), the article title is reduced to the extent of losing letters. Reduce the window so that ""Tiruchirapalli"" is the first word of second line (that's about 50% of my screen width, and a likely width for consulting a source document on screen beside the WP page I'm working on), and note that the article title now displays minus its last four letters. Not wrapped, just disappeared. Ugly. In multi-word articles, it displays as a column but again truncates long words - try Thomas Lumley-Saunderson, 3rd Earl of Scarbrough.
+
+I'm using Firefox 22 on Vista. PamD 10:18, 22 July 2013 (UTC)
+
+She adds that the original screenshots (truncated to hide non-free elements) demonstrate that her windows were not unreasonably narrow and that she ""might well want to have two 50% width windows, one for the source and one for my article.""
+
+
+See images:
+*http://en.wikipedia.org/wiki/File:Screenshot_of_title_overlapping_border.jpg
+
+*http://en.wikipedia.org/wiki/File:Screenshot_of_truncated_title_word_in_narrow_window.jpg
+
+Original thread here:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=565350848#Article_title_overlaps_header_bar_in_slightly_narrow_edit_window.3B_article_title_letters_lost_in_narrower_window
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52187
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51867",task_description,"[""VisualEditor: When window is narrowed, article title can display over the top of the toolbar\n\nFrom English Wikipedia:\n\nI've noticed in several articles today that the article title has displayed, in VE, on top of the lower border of the editing header bar."", ""I've not noticed it before."", 'I prefer to edit in a window less wide than my laptop screen, as reading long lines of text is a pain.', 'On investigation: if I reduce the editing window to the point where the Question mark in a circle to the left of BETA is underneath the greyed-out ""Decrease paragraph indentation"" icon, there\'s a critical point where reducing the window width a little more moves that Question-mark back slightly to the right and jumps the article title up to display on top of the lower border of the editing bar.', 'And a second problem: if I reduce the width even more, then the article title is displayed in a very narrow column.', ""Look at Sengattuppatti, reduce the width, and at a point where the lines of text are still perfectly workable (perhaps you're working from a text open in another window on the screen), the article title is reduced to the extent of losing letters."", 'Reduce the window so that ""Tiruchirapalli"" is the first word of second line (that\'s about 50% of my screen width, and a likely width for consulting a source document on screen beside the WP page I\'m working on), and note that the article title now displays minus its last four letters.', 'Not wrapped, just disappeared.', 'Ugly.', 'In multi-word articles, it displays as a column but again truncates long words - try Thomas Lumley-Saunderson, 3rd Earl of Scarbrough.', ""I'm using Firefox 22 on Vista."", 'PamD 10:18, 22 July 2013 (UTC)\n\nShe adds that the original screenshots (truncated to hide non-free elements) demonstrate that her windows were not unreasonably narrow and that she ""might well want to have two 50% width windows, one for the source and one for my article.""', 'See images:\n*URL\n\n*URL\n\nOriginal thread here:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+245692,"VisualEditor: When window is narrowed, article title can display over the top of the toolbar","Thanks - as the editor who reported this bug in the first place. I didn't notice it had been fixed because AFAIK there was no report to say so, and I'm not using VE regularly until some other issues have been fixed to make it usable. (Glad to notice that there's some action on redlinks, but the dialog box hiding all article content is still the dealbreaker for me).",task_subcomment,"['Thanks - as the editor who reported this bug in the first place.', ""I didn't notice it had been fixed because AFAIK there was no report to say so, and I'm not using VE regularly until some other issues have been fixed to make it usable."", ""(Glad to notice that there's some action on redlinks, but the dialog box hiding all article content is still the dealbreaker for me).""]","['ACTION ON ISSUE', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+245689,"VisualEditor: When window is narrowed, article title can display over the top of the toolbar",*** Bug 58933 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 58933 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245688,"VisualEditor: When window is narrowed, article title can display over the top of the toolbar",This was fixed by Trevor in January.,task_subcomment,['This was fixed by Trevor in January.'],['BUG REPRODUCTION']
+245686,"VisualEditor: When window is narrowed, article title can display over the top of the toolbar","Though I spent a lot of time reporting these, both these are cases of the system behaving oddly rather than things which seriously affect editing. I reported them more in the sense of ""The system is doing these odd things which I'm telling you about in case it's symptomatic of something significant you should know about"" rather than ""Please fix them now"".
+
+The first, that the title appears superimposed on the lower border of the editing toolbar area, is ugly, mildly disconcerting, and occurs at a very reasonable window width - I wasn't experimenting, just editing naturally this morning, when I found it happening. It's odd-looking, but does no serious harm.
+
+The second, that the title only displays in a column much narrower than the width of the displayed text, and that long title words are truncated at a certain point, only occurs on quite narrow windows but looks very odd when it does happen. It's not going to seriously hamper anyone's editing.
+
+I wouldn't like any effort to go into these bugs which could be used to address really important things like the {{Bug|49603}} on the invisibility of hidden comments and templates, or {{Bug|49969}} on dialog boxes hiding all article content: now those really do seriously affect editing.",task_subcomment,"['Though I spent a lot of time reporting these, both these are cases of the system behaving oddly rather than things which seriously affect editing.', 'I reported them more in the sense of ""The system is doing these odd things which I\'m telling you about in case it\'s symptomatic of something significant you should know about"" rather than ""Please fix them now"".', ""The first, that the title appears superimposed on the lower border of the editing toolbar area, is ugly, mildly disconcerting, and occurs at a very reasonable window width - I wasn't experimenting, just editing naturally this morning, when I found it happening."", ""It's odd-looking, but does no serious harm."", 'The second, that the title only displays in a column much narrower than the width of the displayed text, and that long title words are truncated at a certain point, only occurs on quite narrow windows but looks very odd when it does happen.', ""It's not going to seriously hamper anyone's editing."", ""I wouldn't like any effort to go into these bugs which could be used to address really important things like the {{Bug|49603}} on the invisibility of hidden comments and templates, or {{Bug|49969}} on dialog boxes hiding all article content: now those really do seriously affect editing.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+245683,"VisualEditor: When window is narrowed, article title can display over the top of the toolbar","Note I've been unable to reproduce this using Firefox 22 on Linux, so it might be OS-specific.",task_subcomment,"[""Note I've been unable to reproduce this using Firefox 22 on Linux, so it might be OS-specific.""]",['OBSERVED BUG BEHAVIOR']
+53812,Transclusion editor: remove template creates blank dialog,"If the only template is removed, the dialog is almost entirely blank.  It should reset back to the 'New template' form, or do something with all that white space.
+
+Steps to reproduce:
+1. Open Transclusion dialog
+2. Add 'cite web'
+3. Remove 'cite web'
+
+Result:
+Stare at the whiteness
+
+Expected results:
+Something, anything, except a sea of white
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Transclusion editor: remove template creates blank dialog\n\nIf the only template is removed, the dialog is almost entirely blank.', ""It should reset back to the 'New template' form, or do something with all that white space."", 'Steps to reproduce:\n1.', 'Open Transclusion dialog\n2.', ""Add 'cite web'\n3."", ""Remove 'cite web'\n\nResult:\nStare at the whiteness\n\nExpected results:\nSomething, anything, except a sea of white\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+245198,Transclusion editor: remove template creates blank dialog,"
+
+*** This bug has been marked as a duplicate of bug 50281 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50281 ***'],['ACTION ON ISSUE']
+245193,Transclusion editor: remove template creates blank dialog,"Bug 50281 (which I think this duplicates) wins for mildly amusing title though - ""VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message""",task_subcomment,"['Bug 50281 (which I think this duplicates) wins for mildly amusing title though - ""VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message""']",['SOLUTION DISCUSSION']
+245187,Transclusion editor: remove template creates blank dialog,"Creepy; I was about to submit this with the title ""VisualEditor: removing a template creates a blank dialog"" ;p.",task_subcomment,"['Creepy; I was about to submit this with the title ""VisualEditor: removing a template creates a blank dialog"" ;p.']",['INVESTIGATION AND EXPLORATION']
+53806,"VisualEditor shows rowspan=""4"" on template generated tables","Screenshot of the table
+
+See the link above and the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://pt.wikipedia.org/wiki/La_Liga_de_2006%E2%80%9307?oldid=36362539&veaction=edit
+
+**Attached**: {F11541}",task_description,"['VisualEditor shows rowspan=""4"" on template generated tables\n\nScreenshot of the table\n\nSee the link above and the attached screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n\n**Attached**: {F11541}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244936,"VisualEditor shows rowspan=""4"" on template generated tables","Thanks for fixing the templates -- I will close this bug now without making any fixes in Parsoid.  While we could fix Parsoid to accommodate bugs in wikitext and templates (and there are several scenarios that we handle), for one-off scenarios, it is better to fix the templates/wikitext rather than clutter the Parsoid code base with exceptional conditions.  It is better in the long run and will enable maintenance of the code base.",task_subcomment,"['Thanks for fixing the templates -- I will close this bug now without making any fixes in Parsoid.', 'While we could fix Parsoid to accommodate bugs in wikitext and templates (and there are several scenarios that we handle), for one-off scenarios, it is better to fix the templates/wikitext rather than clutter the Parsoid code base with exceptional conditions.', 'It is better in the long run and will enable maintenance of the code base.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244933,"VisualEditor shows rowspan=""4"" on template generated tables","For now, I moved the relevant code from [[pt:Template:Tabfootrow]] to [[pt:Template:Tabfoot]] and then I updated the only two articles which uses that template and informed about this change in the talk page of one of them:
+https://pt.wikipedia.org/wiki/Special:Contribs/Helder.wiki?dir=prev&offset=20130805170824&limit=11&uselang=en",task_subcomment,"['For now, I moved the relevant code from [[pt:Template:Tabfootrow]] to [[pt:Template:Tabfoot]] and then I updated the only two articles which uses that template and informed about this change in the talk page of one of them:\nURL']",['SOLUTION USAGE']
+244932,"VisualEditor shows rowspan=""4"" on template generated tables","I left a message in the talk page of one of the articles which uses the template:
+https://pt.wikipedia.org/wiki/Discuss%C3%A3o:Primeira_Liga_de_2013%E2%80%9314
+and in the thread where its author announced the new template:
+https://pt.wikipedia.org/wiki/WP:EA#Novas_predefini.C3.A7.C3.B5es_para_tabelas_de_futebol",task_subcomment,['I left a message in the talk page of one of the articles which uses the template:\nURL\nand in the thread where its author announced the new template:\nURL'],['OBSERVED BUG BEHAVIOR']
+244929,"VisualEditor shows rowspan=""4"" on template generated tables","I am not editing the template -- someone on pt wikipedia (matmarex) should verify that existing pages wont break with the change and do it.  But, offhand it does seem safe to fix.",task_subcomment,"['I am not editing the template -- someone on pt wikipedia (matmarex) should verify that existing pages wont break with the change and do it.', 'But, offhand it does seem safe to fix.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+244921,"VisualEditor shows rowspan=""4"" on template generated tables","Buggy template: http://pt.wikipedia.org/w/index.php?title=Predefini%C3%A7%C3%A3o:Tabfootrow&action=edit
+
+It should be ""|rowspan=..."" instead of ""||rowspan=...""
+
+echo ""{|\n|foo{{User:Ssastry/Templates/tabfootrow|rows=2|content=foobar}}\n|}"" | node parse
+
+works properly with the correct wikitext.",task_subcomment,"['Buggy template: URL\n\nIt should be ""|rowspan=..."" instead of ""||rowspan=...""\n\necho ""{|\\n|foo{{User:Ssastry/Templates/tabfootrow|rows=2|content=foobar}}\\n|}"" | node parse\n\nworks properly with the correct wikitext.']",['SOLUTION DISCUSSION']
+244915,"VisualEditor shows rowspan=""4"" on template generated tables",Parsoid bug: http://parsoid.wmflabs.org/pt/La_Liga_de_2006%E2%80%9307?oldid=36362539 (you'll have to scroll down quite a bit),task_subcomment,"[""Parsoid bug: URL (you'll have to scroll down quite a bit)""]",['OBSERVED BUG BEHAVIOR']
+53805,VisualEditor: It's possible to edit pages that were translated using the Translate extension,"The page https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/he was created by the Translate extension. It's impossible to translate it using the source editor and trying to do this gives the user a link to the translation interface. But it seems to be possible to edit it using the VisualEditor. I didn't actually try to change anything, because I was afraid of breaking something badly.
+
+I'm also not completely sure whether it's a VE or a Translate issue; I file it under VE because there are other issues in which VE behaves differently from the regular edit action, such as Bug 51459. But it may also be on the Translate side; CCing Niklas and Siebrand.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"[""VisualEditor: It's possible to edit pages that were translated using the Translate extension\n\nThe page URL was created by the Translate extension."", ""It's impossible to translate it using the source editor and trying to do this gives the user a link to the translation interface."", 'But it seems to be possible to edit it using the VisualEditor.', ""I didn't actually try to change anything, because I was afraid of breaking something badly."", ""I'm also not completely sure whether it's a VE or a Translate issue; I file it under VE because there are other issues in which VE behaves differently from the regular edit action, such as Bug 51459."", 'But it may also be on the Translate side; CCing Niklas and Siebrand.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+244865,VisualEditor: It's possible to edit pages that were translated using the Translate extension,"It's never actually been able to bypass the Translate extension's system-level protection of the page - but the problem is you shouldn't be able to trigger VE on the page in the first place, which is bug 50284.
+
+*** This bug has been marked as a duplicate of bug 50284 ***",task_subcomment,"[""It's never actually been able to bypass the Translate extension's system-level protection of the page - but the problem is you shouldn't be able to trigger VE on the page in the first place, which is bug 50284."", '*** This bug has been marked as a duplicate of bug 50284 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244857,VisualEditor: It's possible to edit pages that were translated using the Translate extension,"Urged by Niklas, I tried to save and got: ""Unsuccessful request: Unknown error: ""tpt-target-page"".""
+
+So at least it doesn't ruin anything, but it should be more intuitive.",task_subcomment,"['Urged by Niklas, I tried to save and got: ""Unsuccessful request: Unknown error: ""tpt-target-page"".""', ""So at least it doesn't ruin anything, but it should be more intuitive.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53793,VE: Page settings: Languages list cut off,"Screenshot of VisualEditor in Mozilla Firefox with Firebug enabled (which creates the blue overlay that indicates the contained element is bigger than shown and shows its size in the ""Schnellinfo""-Box
+
+Original Bug title: VE: Page settings: Languages list cut off
+
+In the page settings dialog, the languages list is not completely visible. This is due to the higher CSS selector precedence of 
+.ve-ui-pagedDialog-pagesPanel .ve-ui-panelLayout (setting overflow:hidden) 
+over 
+.ve-ui-panelLayout-scrollable (setting overflow-y:auto)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11501}",task_description,"['VE: Page settings: Languages list cut off\n\nScreenshot of VisualEditor in Mozilla Firefox with Firebug enabled (which creates the blue overlay that indicates the contained element is bigger than shown and shows its size in the ""Schnellinfo""-Box\n\nOriginal Bug title: VE: Page settings: Languages list cut off\n\nIn the page settings dialog, the languages list is not completely visible.', 'This is due to the higher CSS selector precedence of \n.ve-ui-pagedDialog-pagesPanel .ve-ui-panelLayout (setting overflow:hidden) \nover \n.ve-ui-panelLayout-scrollable (setting overflow-y:auto)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11501}']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+244064,VE: Page settings: Languages list cut off,"Change 75083 abandoned by Rillke:
+Adding important to overflow:auto on scrollable elements
+
+Reason:
+Fixed by If2d5ec3168a874eb4f856450583d6c89967513df
+
+https://gerrit.wikimedia.org/r/75083",task_subcomment,['Change 75083 abandoned by Rillke:\nAdding important to overflow:auto on scrollable elements\n\nReason:\nFixed by If2d5ec3168a874eb4f856450583d6c89967513df\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244059,VE: Page settings: Languages list cut off,"I'm pretty sure it's the same issue as on bug 51739.
+
+*** This bug has been marked as a duplicate of bug 51739 ***",task_subcomment,"[""I'm pretty sure it's the same issue as on bug 51739."", '*** This bug has been marked as a duplicate of bug 51739 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244055,VE: Page settings: Languages list cut off,"Change 75083 had a related patch set uploaded by Rillke:
+Adding important to overflow:auto on scrollable elements
+
+https://gerrit.wikimedia.org/r/75083",task_subcomment,['Change 75083 had a related patch set uploaded by Rillke:\nAdding important to overflow:auto on scrollable elements\n\nGERRIT_URL'],['ACTION ON ISSUE']
+53791,TemplateData for redirected templates,"Many templates are redirects from a short name to a long name. An example is
+http://en.wikipedia.org/wiki/Template:Commons_cat which is a redirect to
+http://en.wikipedia.org/wiki/Template:Commons_category and has 68742 pages transcluding it. Even though Commons_category has template data specified, and http://en.wikipedia.org/wiki/Template:Commons_cat/doc redirects to http://en.wikipedia.org/wiki/Template:Commons_category the visual editor does not pick up the correct parameters in the template dialog box. 
+
+There should be a way of making the dialog work for redirecting templates without having to duplicate the documentation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['TemplateData for redirected templates\n\nMany templates are redirects from a short name to a long name.', 'An example is\nURL which is a redirect to\nURL and has 68742 pages transcluding it.', 'Even though Commons_category has template data specified, and URL redirects to URL the visual editor does not pick up the correct parameters in the template dialog box.', 'There should be a way of making the dialog work for redirecting templates without having to duplicate the documentation.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+243977,TemplateData for redirected templates,"
+
+*** This bug has been marked as a duplicate of bug 50964 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50964 ***'],['ACTION ON ISSUE']
+243973,TemplateData for redirected templates,Discussed at http://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor/TemplateData#What_about_redirected_templates,task_subcomment,['Discussed at URL'],['OBSERVED BUG BEHAVIOR']
+53771,VisualEditor: Search box and button intermittently appearing atop transclusion editor in Monobook skin,"Reported on English Wikipedia by User:Cryptic C62:
+
+""Upon opening the transclusion editor, or upon moving a component up/down using the arrows in the bottom left, the Wikipedia search box and accompanying buttons occasionally appear in front of the transclusion editor. The behavior does not occur consistently.
+
+Occurs in Firefox v21.0, cannot replicate in Chrome v28.0""
+
+See image:
+http://en.wikipedia.org/wiki/File:VE_Searchbox_Passthrough.jpg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Search box and button intermittently appearing atop transclusion editor in Monobook skin\n\nReported on English Wikipedia by User:Cryptic C62:\n\n""Upon opening the transclusion editor, or upon moving a component up/down using the arrows in the bottom left, the Wikipedia search box and accompanying buttons occasionally appear in front of the transclusion editor.', 'The behavior does not occur consistently.', 'Occurs in Firefox v21.0, cannot replicate in Chrome v28.0""\n\nSee image:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+242861,VisualEditor: Search box and button intermittently appearing atop transclusion editor in Monobook skin,"This was caused by some issues with how the dialogs interacted with the Monobook skin, which have been subsequently fixed. Sorry for the slow triage.",task_subcomment,"['This was caused by some issues with how the dialogs interacted with the Monobook skin, which have been subsequently fixed.', 'Sorry for the slow triage.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+53759,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'info' of undefined"" (when saving the page)","After clicking the ""Save page"" button in the ""Save your changes"" dialog, the spinner (progress bar) appears for a few seconds, then vanishes again. The ""Save your changes"" dialog remains open and the edit is not saved. 
+
+Here is the output of the JavaScript Console in Chromium:
+
+Uncaught TypeError: Cannot read property 'info' of undefined load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:83
+
+ve.init.mw.ViewPageTarget.onSaveError load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:83
+
+oo.EventEmitter.emit load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…xt%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:124
+
+ve.init.mw.Target.onSaveError load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:16
+
+ve.init.mw.Target.onSave load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:16
+
+proxy load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:10
+
+fire load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:12
+
+self.fireWith load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:14
+
+done load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:119
+
+callback load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:129
+
+
+The error is reproducible (with this exact console output) even when I make further edits to the article content or change the edit summary and then go back to the ""Save your changes"" dialog: I can't save seem to save my edit at all. Haven't yet seen this occur in other articles, though (this was an enwiki article).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Fix ""Uncaught TypeError: Cannot read property \'info\' of undefined"" (when saving the page)\n\nAfter clicking the ""Save page"" button in the ""Save your changes"" dialog, the spinner (progress bar) appears for a few seconds, then vanishes again.', 'The ""Save your changes"" dialog remains open and the edit is not saved.', 'Here is the output of the JavaScript Console in Chromium:\n\nUncaught TypeError: Cannot read property \'info\' of undefined load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:83\n\nve.init.mw.ViewPageTarget.onSaveError load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:83\n\noo.EventEmitter.emit load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…xt%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:124\n\nve.init.mw.Target.onSaveError load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:16\n\nve.init.mw.Target.onSave load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ext%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130719T023752Z&*:16\n\nproxy load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:10\n\nfire load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:12\n\nself.fireWith load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:14\n\ndone load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:119\n\ncallback load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130719T023752Z:129\n\n\nThe error is reproducible (with this exact console output) even when I make further edits to the article content or change the edit summary and then go back to the ""Save your changes"" dialog: I can\'t save seem to save my edit at all.', ""Haven't yet seen this occur in other articles, though (this was an enwiki article)."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242084,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'info' of undefined"" (when saving the page)","No reproduction steps; likely caused by an old issue in alien content blocks, fixed ages ago.",task_subcomment,"['No reproduction steps; likely caused by an old issue in alien content blocks, fixed ages ago.']",['OBSERVED BUG BEHAVIOR']
+242082,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'info' of undefined"" (when saving the page)",Which article did this occur on?,task_subcomment,['Which article did this occur on?'],['OBSERVED BUG BEHAVIOR']
+53756,VisualEditor: Make it clearer that the clear formatting button does something (clears pre-annotations) if any are set,"In the visual editor, the button to remove formatting activates if the cursor is placed on a formatted (bold or italic) character. However clicking the button has no effect unless text is selected.
+
+Either the button should be disabled when no text is selected, or clicking it when no text is selected should have an effect (probably remove formatting from the current word).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Make it clearer that the clear formatting button does something (clears pre-annotations) if any are set\n\nIn the visual editor, the button to remove formatting activates if the cursor is placed on a formatted (bold or italic) character.', 'However clicking the button has no effect unless text is selected.', 'Either the button should be disabled when no text is selected, or clicking it when no text is selected should have an effect (probably remove formatting from the current word).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+241932,VisualEditor: Make it clearer that the clear formatting button does something (clears pre-annotations) if any are set,This was fixed by only showing it as enabled when there's a pre-annnotation stack.,task_subcomment,"[""This was fixed by only showing it as enabled when there's a pre-annnotation stack.""]",['OBSERVED BUG BEHAVIOR']
+241928,VisualEditor: Make it clearer that the clear formatting button does something (clears pre-annotations) if any are set,"Although the interface doesn't clearly indicate this, when the cursor is inside bold text, the toolbar shows ""Bold"" active. When you then click ""Clear formatting"", nothing inside the document will change (since no text is selected) however it does affect text entered from this point on.
+
+Basically when your cursor is inside or against bold text, you'd expect text entered after it will also be bold. Clearing formatting at that point means it will unbold your cursor (if you know what I mean).",task_subcomment,"['Although the interface doesn\'t clearly indicate this, when the cursor is inside bold text, the toolbar shows ""Bold"" active.', 'When you then click ""Clear formatting"", nothing inside the document will change (since no text is selected) however it does affect text entered from this point on.', ""Basically when your cursor is inside or against bold text, you'd expect text entered after it will also be bold."", 'Clearing formatting at that point means it will unbold your cursor (if you know what I mean).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+53752,VisualEditor: In a page with many categories only the first categories are visible in the editor,"The English [[Barack Obama]] article has dozens of categories. When editing the categories using Page settings, only the first few of them are visible and editable, and it's impossible to get to the rest of them, because there is not scrollbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: In a page with many categories only the first categories are visible in the editor\n\nThe English [[Barack Obama]] article has dozens of categories.', ""When editing the categories using Page settings, only the first few of them are visible and editable, and it's impossible to get to the rest of them, because there is not scrollbar."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+241746,VisualEditor: In a page with many categories only the first categories are visible in the editor,This was fixed in August; sorry for the slow triage.,task_subcomment,['This was fixed in August; sorry for the slow triage.'],['ACTION ON ISSUE']
+53732,VisualEditor: Removal of blank lines when there are HTML comments seems not to work,"As reported on the Swedish feedback page:
+http://sv.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2F%C3%85terkoppling&diff=22695791&oldid=22693792
+
+When there are blank lines before and after HTML comments, it seems like it is not possible to remove all of them. 
+
+Ideally it should pe bossible to edit this version:
+
+http://sv.wikipedia.org/w/index.php?title=Abrostola_major&oldid=21896423
+
+in a way that it gets like this:
+
+http://sv.wikipedia.org/w/index.php?title=Abrostola_major&diff=22695707&oldid=21896423
+
+But in VE editing mode it is not possible to format it like that without accidentaly deleting templates on the page. Is it perhaps because of the HTML comments?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Removal of blank lines when there are HTML comments seems not to work\n\nAs reported on the Swedish feedback page:\nURL\n\nWhen there are blank lines before and after HTML comments, it seems like it is not possible to remove all of them.', 'Ideally it should pe bossible to edit this version:\n\nURL\n\nin a way that it gets like this:\n\nURL\n\nBut in VE editing mode it is not possible to format it like that without accidentaly deleting templates on the page.', 'Is it perhaps because of the HTML comments?', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+240488,VisualEditor: Removal of blank lines when there are HTML comments seems not to work,"Yes, this is caused by the lack of ability to edit HTML comments making it impossible for users to understand what they're doing; though there are slightly distinct issues here, I'm going to merge it with that feature request.
+
+*** This bug has been marked as a duplicate of bug 49603 ***",task_subcomment,"[""Yes, this is caused by the lack of ability to edit HTML comments making it impossible for users to understand what they're doing; though there are slightly distinct issues here, I'm going to merge it with that feature request."", '*** This bug has been marked as a duplicate of bug 49603 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+53726,Incorrect URL used for magic RFC links,"js/lib/pegTokenizer.pegjs.txt currently contains the following:
+
+    var base_urls = {
+            'RFC'  : '//tools.ietfs.org/html/rfc%s',
+            'PMID' : '//www.ncbi.nlm.nih.gov/pubmed/%s?dopt=Abstract'
+        }
+
+base_urls['RFC'] is wrong; the hostname should be tools.ietf.org .
+
+I spotted this when looking at Firebug's HTML tab while VisualEditor was
+open on https://en.wikipedia.org/wiki/MD4#Security .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Incorrect URL used for magic RFC links\n\njs/lib/pegTokenizer.pegjs.txt currently contains the following:\n\n    var base_urls = {\n            'RFC'  : '//tools.ietfs.org/html/rfc%s',\n            'PMID' : '//www.ncbi.nlm.nih.gov/pubmed/%s?dopt=Abstract'\n        }\n\nbase_urls['RFC'] is wrong; the hostname should be tools.ietf.org ."", ""I spotted this when looking at Firebug's HTML tab while VisualEditor was\nopen on URL ."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240170,Incorrect URL used for magic RFC links,"Change 75118 merged by jenkins-bot:
+(Bug 51726) Fixed typo in url base for RFCs
+
+https://gerrit.wikimedia.org/r/75118",task_subcomment,['Change 75118 merged by jenkins-bot:\n(Bug 51726) Fixed typo in url base for RFCs\n\nGERRIT_URL'],['ACTION ON ISSUE']
+240168,Incorrect URL used for magic RFC links,"Change 75118 had a related patch set uploaded by Subramanya Sastry:
+(Bug 51726) Fixed typo in url base for RFCs
+
+https://gerrit.wikimedia.org/r/75118",task_subcomment,['Change 75118 had a related patch set uploaded by Subramanya Sastry:\n(Bug 51726) Fixed typo in url base for RFCs\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53714,VisualEditor: add new categories after old categories,"At the moment, categories are pushed right to the bottom of the page. This is mostly useful, but not always; it causes policy issues if there are stub templates around. While this is not something we can or will support, the fact remains that we're essentially imposing a structure on wikis by saying ""categories will always go at the bottom"".
+
+What would be a nice way around this problem, at least with existing articles, is to have newly-added categories stuck immediately after existing categories - wherever they are in the page. We get some degree of consistency within articles that would otherwise be lacking.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: add new categories after old categories\n\nAt the moment, categories are pushed right to the bottom of the page.', 'This is mostly useful, but not always; it causes policy issues if there are stub templates around.', 'While this is not something we can or will support, the fact remains that we\'re essentially imposing a structure on wikis by saying ""categories will always go at the bottom"".', 'What would be a nice way around this problem, at least with existing articles, is to have newly-added categories stuck immediately after existing categories - wherever they are in the page.', 'We get some degree of consistency within articles that would otherwise be lacking.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239615,VisualEditor: add new categories after old categories,"This is a duplicate of the (heretofore-confusingly-named) bug 50882.
+
+*** This bug has been marked as a duplicate of bug 50882 ***",task_subcomment,"['This is a duplicate of the (heretofore-confusingly-named) bug 50882.', '*** This bug has been marked as a duplicate of bug 50882 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53674,VisualEditor: Rearranging transclusions breaks the ability to select parameters.,"If you add multiple templates in one transclusion it is possible to rearrange them. Once rearranged, once cannot select the parameters from the first template anymore.
+
+Steps to reproduce:
+- Open any random page in the visual Editor.
+- Open the ""Transclusion"" window. Select the ""Cite web"" template and click the ""Add template"" button. It should be added with two default parameters.
+- Click the + icon in the bottom left of the Transclusion dialog, and click the button to add another template.
+- Add another ""Cite web"" template as described in step 2. Again it should come with two default parameters.
+
+Right now you should have a transclusion window containing two cite web templates.
+
+- Click the bottom template, and press the ^ icon to move that template to the top of the list. 
+- Now try to click the default ""Source Title"" or ""URL"" parameter in the top template. It is no longer possible to select or alter them. 
+- Extra: If you move the other template as well the same problem occurs; In that case both template's parameters can no longer be edited.
+
+Tested on Firefox 22 and Chrome 28 on Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Rearranging transclusions breaks the ability to select parameters.', 'If you add multiple templates in one transclusion it is possible to rearrange them.', 'Once rearranged, once cannot select the parameters from the first template anymore.', 'Steps to reproduce:\n- Open any random page in the visual Editor.', '- Open the ""Transclusion"" window.', 'Select the ""Cite web"" template and click the ""Add template"" button.', 'It should be added with two default parameters.', '- Click the + icon in the bottom left of the Transclusion dialog, and click the button to add another template.', '- Add another ""Cite web"" template as described in step 2.', 'Again it should come with two default parameters.', 'Right now you should have a transclusion window containing two cite web templates.', '- Click the bottom template, and press the ^ icon to move that template to the top of the list.', '- Now try to click the default ""Source Title"" or ""URL"" parameter in the top template.', 'It is no longer possible to select or alter them.', ""- Extra: If you move the other template as well the same problem occurs; In that case both template's parameters can no longer be edited."", 'Tested on Firefox 22 and Chrome 28 on Windows 7.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237251,VisualEditor: Rearranging transclusions breaks the ability to select parameters.,This was fixed as part of the transclusion dialog re-write in August; sorry for the slow triage.,task_subcomment,['This was fixed as part of the transclusion dialog re-write in August; sorry for the slow triage.'],['ACTION ON ISSUE']
+237242,VisualEditor: Rearranging transclusions breaks the ability to select parameters.,Also happens on Linux.,task_subcomment,['Also happens on Linux.'],['OBSERVED BUG BEHAVIOR']
+237235,VisualEditor: Rearranging transclusions breaks the ability to select parameters.,"Addendum: It seems that this does not only affect parameters. If you try to move the templates around more then once it will no longer be possible to rearrange them (The buttons for this no longer work). Also, any template ""Corrupted"" by moving them around will not be added to the page when one presses ""Apply Changes"".",task_subcomment,"['Addendum: It seems that this does not only affect parameters.', 'If you try to move the templates around more then once it will no longer be possible to rearrange them (The buttons for this no longer work).', 'Also, any template ""Corrupted"" by moving them around will not be added to the page when one presses ""Apply Changes"".']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+53655,"VisualEditor: Relabel buttons in ""cancel editing"" confirmation dialog","**Author:** `ignatzmice.wiki`
+
+**Description:**
+The button to cancel edits and return to read mode is labeled ""cancel""; clicking it brings up a dialog box with buttons ""OK"" and ""cancel"". Clicking *that* ""cancel"" cancels the cancel and returns to editing mode—not blatantly wrong, but confusing. Perhaps the first button should be renamed ""discard edits"" or similar?
+
+Original thread: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564868353#Ambiguity_in_.22Are_you_sure_you_want_to_cancel.22_dialog.3F See also bug 47676, closed as WONTFIX.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Relabel buttons in ""cancel editing"" confirmation dialog\n\n**Author:** CODE\n\n**Description:**\nThe button to cancel edits and return to read mode is labeled ""cancel""; clicking it brings up a dialog box with buttons ""OK"" and ""cancel"".', 'Clicking *that* ""cancel"" cancels the cancel and returns to editing mode—not blatantly wrong, but confusing.', 'Perhaps the first button should be renamed ""discard edits"" or similar?', 'Original thread: URL See also bug 47676, closed as WONTFIX.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+236185,"VisualEditor: Relabel buttons in ""cancel editing"" confirmation dialog","Merging with bug 50955.
+
+*** This bug has been marked as a duplicate of bug 50955 ***",task_subcomment,"['Merging with bug 50955.', '*** This bug has been marked as a duplicate of bug 50955 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+236180,"VisualEditor: Relabel buttons in ""cancel editing"" confirmation dialog","The confirmation dialog should have more descriptive buttons, such as [Discard edits] [Continue editing], or [Leave editing mode] [Return to editing], etc.
+
+For this to happen, it needs to become a jQuery dialog.
+
+In fact, VE shouldn't use native confirm() dialogs; the implementation in most browsers is crappy.",task_subcomment,"['The confirmation dialog should have more descriptive buttons, such as [Discard edits] [Continue editing], or [Leave editing mode] [Return to editing], etc.', 'For this to happen, it needs to become a jQuery dialog.', ""In fact, VE shouldn't use native confirm() dialogs; the implementation in most browsers is crappy.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53653,"VisualEditor: Double-clicking inside edit surface sometimes causes uncaught JS ""offset could not be translated"" errors","Steps to reproduce:
+
+1) Open https://en.wikipedia.org/wiki/Jam,_Iran?veaction=edit
+
+2) Double-click repeatedly inside one of the templates (e.g. infobox)
+
+The following JavaScript error appears on the console:
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 442 
+
+Chrome 28/Ubuntu
+
+See also: bug 51526
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Double-clicking inside edit surface sometimes causes uncaught JS ""offset could not be translated"" errors\n\nSteps to reproduce:\n\n1) Open URL\n\n2) Double-click repeatedly inside one of the templates (e.g.', 'infobox)\n\nThe following JavaScript error appears on the console:\n\nUncaught Error: Offset could not be translated to a DOM element and offset: 442 \n\nChrome 28/Ubuntu\n\nSee also: bug 51526\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+236087,"VisualEditor: Double-clicking inside edit surface sometimes causes uncaught JS ""offset could not be translated"" errors",I can't reproduce this now' provisionally closing as WORKSFORME. Please re-open if you can still reproduce.,task_subcomment,"[""I can't reproduce this now' provisionally closing as WORKSFORME."", 'Please re-open if you can still reproduce.']","['WORKAROUNDS', 'BUG REPRODUCTION']"
+53619,"VisualEditor: ""Leave Feedback"" link greyed out; might confuse users","The ""leave feedback"" link renders in grey, which might suggest to users that is not a functional element. Issue raised by English Wikipedia editor Hhhippo.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: ""Leave Feedback"" link greyed out; might confuse users\n\nThe ""leave feedback"" link renders in grey, which might suggest to users that is not a functional element.', 'Issue raised by English Wikipedia editor Hhhippo.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+234208,"VisualEditor: ""Leave Feedback"" link greyed out; might confuse users",This design was fixed some time ago but I forgot to tag this bug; sorry!,task_subcomment,['This design was fixed some time ago but I forgot to tag this bug; sorry!'],['OBSERVED BUG BEHAVIOR']
+53618,"""Leave Feedback"" link rendering as two lines in some fonts","Using Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that ""I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)""
+
+The culprit, evidently is ""Ubuntu's default font: DejaVu Sans. That's a bit wider than e.g. Arial, so it causes a linebreak in the link. Maybe one could make that space non-breaking and have the flyout widen instead?""
+
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564802026#Follow-up
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['""Leave Feedback"" link rendering as two lines in some fonts\n\nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that ""I see an empty line between \'\'User guide\'\' and \'\'Leave\'\' and another one between \'\'Leave\'\' and \'\'feedback\'\'.', 'My very first thought was that \'\'Leave\'\' would be the switch for signing out of the beta test (note that I didn\'t click it ;-)""\n\nThe culprit, evidently is ""Ubuntu\'s default font: DejaVu Sans.', ""That's a bit wider than e.g."", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?""', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+234164,"""Leave Feedback"" link rendering as two lines in some fonts","This was already reported as bug 51335 (sorry!).
+
+*** This bug has been marked as a duplicate of bug 51335 ***",task_subcomment,"['This was already reported as bug 51335 (sorry!).', '*** This bug has been marked as a duplicate of bug 51335 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53567,VisualEditor: Image is not displayed on Visual Editor,"The image from [1] and is not rendered on VisualEditor [2].
+
+[1] https://pt.wikipedia.org/w/index.php?oldid=36419116
+[2] https://pt.wikipedia.org/w/index.php?oldid=36419116&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51248",task_description,"['VisualEditor: Image is not displayed on Visual Editor\n\nThe image from [1] and is not rendered on VisualEditor [2].', '[1] URL\n[2] URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+255955,VisualEditor: Image is not displayed on Visual Editor,"I believe that this was a dupe of bug 51248.
+
+*** This bug has been marked as a duplicate of bug 51248 ***",task_subcomment,"['I believe that this was a dupe of bug 51248.', '*** This bug has been marked as a duplicate of bug 51248 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53554,"VisualEditor:  tags added to all markup in paragraph, including pre-existing","At https://en.wikipedia.org/w/index.php?title=List_of_American_Dad!_characters&curid=2082680&diff=564675517&oldid=564302759 a user added a link using wikitext. The VisualEditor added  tags around it (correct according to apparent design, incorrect according to desired behaviour). 
+
+However, it also added  tags around every other bit of pre-existing markup in the paragraph. This is incorrect according to my understanding of the design because even if they did want to include a literal string surrounded by square brackets they did not want to alter the existing markup.
+
+Bug 5069 comment 5 suggests to me that this isn't that bug but a different one, but not what number that other bug is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor:  tags added to all markup in paragraph, including pre-existing\n\nAt URL a user added a link using wikitext.', 'The VisualEditor added  tags around it (correct according to apparent design, incorrect according to desired behaviour).', 'However, it also added  tags around every other bit of pre-existing markup in the paragraph.', 'This is incorrect according to my understanding of the design because even if they did want to include a literal string surrounded by square brackets they did not want to alter the existing markup.', ""Bug 5069 comment 5 suggests to me that this isn't that bug but a different one, but not what number that other bug is."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+255037,"VisualEditor:  tags added to all markup in paragraph, including pre-existing",This seems to have been fixed (I now can't reproduce) in the re-write of nowiki-ing code; sorry for the bug.,task_subcomment,"[""This seems to have been fixed (I now can't reproduce) in the re-write of nowiki-ing code; sorry for the bug.""]",['OBSERVED BUG BEHAVIOR']
+255030,"VisualEditor:  tags added to all markup in paragraph, including pre-existing","Really sorry, but I meant Bug 50659 comment 5 
+Dyslexia + typos to blame so entirely my fault.",task_subcomment,"['Really sorry, but I meant Bug 50659 comment 5 \nDyslexia + typos to blame so entirely my fault.']",['BUG REPRODUCTION']
+255023,"VisualEditor:  tags added to all markup in paragraph, including pre-existing","Sorry, typo in that last line. It should refer to Bug 50569 comment 5",task_subcomment,"['Sorry, typo in that last line.', 'It should refer to Bug 50569 comment 5']","['OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+53534,Can't save,"Using Firefox 24, Ubuntu 13.04
+
+What I did:
+1. I was editing a page[1], made several small changes (fixing typos, rephrasing)
+2. I clicked ""Save page"" which brings up the save dialog
+3. I wrote a summary and clicked ""Save page"" again
+4. The blue throbber line appears, disappears and leaves me with the save dialog still open (not saving anything)
+5. I open the JS console and when I try to save again I see:
+  a. The HTML is submitted to the API
+  b. Before the response arrives (?) a JS error appears: ""TypeError: editApi is undefined""[2]
+  c. The API responds with a ""200 OK"" which includes a JSON error[3]
+
+When I open the JavaScript console I see the following: 1) The HTML is submitted to the API, and while that request to the API is in transit a JS error appears: 
+
+[1] https://www.mediawiki.org/wiki/VisualEditor/Portal/sv
+[2] File: https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.visibleText%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130717T024027Z&* Line: 85
+[3] {""servedby"":""mw1203"",""error"":{""code"":""unknownerror"",""info"":""Unknown error: \""tpt-target-page\""""}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Can't save\n\nUsing Firefox 24, Ubuntu 13.04\n\nWhat I did:\n1."", 'I was editing a page[1], made several small changes (fixing typos, rephrasing)\n2.', 'I clicked ""Save page"" which brings up the save dialog\n3.', 'I wrote a summary and clicked ""Save page"" again\n4.', 'The blue throbber line appears, disappears and leaves me with the save dialog still open (not saving anything)\n5.', 'I open the JS console and when I try to save again I see:\n  a.', 'The HTML is submitted to the API\n  b.', 'Before the response arrives (?)', 'a JS error appears: ""TypeError: editApi is undefined""[2]\n  c. The API responds with a ""200 OK"" which includes a JSON error[3]\n\nWhen I open the JavaScript console I see the following: 1) The HTML is submitted to the API, and while that request to the API is in transit a JS error appears: \n\n[1] URL\n[2] File: URL Line: 85\n[3] {""servedby"":""mw1203"",""error"":{""code"":""unknownerror"",""info"":""Unknown error: \\""tpt-target-page\\""""}}\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253978,Can't save,"
+
+%%%*** This bug has been marked as a duplicate of bug 50284 ***%%%",task_subcomment,['\n\n%%%*** This bug has been marked as a duplicate of bug 50284 ***%%%'],['ACTION ON ISSUE']
+253968,Can't save,"...and when I try to edit it using the traditional ""Edit source"" I actually get a real error message: ""This page cannot be updated manually. This page is a translation of the page VisualEditor/Portal and the translation can be updated using the translation tool.""
+
+That message should be shown also when trying to edit with the VisualEditor.",task_subcomment,"['...and when I try to edit it using the traditional ""Edit source"" I actually get a real error message: ""This page cannot be updated manually.', 'This page is a translation of the page VisualEditor/Portal and the translation can be updated using the translation tool.""', 'That message should be shown also when trying to edit with the VisualEditor.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53531,Visual Editor: Adding text after a link includes that text in the link,"If you place the cursor after the last character of a link and start typing then your text becomes part of the displayed text for that link: [[Fish]] → [[Fish|Fish and chips]] rather than the inte.nded [[Fish]] and chips or [[Fish and chips]] which would be expected from a WYSIWYG editor (even if it isn't what is wanted).
+
+There is no way to edit part of a link at all, the only way around it is to unlink the whole phrase and relink the part you want linked.
+
+This is not usually a problem, as you can work around by starting from after the space after the link.
+
+However, this is counter intuitive if you want to add punctuation after the link (add it after the space, delete the space, add space after the punctuation). It also means it is impossible to add unlinked text when the link ends the line, as happens often on disambiguation pages. For example try adding context to the links at Mandi#People. Apparently a workaround is to insert a line break, add the text and then delete the line break. I've not tested this myself though
+
+It is possible this is the same as bug 50945 but I don't think it is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Visual Editor: Adding text after a link includes that text in the link\n\nIf you place the cursor after the last character of a link and start typing then your text becomes part of the displayed text for that link: [[Fish]] → [[Fish|Fish and chips]] rather than the inte.nded [[Fish]] and chips or [[Fish and chips]] which would be expected from a WYSIWYG editor (even if it isn't what is wanted)."", 'There is no way to edit part of a link at all, the only way around it is to unlink the whole phrase and relink the part you want linked.', 'This is not usually a problem, as you can work around by starting from after the space after the link.', 'However, this is counter intuitive if you want to add punctuation after the link (add it after the space, delete the space, add space after the punctuation).', 'It also means it is impossible to add unlinked text when the link ends the line, as happens often on disambiguation pages.', 'For example try adding context to the links at Mandi#People.', 'Apparently a workaround is to insert a line break, add the text and then delete the line break.', ""I've not tested this myself though\n\nIt is possible this is the same as bug 50945 but I don't think it is."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'WORKAROUNDS', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253720,Visual Editor: Adding text after a link includes that text in the link,"This is actually the same as bug 51463 which we just fixed and are deploying now. Sorry for the inconvenience.
+
+*** This bug has been marked as a duplicate of bug 51463 ***",task_subcomment,"['This is actually the same as bug 51463 which we just fixed and are deploying now.', 'Sorry for the inconvenience.', '*** This bug has been marked as a duplicate of bug 51463 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253712,Visual Editor: Adding text after a link includes that text in the link,"**JohnCD67** wrote:
+
+This is quite a serious problem because a user who tries to set up a link at the right hand end of a line, i.e. without having first typed at least one space beyond it, becomes trapped in a mode where all further typing goes inside the link, and there is no easy way out. I think this is what is causing peculiar links, e.g. a link to ""Chendo"" piped to ""Chendo, "" and one to ""Manolo Sanchís"" piped to ""Manolo Sanchís and "". See report at
+
+[[:en:WP:VisualEditor/Feedback#You have to type something after a word before attempting to wikilink it]]",task_subcomment,"['**JohnCD67** wrote:\n\nThis is quite a serious problem because a user who tries to set up a link at the right hand end of a line, i.e.', 'without having first typed at least one space beyond it, becomes trapped in a mode where all further typing goes inside the link, and there is no easy way out.', 'I think this is what is causing peculiar links, e.g.', 'a link to ""Chendo"" piped to ""Chendo, "" and one to ""Manolo Sanchís"" piped to ""Manolo Sanchís and "".', 'See report at\n\n[[:en:WP:VisualEditor/Feedback#You have to type something after a word before attempting to wikilink it]]']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+53530,VisualEditor: Tab key moves focus between citations; doesn't indent text as expected,"Editor HHHIPPO on English Wikipedia notes that the tab key does not increase indentation (as promised in the greyed out icon on the ribbon) but rather jumps from citation to citation. (For me, it also lands on wikilinks in templates.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Tab key moves focus between citations; doesn't indent text as expected\n\nEditor HHHIPPO on English Wikipedia notes that the tab key does not increase indentation (as promised in the greyed out icon on the ribbon) but rather jumps from citation to citation."", '(For me, it also lands on wikilinks in templates.)', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253661,VisualEditor: Tab key moves focus between citations; doesn't indent text as expected,"
+
+*** This bug has been marked as a duplicate of bug 48010 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 48010 ***'],['ISSUE CONTENT MANAGEMENT']
+53528,"VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded s","On English Wikipedia, a user reports the following:
+*Added leading whitespace to paragraph in VE. Text appears fine in VE, with leading whitespace as an indentation.
+*Saved. VE adds nowiki tags before the whitespace and after the first few words. Text displays without indent.
+*Tried removing the whitespace in VE.
+*VE won't allow the whitespace to be removed, but instead will only permit the first few words to be deleted.
+This is with Chrome 28 + Windows 7. I'll see if I can work out the conditions that would have created the first problem. - Bilby (talk) 02:37, 16 July 2013 (UTC)
+VEspaceremoval.png
+
+I tried to replicate this myself.
+*Added whitespace to the lead of an article, and it nowikied. http://en.wikipedia.org/w/index.php?title=Quadrangle_%28architecture%29&diff=564486949&oldid=563578917
+
+*It turned the first word into an uneditable element. See image: http://en.wikipedia.org/wiki/File:VEspaceremoval.png 
+
+*Curious as to what the nowikis would do to formatting, I found an article that had formatting on the first word. It added space, no ""nowiki."" http://en.wikipedia.org/w/index.php?title=Marloth_Park&diff=564487138&oldid=557816381
+
+* It allowed me to remove the space in VE.
+
+
+(Also using Chrome on 7.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded s\n\nOn English Wikipedia, a user reports the following:\n*Added leading whitespace to paragraph in VE."", 'Text appears fine in VE, with leading whitespace as an indentation.', '*Saved.', 'VE adds nowiki tags before the whitespace and after the first few words.', 'Text displays without indent.', '*Tried removing the whitespace in VE.', ""*VE won't allow the whitespace to be removed, but instead will only permit the first few words to be deleted."", 'This is with Chrome 28 + Windows 7.', ""I'll see if I can work out the conditions that would have created the first problem."", '- Bilby (talk) 02:37, 16 July 2013 (UTC)\nVEspaceremoval.png\n\nI tried to replicate this myself.', '*Added whitespace to the lead of an article, and it nowikied.', 'URL\n\n*It turned the first word into an uneditable element.', 'See image: URL \n\n*Curious as to what the nowikis would do to formatting, I found an article that had formatting on the first word.', 'It added space, no ""nowiki.""', 'URL\n\n* It allowed me to remove the space in VE.', '(Also using Chrome on 7.)', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253588,"VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded s",This was fixed in July; sorry for the slow triage.,task_subcomment,['This was fixed in July; sorry for the slow triage.'],['ACTION ON ISSUE']
+53514,update.php does not give any response.,"I meat an annoying problem. I tried to upgrade my wiki from 1.20.6 (0727d6a) to 1.22wmf9 in order to use VisualEditor. (nginx/1.2.5 php_version5.3.23 on Linode VPS)
+
+The serves running few wikis using one set mediawiki software. I tried to php update.php the largest 1.5G Chinese version, but the script simple give no response.
+
+example: 
+ [root@moegirl maintenance]# php  update.php
+ [root@moegirl maintenance]# 
+I tried other smaller site, it react like this:
+
    +MediaWiki 1.22wmf9 Updater
+
+Going to run database updates for enwiki
+Depending on the size of your database this may take a while!
+Abort with control-c in the next five seconds (skip this countdown with --quick)
+ ... 0
+[root@moegirl maintenance]#
+
    
+The web updater works good for small wiki, but the 1.5G one will receive ""Timeout""
+
+The most annoying thing is when I tried to upgrade same database to 1.22wmf9, all of then works as normal. Only the major linode VPS we are using have this problem.
+
+Anyone had ever meet same problem? Is this a new bug? How to solve it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['update.php does not give any response.', 'I meat an annoying problem.', 'I tried to upgrade my wiki from 1.20.6 (0727d6a) to 1.22wmf9 in order to use VisualEditor.', '(nginx/1.2.5 php_version5.3.23 on Linode VPS)\n\nThe serves running few wikis using one set mediawiki software.', 'I tried to php update.php the largest 1.5G Chinese version, but the script simple give no response.', 'example: \n [root@moegirl maintenance]# php  update.php\n [root@moegirl maintenance]# \nI tried other smaller site, it react like this:\n
    \nMediaWiki 1.22wmf9 Updater\n\nGoing to run database updates for enwiki\nDepending on the size of your database this may take a while!', 'Abort with control-c in the next five seconds (skip this countdown with --quick)\n ... 0\n[root@moegirl maintenance]#\n
    \nThe web updater works good for small wiki, but the 1.5G one will receive ""Timeout""\n\nThe most annoying thing is when I tried to upgrade same database to 1.22wmf9, all of then works as normal.', 'Only the major linode VPS we are using have this problem.', 'Anyone had ever meet same problem?', 'Is this a new bug?', 'How to solve it?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252854,update.php does not give any response.,"Find out reason. For some unknown reason, the php does not shows error message. When one of my friend tried 
+
+php -n update.php
+
+it showed the error message and we fix it very soon according to it.",task_subcomment,"['Find out reason.', 'For some unknown reason, the php does not shows error message.', 'When one of my friend tried \n\nphp -n update.php\n\nit showed the error message and we fix it very soon according to it.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252847,update.php does not give any response.,"The most annoying thing is when I tried to upgrade same database to 1.22wmf9 on other vps, all of then works as normal.",task_subcomment,"['The most annoying thing is when I tried to upgrade same database to 1.22wmf9 on other vps, all of then works as normal.']",['OBSERVED BUG BEHAVIOR']
+252840,update.php does not give any response.,"BTW, I tried 1.20.6 and 1.21.1 as well. None of them work in that server.",task_subcomment,"['BTW, I tried 1.20.6 and 1.21.1 as well.', 'None of them work in that server.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53481,&veaction= as a second parameter works on enwiki but not zhwiki,"Dunno why but:
+
+https://en.wikipedia.org/w/index.php?title=Fish&veaction=edit loads VE-edit mode
+
+https://zh.wikipedia.org/w/index.php?title=%E9%B1%BC&veaction=edit doesn't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""&veaction= as a second parameter works on enwiki but not zhwiki\n\nDunno why but:\n\nURL loads VE-edit mode\n\nURL doesn't."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250734,&veaction= as a second parameter works on enwiki but not zhwiki,"(In reply to comment #2)
+> Do you perhaps have the VE preference enabled on enwiki but not on zhwiki?
+> veaction=edit will only work if VisualEditor is available, i.e. you didn't
+> disable it and it didn't detect some problem with your browser that made it
+> disable itself.
+
+Well it works for me now on zhwiki.",task_subcomment,['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell it works for me now on zhwiki.'],['SOLUTION USAGE']
+250728,&veaction= as a second parameter works on enwiki but not zhwiki,"Do you perhaps have the VE preference enabled on enwiki but not on zhwiki? veaction=edit will only work if VisualEditor is available, i.e. you didn't disable it and it didn't detect some problem with your browser that made it disable itself.",task_subcomment,"['Do you perhaps have the VE preference enabled on enwiki but not on zhwiki?', 'veaction=edit will only work if VisualEditor is available, i.e.', ""you didn't disable it and it didn't detect some problem with your browser that made it disable itself.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250721,&veaction= as a second parameter works on enwiki but not zhwiki,I cant reproduce this now.,task_subcomment,['I cant reproduce this now.'],['BUG REPRODUCTION']
+53456,"Rearranging, removing, or reorganizing sections, then saving the page, causes the Table of Contents to link to 'Edit' instead of the section","From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#How_did_it_go_to_Vedit_mode.3F
+
+""After saving an V-edit on Shiva, I saved the page. From contents, I clicked on a section. Instead of going to the section, it went in Vedit mode. --Redtigerxyz Talk 09:48, 14 July 2013 (UTC)""
+
+
+The problem was replicated in at least two articles, and only appears when reorganizing or removing sections.  The editor is running Chrome Version 28.0.1500.72 m and Windows 7 Home edition.  I couldn't replicate it using either Safari or Firefox on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7",task_description,"['Rearranging, removing, or reorganizing sections, then saving the page, causes the Table of Contents to link to \'Edit\' instead of the section\n\nFrom URL\n\n""After saving an V-edit on Shiva, I saved the page.', 'From contents, I clicked on a section.', 'Instead of going to the section, it went in Vedit mode.', '--Redtigerxyz Talk 09:48, 14 July 2013 (UTC)""\n\n\nThe problem was replicated in at least two articles, and only appears when reorganizing or removing sections.', 'The editor is running Chrome Version 28.0.1500.72 m and Windows 7 Home edition.', ""I couldn't replicate it using either Safari or Firefox on a Mac."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Windows 7']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249290,"Rearranging, removing, or reorganizing sections, then saving the page, causes the Table of Contents to link to 'Edit' instead of the section","I still cannot replicate this; possibly a transient caching bug?
+
+Marking as INVALID. Please re-open if it recurs.",task_subcomment,"['I still cannot replicate this; possibly a transient caching bug?', 'Marking as INVALID.', 'Please re-open if it recurs.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+249285,"Rearranging, removing, or reorganizing sections, then saving the page, causes the Table of Contents to link to 'Edit' instead of the section","fwiw, I also tried to replicate it back in July and failed.",task_subcomment,"['fwiw, I also tried to replicate it back in July and failed.']",['OBSERVED BUG BEHAVIOR']
+53453,VisualEditor:Wrong reference subnumbering used for some wikis,"Screenshot
+
+Multiple uses of a references are shown in the reference list:
+
+Default: is ""1.0 1.1 1.2 1.3"" etc.
+
+Some wikis, like dewiki, uses ""a b c"" etc. 
+
+
+VE rendering always use the default.
+
+This is configured onwiki with [[MediaWiki:Cite references link many format]]. It depends on usage of $2 or $3:
+
+Default content: [[#$1|$2]]. $2 responsible for showing ""1.0 1.1 1.2 1.3"" etc
+
+dewiki content: [[#$1|$3]]. $3 is responsible for showing ""a b c"" etc
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11692}",task_description,"['VisualEditor:Wrong reference subnumbering used for some wikis\n\nScreenshot\n\nMultiple uses of a references are shown in the reference list:\n\nDefault: is ""1.0 1.1 1.2 1.3"" etc.', 'Some wikis, like dewiki, uses ""a b c"" etc.', 'VE rendering always use the default.', 'This is configured onwiki with [[MediaWiki:Cite references link many format]].', 'It depends on usage of $2 or $3:\n\nDefault content: [[#$1|$2]].', '$2 responsible for showing ""1.0 1.1 1.2 1.3"" etc\n\ndewiki content: [[#$1|$3]].', '$3 is responsible for showing ""a b c"" etc\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11692}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+249176,VisualEditor:Wrong reference subnumbering used for some wikis,"This is covered by bug 49346 which is assigned and prioritised, so I'm marking this as a duplicate.
+
+*** This bug has been marked as a duplicate of bug 49346 ***",task_subcomment,"[""This is covered by bug 49346 which is assigned and prioritised, so I'm marking this as a duplicate."", '*** This bug has been marked as a duplicate of bug 49346 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+249172,VisualEditor:Wrong reference subnumbering used for some wikis,"(In reply to comment #1)
+> (Are the letters in ref.1 at
+> https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/
+> Sandbox&diff=next&oldid=570373191
+> different from what you describe?)
+
+In read mode I see
+
+1. ^ a b pippo
+
+In VE edit mode I see:
+
+1.   1.0 1.1 pippo
+
+The latter is wrong. I except to see in VE edit mode the same letters a b as in read mode",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIn read mode I see\n\n1.', '^ a b pippo\n\nIn VE edit mode I see:\n\n1.', '1.0 1.1 pippo\n\nThe latter is wrong.', 'I except to see in VE edit mode the same letters a b as in read mode']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+249167,VisualEditor:Wrong reference subnumbering used for some wikis,(Are the letters in ref.1 at https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=570373191 different from what you describe?),task_subcomment,['(Are the letters in ref.1 at URL different from what you describe?)'],['OBSERVED BUG BEHAVIOR']
+53452,VisualEditor: Category adding interface is hard to find,"I was surprised to find that I couldn't add any categories with the Visual Editor. I'm sure if we can add images, references, and templates, we should be able to add categories without too much trouble. Is this feature in beta or something?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Category adding interface is hard to find\n\nI was surprised to find that I couldn't add any categories with the Visual Editor."", ""I'm sure if we can add images, references, and templates, we should be able to add categories without too much trouble."", 'Is this feature in beta or something?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+249101,VisualEditor: Category adding interface is hard to find,"
+
+*** This bug has been marked as a duplicate of bug 51153 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51153 ***'],['ACTION ON ISSUE']
+249097,VisualEditor: Category adding interface is hard to find,"Nevermind. I found it under Page Settings. Seems like a strange place to put it. I would expect page settings to be stuff like font size or disabling the table of contents. Also the gear icon seems like a strange choice since all of our other uses of the gear icon (Echo, ULS) are about changing user preferences. Definitely not an icon I would associate with adding categories.
+
+Changing bug summary.",task_subcomment,"['Nevermind.', 'I found it under Page Settings.', 'Seems like a strange place to put it.', 'I would expect page settings to be stuff like font size or disabling the table of contents.', 'Also the gear icon seems like a strange choice since all of our other uses of the gear icon (Echo, ULS) are about changing user preferences.', 'Definitely not an icon I would associate with adding categories.', 'Changing bug summary.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+53440,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'end' of null""","Can't reliably reproduce but I was turning text into a link, enter a url but didn't save the new link target (so it was saved as an internal link with the label as link target), then when entering the Save dialog and saving, this exception was thrown.
+
+
+> Uncaught TypeError: Cannot read property 'end' of null
+  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cexperimental%2…ageTarget.icons-vector%7Crangy&skin=vector&version=20130716T133516Z&*:9463
+* ve.ui.Context.updateDimensions
+  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cexperimental%2…ageTarget.icons-vector%7Crangy&skin=vector&version=20130716T133516Z&*:9463
+* (anonymous function)
+  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cexperimental%2…ageTarget.icons-vector%7Crangy&skin=vector&version=20130716T133516Z&*:9499
+* proxy
+  load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20130715T175253Z:10
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Fix ""Uncaught TypeError: Cannot read property \'end\' of null""\n\nCan\'t reliably reproduce but I was turning text into a link, enter a url but didn\'t save the new link target (so it was saved as an internal link with the label as link target), then when entering the Save dialog and saving, this exception was thrown.', 'QUOTE\n  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cexperimental%2…ageTarget.icons-vector%7Crangy&skin=vector&version=20130716T133516Z&*:9463\n* ve.ui.Context.updateDimensions\n  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cexperimental%2…ageTarget.icons-vector%7Crangy&skin=vector&version=20130716T133516Z&*:9463\n* (anonymous function)\n  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cexperimental%2…ageTarget.icons-vector%7Crangy&skin=vector&version=20130716T133516Z&*:9499\n* proxy\n  load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20130715T175253Z:10\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+248308,"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'end' of null""",Provisionally closing as WORKSFORME.,task_subcomment,['Provisionally closing as WORKSFORME.'],['WORKAROUNDS']
+53438,VisualEditor: Link inspector should make it easier to change the label,"There's a few problems, if we end up solving them in different ways we should create separate bugs for one or more of them.
+
+
+1) Changing the label of an internal link
+
+Given a simple link like [[example]] or [[Example]] (e.g. no custom label), when changing the link target, it seems to the user that the link has not updated since the label (which is all we see in the editor, hovering the link does nothing since it isn't a clickable link in edit mode).. since the label has not changed.
+
+Now one could argue the label shouldn't update at this point so that the sentence still reads the same (e.g. when changing intending to change the link from ""He was [[foolian]]."" to ""He was [[Foo|foonier]]."") and to be consistent for cases where the link does have a custom label (in which case it is more likely the label should stay the same?).
+
+However given the following two cases:
+
+* ""... is an [[United States|American]] thing ...""
+  -> "" is a [[Germany|German]] thing ...""
+
+* ""... according to [[David Tennant]] ...""
+  -> "" according to [[Russell T Davies]] ...""
+
+It is very common that the label should change to the target automatically (the second case) or at least be easy to change right after (first case). Ideally for the first case above it would automatically change to Germany and then the user can correct it to German.
+
+2) Change the label of any link
+
+Whether internal or external, it seems quite difficult to change the label of a link. When selecting the entire link text and typing over it, it currently behaves as follows:
+
+ > Some link
+ Select link (has to be done manually (tedious and error prone) 
+ > Some [selection]    link[/selection]""
+ Type ""hello"".
+ > Some hello.
+
+wtf?
+
+
+Though I'm open to other ideas, I'd recommend we start by putting an input field in the link inspector for the label so that they can be changed together. Though even without that, one should be able to replace the label without opening the inspector or running into the weird ""first charother chars"" case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48463",task_description,"[""VisualEditor: Link inspector should make it easier to change the label\n\nThere's a few problems, if we end up solving them in different ways we should create separate bugs for one or more of them."", '1) Changing the label of an internal link\n\nGiven a simple link like [[example]] or [[Example]] (e.g.', ""no custom label), when changing the link target, it seems to the user that the link has not updated since the label (which is all we see in the editor, hovering the link does nothing since it isn't a clickable link in edit mode).. since the label has not changed."", ""Now one could argue the label shouldn't update at this point so that the sentence still reads the same (e.g."", 'when changing intending to change the link from ""He was [[foolian]].""', 'to ""He was [[Foo|foonier]]."")', 'and to be consistent for cases where the link does have a custom label (in which case it is more likely the label should stay the same?).', 'However given the following two cases:\n\n* ""... is an [[United States|American]] thing ...""\n  -> "" is a [[Germany|German]] thing ...""\n\n* ""... according to [[David Tennant]] ...""\n  -> "" according to [[Russell T Davies]] ...""\n\nIt is very common that the label should change to the target automatically (the second case) or at least be easy to change right after (first case).', 'Ideally for the first case above it would automatically change to Germany and then the user can correct it to German.', '2) Change the label of any link\n\nWhether internal or external, it seems quite difficult to change the label of a link.', 'When selecting the entire link text and typing over it, it currently behaves as follows:\n\nQUOTE\n Select link (has to be done manually (tedious and error prone) \nQUOTE\n Type ""hello"".', 'QUOTE\n\nwtf?', ""Though I'm open to other ideas, I'd recommend we start by putting an input field in the link inspector for the label so that they can be changed together."", 'Though even without that, one should be able to replace the label without opening the inspector or running into the weird ""first charother chars"" case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+248200,VisualEditor: Link inspector should make it easier to change the label,"
+
+*** This bug has been marked as a duplicate of bug 53973 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 53973 ***'],['ACTION ON ISSUE']
+248194,VisualEditor: Link inspector should make it easier to change the label,"Here's a link that shows one of the main problems with the current approach:  https://hif.wikipedia.org/w/index.php?title=Akbar_the_Great&diff=194531&oldid=194146
+
+The editor almost certainly did not intend to end up with [[15 October|14 October]], and the editor almost certainly does not know that his effort to change the link failed.",task_subcomment,"[""Here's a link that shows one of the main problems with the current approach:  URL\n\nThe editor almost certainly did not intend to end up with [[15 October|14 October]], and the editor almost certainly does not know that his effort to change the link failed.""]",['BUG REPRODUCTION']
+248190,VisualEditor: Link inspector should make it easier to change the label,"I'd rather have a label input (or at least a label display) in the link inspector, but some method of indicating that the link is piped or has separate trailing text is important.  
+
+If you see a redlink like ""Alice Expert"", you can't tell from looking at the link in VisualEditor that it's actually piped:  [[Alice D Expert|Alice Expert]].  Fixing the label to match the actual article title name (""Alice D. Expert"") does not fix the broken link.  
+
+There's no way to see that the redlink didn't get fixed when you changed the label to ""Alice D. Expert"" (because VisualEditor's ""red"" links are blue).  
+
+There is also no reason for you to suspect that the problem is due to a hidden piped link, because there is no visual cue that you need to go into the link inspector to address the hidden/piped link.",task_subcomment,"[""I'd rather have a label input (or at least a label display) in the link inspector, but some method of indicating that the link is piped or has separate trailing text is important."", 'If you see a redlink like ""Alice Expert"", you can\'t tell from looking at the link in VisualEditor that it\'s actually piped:  [[Alice D Expert|Alice Expert]].', 'Fixing the label to match the actual article title name (""Alice D. Expert"") does not fix the broken link.', 'There\'s no way to see that the redlink didn\'t get fixed when you changed the label to ""Alice D. Expert"" (because VisualEditor\'s ""red"" links are blue).', 'There is also no reason for you to suspect that the problem is due to a hidden piped link, because there is no visual cue that you need to go into the link inspector to address the hidden/piped link.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248188,VisualEditor: Link inspector should make it easier to change the label,I think this duplicates Bug 50945,task_subcomment,['I think this duplicates Bug 50945'],['OBSERVED BUG BEHAVIOR']
+248186,VisualEditor: Link inspector should make it easier to change the label,"We shouldn't put a label input in the link inspector because:
+
+1. It doesn't support rich text
+2. We cannot and should not put a subsurface in an inspector
+3. Links should remain a lightweight task, and dialogs are not lightweight
+4. This doesn't elegantly solve the problem anyway
+
+Some steps towards a better approach:
+
+1. We could decorate the ""linked"" portion of a link differently than
+   the link trail portion - at lease during certain interactions.
+2. We could add extra cursor positions on each side of a link to indicate being
+   next to or inside the link tag, decorate the link when you are inside those
+   boundaries.",task_subcomment,"[""We shouldn't put a label input in the link inspector because:\n\n1."", ""It doesn't support rich text\n2."", 'We cannot and should not put a subsurface in an inspector\n3.', 'Links should remain a lightweight task, and dialogs are not lightweight\n4.', ""This doesn't elegantly solve the problem anyway\n\nSome steps towards a better approach:\n\n1."", 'We could decorate the ""linked"" portion of a link differently than\n   the link trail portion - at lease during certain interactions.', '2.', 'We could add extra cursor positions on each side of a link to indicate being\n   next to or inside the link tag, decorate the link when you are inside those\n   boundaries.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53427,Syndicated feeds of Watchlists include non-existent edits,"XML file of syndicated watchlist, slightly modified
+
+MediaWiki creates Atom feeds for watchlists. I use a feed reader to read a few on Wikia as well as en.wp. The feeds from Wikia are all sensible and useful but the one from en.wp includes edits that do not exist. Attached is an XML file that I generated with wget (through the assistance of persons on #mediawiki) which I have slightly redacted to remove my watchlist token. Edits which did not occur can be found c. line 229 where the syndication claims that User:FelGru edited the page Everything That Happens Will Happen Today and starting around line 373 there are a spate of edits to categories by User:InMontreal which also did not occur.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11634}",task_description,"['Syndicated feeds of Watchlists include non-existent edits\n\nXML file of syndicated watchlist, slightly modified\n\nMediaWiki creates Atom feeds for watchlists.', 'I use a feed reader to read a few on Wikia as well as en.wp.', 'The feeds from Wikia are all sensible and useful but the one from en.wp includes edits that do not exist.', 'Attached is an XML file that I generated with wget (through the assistance of persons on #mediawiki) which I have slightly redacted to remove my watchlist token.', 'Edits which did not occur can be found c. line 229 where the syndication claims that User:FelGru edited the page Everything That Happens Will Happen Today and starting around line 373 there are a spate of edits to categories by User:InMontreal which also did not occur.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11634}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247612,Syndicated feeds of Watchlists include non-existent edits,This seems fixed now for me.,task_subcomment,['This seems fixed now for me.'],['BUG REPRODUCTION']
+247607,Syndicated feeds of Watchlists include non-existent edits,"Core should exclude RC_EXTERNAL by default for feeds or the extension has to provide a feed formatter for that row, but should also respect the setting, that external not always include in the result.
+
+You can use wltype=edit|new|log to exclude the external edits.",task_subcomment,"['Core should exclude RC_EXTERNAL by default for feeds or the extension has to provide a feed formatter for that row, but should also respect the setting, that external not always include in the result.', 'You can use wltype=edit|new|log to exclude the external edits.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247602,Syndicated feeds of Watchlists include non-existent edits,"Problem solved? This user edited d:Q3977961 (several times in a row: https://www.wikidata.org/w/index.php?title=Q3977961&diff=60842173&oldid=37167299 ). Evidently, related items from Wikidata cause these phantom changes to occur...",task_subcomment,"['Problem solved?', 'This user edited d:Q3977961 (several times in a row: URL ).', 'Evidently, related items from Wikidata cause these phantom changes to occur...']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247597,Syndicated feeds of Watchlists include non-existent edits,"For what it's worth, I just caught a live one showing up in my Special:Watchlist Atom feed and then checked against Special:RecentChanges on en.wp:
+
+At 1:23, my watchlist claims that User:Andreasmperu edited Superman (The Clique song).
+
+Here is a copy-and-paste from every edit that happened from 1:23:00 to 1:23:59:
+
+(diff | hist) . . Begusarai district‎; 01:23:59 . . (+19)‎ . . ‎101.62.52.201 (talk)‎ (→‎Education)
+(diff | hist) . . Wikipedia:WikiProject Guild of Copy Editors/Backlog elimination drives/July 2013‎; 01:23:58 . . (+59)‎ . . ‎JudyCS (talk | contribs)‎ (→‎JudyCS (talk): updated totals)
+(diff | hist) . . Kojak‎; 01:23:57 . . (+14)‎ . . ‎71.180.138.175 (talk)‎ (→‎Plot) [rollback]
+(diff | hist) . . N User:TinyURLDotComSlashMb4tstl‎; 01:23:55 . . (+27)‎ . . ‎Prolog (talk | contribs)‎ (blockedsock)
+(diff | hist) . . N! User:Djdubay/sandbox/Userbox/Project‎; 01:23:53 . . (+802)‎ . . ‎Djdubay (talk | contribs)‎ (Creating new sandbox subpage.)
+(diff | hist) . . Wikipedia:WikiProject Military history/Fortifications task force/Popular pages‎; 01:23:52 . . (-30)‎ . . ‎Mr.Z-bot (talk | contribs)‎ (Popularity stats for WikiProject Military history/Fortifications task force) [rollback]
+(diff | hist) . . User:DGG/CSD log‎; 01:23:51 . . (+166)‎ . . ‎DGG (talk | contribs)‎ (Logging speedy deletion nomination of Wikipedia talk:Articles for creation/TPRG KANGAROO BRAND. (TW])) [rollback]
+(diff | hist) . . Margareta Huitfeldt‎; 01:23:49 . . (+66)‎ . . ‎Aciram (talk | contribs)‎ (→‎References) [rollback]
+(diff | hist) . . m Stella Women’s Academy, High School Division Class C3‎; 01:23:47 . . (+20)‎ . . ‎Xezbeth (talk | contribs)‎ (Disambiguated: Rambo → Rambo (film series)) [rollback]
+(diff | hist) . . N. T. Rama Rao Jr.‎; 01:23:47 . . (-12)‎ . . ‎117.241.0.199 (talk)‎ (→‎As actor) [rollback]
+(User creation log); 01:23:45 . . User account Thundercatmd (talk | contribs) was created ‎
+(diff | hist) . . Sadabad, India‎; 01:23:45 . . (+77)‎ . . ‎117.243.196.54 (talk)‎ (→‎Education) [rollback]
+(diff | hist) . . Crestar Bank‎; 01:23:42 . . (0)‎ . . ‎173.71.136.155 (talk)‎
+(diff | hist) . . Template:Did you know nominations/Russian submarine K-18 Karelia‎; 01:23:40 . . (+350)‎ . . ‎Daniel Case (talk | contribs)‎ (dull hook) [rollback]
+(diff | hist) . . Aubrey Plaza‎; 01:23:40 . . (+46)‎ . . ‎Captain Assassin! (talk | contribs)‎ (Life After Beth) [rollback]
+(diff | hist) . . WVQS-LD‎; 01:23:39 . . (-1)‎ . . ‎142.255.235.18 (talk)‎ [rollback]
+(User creation log); 01:23:39 . . User account Reginawong71 (talk | contribs) was created ‎
+(diff | hist) . . Wikipedia:Categories for discussion/Log/2013 July 9‎; 01:23:38 . . (+312)‎ . . ‎DexDor (talk | contribs)‎ (→‎Category:Modern surface-to-air missiles: cmt) [rollback]
+(diff | hist) . . Richard Lee McNair‎; 01:23:37 . . (0)‎ . . ‎Download (talk | contribs)‎ (→‎Attempts to avoid recapture: caps)
+(diff | hist) . . Wikipedia:WikiProject Motorcycling/Popular pages‎; 01:23:36 . . (+2)‎ . . ‎Mr.Z-bot (talk | contribs)‎ (Popularity stats for WikiProject Motorcycling) [rollback]
+(diff | hist) . . User:Aghaz Tech Systems‎; 01:23:35 . . (+16)‎ . . ‎I am One of Many (talk | contribs)‎ (Requesting speedy deletion (CSD G11). (TW)) [rollback]
+(diff | hist) . . Akkineni Nageswara Rao‎; 01:23:34 . . (-12)‎ . . ‎DMacks (talk | contribs)‎ (MOS) [rollback]
+(diff | hist) . . Prince William, Duke of Cambridge‎; 01:23:33 . . (+400)‎ . . ‎71.167.157.25 (talk)‎ (→‎Royal duties: tidies) [rollback]
+(diff | hist) . . User talk:Praghadeshkar‎; 01:23:32 . . (+1,977)‎ . . ‎DGG (talk | contribs)‎ (Notification: speedy deletion nomination of Wikipedia talk:Articles for creation/TPRG KANGAROO BRAND. (TW])) [rollback]
+(diff | hist) . . N! Wikipedia:Articles for creation/RJ Sridharan‎; 01:23:32 . . (+5,171)‎ . . ‎Anandhi1212 (talk | contribs)‎ (←Created page with ''''RJ Sridharan''' Rajendram Jagannathan Sridharan, affectionately addressed as Com RJS by the Indian banking fraternity was born on April 9th, 1949. He was bor...')
+(diff | hist) . . Seoul Metropolitan Police Agency‎; 01:23:30 . . (+95)‎ . . ‎Howard61313 (talk | contribs)‎ [rollback]
+(diff | hist) . . Wikipedia talk:Articles for creation/TPRG KANGAROO BRAND‎; 01:23:30 . . (+12)‎ . . ‎DGG (talk | contribs)‎ (Requesting speedy deletion (CSD G11). (TW])) [rollback]
+(diff | hist) . . Gabrielle Union‎; 01:23:29 . . (-3)‎ . . ‎Monkelese (talk | contribs)‎ [rollback]
+(diff | hist) . . Kashmere Stage Band‎; 01:23:28 . . (-57)‎ . . ‎107.196.30.182 (talk)‎ (→‎History) [rollback]
+(Article Feedback Activity Log); 01:23:28 . . 122.178.233.254 (talk) submitted feedback post #050027e... on Dhanush ‎(i am happy to be a fan of dhanush)
+(diff | hist) . . Fahadh Faasil‎; 01:23:28 . . (+103)‎ . . ‎92.97.8.139 (talk)‎ (→‎Filmography)
+(diff | hist) . . m Waldemar Klingelhöfer‎; 01:23:24 . . (-1)‎ . . ‎Robert4565 (talk | contribs)‎ (Tag: VisualEditor) [rollback]
+(diff | hist) . . m Maiden's Tower‎; 01:23:23 . . (+3)‎ . . ‎Thewolfchild (talk | contribs)‎ (→‎Legend) [rollback]
+(diff | hist) . . Ball State University‎; 01:23:23 . . (-276)‎ . . ‎184.17.231.231 (talk)‎ (removed Points of interest section → all places are listed in Ball State navigation box and/or are mentioned throughout the article) (Tag: section blanking) [rollback]
+(diff | hist) . . m Adas Israel Congregation (Washington, D.C.)‎; 01:23:21 . . (+37)‎ . . ‎Bizzurp (talk | contribs)‎ (Category:Conservative synagogues) [rollback]
+(diff | hist) . . Wikipedia:WikiProject Arthropods/Popular pages‎; 01:23:21 . . (+12)‎ . . ‎Mr.Z-bot (talk | contribs)‎ (Popularity stats for WikiProject Arthropods) [rollback]
+(diff | hist) . . Animethon‎; 01:23:19 . . (-103)‎ . . ‎Ceasol (talk | contribs)‎ (Animethon has become largest Anime Convention with an attendance in 2012 of 6404 against Anime Revolution with 5233) (Tag: VisualEditor) [rollback]
+(diff | hist) . . Talk:Sex at Dawn‎; 01:23:17 . . (+245)‎ . . ‎NorthBySouthBaranof (talk | contribs)‎ (→‎Removal of Ellsworth's ""Sex at Dusk"" review)
+(diff | hist) . . N! User:MOTOI Kenkichi/北乃カムイ‎; 01:23:17 . . (+5,636)‎ . . ‎MOTOI Kenkichi (talk | contribs)‎ (翻訳用テンプレ)
+(diff | hist) . . m William Fulton (urban planner)‎; 01:23:16 . . (+4)‎ . . ‎Billfulton00 (talk | contribs)‎ (Tag: VisualEditor) [rollback]
+(Protection log); 01:23:16 . . Prolog (talk | contribs) protected Patient Protection and Affordable Care Act‎ ‎[edit=autoconfirmed] (expires 05:23, 30 July 2013 (UTC)) ‎[move=autoconfirmed] (expires 05:23, 30 July 2013 (UTC)) ‎(Persistent sock puppetry)
+(diff | hist) . . Barbro Eriksdotter (Bielke)‎; 01:23:14 . . (+32)‎ . . ‎Aciram (talk | contribs)‎ (→‎Sources) [rollback]
+(diff | hist) . . Ohio State Route 357‎; 01:23:14 . . (+94)‎ . . ‎CycloneIsaac (talk | contribs)‎ (→‎References: separate) [rollback]
+(diff | hist) . . Gwangju FC‎; 01:23:12 . . (+69)‎ . . ‎Z4617925 (talk | contribs)‎ (→‎Current squad) [rollback]
+(diff | hist) . . N Talk:Lavender Country‎; 01:23:12 . . (+419)‎ . . ‎Bearcat (talk | contribs)‎ (←Created page with '{{Old AfD|Lavender Country|delete}} ==Prior AFD== Please note that this version of the article is significantly expanded, and its sourcing significant...')
+(diff | hist) . . Argentine legislative election, 2013‎; 01:23:12 . . (-59)‎ . . ‎186.61.49.196 (talk)‎
+(diff | hist) . . Brian Nieves‎; 01:23:08 . . (+14)‎ . . ‎PaulinSaudi (talk | contribs)‎ (fix many capitals) [rollback]
+(diff | hist) . . SeaWorld Entertainment‎; 01:23:07 . . (+17)‎ . . ‎67.238.188.192 (talk)‎ (Tag: VisualEditor) [rollback]
+(diff | hist) . . British Expedition to Abyssinia‎; 01:23:05 . . (+7)‎ . . ‎Reenem (talk | contribs)‎ (→‎The campaign) [rollback]
+(User creation log); 01:23:04 . . User account Rblak87 (talk | contribs) was created ‎
+(diff | hist) . . Arunachal Pradesh‎; 01:23:04 . . (-1,141)‎ . . ‎BijoyChakrabarty (talk | contribs)‎ (Undid revision 565431133 by Qwyrxian (talk) Hindi is not official language in Arunachal pradesh, it's English. Official Gov cite provided) [rollback]
+(diff | hist) . . Wikipedia:WikiProject Solar System/Popular pages‎; 01:23:03 . . (-17)‎ . . ‎Mr.Z-bot (talk | contribs)‎ (Popularity stats for WikiProject Solar System) [rollback]
+(diff | hist) . . Wikipedia:Huggle/Users‎; 01:23:03 . . (+38)‎ . . ‎Czar (talk | contribs)‎ (Adding czar (HG)) [rollback]
+(User creation log); 01:23:01 . . User account Huskers3155 (talk | contribs) was created ‎
+(diff | hist) . . m Southern Cross All-Stars‎; 01:23:01 . . (+31)‎ . . ‎Loudestpenguin (talk | contribs)‎ (Tag: VisualEditor)
+(diff | hist) . . Talk:List of tallest buildings in Christchurch‎; 01:23:00 . . (+282)‎ . . ‎Grutness (talk | contribs)‎ (→‎Minimum height)",task_subcomment,"[""For what it's worth, I just caught a live one showing up in my Special:Watchlist Atom feed and then checked against Special:RecentChanges on en.wp:\n\nAt 1:23, my watchlist claims that User:Andreasmperu edited Superman (The Clique song)."", 'Here is a copy-and-paste from every edit that happened from 1:23:00 to 1:23:59:\n\n(diff | hist) .', '.', 'Begusarai district\u200e; 01:23:59 .', '.', '(+19)\u200e .', '.', '\u200e101.62.52.201 (talk)\u200e (→\u200eEducation)\n(diff | hist) .', '.', 'Wikipedia:WikiProject Guild of Copy Editors/Backlog elimination drives/July 2013\u200e; 01:23:58 .', '.', '(+59)\u200e .', '.', '\u200eJudyCS (talk | contribs)\u200e (→\u200eJudyCS (talk): updated totals)\n(diff | hist) .', '.', 'Kojak\u200e; 01:23:57 .', '.', '(+14)\u200e .', '.', '\u200e71.180.138.175 (talk)\u200e (→\u200ePlot) [rollback]\n(diff | hist) .', '.', 'N User:TinyURLDotComSlashMb4tstl\u200e; 01:23:55 .', '.', '(+27)\u200e .', '.', '\u200eProlog (talk | contribs)\u200e (blockedsock)\n(diff | hist) .', '.', 'N!', 'User:Djdubay/sandbox/Userbox/Project\u200e; 01:23:53 .', '.', '(+802)\u200e .', '.', '\u200eDjdubay (talk | contribs)\u200e (Creating new sandbox subpage.)', '(diff | hist) .', '.', 'Wikipedia:WikiProject Military history/Fortifications task force/Popular pages\u200e; 01:23:52 .', '.', '(-30)\u200e .', '.', '\u200eMr.Z-bot (talk | contribs)\u200e (Popularity stats for WikiProject Military history/Fortifications task force) [rollback]\n(diff | hist) .', '.', 'User:DGG/CSD log\u200e; 01:23:51 .', '.', '(+166)\u200e .', '.', '\u200eDGG (talk | contribs)\u200e (Logging speedy deletion nomination of Wikipedia talk:Articles for creation/TPRG KANGAROO BRAND.', '(TW])) [rollback]\n(diff | hist) .', '.', 'Margareta Huitfeldt\u200e; 01:23:49 .', '.', '(+66)\u200e .', '.', '\u200eAciram (talk | contribs)\u200e (→\u200eReferences) [rollback]\n(diff | hist) .', '.', 'm Stella Women’s Academy, High School Division Class C3\u200e; 01:23:47 .', '.', '(+20)\u200e .', '.', '\u200eXezbeth (talk | contribs)\u200e (Disambiguated: Rambo → Rambo (film series)) [rollback]\n(diff | hist) .', '.', 'N. T. Rama Rao Jr.\u200e; 01:23:47 .', '.', '(-12)\u200e .', '.', '\u200e117.241.0.199 (talk)\u200e (→\u200eAs actor) [rollback]\n(User creation log); 01:23:45 .', '.', 'User account Thundercatmd (talk | contribs) was created \u200e\n(diff | hist) .', '.', 'Sadabad, India\u200e; 01:23:45 .', '.', '(+77)\u200e .', '.', '\u200e117.243.196.54 (talk)\u200e (→\u200eEducation) [rollback]\n(diff | hist) .', '.', 'Crestar Bank\u200e; 01:23:42 .', '.', '(0)\u200e .', '.', '\u200e173.71.136.155 (talk)\u200e\n(diff | hist) .', '.', 'Template:Did you know nominations/Russian submarine K-18 Karelia\u200e; 01:23:40 .', '.', '(+350)\u200e .', '.', '\u200eDaniel Case (talk | contribs)\u200e (dull hook) [rollback]\n(diff | hist) .', '.', 'Aubrey Plaza\u200e; 01:23:40 .', '.', '(+46)\u200e .', '.', '\u200eCaptain Assassin!', '(talk | contribs)\u200e (Life After Beth) [rollback]\n(diff | hist) .', '.', 'WVQS-LD\u200e; 01:23:39 .', '.', '(-1)\u200e .', '.', '\u200e142.255.235.18 (talk)\u200e [rollback]\n(User creation log); 01:23:39 .', '.', 'User account Reginawong71 (talk | contribs) was created \u200e\n(diff | hist) .', '.', 'Wikipedia:Categories for discussion/Log/2013 July 9\u200e; 01:23:38 .', '.', '(+312)\u200e .', '.', '\u200eDexDor (talk | contribs)\u200e (→\u200eCategory:Modern surface-to-air missiles: cmt) [rollback]\n(diff | hist) .', '.', 'Richard Lee McNair\u200e; 01:23:37 .', '.', '(0)\u200e .', '.', '\u200eDownload (talk | contribs)\u200e (→\u200eAttempts to avoid recapture: caps)\n(diff | hist) .', '.', 'Wikipedia:WikiProject Motorcycling/Popular pages\u200e; 01:23:36 .', '.', '(+2)\u200e .', '.', '\u200eMr.Z-bot (talk | contribs)\u200e (Popularity stats for WikiProject Motorcycling) [rollback]\n(diff | hist) .', '.', 'User:Aghaz Tech Systems\u200e; 01:23:35 .', '.', '(+16)\u200e .', '.', '\u200eI am One of Many (talk | contribs)\u200e (Requesting speedy deletion (CSD G11).', '(TW)) [rollback]\n(diff | hist) .', '.', 'Akkineni Nageswara Rao\u200e; 01:23:34 .', '.', '(-12)\u200e .', '.', '\u200eDMacks (talk | contribs)\u200e (MOS) [rollback]\n(diff | hist) .', '.', 'Prince William, Duke of Cambridge\u200e; 01:23:33 .', '.', '(+400)\u200e .', '.', '\u200e71.167.157.25 (talk)\u200e (→\u200eRoyal duties: tidies) [rollback]\n(diff | hist) .', '.', 'User talk:Praghadeshkar\u200e; 01:23:32 .', '.', '(+1,977)\u200e .', '.', '\u200eDGG (talk | contribs)\u200e (Notification: speedy deletion nomination of Wikipedia talk:Articles for creation/TPRG KANGAROO BRAND.', '(TW])) [rollback]\n(diff | hist) .', '.', 'N!', 'Wikipedia:Articles for creation/RJ Sridharan\u200e; 01:23:32 .', '.', '(+5,171)\u200e .', '.', ""\u200eAnandhi1212 (talk | contribs)\u200e (←Created page with ''''RJ Sridharan''' Rajendram Jagannathan Sridharan, affectionately addressed as Com RJS by the Indian banking fraternity was born on April 9th, 1949."", ""He was bor...')\n(diff | hist) ."", '.', 'Seoul Metropolitan Police Agency\u200e; 01:23:30 .', '.', '(+95)\u200e .', '.', '\u200eHoward61313 (talk | contribs)\u200e [rollback]\n(diff | hist) .', '.', 'Wikipedia talk:Articles for creation/TPRG KANGAROO BRAND\u200e; 01:23:30 .', '.', '(+12)\u200e .', '.', '\u200eDGG (talk | contribs)\u200e (Requesting speedy deletion (CSD G11).', '(TW])) [rollback]\n(diff | hist) .', '.', 'Gabrielle Union\u200e; 01:23:29 .', '.', '(-3)\u200e .', '.', '\u200eMonkelese (talk | contribs)\u200e [rollback]\n(diff | hist) .', '.', 'Kashmere Stage Band\u200e; 01:23:28 .', '.', '(-57)\u200e .', '.', '\u200e107.196.30.182 (talk)\u200e (→\u200eHistory) [rollback]\n(Article Feedback Activity Log); 01:23:28 .', '.', '122.178.233.254 (talk) submitted feedback post #050027e... on Dhanush \u200e(i am happy to be a fan of dhanush)\n(diff | hist) .', '.', 'Fahadh Faasil\u200e; 01:23:28 .', '.', '(+103)\u200e .', '.', '\u200e92.97.8.139 (talk)\u200e (→\u200eFilmography)\n(diff | hist) .', '.', 'm Waldemar Klingelhöfer\u200e; 01:23:24 .', '.', '(-1)\u200e .', '.', '\u200eRobert4565 (talk | contribs)\u200e (Tag: VisualEditor) [rollback]\n(diff | hist) .', '.', ""m Maiden's Tower\u200e; 01:23:23 ."", '.', '(+3)\u200e .', '.', '\u200eThewolfchild (talk | contribs)\u200e (→\u200eLegend) [rollback]\n(diff | hist) .', '.', 'Ball State University\u200e; 01:23:23 .', '.', '(-276)\u200e .', '.', '\u200e184.17.231.231 (talk)\u200e (removed Points of interest section → all places are listed in Ball State navigation box and/or are mentioned throughout the article) (Tag: section blanking) [rollback]\n(diff | hist) .', '.', 'm Adas Israel Congregation (Washington, D.C.)\u200e; 01:23:21 .', '.', '(+37)\u200e .', '.', '\u200eBizzurp (talk | contribs)\u200e (Category:Conservative synagogues) [rollback]\n(diff | hist) .', '.', 'Wikipedia:WikiProject Arthropods/Popular pages\u200e; 01:23:21 .', '.', '(+12)\u200e .', '.', '\u200eMr.Z-bot (talk | contribs)\u200e (Popularity stats for WikiProject Arthropods) [rollback]\n(diff | hist) .', '.', 'Animethon\u200e; 01:23:19 .', '.', '(-103)\u200e .', '.', '\u200eCeasol (talk | contribs)\u200e (Animethon has become largest Anime Convention with an attendance in 2012 of 6404 against Anime Revolution with 5233) (Tag: VisualEditor) [rollback]\n(diff | hist) .', '.', 'Talk:Sex at Dawn\u200e; 01:23:17 .', '.', '(+245)\u200e .', '.', '\u200eNorthBySouthBaranof (talk | contribs)\u200e (→\u200eRemoval of Ellsworth\'s ""Sex at Dusk"" review)\n(diff | hist) .', '.', 'N!', 'User:MOTOI Kenkichi/北乃カムイ\u200e; 01:23:17 .', '.', '(+5,636)\u200e .', '.', '\u200eMOTOI Kenkichi (talk | contribs)\u200e (翻訳用テンプレ)\n(diff | hist) .', '.', 'm William Fulton (urban planner)\u200e; 01:23:16 .', '.', '(+4)\u200e .', '.', '\u200eBillfulton00 (talk | contribs)\u200e (Tag: VisualEditor) [rollback]\n(Protection log); 01:23:16 .', '.', 'Prolog (talk | contribs) protected Patient Protection and Affordable Care Act\u200e \u200e[edit=autoconfirmed] (expires 05:23, 30 July 2013 (UTC)) \u200e[move=autoconfirmed] (expires 05:23, 30 July 2013 (UTC)) \u200e(Persistent sock puppetry)\n(diff | hist) .', '.', 'Barbro Eriksdotter (Bielke)\u200e; 01:23:14 .', '.', '(+32)\u200e .', '.', '\u200eAciram (talk | contribs)\u200e (→\u200eSources) [rollback]\n(diff | hist) .', '.', 'Ohio State Route 357\u200e; 01:23:14 .', '.', '(+94)\u200e .', '.', '\u200eCycloneIsaac (talk | contribs)\u200e (→\u200eReferences: separate) [rollback]\n(diff | hist) .', '.', 'Gwangju FC\u200e; 01:23:12 .', '.', '(+69)\u200e .', '.', '\u200eZ4617925 (talk | contribs)\u200e (→\u200eCurrent squad) [rollback]\n(diff | hist) .', '.', 'N Talk:Lavender Country\u200e; 01:23:12 .', '.', '(+419)\u200e .', '.', ""\u200eBearcat (talk | contribs)\u200e (←Created page with '{{Old AfD|Lavender Country|delete}} ==Prior AFD== Please note that this version of the article is significantly expanded, and its sourcing significant...')\n(diff | hist) ."", '.', 'Argentine legislative election, 2013\u200e; 01:23:12 .', '.', '(-59)\u200e .', '.', '\u200e186.61.49.196 (talk)\u200e\n(diff | hist) .', '.', 'Brian Nieves\u200e; 01:23:08 .', '.', '(+14)\u200e .', '.', '\u200ePaulinSaudi (talk | contribs)\u200e (fix many capitals) [rollback]\n(diff | hist) .', '.', 'SeaWorld Entertainment\u200e; 01:23:07 .', '.', '(+17)\u200e .', '.', '\u200e67.238.188.192 (talk)\u200e (Tag: VisualEditor) [rollback]\n(diff | hist) .', '.', 'British Expedition to Abyssinia\u200e; 01:23:05 .', '.', '(+7)\u200e .', '.', '\u200eReenem (talk | contribs)\u200e (→\u200eThe campaign) [rollback]\n(User creation log); 01:23:04 .', '.', 'User account Rblak87 (talk | contribs) was created \u200e\n(diff | hist) .', '.', 'Arunachal Pradesh\u200e; 01:23:04 .', '.', '(-1,141)\u200e .', '.', ""\u200eBijoyChakrabarty (talk | contribs)\u200e (Undid revision 565431133 by Qwyrxian (talk) Hindi is not official language in Arunachal pradesh, it's English."", 'Official Gov cite provided) [rollback]\n(diff | hist) .', '.', 'Wikipedia:WikiProject Solar System/Popular pages\u200e; 01:23:03 .', '.', '(-17)\u200e .', '.', '\u200eMr.Z-bot (talk | contribs)\u200e (Popularity stats for WikiProject Solar System) [rollback]\n(diff | hist) .', '.', 'Wikipedia:Huggle/Users\u200e; 01:23:03 .', '.', '(+38)\u200e .', '.', '\u200eCzar (talk | contribs)\u200e (Adding czar (HG)) [rollback]\n(User creation log); 01:23:01 .', '.', 'User account Huskers3155 (talk | contribs) was created \u200e\n(diff | hist) .', '.', 'm Southern Cross All-Stars\u200e; 01:23:01 .', '.', '(+31)\u200e .', '.', '\u200eLoudestpenguin (talk | contribs)\u200e (Tag: VisualEditor)\n(diff | hist) .', '.', 'Talk:List of tallest buildings in Christchurch\u200e; 01:23:00 .', '.', '(+282)\u200e .', '.', '\u200eGrutness (talk | contribs)\u200e (→\u200eMinimum height)']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ISSUE CONTENT MANAGEMENT', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ISSUE CONTENT MANAGEMENT', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247591,Syndicated feeds of Watchlists include non-existent edits,"Recent changes for this article (according to toolserver.org):
+
+mysql> select * from recentchanges where rc_namespace = 0 and rc_title = 'Everything_That_Happens_Will_Happen_Today' order by rc_id desc limit 2 \G
+*************************** 1. row ***************************
+        rc_id: 590682778
+ rc_timestamp: 20130715213627
+  rc_cur_time: 20130715213627
+      rc_user: 0
+ rc_user_text: FelGru
+ rc_namespace: 0
+     rc_title: Everything_That_Happens_Will_Happen_Today
+   rc_comment: 
+     rc_minor: 1
+       rc_bot: 0
+       rc_new: 0
+    rc_cur_id: 18622850
+rc_this_oldid: 562841657
+rc_last_oldid: 562841657
+      rc_type: 5
+ rc_patrolled: 1
+   rc_old_len: 131636
+   rc_new_len: 131636
+   rc_deleted: 0
+     rc_logid: 0
+  rc_log_type: NULL
+rc_log_action: 
+        rc_ip: 
+    rc_params: a:1:{s:20:""wikibase-repo-change"";a:13:{s:2:""id"";i:56980275;s:4:""type"";s:20:""wikibase-item~update"";s:4:""time"";s:14:""20130715213627"";s:9:""object_id"";s:5:""q6336"";s:7:""user_id"";i:180688;s:11:""revision_id"";i:58328008;s:11:""entity_type"";s:4:""item"";s:9:""user_text"";s:6:""FelGru"";s:3:""bot"";i:0;s:7:""page_id"";i:7449;s:6:""rev_id"";i:58328008;s:9:""parent_id"";i:58327906;s:7:""comment"";s:23:""wikibase-comment-update"";}}
+*************************** 2. row ***************************
+        rc_id: 588688216
+ rc_timestamp: 20130704145433
+  rc_cur_time: 20130704145433
+      rc_user: 205121
+ rc_user_text: Koavf
+ rc_namespace: 0
+     rc_title: Everything_That_Happens_Will_Happen_Today
+   rc_comment: fmt
+     rc_minor: 1
+       rc_bot: 0
+       rc_new: 0
+    rc_cur_id: 18622850
+rc_this_oldid: 562841657
+rc_last_oldid: 562815320
+      rc_type: 0
+ rc_patrolled: 0
+   rc_old_len: 131440
+   rc_new_len: 131636
+   rc_deleted: 0
+     rc_logid: 0
+  rc_log_type: NULL
+rc_log_action: 
+        rc_ip: 
+    rc_params:",task_subcomment,"['Recent changes for this article (according to toolserver.org):\n\nmysql> select * from recentchanges where rc_namespace = 0 and rc_title = \'Everything_That_Happens_Will_Happen_Today\' order by rc_id desc limit 2 \\G\n*************************** 1. row ***************************\n        rc_id: 590682778\n rc_timestamp: 20130715213627\n  rc_cur_time: 20130715213627\n      rc_user: 0\n rc_user_text: FelGru\n rc_namespace: 0\n     rc_title: Everything_That_Happens_Will_Happen_Today\n   rc_comment: \n     rc_minor: 1\n       rc_bot: 0\n       rc_new: 0\n    rc_cur_id: 18622850\nrc_this_oldid: 562841657\nrc_last_oldid: 562841657\n      rc_type: 5\n rc_patrolled: 1\n   rc_old_len: 131636\n   rc_new_len: 131636\n   rc_deleted: 0\n     rc_logid: 0\n  rc_log_type: NULL\nrc_log_action: \n        rc_ip: \n    rc_params: a:1:{s:20:""wikibase-repo-change"";a:13:{s:2:""id"";i:56980275;s:4:""type"";s:20:""wikibase-item~update"";s:4:""time"";s:14:""20130715213627"";s:9:""object_id"";s:5:""q6336"";s:7:""user_id"";i:180688;s:11:""revision_id"";i:58328008;s:11:""entity_type"";s:4:""item"";s:9:""user_text"";s:6:""FelGru"";s:3:""bot"";i:0;s:7:""page_id"";i:7449;s:6:""rev_id"";i:58328008;s:9:""parent_id"";i:58327906;s:7:""comment"";s:23:""wikibase-comment-update"";}}\n*************************** 2. row ***************************\n        rc_id: 588688216\n rc_timestamp: 20130704145433\n  rc_cur_time: 20130704145433\n      rc_user: 205121\n rc_user_text: Koavf\n rc_namespace: 0\n     rc_title: Everything_That_Happens_Will_Happen_Today\n   rc_comment: fmt\n     rc_minor: 1\n       rc_bot: 0\n       rc_new: 0\n    rc_cur_id: 18622850\nrc_this_oldid: 562841657\nrc_last_oldid: 562815320\n      rc_type: 0\n rc_patrolled: 0\n   rc_old_len: 131440\n   rc_new_len: 131636\n   rc_deleted: 0\n     rc_logid: 0\n  rc_log_type: NULL\nrc_log_action: \n        rc_ip: \n    rc_params:']",['BUG REPRODUCTION']
+247586,Syndicated feeds of Watchlists include non-existent edits,"Also, checking https://en.wikipedia.org/wiki/Special:Watchlist does not display these non-existent edits nor does the page history of the individual articles and categories mentioned.",task_subcomment,"['Also, checking URL does not display these non-existent edits nor does the page history of the individual articles and categories mentioned.']",['OBSERVED BUG BEHAVIOR']
+53422,Adding formatting to wiki link formats text not link,"See http://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=564459649#Italicizing_wikilinks
+
+When someone italicizes (or bolds) a wiki link instead of placing quote marks around the link itself (like ''[[link]]'' ) it pipes a link with the same text but with quotes (for example [[link|''link'']] ) creating unneeded wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Adding formatting to wiki link formats text not link\n\nSee URL\n\nWhen someone italicizes (or bolds) a wiki link instead of placing quote marks around the link itself (like ''[[link]]'' ) it pipes a link with the same text but with quotes (for example [[link|''link'']] ) creating unneeded wikitext."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+247312,Adding formatting to wiki link formats text not link,"This is the same as bug 50098, yes; merging.
+
+(In reply to comment #1)
+> It has been noted today that VE still has issues with large pages, so it
+> really
+> shouldn't be adding unnecessary bytes to a page like this.
+
+The length of a page's wikitext has no direct impact on VisualEditor's performance; it's the length and complexity of the HTML that's in question. In this case, the HTML is identical, so this has no performance impact.
+
+*** This bug has been marked as a duplicate of bug 50098 ***",task_subcomment,"['This is the same as bug 50098, yes; merging.', ""(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\n\nThe length of a page's wikitext has no direct impact on VisualEditor's performance; it's the length and complexity of the HTML that's in question."", 'In this case, the HTML is identical, so this has no performance impact.', '*** This bug has been marked as a duplicate of bug 50098 ***']","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+247304,Adding formatting to wiki link formats text not link,"As I wrote in 50098, to avoid [[Foo|''Bar'']] you should italicize first, and link only after
+that. I added this to the Italian User guide and I am looking for other similar tips I might be missing.
+Thanks.",task_subcomment,"[""As I wrote in 50098, to avoid [[Foo|''Bar'']] you should italicize first, and link only after\nthat."", 'I added this to the Italian User guide and I am looking for other similar tips I might be missing.', 'Thanks.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+247295,Adding formatting to wiki link formats text not link,"It has been noted today that VE still has issues with large pages, so it really shouldn't be adding unnecessary bytes to a page like this.",task_subcomment,"[""It has been noted today that VE still has issues with large pages, so it really shouldn't be adding unnecessary bytes to a page like this.""]",['OBSERVED BUG BEHAVIOR']
+53417,Blanking last section of page corrupts heading,"Reported here: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=564438586&oldid=564436653
+
+IP editor removes contents from last section of page.  VE replaces heading text with nowiki.
+
+Diff:https://en.wikipedia.org/w/index.php?title=Best:_The_Greatest_Hits_of_S_Club_7&curid=3428260&diff=564438205&oldid=564438086
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Blanking last section of page corrupts heading\n\nReported here: URL\n\nIP editor removes contents from last section of page.', 'VE replaces heading text with nowiki.', 'Diff:URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246916,Blanking last section of page corrupts heading,"
+
+%%%*** This bug has been marked as a duplicate of bug 50100 ***%%%",task_subcomment,['\n\n%%%*** This bug has been marked as a duplicate of bug 50100 ***%%%'],['ACTION ON ISSUE']
+53409,color picker,"Copied from English language Wikipedia:
+
+When the user edits for example, a {{Legend}} template, color picker may be very useful. We should also think about adding there a table of basic colors. --Rezonansowy (talk) 13:32, 15 July 2013 (UTC)
+
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564427033#Color_picker
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['color picker\n\nCopied from English language Wikipedia:\n\nWhen the user edits for example, a {{Legend}} template, color picker may be very useful.', 'We should also think about adding there a table of basic colors.', '--Rezonansowy (talk) 13:32, 15 July 2013 (UTC)\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+246442,color picker,"
+
+*** This bug has been marked as a duplicate of bug 52645 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 52645 ***'],['ACTION ON ISSUE']
+53389,Disabling VisualEditor completely,"How can we Disable VisualEditor completely to have old style (for example in en.wikipedia which is activated how can we disable completely the too and make it like old style)?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Disabling VisualEditor completely\n\nHow can we Disable VisualEditor completely to have old style (for example in en.wikipedia which is activated how can we disable completely the too and make it like old style)?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+245136,Disabling VisualEditor completely,"In general, VE questions should be filed on [[WP:VE/F]] as that is the best place to give feedback for the VisualEditor.
+
+This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.
+
+*** This bug has been marked as a duplicate of bug 50929 ***",task_subcomment,"['In general, VE questions should be filed on [[WP:VE/F]] as that is the best place to give feedback for the VisualEditor.', 'This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.', '*** This bug has been marked as a duplicate of bug 50929 ***']","['FUTURE PLAN', 'ISSUE CONTENT MANAGEMENT', 'OBSERVED BUG BEHAVIOR']"
+53369,VisualEditor: spurious parentheses added,"See https://en.wikipedia.org/w/index.php?title=Wormshill&diff=564367057&oldid=557770558 for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: spurious parentheses added\n\nSee URL for example.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244045,VisualEditor: spurious parentheses added,"This is caused by an unbalanced 
     in the infobox, which ""works"" (ish) in MediaWiki's PHP parser but didn't in Parsoid at the time; this is subsequently worked around. Closing as WORKSFORME.",task_subcomment,"['This is caused by an unbalanced 
     in the infobox, which ""works"" (ish) in MediaWiki\'s PHP parser but didn\'t in Parsoid at the time; this is subsequently worked around.', 'Closing as WORKSFORME.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+53366,504 timeout with Parsoid service,"**Author:** `brunsa2`
+
+**Description:**
+I currently have VisualEditor running on an Ubuntu Server with Nginx, MediaWiki version 1.22alpha, Node.js 0.8.22. I get timeouts (504) when trying to use the VisualEditor (running Parsoid in debug often gives messages such as:
+
+T:html: {""type"":""TagTk"",""name"":""body"",""attribs"":[],""dataAttribs"":{}} {
+ ""0"": ""WARNING: RETRY:"",
+ ""1"": {
+   ""code"": ""ETIMEDOUT""
+ }
+} Retrying Page Fetch request for null, 4 remaining {
+ ""0"": ""WARNING: RETRY:"",
+ ""1"": {
+   ""code"": ""ETIMEDOUT""
+ }
+}
+
+Retrying Page Fetch request for null, 3 remaining ). I've tried with as many possible headers from a REST client and do not get any errors from Parsoid with that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC
+**Whiteboard**: aklapper-moreinfo",task_description,"['504 timeout with Parsoid service\n\n**Author:** CODE\n\n**Description:**\nI currently have VisualEditor running on an Ubuntu Server with Nginx, MediaWiki version 1.22alpha, Node.js 0.8.22.', 'I get timeouts (504) when trying to use the VisualEditor (running Parsoid in debug often gives messages such as:\n\nT:html: {""type"":""TagTk"",""name"":""body"",""attribs"":[],""dataAttribs"":{}} {\n ""0"": ""WARNING: RETRY:"",\n ""1"": {\n   ""code"": ""ETIMEDOUT""\n }\n} Retrying Page Fetch request for null, 4 remaining {\n ""0"": ""WARNING: RETRY:"",\n ""1"": {\n   ""code"": ""ETIMEDOUT""\n }\n}\n\nRetrying Page Fetch request for null, 3 remaining ).', ""I've tried with as many possible headers from a REST client and do not get any errors from Parsoid with that."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**Whiteboard**: aklapper-moreinfo']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243919,504 timeout with Parsoid service,"**brunsa2** wrote:
+
+I've upgrades both VisualEditor and Parsoid, after converting wiki installation to  use SSL and then turning it off, Parsoid spontaneously started working.",task_subcomment,"[""**brunsa2** wrote:\n\nI've upgrades both VisualEditor and Parsoid, after converting wiki installation to  use SSL and then turning it off, Parsoid spontaneously started working.""]",['INVESTIGATION AND EXPLORATION']
+243915,504 timeout with Parsoid service,See http://www.mediawiki.org/wiki/MediaWiki_on_IRC for information on IRC.,task_subcomment,['See URL for information on IRC.'],['ACTION ON ISSUE']
+243910,504 timeout with Parsoid service,Please come on #mediawiki-parsoid IRC channel to debug these issues.  It appears that Parsoid might be having trouble connecting with your mediawiki instance.,task_subcomment,"['Please come on #mediawiki-parsoid IRC channel to debug these issues.', 'It appears that Parsoid might be having trouble connecting with your mediawiki instance.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+53364,VisualEditor: Edit this Page button ignores &oldid=prev parameter.,"When editing a page the editor seems to ignore the ""&oldid=prev"" parameter entirely. Instead of editing the old revision, the editor loads the most recent revision.
+
+Steps to reproduce:
+
+* Navigate to http://en.wikipedia.org/w/index.php?title=Baylor_University_Institute_for_Oral_History&diff=540967084&oldid=prev
+* Press ""Edit this Page""
+
+I would except that the editor would load the page currently displayed on the screen. Instead it seems to omit &oldid=prev entirely, and loads the most recent revision instead. 
+
+(Tested on Firefox 22, Monobook skin. Possibly related:50615)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Edit this Page button ignores &oldid=prev parameter.', 'When editing a page the editor seems to ignore the ""&oldid=prev"" parameter entirely.', 'Instead of editing the old revision, the editor loads the most recent revision.', 'Steps to reproduce:\n\n* Navigate to URL\n* Press ""Edit this Page""\n\nI would except that the editor would load the page currently displayed on the screen.', 'Instead it seems to omit &oldid=prev entirely, and loads the most recent revision instead.', '(Tested on Firefox 22, Monobook skin.', 'Possibly related:50615)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243826,VisualEditor: Edit this Page button ignores &oldid=prev parameter.,This seems to now be fixed. Please re-open if you think I'm wrong!,task_subcomment,"['This seems to now be fixed.', ""Please re-open if you think I'm wrong!""]","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+243821,VisualEditor: Edit this Page button ignores &oldid=prev parameter.,"Preference 'Do not show page content below diffs' also affects this bug.
+
+If enabled, the 'Edit source' link currently edits the current version of the page, so I think 'Edit' is doing the right thing in that case.
+
+If disabled, the diff block on the page should be deleted and the html on the page should be editable as-is.",task_subcomment,"[""Preference 'Do not show page content below diffs' also affects this bug."", ""If enabled, the 'Edit source' link currently edits the current version of the page, so I think 'Edit' is doing the right thing in that case."", 'If disabled, the diff block on the page should be deleted and the html on the page should be editable as-is.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+53356,Add ULS language setting dialogue box in VisualEditor page settings,"Hi,
+
+In VisualEditor pagesettings>>languages below MediaWiki:Visualeditor-dialog-meta-languages-section the option button should be available 'Visit ULS language settings' for current {{contentlanguage}}wiki >> Then dialog box of ULS language settings should open up
+
+
+*To understand further the need for above request,please do refer to survey
+data and analysis provided at
+http://www.mediawiki.org/wiki/Talk:Universal_Language_Selector#feature_to_make_content_language_input__default_28864
+
+	
+
+Thanks and Warm Regards
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""Add ULS language setting dialogue box in VisualEditor page settings\n\nHi,\n\nIn VisualEditor pagesettings>>languages below MediaWiki:Visualeditor-dialog-meta-languages-section the option button should be available 'Visit ULS language settings' for current {{contentlanguage}}wiki >> Then dialog box of ULS language settings should open up\n\n\n*To understand further the need for above request,please do refer to survey\ndata and analysis provided at\nURL\n\n\t\n\nThanks and Warm Regards\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement""]",['SOLUTION DISCUSSION']
+243369,Add ULS language setting dialogue box in VisualEditor page settings,"Closing as invalid for now. I think what is implicit here, is present explicitly in other, unreferenced issues.",task_subcomment,"['Closing as invalid for now.', 'I think what is implicit here, is present explicitly in other, unreferenced issues.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+243363,Add ULS language setting dialogue box in VisualEditor page settings,"(In reply to comment #5)
+
+What Mr. Amir discussing higher end facilities are welcome.
+
+As far as this bug is concrned simply this bug intends/requests for basic feature requirement provide ULS input method selection at VE tool bar. sans any icons . As of now ULS icons have not been understood by 60% of targeted new user group.VE tool bar is right in front of eyes I can select every thing including intended language input from VE tool bar itself before I start editing, this I am looking for . Am I asking for some thing too much and too defficult ?",task_subcomment,"['(In reply to comment #5)\n\nWhat Mr. Amir discussing higher end facilities are welcome.', 'As far as this bug is concrned simply this bug intends/requests for basic feature requirement provide ULS input method selection at VE tool bar.', 'sans any icons .', 'As of now ULS icons have not been understood by 60% of targeted new user group.VE tool bar is right in front of eyes I can select every thing including intended language input from VE tool bar itself before I start editing, this I am looking for .', 'Am I asking for some thing too much and too defficult ?']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION']"
+243356,Add ULS language setting dialogue box in VisualEditor page settings,Mahitgar: Could you please answer comment 5?,task_subcomment,['Mahitgar: Could you please answer comment 5?'],['ACTION ON ISSUE']
+243350,Add ULS language setting dialogue box in VisualEditor page settings,"ULS is a flexible tool for selecting a language out of a long list of possible languages. It may or may not be relevant for this request.
+
+The ULS may be used in the future for switching to Wikipedia in another language; I refer to the thing that is done today with the interlanguage links.
+
+Setting a different content language for a whole page is a useful feature, and the ULS can be used for selecting the language there, but first the MediaWiki core must support it; see Bug 9360. It is also mentioned in the i18n specification for VE: https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .
+
+To summarize: Mahitgar, can you please write *what* are you asking to do? ULS may or may not be the a good *way* to do it, but first the actual feature must be defined. I tried to read the the thread, and I didn't quite understand the requirement.",task_subcomment,"['ULS is a flexible tool for selecting a language out of a long list of possible languages.', 'It may or may not be relevant for this request.', 'The ULS may be used in the future for switching to Wikipedia in another language; I refer to the thing that is done today with the interlanguage links.', 'Setting a different content language for a whole page is a useful feature, and the ULS can be used for selecting the language there, but first the MediaWiki core must support it; see Bug 9360.', 'It is also mentioned in the i18n specification for VE: URL .', 'To summarize: Mahitgar, can you please write *what* are you asking to do?', 'ULS may or may not be the a good *way* to do it, but first the actual feature must be defined.', ""I tried to read the the thread, and I didn't quite understand the requirement.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+243343,Add ULS language setting dialogue box in VisualEditor page settings,Im not sure this is desirable or not; adding people and tracking to help sort that out.  Is runa@wikimedia.org on bugzilla yet?,task_subcomment,"['Im not sure this is desirable or not; adding people and tracking to help sort that out.', 'Is runa@wikimedia.org on bugzilla yet?']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+243339,Add ULS language setting dialogue box in VisualEditor page settings,So far this report does not explain which problem you would like to solve by this.,task_subcomment,['So far this report does not explain which problem you would like to solve by this.'],['OBSERVED BUG BEHAVIOR']
+243335,Add ULS language setting dialogue box in VisualEditor page settings,"Created attachment 12858
+Request for ULS language settings in VE page settings-languages
+
+Request for ULS language settings link in VE page settings-languages .When clicked should open up ULS dialogue box for language settings
+
+**Attached**: {F11465}",task_subcomment,['Created attachment 12858\nRequest for ULS language settings in VE page settings-languages\n\nRequest for ULS language settings link in VE page settings-languages .When clicked should open up ULS dialogue box for language settings\n\n**Attached**: {F11465}'],['REQUEST FOR FEATURE']
+243329,Add ULS language setting dialogue box in VisualEditor page settings,"(In reply to comment #0)
+> In VisualEditor pagesettings>>languages below
+> MediaWiki:Visualeditor-dialog-meta-languages-section the option button should
+> be available 'Visit ULS language settings' for current
+> {{contentlanguage}}wiki
+> >> Then dialog box of ULS language settings should open up
+
+Please provide a screenshot of the current problem that you would like to
+solve, plus a link to reproduce. 
+Also see https://www.mediawiki.org/wiki/How_to_report_a_bug
+
+> 
+> *To understand further the need for above request,please do refer to survey
+> data and analysis provided at
+> http://www.mediawiki.org/wiki/Talk:
+> Universal_Language_Selector#feature_to_make_content_language_input__default_2
+> 8864
+
+Please summarize the points made there instead of making me read a long thread.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nPlease provide a screenshot of the current problem that you would like to\nsolve, plus a link to reproduce.', 'Also see URL\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nPlease summarize the points made there instead of making me read a long thread.']","['MOTIVATION', 'ACTION ON ISSUE']"
+53354,ULS input options visibility in VE with a drop down menu,"All wikis,other than english wikipedia ULS input options for input should be availabe as dropdown menu on VisualEditor toolbar [[:File:VisualEditor.toolbar.png]] just below the page settings [[File:VisualEditor - Toolbar - Page settings.png|80px]] with sign [[File:WMF-Agora-Input settings-000000.svg]] + enable input methods/'select input method'/name of current selected input method as heading.  
+
+
+
+*To understand further the need for above request,please do refer to survey
+data and analysis provided at
+http://www.mediawiki.org/wiki/Talk:Universal_Language_Selector#feature_to_make_content_language_input__default_28864 
+
+
+Thanks and Warm Regards
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""ULS input options visibility in VE with a drop down menu\n\nAll wikis,other than english wikipedia ULS input options for input should be availabe as dropdown menu on VisualEditor toolbar [[:File:VisualEditor.toolbar.png]] just below the page settings [[File:VisualEditor - Toolbar - Page settings.png|80px]] with sign [[File:WMF-Agora-Input settings-000000.svg]] + enable input methods/'select input method'/name of current selected input method as heading."", '*To understand further the need for above request,please do refer to survey\ndata and analysis provided at\nURL \n\n\nThanks and Warm Regards\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'FUTURE PLAN']"
+243199,ULS input options visibility in VE with a drop down menu,"Hi Mahitgar. Thanks for taking the time to report this!
+This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.
+
+*** This bug has been marked as a duplicate of bug 49569 ***",task_subcomment,"['Hi Mahitgar.', 'Thanks for taking the time to report this!', 'This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.', '*** This bug has been marked as a duplicate of bug 49569 ***']","['INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE', 'ISSUE CONTENT MANAGEMENT', 'OBSERVED BUG BEHAVIOR']"
+243194,ULS input options visibility in VE with a drop down menu,"Created attachment 12855
+Example Needed ULS input method dropdown menu at VisualEditor.toolbar
+
+**Attached**: {F11453}",task_subcomment,['Created attachment 12855\nExample Needed ULS input method dropdown menu at VisualEditor.toolbar\n\n**Attached**: {F11453}'],['INVESTIGATION AND EXPLORATION']
+243191,ULS input options visibility in VE with a drop down menu,"(In reply to comment #0)
+> All wikis,other than english wikipedia ULS input options for input should be
+> availabe as dropdown menu on VisualEditor toolbar
+> [[:File:VisualEditor.toolbar.png]] just below the page settings
+> [[File:VisualEditor - Toolbar - Page settings.png|80px]] with sign
+> [[File:WMF-Agora-Input settings-000000.svg]] + enable input methods/'select
+> input method'/name of current selected input method as heading.  
+
+It is unclear to me what is requested here. Could you please provide steps to reproduce as a numbered list, click by click, plus the current outcome, and the outcome that you expect?
+Also see https://www.mediawiki.org/wiki/How_to_report_a_bug
+
+> *To understand further the need for above request,please do refer to survey
+> data and analysis provided at
+> http://www.mediawiki.org/wiki/Talk:
+> Universal_Language_Selector#feature_to_make_content_language_input__default_2
+> 8864 
+
+Please summarize the points made there instead of making me read a long thread.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIt is unclear to me what is requested here.', 'Could you please provide steps to reproduce as a numbered list, click by click, plus the current outcome, and the outcome that you expect?', 'Also see URL\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nPlease summarize the points made there instead of making me read a long thread.']","['ACTION ON ISSUE', 'BUG REPRODUCTION', 'SOLUTION USAGE']"
+53343,VisualEditor: Automatically add title of the section to edit summary,"It would be very usefull if VE added the title of the section automatically to the edit summary, if the user only changed contents in one section. This is not the same request as bug 48429, the section should be added even if the user edited the whole page, but only changed contents of one section.
+
+Rationale: The automatic section in the summary is very usefull if you check edits of other users. Two examples:
+
+1. A user adds a new external link (without summary). Without the section you have to look at the diff, but if the edit summary contained a /* External links */ you can guess what the user did even without summary.
+
+2. You want to find the user who added the image to section ""Foo"". Even if there are summaries like ""+image"" this doesn't help you much, but the summary /* Foo */ +image does help you. The section is also usefull if no additional summary is given, in the worst case you have to look at all changes to the whole article and to the section ""Foo"" to find the author.
+
+Pseudo-algorithm:
+
+1. Find the position of the first and the last change in the new text (i.e. find the common initial and final strings in the old and the new text).
+2. Find the first headline above the last change (a line that starts with that character or before it and matches the pattern for headlines).
+3. If this headline is before the first change, you found the section.
+4. Else look for the next headline before it of higher level.
+5. If there is such a headline, go to step 3, else more than one section was changed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Automatically add title of the section to edit summary\n\nIt would be very usefull if VE added the title of the section automatically to the edit summary, if the user only changed contents in one section.', 'This is not the same request as bug 48429, the section should be added even if the user edited the whole page, but only changed contents of one section.', 'Rationale: The automatic section in the summary is very usefull if you check edits of other users.', 'Two examples:\n\n1.', 'A user adds a new external link (without summary).', 'Without the section you have to look at the diff, but if the edit summary contained a /* External links */ you can guess what the user did even without summary.', '2.', 'You want to find the user who added the image to section ""Foo"".', 'Even if there are summaries like ""+image"" this doesn\'t help you much, but the summary /* Foo */ +image does help you.', 'The section is also usefull if no additional summary is given, in the worst case you have to look at all changes to the whole article and to the section ""Foo"" to find the author.', 'Pseudo-algorithm:\n\n1.', 'Find the position of the first and the last change in the new text (i.e.', 'find the common initial and final strings in the old and the new text).', '2.', 'Find the first headline above the last change (a line that starts with that character or before it and matches the pattern for headlines).', '3.', 'If this headline is before the first change, you found the section.', '4.', 'Else look for the next headline before it of higher level.', '5.', 'If there is such a headline, go to step 3, else more than one section was changed.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+242555,VisualEditor: Automatically add title of the section to edit summary,"This is the same as bug 50872; merging.
+
+*** This bug has been marked as a duplicate of bug 50872 ***",task_subcomment,"['This is the same as bug 50872; merging.', '*** This bug has been marked as a duplicate of bug 50872 ***']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+242550,VisualEditor: Automatically add title of the section to edit summary,"**ignatzmice.wiki** wrote:
+
+I agree with Michael, this would be very useful.",task_subcomment,"['**ignatzmice.wiki** wrote:\n\nI agree with Michael, this would be very useful.']",['EXPECTED BEHAVIOR']
+53341,"VisualEditor: double-clicking ""create reference"" generates a quasi-broken ref form.","Screenshot
+
+If you double-click ""create reference"", having clicked ""insert new reference"", it generates...well, see the screenshot. Even when the window is closed, this persists for all subsequent loadings of the references tool on that page.
+
+Windows 7, Firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11430}",task_description,"['VisualEditor: double-clicking ""create reference"" generates a quasi-broken ref form.', 'Screenshot\n\nIf you double-click ""create reference"", having clicked ""insert new reference"", it generates...well, see the screenshot.', 'Even when the window is closed, this persists for all subsequent loadings of the references tool on that page.', 'Windows 7, Firefox 22.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11430}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242434,"VisualEditor: double-clicking ""create reference"" generates a quasi-broken ref form.",This has been fixed since July; sorry for slow update.,task_subcomment,['This has been fixed since July; sorry for slow update.'],['ACTION ON ISSUE']
+53340,VisualEditor: Applying a transclusion that only contains content brackets breaks the edit toolbar.,"Reported on EnWiki by John Broughton:
+
+Steps to Reproduce:
+(1) Click the ""transclusion"" icon
+(2) In the lower left of the resulting dialog box, hover over the ""+"" sign until the bracket pair  (""[ ]"") is visible; click on that.
+(3) Click on ""[ ] Content""
+(4) Click on ""Apply changes""
+
+Now none of the ""insert"" icons work, and a number of other icons on the tool bar also don't work. (The user guide is silent as to what these brackets are ''supposed'' to do.)
+
+I can confirm the same issue also occurs for me on Firefox 22, Monobook interface.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Applying a transclusion that only contains content brackets breaks the edit toolbar.', 'Reported on EnWiki by John Broughton:\n\nSteps to Reproduce:\n(1) Click the ""transclusion"" icon\n(2) In the lower left of the resulting dialog box, hover over the ""+"" sign until the bracket pair  (""[ ]"") is visible; click on that.', '(3) Click on ""[ ] Content""\n(4) Click on ""Apply changes""\n\nNow none of the ""insert"" icons work, and a number of other icons on the tool bar also don\'t work.', ""(The user guide is silent as to what these brackets are ''supposed'' to do.)"", 'I can confirm the same issue also occurs for me on Firefox 22, Monobook interface.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242400,VisualEditor: Applying a transclusion that only contains content brackets breaks the edit toolbar.,We fixed this quite some time ago; apologies for the slowness of updating this bug report.,task_subcomment,['We fixed this quite some time ago; apologies for the slowness of updating this bug report.'],['SOLUTION USAGE']
+242397,VisualEditor: Applying a transclusion that only contains content brackets breaks the edit toolbar.,*** Bug 51437 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51437 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53332,VisualEditor: Deletion of alienated content blocks can delete across (rather than deleting them),"Galleries are not supported yet (bug 43037), however it is possible to select a gallery object and press delete.  However that operation doesnt appear to work correctly all the time.
+
+Steps to reproduce
+1. Go to a page with a gallery (https://en.wikipedia.org/wiki/Branford,_Florida?veaction=edit)
+2. Click on the gallery
+3. Press delete
+
+Expected results:
+The gallery is removed
+
+Actual results:
+The gallery object remains, and the object after the gallery is affected.
+In the case of [[Branford,_Florida]], the ""See also"" changes from being a section to being a piece of normal text placed above the gallery.
+
+However, the same procedure at on [[Lip]] results in the 1) gallery being removed (yay!), 2) the two section titles being merged together (not so good).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Deletion of alienated content blocks can delete across (rather than deleting them)\n\nGalleries are not supported yet (bug 43037), however it is possible to select a gallery object and press delete.', 'However that operation doesnt appear to work correctly all the time.', 'Steps to reproduce\n1.', 'Go to a page with a gallery (URL\n2.', 'Click on the gallery\n3.', 'Press delete\n\nExpected results:\nThe gallery is removed\n\nActual results:\nThe gallery object remains, and the object after the gallery is affected.', 'In the case of [[Branford,_Florida]], the ""See also"" changes from being a section to being a piece of normal text placed above the gallery.', 'However, the same procedure at on [[Lip]] results in the 1) gallery being removed (yay!', '), 2) the two section titles being merged together (not so good).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+241991,VisualEditor: Deletion of alienated content blocks can delete across (rather than deleting them),This was fixed in the re-work of selection and deletion recently; sorry for the slow triage.,task_subcomment,['This was fixed in the re-work of selection and deletion recently; sorry for the slow triage.'],['BUG REPRODUCTION']
+53311,Allow wikitext e.g. links to documentation in templatedata,"When trying to describe complex template parameters there is a need to be able to link to a specific documentation page. For instance in in the Taxobox  there is a need to link to the main doc page
+http://en.wikipedia.org/wiki/Template:Taxobox/doc
+as there are lots of subtitles in using the template.
+
+Further there is also a need for links in some of the individual parameter. 
+For the ""name"" parameter the description currently reads 
+
+For plants, see [[Wikipedia:Naming conventions (flora)]]. For all other living things, the name should be the most common vernacular name, when one is in widespread use, and a scientific name otherwise.
+
+as the precise policy on whether plants should be given common or latin names is quite involved. There other places where there is a need to provide links to further information: [[Wikipedia:Conservation status]], [[APG III system]] of classification of flowering plants, [[virus classification]], [[Template:Species list]] and [[Template:Taxon list]] for some sub templates used. 
+
+Good documentation requires sufficient detail, more than can be provided in one line. 
+
+I've a few thoughts on how this could be implements, the whole template could have a ""documentation"": ""Template:Taxobox/doc"". You could allow wikilinks inside the ""description"" or provide an optional ""link"" parameter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49772",task_description,"['Allow wikitext e.g.', 'links to documentation in templatedata\n\nWhen trying to describe complex template parameters there is a need to be able to link to a specific documentation page.', 'For instance in in the Taxobox  there is a need to link to the main doc page\nURL\nas there are lots of subtitles in using the template.', 'Further there is also a need for links in some of the individual parameter.', 'For the ""name"" parameter the description currently reads \n\nFor plants, see [[Wikipedia:Naming conventions (flora)]].', 'For all other living things, the name should be the most common vernacular name, when one is in widespread use, and a scientific name otherwise.', 'as the precise policy on whether plants should be given common or latin names is quite involved.', 'There other places where there is a need to provide links to further information: [[Wikipedia:Conservation status]], [[APG III system]] of classification of flowering plants, [[virus classification]], [[Template:Species list]] and [[Template:Taxon list]] for some sub templates used.', 'Good documentation requires sufficient detail, more than can be provided in one line.', 'I\'ve a few thoughts on how this could be implements, the whole template could have a ""documentation"": ""Template:Taxobox/doc"".', 'You could allow wikilinks inside the ""description"" or provide an optional ""link"" parameter.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+240797,Allow wikitext e.g. links to documentation in templatedata,"
+
+*** This bug has been marked as a duplicate of bug 50656 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50656 ***'],['ACTION ON ISSUE']
+240795,Allow wikitext e.g. links to documentation in templatedata,*** Bug 50656 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50656 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240791,Allow wikitext e.g. links to documentation in templatedata,"At [https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564196505#Quotes_in_template_data] there is a related request to allow wikitext generally in Template Data documentation. 
+
+The specific request for the example given there is the  tag to all better distinguishing of '' (two apostrophes for italic markup) and "" (double quote) by rendering them in a monospace font.",task_subcomment,"['At [URL there is a related request to allow wikitext generally in Template Data documentation.', 'The specific request for the example given there is the  tag to all better distinguishing of \'\' (two apostrophes for italic markup) and "" (double quote) by rendering them in a monospace font.']","['POTENTIAL NEW ISSUES AND REQUESTS', 'INVESTIGATION AND EXPLORATION']"
+53280,VisualEditor: External link missing in template due to linkname with ampersand in it,"Here in VE, the {{Discogs master}} template usage at the bottom of the page in the external links does not render.
+
+Escaping the ampersand in the page name seems to make it work: https://en.wikipedia.org/w/index.php?title=Bossalinis_%26_Fooliyones&diff=564046051&oldid=564034183
+
+So possible entity escaping problem
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Bossalinis_%26_Fooliyones&oldid=564034183",task_description,"['VisualEditor: External link missing in template due to linkname with ampersand in it\n\nHere in VE, the {{Discogs master}} template usage at the bottom of the page in the external links does not render.', 'Escaping the ampersand in the page name seems to make it work: URL\n\nSo possible entity escaping problem\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+239102,VisualEditor: External link missing in template due to linkname with ampersand in it,confirmed,task_subcomment,['confirmed'],['SOLUTION DISCUSSION']
+239092,VisualEditor: External link missing in template due to linkname with ampersand in it,I think this has been subsequently fixed - can you confirm?,task_subcomment,['I think this has been subsequently fixed - can you confirm?'],['OBSERVED BUG BEHAVIOR']
+53249,VisualEditor: Interface has elements untranslated in Spanish,"**Author:** `jduranboger`
+
+**Description:**
+In Wikipedia in spanish its neccesary tranaslate the interface for link of edit section still apear ""edit surce"" it should be ""editar fuente"".
+
+En Wikipedia en español es necesario traducir la interface para el enlace de Editar secciones, sigue apareciendo como ""edit source"", lo correcto es ""editar fuente""
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",task_description,"['VisualEditor: Interface has elements untranslated in Spanish\n\n**Author:** CODE\n\n**Description:**\nIn Wikipedia in spanish its neccesary tranaslate the interface for link of edit section still apear ""edit surce"" it should be ""editar fuente"".', 'En Wikipedia en español es necesario traducir la interface para el enlace de Editar secciones, sigue apareciendo como ""edit source"", lo correcto es ""editar fuente""\n\n--------------------------\n**Version**: unspecified\n**Severity**: trivial']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237026,VisualEditor: Interface has elements untranslated in Spanish,"[Sorry for bad auto-translation.]
+
+La traducción de la interfaz del software se realiza en TranslateWiki.Net.
+
+Puede ver todos los mensajes traducidas existentes para VisualEditor en Español
+en:
+
+http://translatewiki.net/w/i.php?title=Special:Translate&language=es&group=ext-visualeditor
+
+Estoy de acuerdo en que hay demasiados mensajes sin traducir.
+
+Para convertirse en un traductor de sí mismo, por favor vaya a:
+
+
+https://translatewiki.net/w/i.php?title=Special:UserLogin&returnto=Special%3AFirstSteps&type=signup&uselang=es",task_subcomment,"['[Sorry for bad auto-translation.]', 'La traducción de la interfaz del software se realiza en TranslateWiki.Net.', 'Puede ver todos los mensajes traducidas existentes para VisualEditor en Español\nen:\n\nURL\n\nEstoy de acuerdo en que hay demasiados mensajes sin traducir.', 'Para convertirse en un traductor de sí mismo, por favor vaya a:\n\n\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'CONTRIBUTION AND COMMITMENT', 'OBSERVED BUG BEHAVIOR']"
+237022,VisualEditor: Interface has elements untranslated in Spanish,"Translation of the software interface is done on TranslateWiki.Net.
+
+You can see all the existing untranslated messages for VisualEditor in Spanish at:
+
+ http://translatewiki.net/w/i.php?title=Special:Translate&language=es&group=ext-visualeditor
+
+I agree that there are too many untranslated messages.
+
+To become a translator yourself, please go to:
+
+  https://translatewiki.net/w/i.php?title=Special:UserLogin&returnto=Special%3AFirstSteps&type=signup&uselang=es",task_subcomment,"['Translation of the software interface is done on TranslateWiki.Net.', 'You can see all the existing untranslated messages for VisualEditor in Spanish at:\n\n URL\n\nI agree that there are too many untranslated messages.', 'To become a translator yourself, please go to:\n\n  URL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+53244,VisualEditor: Images disappear when the editor is loaded,"Compare
+1) https://pt.wikipedia.org/wiki/?oldid=36380720&action=edit&preview=yes
+2) https://pt.wikipedia.org/wiki/?oldid=36380720&veaction=edit
+
+There are two images in the first case, but they disappear in the second case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Images disappear when the editor is loaded\n\nCompare\n1) URL\n2) URL\n\nThere are two images in the first case, but they disappear in the second case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236659,VisualEditor: Images disappear when the editor is loaded,"Per http://parsoid.wmflabs.org/pt/Usu%C3%A1rio:Helder.wiki/Testes?oldid=36380720 the images have been replaced by Parsoid with  which is why they don't appear. This is apparently caused by bug 48900 - merging with that.
+
+*** This bug has been marked as a duplicate of bug 48900 ***",task_subcomment,"['Per URL the images have been replaced by Parsoid with  which is why they don\'t appear.', 'This is apparently caused by bug 48900 - merging with that.', '*** This bug has been marked as a duplicate of bug 48900 ***']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+236652,VisualEditor: Images disappear when the editor is loaded,"Parsoid just adds a missing space in the [link syntax]:
+http://parsoid.wmflabs.org/_rt/pt/?oldid=36380720",task_subcomment,['Parsoid just adds a missing space in the [link syntax]:\nURL'],['OBSERVED BUG BEHAVIOR']
+53220,VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.,"Sorry if this turns out to be a duplicate - a search trough the bugs containing the words ""copy paste"" doesn't seem to turn anything up though. 
+
+The problem is as the title says: Cut and Pasting a section in the visual editor will remove all the formatting provided that section contains an image. Tested on Firefox 22, Mono skin.
+
+Steps to reproduce:
+- Navigate to https://en.wikipedia.org/w/index.php?title=Microsoft&oldid=563598458 and edit the page with the visual editor.
+- Cut the ""1972–83: Founding and company beginnings"" section entirely. Eg, anything between the ""1972–83:"" in the section header, and the ""Hodgkin's disease.[4]:231"" in the section content. (This will also select the image in the section)
+- Click the location where the section used to be and paste the text - technically speaking pasting anywhere causes the problem though.
+
+The text that is pasted will be stripped of all formatting, and the image that was selected will be gone as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.', 'Sorry if this turns out to be a duplicate - a search trough the bugs containing the words ""copy paste"" doesn\'t seem to turn anything up though.', 'The problem is as the title says: Cut and Pasting a section in the visual editor will remove all the formatting provided that section contains an image.', 'Tested on Firefox 22, Mono skin.', 'Steps to reproduce:\n- Navigate to URL and edit the page with the visual editor.', '- Cut the ""1972–83: Founding and company beginnings"" section entirely.', 'Eg, anything between the ""1972–83:"" in the section header, and the ""Hodgkin\'s disease.', '[4]\ufeff:231\ufeff"" in the section content.', '(This will also select the image in the section)\n- Click the location where the section used to be and paste the text - technically speaking pasting anywhere causes the problem though.', 'The text that is pasted will be stripped of all formatting, and the image that was selected will be gone as well.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+235424,VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.,"And marking as a duplicate of bug 33105, which is about supporting this functionality.
+
+The cut operation should probably be 'disabled' if it contains elements that can't be pasted again.  However the 'cut' operation could do a 'copy' operation, with a notice to the user that cut is not supported for complex wiki blocks.
+
+The paste operation should probably be disabled until this is fixed, with a notice to the user that they should press undo/Control-Z to get back their text if the last item on the undo stack is a Cut operation.
+
+But there is probably also an 'enhancement' raised about those as well.
+
+*** This bug has been marked as a duplicate of bug 33105 ***",task_subcomment,"['And marking as a duplicate of bug 33105, which is about supporting this functionality.', ""The cut operation should probably be 'disabled' if it contains elements that can't be pasted again."", ""However the 'cut' operation could do a 'copy' operation, with a notice to the user that cut is not supported for complex wiki blocks."", 'The paste operation should probably be disabled until this is fixed, with a notice to the user that they should press undo/Control-Z to get back their text if the last item on the undo stack is a Cut operation.', ""But there is probably also an 'enhancement' raised about those as well."", '*** This bug has been marked as a duplicate of bug 33105 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'POTENTIAL NEW ISSUES AND REQUESTS', 'OBSERVED BUG BEHAVIOR']"
+235419,VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.,Confirming your example.,task_subcomment,['Confirming your example.'],['OBSERVED BUG BEHAVIOR']
+235414,VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.,See also https://bugzilla.wikimedia.org/show_bug.cgi?id=50721,task_subcomment,['See also URL'],['OBSERVED BUG BEHAVIOR']
+53200,Botfixup: VisualEditor shows 6 items in a list which for which MW only generates 2 items,"Compare the result of the wikitext
+#1
+#
+#
+#
+#
+#6
+in the following URLs:
+1) https://pt.wikipedia.org/wiki/?oldid=36373624&veaction=edit
+2) https://pt.wikipedia.org/wiki/?oldid=36373624&action=edit&preview=yes
+
+Visual Editor show us a list with 6 elements, but MediaWiki will only display two items.
+
+Maybe this is related to Tidy?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Botfixup: VisualEditor shows 6 items in a list which for which MW only generates 2 items\n\nCompare the result of the wikitext\n#1\n#\n#\n#\n#\n#6\nin the following URLs:\n1) URL\n2) URL\n\nVisual Editor show us a list with 6 elements, but MediaWiki will only display two items.', 'Maybe this is related to Tidy?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234299,Botfixup: VisualEditor shows 6 items in a list which for which MW only generates 2 items,"It would be difficult to sanely edit undisplayed list items. We would basically have to pretend those list items were never there. They would not be editable in the VE. 
+
+While not impossible, even round-tripping of such collapsed list items would add a lot of special-case code.
+
+So overall I am very doubtful that this would be worth it. IMO it is better to fix the wikitext, possibly with a bot. I'm closing this as wontfix for now. Please reopen if there are good reasons why correcting this with bots is not feasible.",task_subcomment,"['It would be difficult to sanely edit undisplayed list items.', 'We would basically have to pretend those list items were never there.', 'They would not be editable in the VE.', 'While not impossible, even round-tripping of such collapsed list items would add a lot of special-case code.', 'So overall I am very doubtful that this would be worth it.', 'IMO it is better to fix the wikitext, possibly with a bot.', ""I'm closing this as wontfix for now."", 'Please reopen if there are good reasons why correcting this with bots is not feasible.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'ACTION ON ISSUE']"
+234290,Botfixup: VisualEditor shows 6 items in a list which for which MW only generates 2 items,This is in Parsoid: http://parsoid.wmflabs.org/pt/Usu%C3%A1rio:Lechatjaune/Testes?oldid=36373624,task_subcomment,['This is in Parsoid: URL'],['OBSERVED BUG BEHAVIOR']
+53191,Template rearranging itself,"Copied from English Wikipedia:
+
+I was trying to edit a template in a table after the bug of the references inside template was fixed, but the edit broke the whole table. This was also happening before with the references bug. I don't know if the two bugs were reported together...maybe not. [http://en.wikipedia.org/w/index.php?title=Defiance_%28TV_series%29&diff=563767420&oldid=563763824 Here] is what happened.
+
    When I edited the template with the 12th episode, the cite error didn't appear. But when I clicked to save it, the 12th episode moved at the top of the table when it should be at the bottom. I reverted the edit and re-made it using ""edit source"". Can this be reported? Thank you [[User:TeamGale|TeamGale]] ([[User talk:TeamGale|talk]]) 16:58, 11 July 2013 (UTC)
+
+**
+
+This one has been around a while, but I think perhaps it wasn't properly reported earlier. I can't fidn it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Template rearranging itself\n\nCopied from English Wikipedia:\n\nI was trying to edit a template in a table after the bug of the references inside template was fixed, but the edit broke the whole table.', 'This was also happening before with the references bug.', ""I don't know if the two bugs were reported together...maybe not."", '[URL Here] is what happened.', ""
    When I edited the template with the 12th episode, the cite error didn't appear."", 'But when I clicked to save it, the 12th episode moved at the top of the table when it should be at the bottom.', 'I reverted the edit and re-made it using ""edit source"".', 'Can this be reported?', ""Thank you [[User:TeamGale|TeamGale]] ([[User talk:TeamGale|talk]]) 16:58, 11 July 2013 (UTC)\n\n**\n\nThis one has been around a while, but I think perhaps it wasn't properly reported earlier."", ""I can't fidn it."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233796,Template rearranging itself,This was the Parsoid complex templates / VisualEditor dirtying edits bug that got fixed months ago; sorry for the very slow triage.,task_subcomment,['This was the Parsoid complex templates / VisualEditor dirtying edits bug that got fixed months ago; sorry for the very slow triage.'],['OBSERVED BUG BEHAVIOR']
+53188,Template editing within referencing is complex to the point of hampering usability,"See http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563842762#Reference_Issues:_Omnibus_Edition
+
+User Joe Decker has detailed the steps necessary to add a reference to an article using a citation template. While I have as per his request entered some of these as separate bugs or enhancement requests, I am opening this one to note the complexity of the process. As he describes it, it is 73+ steps to achieve in VE what can be achieved in 11 in the older processes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Template editing within referencing is complex to the point of hampering usability\n\nSee URL\n\nUser Joe Decker has detailed the steps necessary to add a reference to an article using a citation template.', 'While I have as per his request entered some of these as separate bugs or enhancement requests, I am opening this one to note the complexity of the process.', 'As he describes it, it is 73+ steps to achieve in VE what can be achieved in 11 in the older processes.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233670,Template editing within referencing is complex to the point of hampering usability,"Merging this in with bug 50768.
+
+*** This bug has been marked as a duplicate of bug 50768 ***",task_subcomment,"['Merging this in with bug 50768.', '*** This bug has been marked as a duplicate of bug 50768 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233663,Template editing within referencing is complex to the point of hampering usability,Another editor has created a potential workflow for references. See http://en.wikipedia.org/wiki/User:Looie496/VE_Reference_editor,task_subcomment,"['Another editor has created a potential workflow for references.', 'See URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+53183,"VisualEditor: Design of the reference re-use pane is confusing, with a bold ""Use an existing source"" title that doesn't look like one","Unclear why the second option is bolded. An editor on English Wikipedia suggests that if only one of them is going to be bolded (create new source/use an existing source), it should be the other way around.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Design of the reference re-use pane is confusing, with a bold ""Use an existing source"" title that doesn\'t look like one\n\nUnclear why the second option is bolded.', 'An editor on English Wikipedia suggests that if only one of them is going to be bolded (create new source/use an existing source), it should be the other way around.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233481,"VisualEditor: Design of the reference re-use pane is confusing, with a bold ""Use an existing source"" title that doesn't look like one",This was fixed some months ago in the re-work of the transclusion dialog; sorry for the slowness of reply.,task_subcomment,['This was fixed some months ago in the re-work of the transclusion dialog; sorry for the slowness of reply.'],['SOLUTION USAGE']
+53175,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","**Author:** `kwwilliams`
+
+**Description:**
+There have been some bug reports focusing on the ordering of template arguments, but there's also a problem with changing the basic layout of the templates. Look at http://en.wikipedia.org/w/index.php?title=Raven-Symon%C3%A9&diff=563794138&oldid=563793891 where a vandal changed the birthname. The parameter order has been maintained, but the diff is still virtually useless because of the spurious formatting change. If the editor changes the value of one parameter to a template, that change is all that should be made to the source.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read\n\n**Author:** CODE\n\n**Description:**\nThere have been some bug reports focusing on the ordering of template arguments, but there's also a problem with changing the basic layout of the templates."", 'Look at URL where a vandal changed the birthname.', 'The parameter order has been maintained, but the diff is still virtually useless because of the spurious formatting change.', 'If the editor changes the value of one parameter to a template, that change is all that should be made to the source.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233175,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","**kwwilliams** wrote:
+
+It's 51150.",task_subcomment,"[""**kwwilliams** wrote:\n\nIt's 51150.""]",['OBSERVED BUG BEHAVIOR']
+233168,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","You have a choice of bug here, but it will be either 51150 (dirty diff) or 51003 (match style for new parameters and use appropriate style for new transclusions).
+
+Bug 51150 seems to be rare these days when you look at the VE recentchanges diffs, but there still seem to be some recent examples of it occuring, which is why it was reopened.
+
+VE recent changes on enwiki:
+https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&limit=100&tagfilter=visualeditor",task_subcomment,"['You have a choice of bug here, but it will be either 51150 (dirty diff) or 51003 (match style for new parameters and use appropriate style for new transclusions).', 'Bug 51150 seems to be rare these days when you look at the VE recentchanges diffs, but there still seem to be some recent examples of it occuring, which is why it was reopened.', 'VE recent changes on enwiki:\nURL']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+233161,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","**kwwilliams** wrote:
+
+This is *not* a duplicate of 51003. You need to maintain the original formatting, not any suggested formatting. If the original source lists the parameters like
+
+{{name
+|arg1|arg2
+|arg3
+|arg4
+|arg5
+}}
+
+and someone changes arg2, all that should occur is that the value of arg2 should be changed. No braces should move. No newlines should be inserted or removed. The ""dirty diff"" is *precisely* what I am complaining about.
+
+The various bugs around allowing a suggested format are all valid, but this isn't a duplicate. Diff lists are how we detect what editors have changed, and anything that dirties a diff is generally a bad thing. Reformatting templates when an argument is modified causes dirty diffs.",task_subcomment,"['**kwwilliams** wrote:\n\nThis is *not* a duplicate of 51003.', 'You need to maintain the original formatting, not any suggested formatting.', 'If the original source lists the parameters like\n\n{{name\n|arg1|arg2\n|arg3\n|arg4\n|arg5\n}}\n\nand someone changes arg2, all that should occur is that the value of arg2 should be changed.', 'No braces should move.', 'No newlines should be inserted or removed.', 'The ""dirty diff"" is *precisely* what I am complaining about.', ""The various bugs around allowing a suggested format are all valid, but this isn't a duplicate."", 'Diff lists are how we detect what editors have changed, and anything that dirties a diff is generally a bad thing.', 'Reformatting templates when an argument is modified causes dirty diffs.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+233156,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","In that case this is duplicate of bug 51003.
+
+*** This bug has been marked as a duplicate of bug 51003 ***",task_subcomment,"['In that case this is duplicate of bug 51003.', '*** This bug has been marked as a duplicate of bug 51003 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233152,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read",The dirty diff is not the question here. Clarifying title.,task_subcomment,"['The dirty diff is not the question here.', 'Clarifying title.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233149,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","**wicke** wrote:
+
+Looks like VE bug 51150. Closing as duplicate.
+
+%%%*** This bug has been marked as a duplicate of bug 51150 ***%%%",task_subcomment,"['**wicke** wrote:\n\nLooks like VE bug 51150.', 'Closing as duplicate.', '%%%*** This bug has been marked as a duplicate of bug 51150 ***%%%']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+233145,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","I think the idea of a TemplateData tag as to whether to keep new lines seems like a good one, if Parsoid would be interested.",task_subcomment,"['I think the idea of a TemplateData tag as to whether to keep new lines seems like a good one, if Parsoid would be interested.']",['SOLUTION DISCUSSION']
+233141,"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","Agreed; this is true for existing templates, but it's also an issue when adding a long infobox to a page, for example.
+
+It was suggested by French Wikipedians to add a tag to TemplateData (like '""collapsed"" = false') that would indicate to VisualEditor that the community consensus for a given template is to have one parameter per line, instead of cramming everything together (which could remain as the default behavior, and makes sense for many short templates).",task_subcomment,"[""Agreed; this is true for existing templates, but it's also an issue when adding a long infobox to a page, for example."", 'It was suggested by French Wikipedians to add a tag to TemplateData (like \'""collapsed"" = false\') that would indicate to VisualEditor that the community consensus for a given template is to have one parameter per line, instead of cramming everything together (which could remain as the default behavior, and makes sense for many short templates).']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+53173, added to wikilinks,"In http://en.wikipedia.org/w/index.php?title=Renewable_energy_in_Seychelles&diff=prev&oldid=563530801, the contributor says that he selected the words ""diesel generators"" for linking, but the editor inserted the nowiki to prevent the plural being part of the display. 
+
+See http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563816729#Changing_link_text_often_results_in_bad_code.2C_wrong_links_and_unmatched_.3C.2Fnowki.3Es for this and other cases. I'm afraid i'm not quite sure how to report this, since I'm not sure what's happening.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33091",task_description,"[' added to wikilinks\n\nIn URL the contributor says that he selected the words ""diesel generators"" for linking, but the editor inserted the nowiki to prevent the plural being part of the display.', 'See URL for this and other cases.', ""I'm afraid i'm not quite sure how to report this, since I'm not sure what's happening."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232892, added to wikilinks,"If the user selects ""diesel generator"" (i.e., misses the 's'), the resultant HTML would be
+
+  diesel generators 
+
+The correct wikitext version of this is indeed
+
+  [[diesel generator]]s
+
+… which is probably not what the user wanted to do, but it appears to be what they asked VisualEditor to do.
+
+Consequently, I'm going to mark this as INVALID [If this is not the case - that the user did indeed select the entirety of the two words and there's a bug, I'd really love to know what browser they were using so we can hunt down the problem in our selection code!]
+
+Had they instead selected ""diesel generators"", VisualEditor/Parsoid would have created this as:
+
+  [[diesel generator|diesel generators]]
+
+… which is not ideal (I'd prefer the shorter [[diesel generator]]s) but does the job. (I've just triple-checked this in Firefox, Chrome and Safari - it doesn't appear to have broken.)
+
+We could always expand users' selections to what we think they should have selected, but this would make it impossible for users to do some things that they may want to do, albeit less frequently. I'm not sure that preventing users from doing things that they can do in wikitext would be a good solution, in general.",task_subcomment,"['If the user selects ""diesel generator"" (i.e., misses the \'s\'), the resultant HTML would be\n\n  diesel generators \n\nThe correct wikitext version of this is indeed\n\n  [[diesel generator]]s\n\n… which is probably not what the user wanted to do, but it appears to be what they asked VisualEditor to do.', ""Consequently, I'm going to mark this as INVALID [If this is not the case - that the user did indeed select the entirety of the two words and there's a bug, I'd really love to know what browser they were using so we can hunt down the problem in our selection code!]"", 'Had they instead selected ""diesel generators"", VisualEditor/Parsoid would have created this as:\n\n  [[diesel generator|diesel generators]]\n\n… which is not ideal (I\'d prefer the shorter [[diesel generator]]s) but does the job.', ""(I've just triple-checked this in Firefox, Chrome and Safari - it doesn't appear to have broken.)"", ""We could always expand users' selections to what we think they should have selected, but this would make it impossible for users to do some things that they may want to do, albeit less frequently."", ""I'm not sure that preventing users from doing things that they can do in wikitext would be a good solution, in general.""]","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53169,VisualEditor: blanking an article and starting from scratch causes malformations,"The screenshot is the result of the following:
+
+1. go to article
+2. blank article, removing everything
+3. type ""1""
+4. type ""2""
+..and what you end up with is:
+
+1
+12
+
+The text is, in addition, impossible to delete.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: blanking an article and starting from scratch causes malformations\n\nThe screenshot is the result of the following:\n\n1. go to article\n2. blank article, removing everything\n3. type ""1""\n4. type ""2""\n..and what you end up with is:\n\n1\n12\n\nThe text is, in addition, impossible to delete.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+232672,VisualEditor: blanking an article and starting from scratch causes malformations,"This is the same as bug 50947, I believe - merging.
+
+*** This bug has been marked as a duplicate of bug 50947 ***",task_subcomment,"['This is the same as bug 50947, I believe - merging.', '*** This bug has been marked as a duplicate of bug 50947 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+232665,VisualEditor: blanking an article and starting from scratch causes malformations,"I'm seeing something very slightly different to this - see https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563808463#Odd_bug_after_blanking_page
+
+If it matters I'm using Firefox 22 on Xubuntu Linux. I don't have another browser to test it in (Konqueror is apparently blacklisted from VE).",task_subcomment,"[""I'm seeing something very slightly different to this - see URL\n\nIf it matters I'm using Firefox 22 on Xubuntu Linux."", ""I don't have another browser to test it in (Konqueror is apparently blacklisted from VE).""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232656,VisualEditor: blanking an article and starting from scratch causes malformations,"I reported something similar in Bug 50947, though there I couldn't type at all. Roan asked for JS console output there, so I guess that it would be useful here, too.
+
+This may also be browser-specific.",task_subcomment,"[""I reported something similar in Bug 50947, though there I couldn't type at all."", 'Roan asked for JS console output there, so I guess that it would be useful here, too.', 'This may also be browser-specific.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232648,VisualEditor: blanking an article and starting from scratch causes malformations,"Screenshot
+
+**Attached**: {F11062}",task_subcomment,['Screenshot\n\n**Attached**: {F11062}'],['OBSERVED BUG BEHAVIOR']
+53165,VisualEditor: easier parameter selection,"It would be nice if double-clicking a parameter name in the template inspector - in the 'insert' view - inserted it, to minimise scrolling and such.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: easier parameter selection\n\nIt would be nice if double-clicking a parameter name in the template inspector - in the 'insert' view - inserted it, to minimise scrolling and such."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232451,VisualEditor: easier parameter selection,"Per my previous comment I'm marking this as a duplicate of bug 51143. Feel free to reopen if this is still not working anywhere.
+
+*** This bug has been marked as a duplicate of bug 51143 ***",task_subcomment,"[""Per my previous comment I'm marking this as a duplicate of bug 51143."", 'Feel free to reopen if this is still not working anywhere.', '*** This bug has been marked as a duplicate of bug 51143 ***']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+232443,VisualEditor: easier parameter selection,I think this can be marked as a duplicate of resolved bug 51143 they seem similar and double-clicking a parameter name does insert the parameter for me.,task_subcomment,['I think this can be marked as a duplicate of resolved bug 51143 they seem similar and double-clicking a parameter name does insert the parameter for me.'],['BUG REPRODUCTION']
+232435,VisualEditor: easier parameter selection,"(I think I had reported something similar, but still :) )
+Users @itwp also ask for drop-down menu or similar solution in order to choose between values (i.e. gender (M/F) and so on).",task_subcomment,"['(I think I had reported something similar, but still :) )\nUsersSCREEN_NAME also ask for drop-down menu or similar solution in order to choose between values (i.e.', 'gender (M/F) and so on).']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53153,VisualEditor: Category interface is hard to find,"Finding the categories under page setting is non intuitive. Adding another icon next to references would help usability.
+
+This is discussed at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Icons_are_incomprehensible
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50239",task_description,"['VisualEditor: Category interface is hard to find\n\nFinding the categories under page setting is non intuitive.', 'Adding another icon next to references would help usability.', 'This is discussed at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+231669,VisualEditor: Category interface is hard to find,"We now split this out into the page settings menu, so closing as INVALID given the evolution of the interface.",task_subcomment,"['We now split this out into the page settings menu, so closing as INVALID given the evolution of the interface.']",['ACTION ON ISSUE']
+231664,VisualEditor: Category interface is hard to find,"So hard to find that I assumed it wasn't implemented yet. Now I've seen it.
+
+Why another icon on the top and not direct manipulation at the bottom? Show the categories at the bottom of the page and allow adding / editing / deleting from there. More or less the way HotCat got us used, if possible with a cleaner UI.",task_subcomment,"[""So hard to find that I assumed it wasn't implemented yet."", ""Now I've seen it."", 'Why another icon on the top and not direct manipulation at the bottom?', 'Show the categories at the bottom of the page and allow adding / editing / deleting from there.', 'More or less the way HotCat got us used, if possible with a cleaner UI.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+231659,VisualEditor: Category interface is hard to find,"See also:
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Categories
+and
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Smaller_popup_dialog_for_Category_labeling_on_pages?",task_subcomment,['See also:\nURL\nand\nURL'],['OBSERVED BUG BEHAVIOR']
+231655,VisualEditor: Category interface is hard to find,*** Bug 51452 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51452 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53134,VisualEditor: Intermittently unable to open page settings after deleting and then adding a stub template,"English Wikipedia user PamD reports that sometimes after replacing one stub template with another she is unable to open the page settings dialog unless she saves and then reedits the page.
+
+I have done a small amount of testing and can confirm that the following steps will reproduce the bug, but only intermittently:
+
+1. Open a page in VE that has one or more stub templates (e.g. any article in [[Category:England stubs]])
+2. Delete the/one stub template by selecting it and then pressing the delete key
+3. Launch the transclusion tool from the toolbar
+4. Enter a different stub template (e.g. Wales-stub), select it from the list and then click ""Add template""
+5. Add the template to the page by clicking the ""Apply changes"" button. In my testing I never entered any parameters or options, PamD has not specified whether she does or not.
+6. Click the ""page settings"" button on the tool bar.
+
+If the dialog opens, choose a different article and try again. In my testing it failed to open just under 50% of the time, PamD implies it happens less frequently to her but doesn't specify. 
+
+A bit more detail is at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563709233#Can.27t_open_.22Page_settings.22_after_changing_stub_template
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Intermittently unable to open page settings after deleting and then adding a stub template\n\nEnglish Wikipedia user PamD reports that sometimes after replacing one stub template with another she is unable to open the page settings dialog unless she saves and then reedits the page.', 'I have done a small amount of testing and can confirm that the following steps will reproduce the bug, but only intermittently:\n\n1.', 'Open a page in VE that has one or more stub templates (e.g.', 'any article in [[Category:England stubs]])\n2.', 'Delete the/one stub template by selecting it and then pressing the delete key\n3.', 'Launch the transclusion tool from the toolbar\n4.', 'Enter a different stub template (e.g.', 'Wales-stub), select it from the list and then click ""Add template""\n5.', 'Add the template to the page by clicking the ""Apply changes"" button.', 'In my testing I never entered any parameters or options, PamD has not specified whether she does or not.', '6.', 'Click the ""page settings"" button on the tool bar.', 'If the dialog opens, choose a different article and try again.', ""In my testing it failed to open just under 50% of the time, PamD implies it happens less frequently to her but doesn't specify."", 'A bit more detail is at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254897,VisualEditor: Intermittently unable to open page settings after deleting and then adding a stub template,I can't reproduce this now; provisionally marking as WORKSFORME.,task_subcomment,"[""I can't reproduce this now; provisionally marking as WORKSFORME.""]",['BUG REPRODUCTION']
+254895,VisualEditor: Intermittently unable to open page settings after deleting and then adding a stub template,"I've just tried reproducing this again, and it is still happening and still only intermittently (2 of 4 articles I tried)",task_subcomment,"[""I've just tried reproducing this again, and it is still happening and still only intermittently (2 of 4 articles I tried)""]",['OBSERVED BUG BEHAVIOR']
+53132,VisualEditor: Auto-generated (bare) external links converted to external links to target null,"VisualEditor appears to be inserting ""null"" into external links occasionally.
+
+Examples:
+
+https://en.wikipedia.org/w/index.php?title=Carrie_(musical)&curid=7695755&diff=563576490&oldid=563235599
+
+at [[Ithaca College]] in [[Ithaca, New York]] by the Macabre Theatre Ensemble,[null http:///www.icmacabre.blogspot.com]
+
+----
+
+https://en.wikipedia.org/w/index.php?title=Embarcadero_Delphi&curid=349208&diff=563574811&oldid=561383018
+
+Delphi has large communities on [[Usenet]] and the [[World Wide Web|web]] (e.g. [null news://newsgroups.codegear.com)] which
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Auto-generated (bare) external links converted to external links to target null\n\nVisualEditor appears to be inserting ""null"" into external links occasionally.', 'Examples:\n\nURL\n\nat [[Ithaca College]] in [[Ithaca, New York]] by the Macabre Theatre Ensemble,[null URL\n\n----\n\nURL\n\nDelphi has large communities on [[Usenet]] and the [[World Wide Web|web]] (e.g.', '[null news://newsgroups.codegear.com)] which\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+254811,VisualEditor: Auto-generated (bare) external links converted to external links to target null,"This was an icky bug that we fixed some time ago; sorry for the bug, and for the slowness of triage.",task_subcomment,"['This was an icky bug that we fixed some time ago; sorry for the bug, and for the slowness of triage.']",['INVESTIGATION AND EXPLORATION']
+53130,VisualEditor: Removing template & Adding content breaks editor,"Copied from En Wikipedia:
+
+***
+When editing a template, when I click remove template, and then without closing the dialog, click add -> content and enter some text, the template is not removed and the editor hangs on saving and reviewing changes. --WS (talk) 11:47, 9 July 2013 (UTC)
+
+***
+Tested with the same result.
+
+Maggie
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Removing template & Adding content breaks editor\n\nCopied from En Wikipedia:\n\n***\nWhen editing a template, when I click remove template, and then without closing the dialog, click add -> content and enter some text, the template is not removed and the editor hangs on saving and reviewing changes.', '--WS (talk) 11:47, 9 July 2013 (UTC)\n\n***\nTested with the same result.', 'Maggie\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254719,VisualEditor: Removing template & Adding content breaks editor,"Bug 51340 is essentially the same issue, and both are now fixed I believe.",task_subcomment,"['Bug 51340 is essentially the same issue, and both are now fixed I believe.']",['BUG REPRODUCTION']
+53125,"VisualEditor: Review changes should show the edit summary, if one has been provided.","Some users add [[links]] to edit summaries, which can be really helpful; unfortunately as markup it needs checking to ensure that it isn't borked. Accordingly, would it be possible to render the edit summary in the 'review changes' pane, if one has been provided?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Review changes should show the edit summary, if one has been provided.', ""Some users add [[links]] to edit summaries, which can be really helpful; unfortunately as markup it needs checking to ensure that it isn't borked."", ""Accordingly, would it be possible to render the edit summary in the 'review changes' pane, if one has been provided?"", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254543,"VisualEditor: Review changes should show the edit summary, if one has been provided.","(In reply to comment #1)
+> I think this duplicates bug 42139
+
+Yeah; merging.
+
+*** This bug has been marked as a duplicate of bug 42139 ***",task_subcomment,"['(In reply to comment #1)\nQUOTE\n\nYeah; merging.', '*** This bug has been marked as a duplicate of bug 42139 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+254537,"VisualEditor: Review changes should show the edit summary, if one has been provided.",I think this duplicates bug 42139,task_subcomment,['I think this duplicates bug 42139'],['OBSERVED BUG BEHAVIOR']
+53119,Transcluded pages quasi-template eats into subsequent entry,"De.WP often uses ""{{:Target page}} in its disambiguation pages and VE produces two problems: 1) The subsequent non-template disambiguation entry in the list gets sucked into the content of the previous template-entry; 2) the template blocks the option to edit the entries surrounding it. See:
+
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563687401#Transcluded_pages
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Transcluded pages quasi-template eats into subsequent entry\n\nDe.WP often uses ""{{:Target page}} in its disambiguation pages and VE produces two problems: 1) The subsequent non-template disambiguation entry in the list gets sucked into the content of the previous template-entry; 2) the template blocks the option to edit the entries surrounding it.', 'See:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+254294,Transcluded pages quasi-template eats into subsequent entry,Opened Parsoid bug 53368 for the issues described in comment #12 above.,task_subcomment,['Opened Parsoid bug 53368 for the issues described in comment #12 above.'],['OBSERVED BUG BEHAVIOR']
+254289,Transcluded pages quasi-template eats into subsequent entry,"A deeper investigation revealed additional issues:
+
+1) Completely templated list items currently always break up lists in Parsoid. Test case: echo -ne '*foo\n{{:User:GWicke/li|bar}}\n*baz' | node parse
+
+2) This covers up another bug in the template encapsulation code. Template-affected lists are only marked as such because the list handler starts a new list for each templated list item. This (correctly) places the meta element we use to track template-affected content outside the 
       triggered by the template-generated list item. Once 1) is fixed, we will have to fix this up with a special rule in the encapsulation code that marks the parent list as template-affected if one of its wikitext-syntax items is template-generated. The meta element will end up between list items, so a propagation rule should be sufficient.
+
+None of this will do much for the ease of editing. I realize that fixing up a lot of pages to use explicit bullets in the page will create a lot of work for bots, but at the same time I don't see a sane alternative that provides a good editing experience.",task_subcomment,"['A deeper investigation revealed additional issues:\n\n1) Completely templated list items currently always break up lists in Parsoid.', ""Test case: echo -ne '*foo\\n{{:User:GWicke/li|bar}}\\n*baz' | node parse\n\n2) This covers up another bug in the template encapsulation code."", 'Template-affected lists are only marked as such because the list handler starts a new list for each templated list item.', 'This (correctly) places the meta element we use to track template-affected content outside the 
         triggered by the template-generated list item.', 'Once 1) is fixed, we will have to fix this up with a special rule in the encapsulation code that marks the parent list as template-affected if one of its wikitext-syntax items is template-generated.', 'The meta element will end up between list items, so a propagation rule should be sufficient.', 'None of this will do much for the ease of editing.', ""I realize that fixing up a lot of pages to use explicit bullets in the page will create a lot of work for bots, but at the same time I don't see a sane alternative that provides a good editing experience.""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254285,Transcluded pages quasi-template eats into subsequent entry,"(In reply to comment #8)
+> That said, there is a possibility that for lists, this problem is solvable by
+> marking a series of adjacent list nodes as template generated -- Parsoid
+> already has the mechanism of marking a forest of adjacent DOM nodes as
+> template-generated instead of marking just a root-node. 
+
+The problem is that the list is also template-affected, and needs to be marked as such. A change in transclusion output (say, from *foo to #foo) will change the list structure significantly, so it is not safe to mark the list items only.
+
+The example page exposes a different issue though, which you mention as well: The comments between transclusions (which probably end up on their own line after expansion) break up the list in Parsoid, but don't do so in PHP (bug 52762). This is not surprising as the PHP parser strips those comments before doing anything else, but still something we could improve by not breaking up the list.
+
+Sadly, the effect of this will be that the entire list will be template-affected.
+
+This problem would not be there if the bullet for the list item was not templated:
+
+* {{:Christian Delius}}
+* [[Christina Rau]], geb. Delius (* 1956), deutsche Politologin
+
+In this case we know that the first list item will always create an unordered list, no matter what the transclusion generates (ignoring unbalanced transclusions for now). Each item will be editable separately without being sucked into a big template-affected block.",task_subcomment,"['(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe problem is that the list is also template-affected, and needs to be marked as such.', 'A change in transclusion output (say, from *foo to #foo) will change the list structure significantly, so it is not safe to mark the list items only.', ""The example page exposes a different issue though, which you mention as well: The comments between transclusions (which probably end up on their own line after expansion) break up the list in Parsoid, but don't do so in PHP (bug 52762)."", 'This is not surprising as the PHP parser strips those comments before doing anything else, but still something we could improve by not breaking up the list.', 'Sadly, the effect of this will be that the entire list will be template-affected.', 'This problem would not be there if the bullet for the list item was not templated:\n\n* {{:Christian Delius}}\n* [[Christina Rau]], geb.', 'Delius (* 1956), deutsche Politologin\n\nIn this case we know that the first list item will always create an unordered list, no matter what the transclusion generates (ignoring unbalanced transclusions for now).', 'Each item will be editable separately without being sucked into a big template-affected block.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254282,Transcluded pages quasi-template eats into subsequent entry,"I personally am not going to apply that metric to this page -- for example, table tags cannot be edited in VE, extension source cannot be edited in VE, and wikitext that shows up in between multi-part templates cannot be edited in VE.  I think this particular issue falls in the same category.
+
+I do agree that the experience is sub-optimal.  But given that it does not break wikitext, I mean no disrespect to your opinion, but I disagree with you that we ought to therefore make the entire page uneditable.  As to your suggestion of providing a generic warning for uneditable pieces in VE, I'll James address that part.
+
+But, as I noted above, at least for dab pages using list items, this problem might be solvable if we can figure out why transclusions are splitting existing lists at the transclusion point.",task_subcomment,"['I personally am not going to apply that metric to this page -- for example, table tags cannot be edited in VE, extension source cannot be edited in VE, and wikitext that shows up in between multi-part templates cannot be edited in VE.', 'I think this particular issue falls in the same category.', 'I do agree that the experience is sub-optimal.', 'But given that it does not break wikitext, I mean no disrespect to your opinion, but I disagree with you that we ought to therefore make the entire page uneditable.', ""As to your suggestion of providing a generic warning for uneditable pieces in VE, I'll James address that part."", 'But, as I noted above, at least for dab pages using list items, this problem might be solvable if we can figure out why transclusions are splitting existing lists at the transclusion point.']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+254278,Transcluded pages quasi-template eats into subsequent entry,"Please read the bug report and reproduce. The current behaviour is sub-optimal. Perhaps its not a high priority as it doesnt break the wiki-text, but that doesn't mean it isnt contrary to user expectations.
+Text on the page (in the wiki text) should be editable on the page. If the VE cant edit all the wikitext on the page, the page is not yet functional in VE, and only SE should be offered to the user (or VE should tell the user to use SE to edit those bits).",task_subcomment,"['Please read the bug report and reproduce.', 'The current behaviour is sub-optimal.', ""Perhaps its not a high priority as it doesnt break the wiki-text, but that doesn't mean it isnt contrary to user expectations."", 'Text on the page (in the wiki text) should be editable on the page.', 'If the VE cant edit all the wikitext on the page, the page is not yet functional in VE, and only SE should be offered to the user (or VE should tell the user to use SE to edit those bits).']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+254274,Transcluded pages quasi-template eats into subsequent entry,"That said, there is a possibility that for lists, this problem is solvable by marking a series of adjacent list nodes as template generated -- Parsoid already has the mechanism of marking a forest of adjacent DOM nodes as template-generated instead of marking just a root-node.  I suspect the reason this is not already happening is because of an (un)related list parsing bug.  Bug 49974, now merged into Bug 52762.  Once that is resolved, this problem will be fixed for the specific example pages on this page.  And as long as most of the disambiguation pages use this pattern (list items), it should be okay for them.",task_subcomment,"['That said, there is a possibility that for lists, this problem is solvable by marking a series of adjacent list nodes as template generated -- Parsoid already has the mechanism of marking a forest of adjacent DOM nodes as template-generated instead of marking just a root-node.', 'I suspect the reason this is not already happening is because of an (un)related list parsing bug.', 'Bug 49974, now merged into Bug 52762.', 'Once that is resolved, this problem will be fixed for the specific example pages on this page.', 'And as long as most of the disambiguation pages use this pattern (list items), it should be okay for them.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+254268,Transcluded pages quasi-template eats into subsequent entry,"(In reply to comment #5)
+> The bug still exists. VE should handle this differently: mark the whole page
+> as
+> not compatible with VE if you must.
+
+John: can you clarify what could be done here? 
+
+As far as I can tell, there is no broken HTML, and neither is there any corruption on edit and save. The only problem is that top-level page content is sucked into transclusion content and is not editable. In the current scenario, at least some part of the page is editable in VE. How would marking the whole page not editable solve this issue?",task_subcomment,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\n\nJohn: can you clarify what could be done here?', 'As far as I can tell, there is no broken HTML, and neither is there any corruption on edit and save.', 'The only problem is that top-level page content is sucked into transclusion content and is not editable.', 'In the current scenario, at least some part of the page is editable in VE.', 'How would marking the whole page not editable solve this issue?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254263,Transcluded pages quasi-template eats into subsequent entry,*** Bug 52814 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52814 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254258,Transcluded pages quasi-template eats into subsequent entry,The bug still exists. VE should handle this differently: mark the whole page as not compatible with VE if you must.,task_subcomment,"['The bug still exists.', 'VE should handle this differently: mark the whole page as not compatible with VE if you must.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+254253,Transcluded pages quasi-template eats into subsequent entry,"As James indicates in https://bugzilla.wikimedia.org/show_bug.cgi?id=51119#c2, there is really not much we can do about this. The implicit 
           is started by a template, so the entire list needs to be marked as template-affected even if some items in it are not templated.
+
+Since I don't see a good way to improve this situation in Parsoid, I'm going to close this bug as wontfix for now. Please reopen this bug if you have an idea on how this could be handled better.",task_subcomment,"['As James indicates in URL there is really not much we can do about this.', 'The implicit 
             is started by a template, so the entire list needs to be marked as template-affected even if some items in it are not templated.', ""Since I don't see a good way to improve this situation in Parsoid, I'm going to close this bug as wontfix for now."", 'Please reopen this bug if you have an idea on how this could be handled better.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+463290,Transcluded pages quasi-template eats into subsequent entry,"This is not really a problem that affects enwp.  If my SQL is right, enwp has only 14 dab pages that transclude mainspace - easily a manual fixup task, esp. when some look of them look like this: https://en.wikipedia.org/wiki/Howes?veaction=edit
+
+Some impact analysis for the next set of wikis in line for VE deployment:
+
+* dewp: 22226 content pages transcluding mainspace - i.e. 1.4% of all 'content pages', of which 9012 are dab pages - i.e. 0.5% of all content pages
+  - not all of those suffer from the second issue raised; sometimes they have whitespace between transclusion and the next item
+  --  e.g. https://de.wikipedia.org/wiki/Kalam?veaction=edit
+* frwp,hewp,nlwp: between 1&4 pages transcluding mainspace
+* svwp: 250, all dab pages
+* ruwp: 1616, all dab pages - i.e. 0.15% of all content pages
+
+Looking at a Russian example; it doesnt face the second problem raised in comment 1; the last item on this dab page is not consumed by the {{:Lloyd's}} above it.
+https://ru.wikipedia.org/wiki/%D0%9B%D0%BB%D0%BE%D0%B9%D0%B4?veaction=edit
+https://ru.wikipedia.org/wiki/Lloyd%E2%80%99s
+
+ruwp uses noinclude instead of onlyinclude.
+
+My SLQ on dewp:
+```
+select count(*)
+from   templatelinks tl inner join page p on (tl.tl_from = p.page_id)
+where  tl_namespace = 0
+and    page_namespace = 0
+and    tl_from in 
+  (select cl_from from categorylinks where cl_to =  'Begriffsklärung')
+;
+```",task_subcomment,"['This is not really a problem that affects enwp.', 'If my SQL is right, enwp has only 14 dab pages that transclude mainspace - easily a manual fixup task, esp.', 'when some look of them look like this: URL\n\nSome impact analysis for the next set of wikis in line for VE deployment:\n\n* dewp: 22226 content pages transcluding mainspace - i.e.', ""1.4% of all 'content pages', of which 9012 are dab pages - i.e."", '0.5% of all content pages\n  - not all of those suffer from the second issue raised; sometimes they have whitespace between transclusion and the next item\n  --  e.g.', 'URL\n* frwp,hewp,nlwp: between 1&4 pages transcluding mainspace\n* svwp: 250, all dab pages\n* ruwp: 1616, all dab pages - i.e.', ""0.15% of all content pages\n\nLooking at a Russian example; it doesnt face the second problem raised in comment 1; the last item on this dab page is not consumed by the {{:Lloyd's}} above it."", 'URL\nURL\n\nruwp uses noinclude instead of onlyinclude.', 'My SLQ on dewp:\n``CODE``']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+463286,Transcluded pages quasi-template eats into subsequent entry,"This is not really a problem that affects enwp.  If my SQL is right, enwp has only 14 dab pages that transclude mainspace - easily a manual fixup task, esp. when some look of them look like this:
+   e.g. https://en.wikipedia.org/wiki/Howes?veaction=edit
+
+Some impact analysis for the next set of wikis in line for VE deployment:
+
+* dewp: 22226 content pages transcluding mainspace - i.e. 1.4% of all 'content pages', of which 9012 are dab pages - i.e. 0.5% of all content pages
+  - not all of those suffer from the second issue raised; sometimes they have whitespace between transclusion and the next item
+  --  e.g. https://de.wikipedia.org/wiki/Kalam?veaction=edit
+* frwp,hewp,nlwp: between 1&4 pages transcluding mainspace
+* svwp: 250, all dab pages
+* ruwp: 1616, all dab pages - i.e. 0.15% of all content pages
+
+Looking at a Russian example; it doesnt face the second problem raised in comment 1; the last item on this dab page is not consumed by the {{:Lloyd's}} above it.
+https://ru.wikipedia.org/wiki/%D0%9B%D0%BB%D0%BE%D0%B9%D0%B4?veaction=edit
+https://ru.wikipedia.org/wiki/Lloyd%E2%80%99s
+
+ruwp uses noinclude instead of onlyinclude.
+
+My SLQ on dewp:
+```
+select count(*)
+from   templatelinks tl inner join page p on (tl.tl_from = p.page_id)
+where  tl_namespace = 0
+and    page_namespace = 0
+and    tl_from in 
+  (select cl_from from categorylinks where cl_to =  'Begriffsklärung')
+;
+```",task_subcomment,"['This is not really a problem that affects enwp.', 'If my SQL is right, enwp has only 14 dab pages that transclude mainspace - easily a manual fixup task, esp.', 'when some look of them look like this:\n   e.g.', 'URL\n\nSome impact analysis for the next set of wikis in line for VE deployment:\n\n* dewp: 22226 content pages transcluding mainspace - i.e.', ""1.4% of all 'content pages', of which 9012 are dab pages - i.e."", '0.5% of all content pages\n  - not all of those suffer from the second issue raised; sometimes they have whitespace between transclusion and the next item\n  --  e.g.', 'URL\n* frwp,hewp,nlwp: between 1&4 pages transcluding mainspace\n* svwp: 250, all dab pages\n* ruwp: 1616, all dab pages - i.e.', ""0.15% of all content pages\n\nLooking at a Russian example; it doesnt face the second problem raised in comment 1; the last item on this dab page is not consumed by the {{:Lloyd's}} above it."", 'URL\nURL\n\nruwp uses noinclude instead of onlyinclude.', 'My SLQ on dewp:\n``CODE``']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254250,Transcluded pages quasi-template eats into subsequent entry,"This is not really a problem that affects enwp.  If my SQL is right, enwp has only 14 dab pages that transclude mainspace - easily a manual fixup task, esp. when some look of them look like this:
+   e.g. https://en.wikipedia.org/wiki/Howes?veaction=edit
+
+Some impact analysis for the next set of wikis in line for VE deployment:
+
+dewp: 22226 content pages transcluding mainspace - i.e. 1.4% of all 'content pages', of which 9012 are dab pages - i.e. 0.5% of all content pages
+ - not all of those suffer from the second issue raised; 
+   sometimes they have whitespace between transclusion and the next item
+   e.g. https://de.wikipedia.org/wiki/Kalam?veaction=edit
+
+frwp,hewp,nlwp: between 1&4 pages transcluding mainspace
+
+svwp: 250, all dab pages
+
+ruwp: 1616, all dab pages - i.e. 0.15% of all content pages
+  Looking at a Russian example; it doesnt face the second problem raised in comment 1; the last item on this dab page is not consumed by the {{:Lloyd's}} above it.
+https://ru.wikipedia.org/wiki/%D0%9B%D0%BB%D0%BE%D0%B9%D0%B4?veaction=edit
+https://ru.wikipedia.org/wiki/Lloyd%E2%80%99s
+
+ruwp uses noinclude instead of onlyinclude.
+
+My SLQ on dewp:
+select count(*)
+from   templatelinks tl inner join page p on (tl.tl_from = p.page_id)
+where  tl_namespace = 0
+and    page_namespace = 0
+and    tl_from in 
+  (select cl_from from categorylinks where cl_to =  'Begriffsklärung')
+;",task_subcomment,"['This is not really a problem that affects enwp.', 'If my SQL is right, enwp has only 14 dab pages that transclude mainspace - easily a manual fixup task, esp.', 'when some look of them look like this:\n   e.g.', 'URL\n\nSome impact analysis for the next set of wikis in line for VE deployment:\n\ndewp: 22226 content pages transcluding mainspace - i.e.', ""1.4% of all 'content pages', of which 9012 are dab pages - i.e."", '0.5% of all content pages\n - not all of those suffer from the second issue raised; \n   sometimes they have whitespace between transclusion and the next item\n   e.g.', 'URL\n\nfrwp,hewp,nlwp: between 1&4 pages transcluding mainspace\n\nsvwp: 250, all dab pages\n\nruwp: 1616, all dab pages - i.e.', ""0.15% of all content pages\n  Looking at a Russian example; it doesnt face the second problem raised in comment 1; the last item on this dab page is not consumed by the {{:Lloyd's}} above it."", 'URL\nURL\n\nruwp uses noinclude instead of onlyinclude.', ""My SLQ on dewp:\nselect count(*)\nfrom   templatelinks tl inner join page p on (tl.tl_from = p.page_id)\nwhere  tl_namespace = 0\nand    page_namespace = 0\nand    tl_from in \n  (select cl_from from categorylinks where cl_to =  'Begriffsklärung')\n;""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254246,Transcluded pages quasi-template eats into subsequent entry,"Relevant wikitext excerpt:
+
+| {{:Christian Delius}}
+| 
+| * [[Christina Rau]], geb. Delius (* 1956), deutsche Politologin
+
+Yeah, this is because the HTML comment and 
          •  in the wikitext below the template insert themselves into the implicit 
               that the template creates (and so get marked as part of the same ""MediaWiki transclusions"" generated content block as the template by Parsoid.
+
+I'm not sure what Parsoid could do to ""fix"" this, really. It's correct parsing of broken-by-design wikitext (which doesn't seem obvious if you're not parsing it).",task_subcomment,"['Relevant wikitext excerpt:\n\n| {{:Christian Delius}}\n| \n| * [[Christina Rau]], geb.', 'Delius (* 1956), deutsche Politologin\n\nYeah, this is because the HTML comment and 
            •  in the wikitext below the template insert themselves into the implicit 
                 that the template creates (and so get marked as part of the same ""MediaWiki transclusions"" generated content block as the template by Parsoid.', 'I\'m not sure what Parsoid could do to ""fix"" this, really.', ""It's correct parsing of broken-by-design wikitext (which doesn't seem obvious if you're not parsing it).""]","['MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254243,Transcluded pages quasi-template eats into subsequent entry,"The cited example is
+https://de.wikipedia.org/wiki/Delius?veaction=edit
+
+The entry 'Christina Rau' is not editable, as VE believes it is part of the 'template' {{:Christian Delius}}
+
+Possibly because the onlyinclude on
+https://de.wikipedia.org/w/index.php?title=Christian_Delius&action=edit",task_subcomment,"[""The cited example is\nURL\n\nThe entry 'Christina Rau' is not editable, as VE believes it is part of the 'template' {{:Christian Delius}}\n\nPossibly because the onlyinclude on\nURL""]",['BUG REPRODUCTION']
+53103,VisualEditor: Auto-external links to image files which are broken (404/etc.) display as the filename and cannot be edited,"When a raw URL with no markup (e.g. http://www.sucs.org/~cmckenna/photos/quizes/tq2012/July/Jun03key.png ) ends in .png, .jpg, .svg or .gif [capitalisation variants not tested] but does not work (e.g. it gives a 404 error) then only the filename portion of the URL (Jun03key.png in this example) is displayed in the visual editor. Visual editor cannot then edit this URL to correct it, meaning that typos, etc cannot be corrected without using the source editor.
+
+Links to other image formats (e.g. tif), html pages, .txt files and pdf files, and all urls enclosed in single bracket markup work as expected and are editable in the Visual editor. See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=563642435 for my sandbox testing.
+
+This is not unlikely related to bug 51092 in some way.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Auto-external links to image files which are broken (404/etc.)', 'display as the filename and cannot be edited\n\nWhen a raw URL with no markup (e.g.', 'URL ) ends in .png, .jpg, .svg or .gif [capitalisation variants not tested] but does not work (e.g.', 'it gives a 404 error) then only the filename portion of the URL (Jun03key.png in this example) is displayed in the visual editor.', 'Visual editor cannot then edit this URL to correct it, meaning that typos, etc cannot be corrected without using the source editor.', 'Links to other image formats (e.g.', 'tif), html pages, .txt files and pdf files, and all urls enclosed in single bracket markup work as expected and are editable in the Visual editor.', 'See URL for my sandbox testing.', 'This is not unlikely related to bug 51092 in some way.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253451,VisualEditor: Auto-external links to image files which are broken (404/etc.) display as the filename and cannot be edited,"This will be entirely fixed by bug 51092 being fixed (well, theoretically if a site administrator wants to have VE but also $wgAllowExternalImages set true, it'd be a problem, but we'll have fixed this issue with a forthcoming re-write of image handling anyway before we've shipped VE as stable).
+
+Marking as a duplicate.
+
+*** This bug has been marked as a duplicate of bug 51092 ***",task_subcomment,"[""This will be entirely fixed by bug 51092 being fixed (well, theoretically if a site administrator wants to have VE but also $wgAllowExternalImages set true, it'd be a problem, but we'll have fixed this issue with a forthcoming re-write of image handling anyway before we've shipped VE as stable)."", 'Marking as a duplicate.', '*** This bug has been marked as a duplicate of bug 51092 ***']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+53094,Editing adds JavaScript,"I just attempted to make https://www.mediawiki.org/w/index.php?title=Lua_scripting&diff=728272&oldid=728271 with VisualEditor and got https://www.mediawiki.org/w/index.php?title=Lua_scripting&diff=728270&oldid=664107 instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Editing adds JavaScript\n\nI just attempted to make URL with VisualEditor and got URL instead.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252900,Editing adds JavaScript,"(In reply to comment #2)
+> How would the addition be the plugin's fault? It isn't added in the normal
+> edit
+> box, or in any other boxes at that.
+
+Your browser's plug-in is inserting HTML into contentEditable 
                s. Some example complaints from around the Web:
+
+* http://wordpress.org/support/topic/appears-after-url-and-unknown-script-inserted
+* http://www.joomlaportal.de/joomla-2-5-allgemeine-fragen/291114-automatische-scriptinstallation-foxlingojs.html
+* http://www.bluestonedesign.de/faq/20-sonstige-fragen/376-foxlingojs-script-in-joomla-und-wordpress-beitraegen
+* http://doc.eklablog.com/blog-de-texte-bizarre-topic48844
+* http://forum.wpde.org/allgemeines/108364-foxlingo-script-evtl-schadsoftware-wer-kennt-es.html
+* https://drupal.org/node/1871476
+
+There is nothing sane that VisualEditor can do to stop your broken browser, except to ask you here to stop using it. (Though I'd recommend use of a global AbuseFilter to prevent this and similar corruptions of wikis' content.)
+
+Reclosing.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nYour browser's plug-in is inserting HTML into contentEditable 
                s."", 'Some example complaints from around the Web:\n\n* URL\n* URL\n* URL\n* URL\n* URL\n* URL\n\nThere is nothing sane that VisualEditor can do to stop your broken browser, except to ask you here to stop using it.', ""(Though I'd recommend use of a global AbuseFilter to prevent this and similar corruptions of wikis' content.)"", 'Reclosing.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE']"
+252894,Editing adds JavaScript,"How would the addition be the plugin's fault? It isn't added in the normal edit box, or in any other boxes at that.",task_subcomment,"[""How would the addition be the plugin's fault?"", ""It isn't added in the normal edit box, or in any other boxes at that.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252886,Editing adds JavaScript,"From a quick Google, this is a faulty browser plugin of some kind, FoxLingoJs.",task_subcomment,"['From a quick Google, this is a faulty browser plugin of some kind, FoxLingoJs.']",['OBSERVED BUG BEHAVIOR']
+53077,"VisualEditor: Link inspector blown to pieces when pressing return after clicking ""Insert link"" (before the inspector has finishes opening)","Screenshot of ripped-apart link inspector
+
+I can consistently reproduce the following:
+
+* Select an unlinked word
+* Create the insert link button (with intention to turn the word into a link)
+* If you hit Return immediately after (before it has finished opening) it will replace the focussed node with a new line. Though that is a separate bug and arguably an invalid use case (why would one be pressing Return at this point, the user hasn't even seen the options yet. It interpreting it as intend to replace the node isn't entirely unreasable, but that's a separate bug - bug 51075).
+* At this point the link inspector dom has blown up. Part of it is gone, and the other part is left half-way across the screen at a seemingly arbitrary offset (see attachment).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11776}",task_description,"['VisualEditor: Link inspector blown to pieces when pressing return after clicking ""Insert link"" (before the inspector has finishes opening)\n\nScreenshot of ripped-apart link inspector\n\nI can consistently reproduce the following:\n\n* Select an unlinked word\n* Create the insert link button (with intention to turn the word into a link)\n* If you hit Return immediately after (before it has finished opening) it will replace the focussed node with a new line.', ""Though that is a separate bug and arguably an invalid use case (why would one be pressing Return at this point, the user hasn't even seen the options yet."", ""It interpreting it as intend to replace the node isn't entirely unreasable, but that's a separate bug - bug 51075)."", '* At this point the link inspector dom has blown up.', 'Part of it is gone, and the other part is left half-way across the screen at a seemingly arbitrary offset (see attachment).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11776}']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252015,"VisualEditor: Link inspector blown to pieces when pressing return after clicking ""Insert link"" (before the inspector has finishes opening)","
+
+*** This bug has been marked as a duplicate of bug 49941 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49941 ***'],['ACTION ON ISSUE']
+53072,Adding a {{cn}} template causes VisualEditor to silently add .. to the edited paragraph,"**Author:** `FT2.wiki`
+
+**Description:**
+Tried to add {{cn}} to an article, visual editor silently added NOWIKI../NOWIKI tags on saving, which had to be manually removed.
+
+http://en.wikipedia.org/w/index.php?title=XFS&diff=563579994&oldid=562618140
+
+Unclear if this is the same or different as other  issues on bugzilla
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Adding a {{cn}} template causes VisualEditor to silently add .. to the edited paragraph\n\n**Author:** CODE\n\n**Description:**\nTried to add {{cn}} to an article, visual editor silently added NOWIKI../NOWIKI tags on saving, which had to be manually removed.', 'URL\n\nUnclear if this is the same or different as other  issues on bugzilla\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+251678,Adding a {{cn}} template causes VisualEditor to silently add .. to the edited paragraph,"Closing as INVALID (this is not a bug, this is exactly expected behaviour). Please re-open if we have mis-judged.",task_subcomment,"['Closing as INVALID (this is not a bug, this is exactly expected behaviour).', 'Please re-open if we have mis-judged.']","['ISSUE CONTENT MANAGEMENT', 'ACTION ON ISSUE']"
+251673,Adding a {{cn}} template causes VisualEditor to silently add .. to the edited paragraph,"Did you type the text ""{{cn}}"" into the editor directly? In that case this is correct behavior: we did what was needed to make the literal text ""{{cn}}"" appear.
+
+To insert a template in VE you'll need to use the puzzle piece icon in the toolbar. Typing wikitext directly into the editor is deliberately not supported.",task_subcomment,"['Did you type the text ""{{cn}}"" into the editor directly?', 'In that case this is correct behavior: we did what was needed to make the literal text ""{{cn}}"" appear.', ""To insert a template in VE you'll need to use the puzzle piece icon in the toolbar."", 'Typing wikitext directly into the editor is deliberately not supported.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+53066,VisualEditor: Link input field identifiers in DOM are bogus,"corrupt  identifier in DOM for Link
+
+see screenshot
+
+what is this ""class""?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11753}",task_description,"['VisualEditor: Link input field identifiers in DOM are bogus\n\ncorrupt  identifier in DOM for Link\n\nsee screenshot\n\nwhat is this ""class""?', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11753}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251306,VisualEditor: Link input field identifiers in DOM are bogus,"It's not corrupt, it's just empty.
+
+jQuery doesn't remove the attribute when removing the last class. In this case, we add the class to make the input ""pending"" and then remove it when the AJAX call is done.
+
+I don't think this is a real problem - if you have code that takes a different path based on whether the class attribute is set, has a non-empty value, or has a value, I suspect the first two cases should just be folded together.",task_subcomment,"[""It's not corrupt, it's just empty."", ""jQuery doesn't remove the attribute when removing the last class."", 'In this case, we add the class to make the input ""pending"" and then remove it when the AJAX call is done.', ""I don't think this is a real problem - if you have code that takes a different path based on whether the class attribute is set, has a non-empty value, or has a value, I suspect the first two cases should just be folded together.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53058,VisualEditor: reference editing bringing you to the wrong citation (template problem?),"Reference editing on, for example, https://en.wikipedia.org/wiki/Friedrich_Nietzsche?veaction=edit, sometimes takes you to the wrong citation. I'm not sure what the problem is. My only current theory, as a luddite, is that the difficulties the VE/Parsoid has with references in templates may be responsible for a numbering screwup somehow between read and edit mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: reference editing bringing you to the wrong citation (template problem?)', 'Reference editing on, for example, URL sometimes takes you to the wrong citation.', ""I'm not sure what the problem is."", 'My only current theory, as a luddite, is that the difficulties the VE/Parsoid has with references in templates may be responsible for a numbering screwup somehow between read and edit mode.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250640,VisualEditor: reference editing bringing you to the wrong citation (template problem?),"Merging this with bug 50474.
+
+*** This bug has been marked as a duplicate of bug 50474 ***",task_subcomment,"['Merging this with bug 50474.', '*** This bug has been marked as a duplicate of bug 50474 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+250635,VisualEditor: reference editing bringing you to the wrong citation (template problem?),"The observation: I was trying to make this edit - http://en.wikipedia.org/w/index.php?title=Friedrich_Nietzsche&curid=10671&diff=563544089&oldid=562894275 - Opened article in VE, saw the ""as as"" was in footnote 134 ... couldn't edit there ... went up to reference 134, clicked on it to edit, and it was the wrong reference link. It actually gave me the reference that's numbered 220 (in that version) to edit!",task_subcomment,"['The observation: I was trying to make this edit - URL - Opened article in VE, saw the ""as as"" was in footnote 134 ... couldn\'t edit there ... went up to reference 134, clicked on it to edit, and it was the wrong reference link.', ""It actually gave me the reference that's numbered 220 (in that version) to edit!""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53054,VisualEditor: duplicate links created if parts of the link are differently italicised/bolded,"See https://en.wikipedia.org/w/index.php?title=User:Okeyes_%28WMF%29/sandbox&diff=next&oldid=563541289 for example; It should be [[''death'' metal]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: duplicate links created if parts of the link are differently italicised/bolded\n\nSee URL for example; It should be [[''death'' metal]]."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250416,VisualEditor: duplicate links created if parts of the link are differently italicised/bolded,"Merging with bug 50098.
+
+*** This bug has been marked as a duplicate of bug 50098 ***",task_subcomment,"['Merging with bug 50098.', '*** This bug has been marked as a duplicate of bug 50098 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+250413,VisualEditor: duplicate links created if parts of the link are differently italicised/bolded,"With the sole exception of plaint text followed by italic text, it seems that a separate link is created for each part of the link that has a different bold/italic status:
+
+https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&diff=574094377&oldid=574094235
+https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&diff=574094083&oldid=574093861
+
+To reproduce:
+1. Create or edit any page that has consecutive words that have different italic/bold annotation, i.e. any of
+''one'' two
+'''un''' deaux
+''ein'' '''zwei'''
+'''un''' ''dai''
+'''uno''' due
+
+2. select both words and make the selection a link (internal or external).
+
+Expected behaviour: One link is created, e.g. [[link|''one'' two]]
+Actual behaviour: Two links are created, e.g. [[link|''one''']] [[link|two]]",task_subcomment,"['With the sole exception of plaint text followed by italic text, it seems that a separate link is created for each part of the link that has a different bold/italic status:\n\nURL\nURL\n\nTo reproduce:\n1.', 'Create or edit any page that has consecutive words that have different italic/bold annotation, i.e.', ""any of\n''one'' two\n'''un''' deaux\n''ein'' '''zwei'''\n'''un''' ''dai''\n'''uno''' due\n\n2. select both words and make the selection a link (internal or external)."", 'Expected behaviour: One link is created, e.g.', ""[[link|''one'' two]]\nActual behaviour: Two links are created, e.g."", ""[[link|''one''']] [[link|two]]""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250409,VisualEditor: duplicate links created if parts of the link are differently italicised/bolded,"Is this still happening? 
+In my sandbox just now, VE changed [[Ancient Carthage]] to [[Ancient Carthage|''Ancient'' Carthage]] as I would expect.
+
+https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=570143239&oldid=568345382",task_subcomment,"['Is this still happening?', ""In my sandbox just now, VE changed [[Ancient Carthage]] to [[Ancient Carthage|''Ancient'' Carthage]] as I would expect."", 'URL']","['OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION']"
+53048,VisualEditor: The transparent color that shows the template goes up to the previous element instead of the top of the template,"a screenshot with the problem
+
+To reproduce:
+
+1. Go to https://en.wikipedia.org/wiki/Boris_Ponomarev?veaction=edit
+2. Click the template at the bottom of the article.
+
+Observed: The transparent bluish color that shows the template tool (puzzle piece) goes all the way up to the paragraph that precedes the page, even though there's a lot of spacing between them because of the infobox on the side.
+
+Expected: The transparent color must only cover the template itself and not other elements.
+
+See the screenshot.
+
+Tested on Firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11723}",task_description,"['VisualEditor: The transparent color that shows the template goes up to the previous element instead of the top of the template\n\na screenshot with the problem\n\nTo reproduce:\n\n1.', 'Go to URL\n2.', 'Click the template at the bottom of the article.', ""Observed: The transparent bluish color that shows the template tool (puzzle piece) goes all the way up to the paragraph that precedes the page, even though there's a lot of spacing between them because of the infobox on the side."", 'Expected: The transparent color must only cover the template itself and not other elements.', 'See the screenshot.', 'Tested on Firefox 22.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11723}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250127,VisualEditor: The transparent color that shows the template goes up to the previous element instead of the top of the template,"This is caused by the phantom starting from the logical position of the content, rather than the rendered position (due to the width being 100%). Merging with bug 50395.
+
+*** This bug has been marked as a duplicate of bug 50395 ***",task_subcomment,"['This is caused by the phantom starting from the logical position of the content, rather than the rendered position (due to the width being 100%).', 'Merging with bug 50395.', '*** This bug has been marked as a duplicate of bug 50395 ***']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+53024,VisualEditor: adding spaces?,"Possibly the most vanilla dirty diff ever, if it is a dirty diff - in https://en.wikipedia.org/w/index.php?title=The_Painted_Bird&diff=563388980&oldid=544897993 the VE has added an extra space (before ""novel"").
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: adding spaces?', 'Possibly the most vanilla dirty diff ever, if it is a dirty diff - in URL the VE has added an extra space (before ""novel"").', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249077,VisualEditor: adding spaces?,"This seems to be bug 48570
+
+*** This bug has been marked as a duplicate of bug 48570 ***",task_subcomment,['This seems to be bug 48570\n\n*** This bug has been marked as a duplicate of bug 48570 ***'],['OBSERVED BUG BEHAVIOR']
+249070,VisualEditor: adding spaces?,"It might be worth noting that spaces keep being added each time you edit an article with this bug (some examples here: https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis#Insertion_d.27une_espace_suppl.C3.A9mentaire_.C3.A0_chaque_.C3.A9dition , it seems related to the colon), and that some of them are not even real whitespaces.",task_subcomment,"['It might be worth noting that spaces keep being added each time you edit an article with this bug (some examples here: URL , it seems related to the colon), and that some of them are not even real whitespaces.']",['OBSERVED BUG BEHAVIOR']
+249060,VisualEditor: adding spaces?,"Other examples:
+
+In this diff, the second whitespace was intended, but the first one wasn't:
+https://fr.wikipedia.org/w/index.php?diff=94475506
+
+In the subsequent edit, the user tried to remove the space that was inserted by VE, and not only was he not able to remove it, but VE actually added /another/ space:
+https://fr.wikipedia.org/w/index.php?diff=94475570&oldid=94475506
+
+I notice that in these 2 cases, as well as in the case reported in comment 1, there's an adjacent colon. Dunno if it's related.",task_subcomment,"[""Other examples:\n\nIn this diff, the second whitespace was intended, but the first one wasn't:\nURL\n\nIn the subsequent edit, the user tried to remove the space that was inserted by VE, and not only was he not able to remove it, but VE actually added /another/ space:\nURL\n\nI notice that in these 2 cases, as well as in the case reported in comment 1, there's an adjacent colon."", ""Dunno if it's related.""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+249053,VisualEditor: adding spaces?,Talking about spaces: https://en.wikipedia.org/w/index.php?title=Genie_%28feral_child%29&diff=564429158&oldid=564425048,task_subcomment,['Talking about spaces: URL'],['OBSERVED BUG BEHAVIOR']
+249047,VisualEditor: adding spaces?,"Same thing here after ""équipes"": http://fr.wikipedia.org/w/index.php?title=Mafia_%28jeu%29&diff=94892395&oldid=91395852",task_subcomment,"['Same thing here after ""équipes"": URL']",['OBSERVED BUG BEHAVIOR']
+53018,"VisualEditor: ""clear formatting"" does not remove links","On enwiki, at least. If you highlight a link, format-clearing does nothing; if you click on the link to the point where the system registers (i.e., the link icon pops up), ditto.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: ""clear formatting"" does not remove links\n\nOn enwiki, at least.', 'If you highlight a link, format-clearing does nothing; if you click on the link to the point where the system registers (i.e., the link icon pops up), ditto.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248445,"VisualEditor: ""clear formatting"" does not remove links","Yeah, this is a really irritating regression; merging with the other.
+
+*** This bug has been marked as a duplicate of bug 50461 ***",task_subcomment,"['Yeah, this is a really irritating regression; merging with the other.', '*** This bug has been marked as a duplicate of bug 50461 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248439,"VisualEditor: ""clear formatting"" does not remove links","Yes, the toolbar button (""No"" symbol) gives the impression that it should remove every skerrick of formatting from the text, including links.",task_subcomment,"['Yes, the toolbar button (""No"" symbol) gives the impression that it should remove every skerrick of formatting from the text, including links.']",['OBSERVED BUG BEHAVIOR']
+53017,VisualEditor: Template dialog crushing parameters together and nowiking links,"See https://en.wikipedia.org/w/index.php?title=Vicarious_Visions&diff=563488422&oldid=563388782 and https://en.wikipedia.org/w/index.php?title=Vicarious_Visions&action=edit&oldid=563488422 for how the markup for that appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Template dialog crushing parameters together and nowiking links\n\nSee URL and URL for how the markup for that appears.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248399,VisualEditor: Template dialog crushing parameters together and nowiking links,"This is now fixed (and has been for some time, I believe). Sorry for the disruption.",task_subcomment,"['This is now fixed (and has been for some time, I believe).', 'Sorry for the disruption.']","['SOLUTION USAGE', 'ACTION ON ISSUE']"
+248392,VisualEditor: Template dialog crushing parameters together and nowiking links,Ditto - https://pl.wikipedia.org/w/index.php?title=Wikipedysta:Sir_Lothar/brudnopis2&diff=prev&oldid=37137604,task_subcomment,['Ditto - URL'],['SOLUTION DISCUSSION']
+248384,VisualEditor: Template dialog crushing parameters together and nowiking links,"I don't think that this is just a problem with browser extensions misbehaving over links.  This edit:
+
+https://pl.wikipedia.org/w/index.php?title=Rory_MacDonald&curid=2849478&diff=37138750&oldid=36592431
+
+involves no links, and yet the data is still placed after a line break and smashed up against the following parameter, instead of up on the previous line where it belongs.",task_subcomment,"[""I don't think that this is just a problem with browser extensions misbehaving over links."", 'This edit:\n\nURL\n\ninvolves no links, and yet the data is still placed after a line break and smashed up against the following parameter, instead of up on the previous line where it belongs.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248376,VisualEditor: Template dialog crushing parameters together and nowiking links,"Some broken browser extension sometimes adds lots of  ... tags around items which is tracked by and edit filter. Attempting to clean these up with the VE worked well in the main text but failed in the templates changing
+
+{{Infobox company
+...
+| foundation     = [[1990 in video gaming|1990]]
+| products       = [[Crash Bandicoot|''Crash Bandicoot'' series]] (2002-2004) (2013- )
                [[Skylanders|''Skylanders'' series]] (2011-2013)0)"">Guitar Hero|''Guitar Hero'' series]] (2007–2010) 
+...
+}}
+
+Into
+{{Infobox company
+|1990]]
+|''Guitar Hero'' series]] (2007–2010) 
+...
+| foundation     = [[1990 in video gaming
+| products       = [[Crash Bandicoot|''Crash Bandicoot'' series]] (2002-2004) (2013- )
                [[Skylanders|''Skylanders'' series]] (2011-2013) Guitar Hero
+...
+}}
+splitting the foundation and product parameters.",task_subcomment,"['Some broken browser extension sometimes adds lots of  ... tags around items which is tracked by and edit filter.', 'Attempting to clean these up with the VE worked well in the main text but failed in the templates changing\n\n{{Infobox company\n...\n| foundation     = [[1990 in video gaming|1990]]\n| products       = [[Crash Bandicoot|\'\'Crash Bandicoot\'\' series]] (2002-2004) (2013- )
                [[Skylanders|\'\'Skylanders\'\' series]] (2011-2013)0)"">Guitar Hero|\'\'Guitar Hero\'\' series]] (2007–2010) \n...\n}}\n\nInto\n{{Infobox company\n|1990]]\n|\'\'Guitar Hero\'\' series]] (2007–2010) \n...\n| foundation     = [[1990 in video gaming\n| products       = [[Crash Bandicoot|\'\'Crash Bandicoot\'\' series]] (2002-2004) (2013- )
                [[Skylanders|\'\'Skylanders\'\' series]] (2011-2013) Guitar Hero\n...\n}}\nsplitting the foundation and product parameters.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52991,VisualEditor: Template highlight is sometimes misplaced in the reference inspector,"There appears to be an elusive bug in the references editor where, when a reference contains a template, the blue highlight surrounding the template in the reference is sometimes misplaced outside the references editor and therefore not usable. 
+
+I've seen this myself a couple of times (in Chrome/Ubuntu), and it usually just stopped happening after a while and I'm not able to repro it now, so it may be some kind of timing issue. Robert Rohde also reported this today (July 8) and provided a screenshot of the bug here:
+
+https://upload.wikimedia.org/wikipedia/en/5/5f/Bad_Ref_Edit.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Template highlight is sometimes misplaced in the reference inspector\n\nThere appears to be an elusive bug in the references editor where, when a reference contains a template, the blue highlight surrounding the template in the reference is sometimes misplaced outside the references editor and therefore not usable.', ""I've seen this myself a couple of times (in Chrome/Ubuntu), and it usually just stopped happening after a while and I'm not able to repro it now, so it may be some kind of timing issue."", 'Robert Rohde also reported this today (July 8) and provided a screenshot of the bug here:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+246993,VisualEditor: Template highlight is sometimes misplaced in the reference inspector,"
+
+*** This bug has been marked as a duplicate of bug 50913 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50913 ***'],['ISSUE CONTENT MANAGEMENT']
+52986,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","1) Open an article such as
+https://en.wikipedia.org/wiki/Convex_function?veaction=edit
+2) Click in a non-linked word ""function""
+3) Click in the link button (CTRL+K)
+
+The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided.
+
+Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."")
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50160",task_description,"['VisualEditor should not encourage links of little relevance (e.g.', 'disambiguation pages, already used links, etc..)\n\n1) Open an article such as\nURL\n2) Click in a non-linked word ""function""\n3) Click in the link button (CTRL+K)\n\nThe list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided.', 'Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g.', 'by having a section in the dropdown menu labeled ""Already used links..."")\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', '1)', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+246781,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon.
+
+*** This bug has been marked as a duplicate of bug 50240 ***",task_subcomment,"['This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon.', '*** This bug has been marked as a duplicate of bug 50240 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+246779,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)",See also gerrit change 70564.,task_subcomment,['See also gerrit change 70564.'],['SOLUTION DISCUSSION']
+246776,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","PS: this was inspired by the commit message of
+https://gerrit.wikimedia.org/r/#/c/72646/",task_subcomment,['PS: this was inspired by the commit message of\nURL'],['OBSERVED BUG BEHAVIOR']
+52977,Selecting text does not work,"How to reproduce:
+* Go to https://www.mediawiki.org/wiki/Extension:TimedMediaHandler/Client_download?veaction=edit
+* Set the caret behind ""supported by the Timed Media Handler extension""
+* Try to drag and drop ""Support for Ogg Theora and WebM"" directy to where you have set the caret.
+
+Current behaviour:
+* Selecting not possible (Dropping mode starts immediately like if something is selected but the caret suggests that nothing was selected)
+
+Expected behaviour:
+* I can select ""Support for Ogg Theora and WebM""
+
+----
+You receive this bug's description kindly in English.
+Rainer Rillke
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['Selecting text does not work\n\nHow to reproduce:\n* Go to URL\n* Set the caret behind ""supported by the Timed Media Handler extension""\n* Try to drag and drop ""Support for Ogg Theora and WebM"" directy to where you have set the caret.', 'Current behaviour:\n* Selecting not possible (Dropping mode starts immediately like if something is selected but the caret suggests that nothing was selected)\n\nExpected behaviour:\n* I can select ""Support for Ogg Theora and WebM""\n\n----\nYou receive this bug\'s description kindly in English.', 'Rainer Rillke\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246291,Selecting text does not work,"Hey, sorry for the confusion; merging with bug 50643 which is about disabling Firefox's misleading interface.
+
+*** This bug has been marked as a duplicate of bug 50643 ***",task_subcomment,"[""Hey, sorry for the confusion; merging with bug 50643 which is about disabling Firefox's misleading interface."", '*** This bug has been marked as a duplicate of bug 50643 ***']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+246288,Selecting text does not work,Selecting text works at the page you provided but drag and drop does not work.,task_subcomment,['Selecting text works at the page you provided but drag and drop does not work.'],['BUG REPRODUCTION']
+246283,Selecting text does not work,"(In reply to comment #3)
+> try it on another page like
+Selecting text work at the page your provided but drag and drop does not work.
+----
+You receive this bug's description kindly in English.
+Rainer Rillke",task_subcomment,"['(In reply to comment #3)\nQUOTE\nSelecting text work at the page your provided but drag and drop does not work.', ""----\nYou receive this bug's description kindly in English."", 'Rainer Rillke']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246277,Selecting text does not work,"(In reply to comment #3)
+I tried editing 2 pages on MediaWiki wiki so far and it did not work as I expected. If it can't deal with  tags, it must be disabled on these pages. Thank you.",task_subcomment,"['(In reply to comment #3)\nI tried editing 2 pages on MediaWiki wiki so far and it did not work as I expected.', ""If it can't deal with  tags, it must be disabled on these pages."", 'Thank you.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+246272,Selecting text does not work,"It seems related to the  tag, try it on another page like https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet",task_subcomment,"['It seems related to the  tag, try it on another page like URL']",['OBSERVED BUG BEHAVIOR']
+246269,Selecting text does not work,"As selecting text is a basic operation, bumping to a major issue.",task_subcomment,"['As selecting text is a basic operation, bumping to a major issue.']",['OBSERVED BUG BEHAVIOR']
+246265,Selecting text does not work,FF 22,task_subcomment,['FF 22'],['SOLUTION DISCUSSION']
+52975,Please turn off VisualEditor as long as it doesn't work,"There are so many things that do not work, I suggest to test the software better before deploying. I will open a second ticket for a new recent issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Please turn off VisualEditor as long as it doesn't work\n\nThere are so many things that do not work, I suggest to test the software better before deploying."", 'I will open a second ticket for a new recent issue.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'POTENTIAL NEW ISSUES AND REQUESTS', 'OBSERVED BUG BEHAVIOR']"
+246148,Please turn off VisualEditor as long as it doesn't work,"> especially as you are not forced to use it.
+If a button (""Edit"") that previously did something else, now shows VE, it is ""forcing"" IMHO.
+
+I think VE will be a great tool but as with UploasWizard please understand the community is not a playground.",task_subcomment,"['QUOTE\nIf a button (""Edit"") that previously did something else, now shows VE, it is ""forcing"" IMHO.', 'I think VE will be a great tool but as with UploasWizard please understand the community is not a playground.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+246143,Please turn off VisualEditor as long as it doesn't work,"(In reply to comment #0)
+> There are so many things that do not work
+
+I cannot elaborate on the deployment schedule here, but I'm pretty sure that it's been explained on https://www.mediawiki.org/wiki/VisualEditor/Feedback recently, as you're not the only person with that impression. :)
+
+I suggest to test the software better before deploying.
+
+See above - testing has taken place for months.
+
+There are no plans to turn VE off currently, especially as you are not forced to use it.",task_subcomment,"[""(In reply to comment #0)\nQUOTE\n\nI cannot elaborate on the deployment schedule here, but I'm pretty sure that it's been explained on URL recently, as you're not the only person with that impression."", ':)\n\nI suggest to test the software better before deploying.', 'See above - testing has taken place for months.', 'There are no plans to turn VE off currently, especially as you are not forced to use it.']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+52974,Redlinks show up as bluelinks in VisualEditor mode,"If there is a link to an non-existent article or page it shows up in red when viewing a page.  When you click to edit with VisualEditor, the redlink shows up as blue which makes it appear that it is linking to a page that has already been created. 
+
+For example, in my sandbox I created a link to the non-existent page ""testinggg"" using [[testinggg]] in source.  After saving the page I returned to the sandbox and saw the link in red.  I clicked to edit the page with VisualEditor, and the link turned blue.  It should remain red if the page has not yet been created.  You can try this for yourself in my sandbox:
+
+https://en.wikipedia.org/wiki/User:Keegan_(WMF)/Sandbox
+
+This may be a Parsoid issue?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Redlinks show up as bluelinks in VisualEditor mode\n\nIf there is a link to an non-existent article or page it shows up in red when viewing a page.', 'When you click to edit with VisualEditor, the redlink shows up as blue which makes it appear that it is linking to a page that has already been created.', 'For example, in my sandbox I created a link to the non-existent page ""testinggg"" using [[testinggg]] in source.', 'After saving the page I returned to the sandbox and saw the link in red.', 'I clicked to edit the page with VisualEditor, and the link turned blue.', 'It should remain red if the page has not yet been created.', 'You can try this for yourself in my sandbox:\n\nURL\n\nThis may be a Parsoid issue?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246102,Redlinks show up as bluelinks in VisualEditor mode,"
+
+*** This bug has been marked as a duplicate of bug 37901 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 37901 ***'],['ACTION ON ISSUE']
+52946,VisualEditor: line endings are not preserved when copying from a text file,"I tried to copy text from a plain text file (in the Kate editor). The line endings were not preserved and the whole text was copied as one big paragraph.
+
+You can see an example here:
+https://www.mediawiki.org/w/index.php?title=Language_portal/Definition_of_Done&oldid=726988
+
+It's the first version of a page that I created in the VisualEditor. I formatted the first few lines manually, but left the blob in the end as is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: line endings are not preserved when copying from a text file\n\nI tried to copy text from a plain text file (in the Kate editor).', 'The line endings were not preserved and the whole text was copied as one big paragraph.', ""You can see an example here:\nURL\n\nIt's the first version of a page that I created in the VisualEditor."", 'I formatted the first few lines manually, but left the blob in the end as is.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244363,VisualEditor: line endings are not preserved when copying from a text file,"This should be fixed up by the fixing of bug 33105.
+
+*** This bug has been marked as a duplicate of bug 33105 ***",task_subcomment,"['This should be fixed up by the fixing of bug 33105.', '*** This bug has been marked as a duplicate of bug 33105 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52915,context specific editor for templates?,"On English Wikipedia, it is stated that some common templates need a context specific editor. 
+
+Examples offered by (and with explanatory text by) User:Clem Rutter
+
+****
+
+*[[Template:convert]]
+([[Template:frac]]
+Those are simple- all we need is to display the parameters so they can be changed, when focus is lost they just display. For useability you could enter the the inline-template-editor by double clicking or ctrl-shift -click.
+
+*[[Template:fact]]
+*[[Template:cn]]
+These two are more complex as editors are there to change the *cn to a reference- of which the *sfn template is ideal. So here on a double-click, you need to change a *cn to a *sfn and enter the inline-template-editor to add the fields which are Name|Year|pp=page-lastpage. For a sfn, on leaving, you need an alert that offers to take you to the reflist to confirm or edit if that reference is missing.
+
+*[[Template:sfn]]
+Explained above.
+
+*[[Template:efn]]
+Simplicity- there is only one parameter. Though an alert may be needed if the Notes {*{notelist|notes=}*} structure is not in place.
+
+*[[Template:reflist]]-
+fiendishly complex from a programming pov but functionally simple- as the functionality we need is
+add a line in wiki code- I C&P common ones from a master list of commonly used texts in field that I keep in a subpage, or as a textfile on the desktop. An easy technique to teach when you are training at a museum or library as you can give your students the file on usbstick
+change some data- for instance an isbn number
+this can be achieved in a popup wikicode editor- or even gedit, vi, geaney, wordpad as no parsing is required.
+
+([[Template:infobox]]
+it is totally essential to just be able to change the content of a field visually. It is desirable to add new fields but this is of lower priority nigh essential, and this wont be achieved until the issue of recursive templates is resolved. (That rates as essential on my list.)
+
+
+I leave the list there for a Linus test, so if you could pass this on to your dev team and ask them to add these to the functional specification. Here is an example of a sample edit for them to try Swanley it keeps coming up on my watchlist:
+
+*first three references contain raw urls- probably could do with a *cite template her- not mentioned above
+*fix a *cn
+*change item in infobox
+*convert acres to hectares needed
+
+All of that could be easily achievable.-- Clem Rutter (talk) 18:20, 5 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['context specific editor for templates?', 'On English Wikipedia, it is stated that some common templates need a context specific editor.', 'Examples offered by (and with explanatory text by) User:Clem Rutter\n\n****\n\n*[[Template:convert]]\n([[Template:frac]]\nThose are simple- all we need is to display the parameters so they can be changed, when focus is lost they just display.', 'For useability you could enter the the inline-template-editor by double clicking or ctrl-shift -click.', '*[[Template:fact]]\n*[[Template:cn]]\nThese two are more complex as editors are there to change the *cn to a reference- of which the *sfn template is ideal.', 'So here on a double-click, you need to change a *cn to a *sfn and enter the inline-template-editor to add the fields which are Name|Year|pp=page-lastpage.', 'For a sfn, on leaving, you need an alert that offers to take you to the reflist to confirm or edit if that reference is missing.', '*[[Template:sfn]]\nExplained above.', '*[[Template:efn]]\nSimplicity- there is only one parameter.', 'Though an alert may be needed if the Notes {*{notelist|notes=}*} structure is not in place.', '*[[Template:reflist]]-\nfiendishly complex from a programming pov but functionally simple- as the functionality we need is\nadd a line in wiki code- I C&P common ones from a master list of commonly used texts in field that I keep in a subpage, or as a textfile on the desktop.', 'An easy technique to teach when you are training at a museum or library as you can give your students the file on usbstick\nchange some data- for instance an isbn number\nthis can be achieved in a popup wikicode editor- or even gedit, vi, geaney, wordpad as no parsing is required.', '([[Template:infobox]]\nit is totally essential to just be able to change the content of a field visually.', 'It is desirable to add new fields but this is of lower priority nigh essential, and this wont be achieved until the issue of recursive templates is resolved.', '(That rates as essential on my list.)', 'I leave the list there for a Linus test, so if you could pass this on to your dev team and ask them to add these to the functional specification.', 'Here is an example of a sample edit for them to try Swanley it keeps coming up on my watchlist:\n\n*first three references contain raw urls- probably could do with a *cite template her- not mentioned above\n*fix a *cn\n*change item in infobox\n*convert acres to hectares needed\n\nAll of that could be easily achievable.-- Clem Rutter (talk) 18:20, 5 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+242508,context specific editor for templates?,"This is a WONTFIX; VisualEditor is not specific to the English Wikipedia, and it is neither appropriate nor sane to create specific dialogs for each of the thousands of templates on hundreds of wikis.",task_subcomment,"['This is a WONTFIX; VisualEditor is not specific to the English Wikipedia, and it is neither appropriate nor sane to create specific dialogs for each of the thousands of templates on hundreds of wikis.']",['SOLUTION DISCUSSION']
+52909,VisualEditor: Template editor turns links into [[link|name]] in CE,"screenshot of CE after transclusion editor
+
+https://en.wikipedia.org/wiki/Luton?veaction=edit
+
+Edit the infobox template. Don't do anything, but apply changes. A lot of the blue links in the infobox are now rendered as black pipe code, for example [[List of towns in the United Kingdom|Town]] instead of Town.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11424}",task_description,"['VisualEditor: Template editor turns links into [[link|name]] in CE\n\nscreenshot of CE after transclusion editor\n\nURL\n\nEdit the infobox template.', ""Don't do anything, but apply changes."", 'A lot of the blue links in the infobox are now rendered as black pipe code, for example [[List of towns in the United Kingdom|Town]] instead of Town.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11424}']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242159,VisualEditor: Template editor turns links into [[link|name]] in CE,"
+
+*** This bug has been marked as a duplicate of bug 50801 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50801 ***'],['ISSUE CONTENT MANAGEMENT']
+52907,VisualEditor: The anchor for the template editor can easily become invisible,"Take a page with a reasonably sized infobox.
+Make your browser window 11"" size or something
+Scroll down a bit
+Click the infobox
+
+The infobox has become selected, but the anchor for the editor, being in the top right, is often out of view well under the toolbar. This leaves the user without a proper hint.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: The anchor for the template editor can easily become invisible\n\nTake a page with a reasonably sized infobox.', 'Make your browser window 11"" size or something\nScroll down a bit\nClick the infobox\n\nThe infobox has become selected, but the anchor for the editor, being in the top right, is often out of view well under the toolbar.', 'This leaves the user without a proper hint.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242091,VisualEditor: The anchor for the template editor can easily become invisible,"@Chris, yes, they are the same.
+
+*** This bug has been marked as a duplicate of bug 49922 ***",task_subcomment,"['SCREEN_NAME, yes, they are the same.', '*** This bug has been marked as a duplicate of bug 49922 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+242087,VisualEditor: The anchor for the template editor can easily become invisible,Is this the same as bug 49922?,task_subcomment,['Is this the same as bug 49922?'],['MOTIVATION']
+52903,VisualEditor: Save dialog behaves as partial modal,"In some respects the save dialog is partially modal, which is a strange and unfamiliar concept to some.
+
+The content is not editable, and partly blurred. Yet I can click links inside the content. The buttons in the toolbar have a functioning look, but don't actually work. Also, when clicking outside this dialog, I would expect it to dismiss, but it doesn't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Save dialog behaves as partial modal\n\nIn some respects the save dialog is partially modal, which is a strange and unfamiliar concept to some.', 'The content is not editable, and partly blurred.', 'Yet I can click links inside the content.', ""The buttons in the toolbar have a functioning look, but don't actually work."", ""Also, when clicking outside this dialog, I would expect it to dismiss, but it doesn't."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241906,VisualEditor: Save dialog behaves as partial modal,"This is an artefact of not being a ""proper"" dialog, which is bug 48566 - we hope to fix that in the next week or so. Sorry for the delay in triaging.
+
+*** This bug has been marked as a duplicate of bug 48566 ***",task_subcomment,"['This is an artefact of not being a ""proper"" dialog, which is bug 48566 - we hope to fix that in the next week or so.', 'Sorry for the delay in triaging.', '*** This bug has been marked as a duplicate of bug 48566 ***']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+241901,VisualEditor: Save dialog behaves as partial modal,"Oh, and you can select and copy and paste text from the disabled edit surface, when the save dialog is open.",task_subcomment,"['Oh, and you can select and copy and paste text from the disabled edit surface, when the save dialog is open.']",['SOLUTION USAGE']
+52835,Nested s considered harmful,"Sometimes Parsoid will wrap a  around an existing ; this is generally a bad idea, even if we have dirtied the reference in VisualEditor. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Your_Face_Sounds_Familiar_%28UK_TV_series%29&diff=562149606&oldid=562149387",task_description,"['Nested s considered harmful\n\nSometimes Parsoid will wrap a  around an existing ; this is generally a bad idea, even if we have dirtied the reference in VisualEditor.', ':-)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237831,Nested s considered harmful,*** Bug 50724 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50724 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237825,Nested s considered harmful,"Change 72971 merged by jenkins-bot:
+Try #2: (Bug 50835) Dont nowiki escape already escaped tpl params
+
+https://gerrit.wikimedia.org/r/72971",task_subcomment,['Change 72971 merged by jenkins-bot:\nTry #2: (Bug 50835) Dont nowiki escape already escaped tpl params\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237819,Nested s considered harmful,"Change 72971 had a related patch set uploaded by Subramanya Sastry:
+Try #2: (Bug 50835) Dont nowiki escape already escaped tpl params
+
+https://gerrit.wikimedia.org/r/72971",task_subcomment,['Change 72971 had a related patch set uploaded by Subramanya Sastry:\nTry #2: (Bug 50835) Dont nowiki escape already escaped tpl params\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+237815,Nested s considered harmful,"Change 72230 merged by jenkins-bot:
+(Bug 50835) Dont nowiki escape already escaped template params
+
+https://gerrit.wikimedia.org/r/72230",task_subcomment,['Change 72230 merged by jenkins-bot:\n(Bug 50835) Dont nowiki escape already escaped template params\n\nGERRIT_URL'],['BUG REPRODUCTION']
+237811,Nested s considered harmful,"Change 72230 had a related patch set uploaded by Subramanya Sastry:
+(Bug 50835) Dont nowiki escape already escaped template params
+
+https://gerrit.wikimedia.org/r/72230",task_subcomment,['Change 72230 had a related patch set uploaded by Subramanya Sastry:\n(Bug 50835) Dont nowiki escape already escaped template params\n\nGERRIT_URL'],['BUG REPRODUCTION']
+52828,VisualEditor: edits fail on hitting the abuse filter (with a cryptic error message),"If a user triggers the abusefilter through the VE, they're informed ""'''Error:''' The modification you tried to make was aborted by an extension hook"".
+
+Probably not helpful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: edits fail on hitting the abuse filter (with a cryptic error message)\n\nIf a user triggers the abusefilter through the VE, they\'re informed ""\'\'\'Error:\'\'\' The modification you tried to make was aborted by an extension hook"".', 'Probably not helpful.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237369,VisualEditor: edits fail on hitting the abuse filter (with a cryptic error message),"
+
+*** This bug has been marked as a duplicate of bug 50472 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50472 ***'],['ACTION ON ISSUE']
+52817,Keyboard shortcut for editing source,"With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page.  Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Keyboard shortcut for editing source\n\nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page.', 'Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+236795,Keyboard shortcut for editing source,"Sorry about this; we fixed this just a few hours ago. Merging with the other report.
+
+*** This bug has been marked as a duplicate of bug 50725 ***",task_subcomment,"['Sorry about this; we fixed this just a few hours ago.', 'Merging with the other report.', '*** This bug has been marked as a duplicate of bug 50725 ***']","['ACTION ON ISSUE', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+52797,Whitespace immediately before a template at the start of the page is swallowed and so unremoveable,"Try removing the whitespace at the top of https://en.wikipedia.org/wiki/Burr%E2%80%93Hamilton_duel and see what happens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid.wmflabs.org/en/User:Jdforrester_(WMF)/Bug_50797?oldid=564303673",task_description,"['Whitespace immediately before a template at the start of the page is swallowed and so unremoveable\n\nTry removing the whitespace at the top of URL and see what happens.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235665,Whitespace immediately before a template at the start of the page is swallowed and so unremoveable,"http://en.wikipedia.org/w/index.php?title=Burr%E2%80%93Hamilton_duel&oldid=561095260&veaction=edit shows the whitespace, and it also seems to be possible to delete a line there by focusing it and pressing 'delete'. Newlines that don't produce a paragraph are also preserved in HTML, but are not editable in wikitext.
+
+See the source of http://parsoid.wmflabs.org/en/Burr%E2%80%93Hamilton_duel?oldid=561095260, in which the first paragraph after the infobox starts with ""

                "".
+
+Closing as worksforme. Please open a bug against VE if you have trouble with focusing or deleting the 
                .",task_subcomment,"[""URL shows the whitespace, and it also seems to be possible to delete a line there by focusing it and pressing 'delete'."", ""Newlines that don't produce a paragraph are also preserved in HTML, but are not editable in wikitext."", 'See the source of URL in which the first paragraph after the infobox starts with ""

                "".', 'Closing as worksforme.', 'Please open a bug against VE if you have trouble with focusing or deleting the 
                .']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'BUG REPRODUCTION']"
+235659,Whitespace immediately before a template at the start of the page is swallowed and so unremoveable,"So, to understand this bug - this is about where is some (mistaken/wrong) wikitext with an extra new line in front of a block template that gets swallowed by Parsoid into the template that follows it (but can't be removed from there as Parsoid quietly hides that)?
+
+(Note that the second extra whitespace is a normal 
                 and so shown in VisualEditor as a ""↵"" and can be removed in-line.)",task_subcomment,"[""So, to understand this bug - this is about where is some (mistaken/wrong) wikitext with an extra new line in front of a block template that gets swallowed by Parsoid into the template that follows it (but can't be removed from there as Parsoid quietly hides that)?"", '(Note that the second extra whitespace is a normal 
                 and so shown in VisualEditor as a ""↵"" and can be removed in-line.)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235651,Whitespace immediately before a template at the start of the page is swallowed and so unremoveable,"Permanent link to the relevant page revision:
+
+http://en.wikipedia.org/w/index.php?title=Burr%E2%80%93Hamilton_duel&oldid=561095260",task_subcomment,['Permanent link to the relevant page revision:\n\nURL'],['SOLUTION DISCUSSION']
+235644,Whitespace immediately before a template at the start of the page is swallowed and so unremoveable,"This is NOT a duplicate of 47790
+
+This bug is about whitespace in the SOURCE, that is not editable in the VE. Where 47790 deals about whitespace in VE that is not in the source.
+
+If you look at https://en.wikipedia.org/wiki/Burr–Hamilton_duel you will see that the first line is slightly below the infobox. In VE mode, https://en.wikipedia.org/wiki/Burr–Hamilton_duel?veaction=edit they look to be at the same height. The linebreaks at the top of the source seem to have been 'compressed' and are ignored in VE, while they do have effect in render mode.",task_subcomment,"['This is NOT a duplicate of 47790\n\nThis bug is about whitespace in the SOURCE, that is not editable in the VE.', 'Where 47790 deals about whitespace in VE that is not in the source.', 'If you look at URL you will see that the first line is slightly below the infobox.', 'In VE mode, URL they look to be at the same height.', ""The linebreaks at the top of the source seem to have been 'compressed' and are ignored in VE, while they do have effect in render mode.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235635,Whitespace immediately before a template at the start of the page is swallowed and so unremoveable,"
+
+*** This bug has been marked as a duplicate of bug 47790 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 47790 ***'],['ACTION ON ISSUE']
+52766,VisualEditor: VE's determination of image size should hook into user preferences,"We very deliberately have user-specific preferences for default image sizing, rather than specify a fixed size in each article - it compensates for varying screen sizes. The VE isn't factoring default size preferences into account.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: VE's determination of image size should hook into user preferences\n\nWe very deliberately have user-specific preferences for default image sizing, rather than specify a fixed size in each article - it compensates for varying screen sizes."", ""The VE isn't factoring default size preferences into account."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233785,VisualEditor: VE's determination of image size should hook into user preferences,Related to bug 47804 too.,task_subcomment,['Related to bug 47804 too.'],['OBSERVED BUG BEHAVIOR']
+233780,VisualEditor: VE's determination of image size should hook into user preferences,"
+
+*** This bug has been marked as a duplicate of bug 50379 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50379 ***'],['ISSUE CONTENT MANAGEMENT']
+52753,VisualEditor: edit conflict handling,"In the case of an edit conflict, the structure of the VE means that the common workaround (taking discrete wikimarkup changes, copying them, opening the newly revised article, pasting them in) doesn't work. What's the plan to handle ECs in the VE?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: edit conflict handling\n\nIn the case of an edit conflict, the structure of the VE means that the common workaround (taking discrete wikimarkup changes, copying them, opening the newly revised article, pasting them in) doesn't work."", ""What's the plan to handle ECs in the VE?"", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']"
+233036,VisualEditor: edit conflict handling,"(In reply to comment #0)
+> In the case of an edit conflict, the structure of the VE means that the
+> common workaround (taking discrete wikimarkup changes, copying them, opening
+> the newly revised article, pasting them in) doesn't work. What's the plan to
+> handle ECs in the VE?
+
+What do you mean, 'plan'? Have you not encountered one yet? It works very simply: on saving, you get a message like ""Sorry, the page couldn't be saved because of an edit conflict. Click here to resolve manually"" and then takes you to the normal wikitext edit conflict page, with the wikitext of your new version below and the new current version above, as always.
+
+It's been this way for months. There are enough bugs filed without adding ones. :-)",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat do you mean, 'plan'?"", 'Have you not encountered one yet?', 'It works very simply: on saving, you get a message like ""Sorry, the page couldn\'t be saved because of an edit conflict.', 'Click here to resolve manually"" and then takes you to the normal wikitext edit conflict page, with the wikitext of your new version below and the new current version above, as always.', ""It's been this way for months."", 'There are enough bugs filed without adding ones.', ':-)']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+52744,"VisualEditor: Once a user has inserted a new transclusion, offer to add another","Copied from English Wikipedia:
+
+When I've added one template using the transclusion icon, please offer me a button which says ""Add another template"", rather than insisting I click on various totally non-intuitive bits of the window to achieve this! I've just managed to add two separate stub templates, but it was still an uphill struggle. PamD 07:32, 4 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Once a user has inserted a new transclusion, offer to add another\n\nCopied from English Wikipedia:\n\nWhen I\'ve added one template using the transclusion icon, please offer me a button which says ""Add another template"", rather than insisting I click on various totally non-intuitive bits of the window to achieve this!', ""I've just managed to add two separate stub templates, but it was still an uphill struggle."", 'PamD 07:32, 4 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+232406,"VisualEditor: Once a user has inserted a new transclusion, offer to add another","Re-worded the summary; I don't think that this is a route we want to go, so marking as a WONTFIX.",task_subcomment,"[""Re-worded the summary; I don't think that this is a route we want to go, so marking as a WONTFIX.""]",['ACTION ON ISSUE']
+232400,"VisualEditor: Once a user has inserted a new transclusion, offer to add another","Maggie: Feel free to drop ""Enhancement request:"" from the report summary and to set severity to ""enhancement"" instead. Thanks. :)",task_subcomment,"['Maggie: Feel free to drop ""Enhancement request:"" from the report summary and to set severity to ""enhancement"" instead.', 'Thanks.', ':)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52738,VisualEditor: Template inspector's parameter display causes smushing,"See https://en.wikipedia.org/wiki/File:VisualEditor_-_Cite_template_layout_issue_%28TemplateData%29.png - Firefox 22, Monobook.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Template inspector's parameter display causes smushing\n\nSee URL - Firefox 22, Monobook."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232107,VisualEditor: Template inspector's parameter display causes smushing,"
+
+%%%*** This bug has been marked as a duplicate of bug 50728 ***%%%",task_subcomment,['\n\n%%%*** This bug has been marked as a duplicate of bug 50728 ***%%%'],['ACTION ON ISSUE']
+52737,VisualEditor: not showing new categories on reload,"If you add categories to a page and save, the newly-loaded version does not include the new additions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: not showing new categories on reload\n\nIf you add categories to a page and save, the newly-loaded version does not include the new additions.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232077,VisualEditor: not showing new categories on reload,"Yeah, this would be a good one to fix; merging with duplicate.
+
+*** This bug has been marked as a duplicate of bug 48560 ***",task_subcomment,"['Yeah, this would be a good one to fix; merging with duplicate.', '*** This bug has been marked as a duplicate of bug 48560 ***']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+232073,VisualEditor: not showing new categories on reload,"An additional note about this on English Wikipedia, with the sensible suggestion that editors are likely to think they have done something wrong when they save the page and their changes do not appear to have worked.",task_subcomment,"['An additional note about this on English Wikipedia, with the sensible suggestion that editors are likely to think they have done something wrong when they save the page and their changes do not appear to have worked.']",['SOLUTION DISCUSSION']
+52724, added to existing  content,"This edit:
+
+https://en.wikipedia.org/w/index.php?title=Percy_Jackson:_Sea_of_Monsters&diff=562794756&oldid=562792500
+
+is an example of a dirty diff where VisualEditor/Parsoid appears to have wrapped  tags around existing  content (in this case the ""|"" symbol in the title of a cited website) inside a template inside a reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[' added to existing  content\n\nThis edit:\n\nURL\n\nis an example of a dirty diff where VisualEditor/Parsoid appears to have wrapped  tags around existing  content (in this case the ""|"" symbol in the title of a cited website) inside a template inside a reference.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+231259, added to existing  content,"
+
+*** This bug has been marked as a duplicate of bug 50835 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50835 ***'],['ISSUE CONTENT MANAGEMENT']
+231256, added to existing  content,"Other example:
+http://en.wikipedia.org/w/index.php?title=Beximco&diff=562685500&oldid=562676888",task_subcomment,['Other example:\nURL'],['SOLUTION DISCUSSION']
+52709,VisualEditor: alt text?,"I can't seem to find a way to add alt text to images, which is pretty important from an accessibility POV. Any mechanism I'm missing?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: alt text?', ""I can't seem to find a way to add alt text to images, which is pretty important from an accessibility POV."", ""Any mechanism I'm missing?"", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+255304,VisualEditor: alt text?,"
+
+*** This bug has been marked as a duplicate of bug 38129 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 38129 ***'],['ISSUE CONTENT MANAGEMENT']
+52684,Template auto-filled with wikitext on edit,"This came from the VisualEditor feedback page in Hebrew. I couldn't replicate, but the problem is evident in this diff:
+
+http://he.wikipedia.org/w/index.php?title=%D7%A2%D7%96%D7%99_%D7%90%D7%99%D7%96%D7%91%D7%99%D7%A6%D7%A7%D7%99&diff=14341709&oldid=14341704
+
+The user only changed the link at line 20 (blue, left) but VE seemed to have injected a bunch of wikitext into the template box above.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Template auto-filled with wikitext on edit\n\nThis came from the VisualEditor feedback page in Hebrew.', ""I couldn't replicate, but the problem is evident in this diff:\n\nURL\n\nThe user only changed the link at line 20 (blue, left) but VE seemed to have injected a bunch of wikitext into the template box above."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253910,Template auto-filled with wikitext on edit,"After talking to gwicke, this seems to be a temporary bug either related to some caching problem or an issue that was resolved, since it cannot be replicated and a lot of other updates were done that fixed related problems.
+
+Closed as likely fixed.",task_subcomment,"['After talking to gwicke, this seems to be a temporary bug either related to some caching problem or an issue that was resolved, since it cannot be replicated and a lot of other updates were done that fixed related problems.', 'Closed as likely fixed.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+253904,Template auto-filled with wikitext on edit,"I couldnt reproduce it on
+https://he.wikipedia.org/wiki/User:John_Vandenberg/test
+
+I cant find any bug for visualeditor dumping in a subst:ed copy of a template.  Very strange.",task_subcomment,"['I couldnt reproduce it on\nURL\n\nI cant find any bug for visualeditor dumping in a subst:ed copy of a template.', 'Very strange.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52675,VisualEditor: Inherited category becomes explicitly invoked,"This null edit to an article (https://en.wikipedia.org/w/index.php?title=List_of_Sam_%26_Cat_episodes&diff=562710419&oldid=562703260) made the category hidden inside of a template in use on the page (template in question: http://en.wikipedia.org/wiki/Template:Episode_list) visible in the editor. It should not be visible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Inherited category becomes explicitly invoked\n\nThis null edit to an article (URL made the category hidden inside of a template in use on the page (template in question: URL visible in the editor.', 'It should not be visible.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253429,VisualEditor: Inherited category becomes explicitly invoked,This was a bug in DM/Parsoid interaction that we fixed months ago; apologies for the slowness of updating.,task_subcomment,['This was a bug in DM/Parsoid interaction that we fixed months ago; apologies for the slowness of updating.'],['OBSERVED BUG BEHAVIOR']
+253424,VisualEditor: Inherited category becomes explicitly invoked,Another example: https://fr.wikipedia.org/w/index.php?diff=94601807,task_subcomment,['Another example: URL'],['SOLUTION DISCUSSION']
+52653,Section 0 (lede) editing does not offer VisualEditor,"**Author:** `wikipedia`
+
+**Description:**
+Using the [edit] next to the lede (section=0) only allows invoking the source editor.
+
+Ideally there should be consistency, and VE options should either be always shown, or never shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Section 0 (lede) editing does not offer VisualEditor\n\n**Author:** CODE\n\n**Description:**\nUsing the [edit] next to the lede (section=0) only allows invoking the source editor.', 'Ideally there should be consistency, and VE options should either be always shown, or never shown.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252191,Section 0 (lede) editing does not offer VisualEditor,"ve.init.mw.ViewPageTarget.prototype.setupSectionEditLinks in /modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js in mediawiki/extensions/VisualEditor.
+
+(It's painful to look at.)",task_subcomment,"['ve.init.mw.ViewPageTarget.prototype.setupSectionEditLinks in /modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js in mediawiki/extensions/VisualEditor.', ""(It's painful to look at.)""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252185,Section 0 (lede) editing does not offer VisualEditor,I recall the pertinent gerrit revision as being https://gerrit.wikimedia.org/r/#/c/69984/ which should give some pointers.,task_subcomment,['I recall the pertinent gerrit revision as being URL which should give some pointers.'],['OBSERVED BUG BEHAVIOR']
+252179,Section 0 (lede) editing does not offer VisualEditor,Can someone point me to the code that is building the VE edit section links ?,task_subcomment,['Can someone point me to the code that is building the VE edit section links ?'],['OBSERVED BUG BEHAVIOR']
+252175,Section 0 (lede) editing does not offer VisualEditor,"**wikipedia** wrote:
+
+Forwarded to:
+
+  http://en.wikipedia.org/wiki/User_talk:TheDJ#edittop.js:_VisualEditor",task_subcomment,['**wikipedia** wrote:\n\nForwarded to:\n\n  URL'],['OBSERVED BUG BEHAVIOR']
+252170,Section 0 (lede) editing does not offer VisualEditor,"The gadgets are maintained by volunteer developers (in this case, TheDJ). It's the responsibility of gadget authors to ensure compatibility with MediaWiki, not the responsibility of MediaWiki developers to ensure compatibility with gadgets. We have ~700 projects, many of which will have their own gadgets; ensuring everything we deploy is always compatible with every one of them is to tie us into knots.",task_subcomment,"['The gadgets are maintained by volunteer developers (in this case, TheDJ).', ""It's the responsibility of gadget authors to ensure compatibility with MediaWiki, not the responsibility of MediaWiki developers to ensure compatibility with gadgets."", 'We have ~700 projects, many of which will have their own gadgets; ensuring everything we deploy is always compatible with every one of them is to tie us into knots.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'FUTURE PLAN']"
+252164,Section 0 (lede) editing does not offer VisualEditor,"**wikipedia** wrote:
+
+As of 2013-07-03 11:42 BST, there were 22,009 accounts with gadgets-edittop enabled.",task_subcomment,"['**wikipedia** wrote:\n\nAs of 2013-07-03 11:42 BST, there were 22,009 accounts with gadgets-edittop enabled.']",['OBSERVED BUG BEHAVIOR']
+52651,VisualEditor: image resizing causing implosion,"See https://en.wikipedia.org/wiki/File:Visual_Editor_-_Implosion_screenshot_for_bugreport.png - it only seems to appear if you have previously resized a different image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: image resizing causing implosion\n\nSee URL - it only seems to appear if you have previously resized a different image.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252074,VisualEditor: image resizing causing implosion,"[17:29]  Could anyone mark bug 50651 as resolved? I think some new rollout fixed the issue since it no longer occurs (Ironholds reported it for me, so i cannot edit its status).
+[17:30]  Resolved fixed?
+[17:30]  !b 50651
+[17:30]  https://bugzilla.wikimedia.org/50651
+[17:30]  Yes, confirmed that the problem no longer occurs.
+[17:30]  Kk",task_subcomment,"['[17:29]  Could anyone mark bug 50651 as resolved?', 'I think some new rollout fixed the issue since it no longer occurs (Ironholds reported it for me, so i cannot edit its status).', '[17:30]  Resolved fixed?', '[17:30]  !b 50651\n[17:30]  URL\n[17:30]  Yes, confirmed that the problem no longer occurs.', '[17:30]  Kk']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52642,Unify post-edit notifications on Wikimedia wikis,"There are currently two similar, but distinct post-edit notifications on some Wikimedia wikis. I'll attach screenshots from  momentarily.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",task_description,"['Unify post-edit notifications on Wikimedia wikis\n\nThere are currently two similar, but distinct post-edit notifications on some Wikimedia wikis.', ""I'll attach screenshots from  @vssun: Any specific browser? Can't reproduce it in Chrome.
+
+I could able to reproduce with Chrome (Version 27.0.1453.116 m)/windows 7",task_subcomment,['(In reply to comment #1)\nQUOTE\n\nI could able to reproduce with Chrome (Version 27.0.1453.116 m)/windows 7'],['OBSERVED BUG BEHAVIOR']
+246954,VisualEditor: Bad typing/backspacing behaviour for Malayalam,"The bug 50507 is very much related to this. There, the reporter says that the characters ്, െ etc are not allowed to type.
+
+Here the case is different but the characters are same. Characters, ി, ് and േ  (the vowel symbols of malayalam, which are joined together with preceeding consonants) are disappearing when pressing the backspace.",task_subcomment,"['The bug 50507 is very much related to this.', 'There, the reporter says that the characters ്, െ etc are not allowed to type.', 'Here the case is different but the characters are same.', 'Characters, ി, ് and േ  (the vowel symbols of malayalam, which are joined together with preceeding consonants) are disappearing when pressing the backspace.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246948,VisualEditor: Bad typing/backspacing behaviour for Malayalam,Browser was Firefox 22.,task_subcomment,['Browser was Firefox 22.'],['OBSERVED BUG BEHAVIOR']
+246944,VisualEditor: Bad typing/backspacing behaviour for Malayalam,@vssun: Any specific browser? Can't reproduce it in Chrome.,task_subcomment,"['SCREEN_NAME: Any specific browser?', ""Can't reproduce it in Chrome.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52555,"VisualEditor: ""old version"" warning shows when opening VE after a VE edit","Steps to reproduce:
+* edit a page with VE; save
+* edit the same page with VE
+
+Expected result: normal editing, no warning
+Actual result: there's a warning telling the user they're editing an old version of the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: ""old version"" warning shows when opening VE after a VE edit\n\nSteps to reproduce:\n* edit a page with VE; save\n* edit the same page with VE\n\nExpected result: normal editing, no warning\nActual result: there\'s a warning telling the user they\'re editing an old version of the page\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR']
+246464,"VisualEditor: ""old version"" warning shows when opening VE after a VE edit","Yeah, really sorry about this - this is bug 50441. Very high priority in getting this fixed.
+
+*** This bug has been marked as a duplicate of bug 50441 ***",task_subcomment,"['Yeah, really sorry about this - this is bug 50441.', 'Very high priority in getting this fixed.', '*** This bug has been marked as a duplicate of bug 50441 ***']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+52554,VisualEditor: Likely round-trip failure involving categories and transclusion content on [[Michala Petri]],"See http://en.wikipedia.org/w/index.php?title=Michala_Petri&diff=562483360&oldid=562482770
+
+It looks like VE inserted categories and default sort at some random place in the DOM, potentially cutting encapsulated transclusion content in two?
+
+The Parsoid template encapsulation and round-tripping for this page looks fine:
+
+http://parsoid.wmflabs.org/_rt/en/Michala_Petri?oldid=562482770
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Likely round-trip failure involving categories and transclusion content on [[Michala Petri]]\n\nSee URL\n\nIt looks like VE inserted categories and default sort at some random place in the DOM, potentially cutting encapsulated transclusion content in two?', 'The Parsoid template encapsulation and round-tripping for this page looks fine:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+246423,VisualEditor: Likely round-trip failure involving categories and transclusion content on [[Michala Petri]],"
+
+*** This bug has been marked as a duplicate of bug 50120 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50120 ***'],['ISSUE CONTENT MANAGEMENT']
+246417,VisualEditor: Likely round-trip failure involving categories and transclusion content on [[Michala Petri]],"Same issue:
+https://en.wikipedia.org/w/index.php?title=Richard_Mouw&curid=1175244&diff=562498507&oldid=562498198",task_subcomment,['Same issue:\nURL'],['BUG REPRODUCTION']
+52553,"VisualEditor: Dialogs layer under the toolbar, hide close button","I've observed this myself:
+
+Clicking ""Page settings"", or the reference, image, and category buttons in the top right brings up a dialogue box for input. To close this box there is an X in the top right. However, when I am not at the top of the page, this dialogue box pops up beneath the standard editing options. This makes it impossible to close the box without adjusting the screen magnification.
+
+In addition, the opening of these boxes freezes scrolling of the underlying page, which not only furthers the problem above, but is also simply annoying and unnecessary, as I can no longer move to another part of the article I wish to see without closing and reopening the box. Reywas92Talk 03:00, 2 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Dialogs layer under the toolbar, hide close button\n\nI\'ve observed this myself:\n\nClicking ""Page settings"", or the reference, image, and category buttons in the top right brings up a dialogue box for input.', 'To close this box there is an X in the top right.', 'However, when I am not at the top of the page, this dialogue box pops up beneath the standard editing options.', 'This makes it impossible to close the box without adjusting the screen magnification.', 'In addition, the opening of these boxes freezes scrolling of the underlying page, which not only furthers the problem above, but is also simply annoying and unnecessary, as I can no longer move to another part of the article I wish to see without closing and reopening the box.', 'Reywas92Talk 03:00, 2 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246370,"VisualEditor: Dialogs layer under the toolbar, hide close button",This was fixed earlier this month as part of the general clean up of positioning; sorry for the slow response.,task_subcomment,['This was fixed earlier this month as part of the general clean up of positioning; sorry for the slow response.'],['SOLUTION DISCUSSION']
+52550,VisualEditor: Likely ref / transclusion round-trip failure,"This edit was flagged by VE as DOM-differing, and looks like a dirty ref/transclusion:
+
+https://en.wikipedia.org/w/index.php?title=Abolitionism&curid=38894&diff=562492192&oldid=560500423
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Likely ref / transclusion round-trip failure\n\nThis edit was flagged by VE as DOM-differing, and looks like a dirty ref/transclusion:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR']
+246212,VisualEditor: Likely ref / transclusion round-trip failure,Fixed in Roan's DOM dirtying fixes drive in July.,task_subcomment,"[""Fixed in Roan's DOM dirtying fixes drive in July.""]",['BUG REPRODUCTION']
+246207,VisualEditor: Likely ref / transclusion round-trip failure,"(In reply to comment #1)
+> Only difference is the removal of two spaces after equals signs.
+
+In which part of the DOM is this change? An attribute value?",task_subcomment,"['(In reply to comment #1)\nQUOTE\n\nIn which part of the DOM is this change?', 'An attribute value?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246203,VisualEditor: Likely ref / transclusion round-trip failure,Only difference is the removal of two spaces after equals signs.,task_subcomment,['Only difference is the removal of two spaces after equals signs.'],['OBSERVED BUG BEHAVIOR']
+52538,VisualEditor: Feedback form moves and jerks the screen around,"**Author:** `Shirudo`
+
+**Description:**
+While filling out the feedback form, the form jumps down the screen with every keystroke, until it's mostly out of view.  Once there, only the current line that I'm typing in is visible right above the edge, and every few keystrokes (seemingly randomly) make the entire screen jerk up and down quickly.  If I scroll down or drag the form back up so that it's centred again, it just jumps back down once I begin typing again.
+
+If it makes a difference, I'm using Firefox 22 on Fedora 18, with Gnome 3 Fallback.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Feedback form moves and jerks the screen around\n\n**Author:** CODE\n\n**Description:**\nWhile filling out the feedback form, the form jumps down the screen with every keystroke, until it's mostly out of view."", ""Once there, only the current line that I'm typing in is visible right above the edge, and every few keystrokes (seemingly randomly) make the entire screen jerk up and down quickly."", ""If I scroll down or drag the form back up so that it's centred again, it just jumps back down once I begin typing again."", ""If it makes a difference, I'm using Firefox 22 on Fedora 18, with Gnome 3 Fallback."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245261,VisualEditor: Feedback form moves and jerks the screen around,*** Bug 50533 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50533 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245253,VisualEditor: Feedback form moves and jerks the screen around,*** Bug 50602 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50602 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245246,VisualEditor: Feedback form moves and jerks the screen around,Sorry about this bug; we've fixed this and just deployed it live.,task_subcomment,"[""Sorry about this bug; we've fixed this and just deployed it live.""]",['ACTION ON ISSUE']
+245240,VisualEditor: Feedback form moves and jerks the screen around,"Change 71844 merged by jenkins-bot:
+Listen to keypress in ve.ce.surface.$ rather than window
+
+https://gerrit.wikimedia.org/r/71844",task_subcomment,['Change 71844 merged by jenkins-bot:\nListen to keypress in ve.ce.surface.$ rather than window\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+245234,VisualEditor: Feedback form moves and jerks the screen around,"Change 71844 had a related patch set uploaded by Robmoen:
+Listen to keypress in ve.ce.surface.$ rather than window.
+
+https://gerrit.wikimedia.org/r/71844",task_subcomment,"['Change 71844 had a related patch set uploaded by Robmoen:\nListen to keypress in ve.ce.surface.$ rather than window.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+245227,VisualEditor: Feedback form moves and jerks the screen around,"This has also been reported on Firefox 22/Windows 7, and by a third user who hasn't specified browser/OS.",task_subcomment,"[""This has also been reported on Firefox 22/Windows 7, and by a third user who hasn't specified browser/OS.""]",['OBSERVED BUG BEHAVIOR']
+245220,VisualEditor: Feedback form moves and jerks the screen around,This sounds really unhelpful; sorry about this.,task_subcomment,['This sounds really unhelpful; sorry about this.'],['SOLUTION DISCUSSION']
+52529,IME selector appears when the VisualEditor headings style selector is clicked,"Enter a wiki with VE and ULS. (Enable ULS in preferences if needed.)
+
+Start editing a page using VE. Press the headings style dropdown.
+
+Observed: IME selector appears near the dropdown.
+
+Expected: IME selector must not appear. It's not a place for writing things.
+
+Background: there's an  element hiding there to capture click events (according to Roan).
+
+https://gerrit.wikimedia.org/r/#/c/68339/ may be able to fix it (though some modifications may be needed).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: ve",task_description,"['IME selector appears when the VisualEditor headings style selector is clicked\n\nEnter a wiki with VE and ULS.', '(Enable ULS in preferences if needed.)', 'Start editing a page using VE.', 'Press the headings style dropdown.', 'Observed: IME selector appears near the dropdown.', 'Expected: IME selector must not appear.', ""It's not a place for writing things."", ""Background: there's an  element hiding there to capture click events (according to Roan)."", 'URL may be able to fix it (though some modifications may be needed).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**Whiteboard**: ve']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+244730,IME selector appears when the VisualEditor headings style selector is clicked,"Change 72356 merged by jenkins-bot:
+Remove unnecessary ULS IME selector from VE headings menu
+
+https://gerrit.wikimedia.org/r/72356",task_subcomment,['Change 72356 merged by jenkins-bot:\nRemove unnecessary ULS IME selector from VE headings menu\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244725,IME selector appears when the VisualEditor headings style selector is clicked,"Change 72356 had a related patch set uploaded by Amire80:
+Remove unnecessary ULS IME selector from VE headings menu
+
+https://gerrit.wikimedia.org/r/72356",task_subcomment,['Change 72356 had a related patch set uploaded by Amire80:\nRemove unnecessary ULS IME selector from VE headings menu\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244723,IME selector appears when the VisualEditor headings style selector is clicked,"I tested, and my assumption is correct: If https://gerrit.wikimedia.org/r/#/c/68339/ is merged, then this bug can be fixed by adding:
+
+$wgULSNoImeSelectors[] = 'ul.ve-ui-menuWidget input';",task_subcomment,"[""I tested, and my assumption is correct: If URL is merged, then this bug can be fixed by adding:\n\n$wgULSNoImeSelectors[] = 'ul.ve-ui-menuWidget input';""]",['INVESTIGATION AND EXPLORATION']
+52527,Tagging articles using old markup on VE,"I note that if an editor uses old markup in VE (like [[link]]), it gets enclosed in  tags
+
+Could we have an additional tag added to the Edit summary, (similar to the Visual Editor tag we have?) which states somethine like ""Old wiki markup""
+
+That way, we can keep track of, and rectify all the cases where the old wiki markup is used while using VE, and remedy it rather than clutter dozens of article with nowiki tags which might not be removed for days
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49820",task_description,"['Tagging articles using old markup on VE\n\nI note that if an editor uses old markup in VE (like [[link]]), it gets enclosed in  tags\n\nCould we have an additional tag added to the Edit summary, (similar to the Visual Editor tag we have?)', 'which states somethine like ""Old wiki markup""\n\nThat way, we can keep track of, and rectify all the cases where the old wiki markup is used while using VE, and remedy it rather than clutter dozens of article with nowiki tags which might not be removed for days\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244645,Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+Removing self from CC.  Tired of spam.  Bug is dead, people.",task_subcomment,"['**nykevin.norris** wrote:\n\nRemoving self from CC.', 'Tired of spam.', 'Bug is dead, people.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+244639,Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+(In reply to comment #20)
+> (In reply to comment #18)
+> kwwilliams: Unrelated to agreeing or disagreeing with others, could you
+> please
+> assume that people mean well instead of calling names, to keep Bugzilla a
+> friendly place? 
+
+I haven't called anyone names. I don't plan on starting to, either. If you can suggest a friendlier wording to describe a conscious decision not to fix a bug and requiring other people to deal with the consequences of the bug every day forever instead, I'm willing to listen to suggestions.",task_subcomment,"[""**kwwilliams** wrote:\n\n(In reply to comment #20)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI haven't called anyone names."", ""I don't plan on starting to, either."", ""If you can suggest a friendlier wording to describe a conscious decision not to fix a bug and requiring other people to deal with the consequences of the bug every day forever instead, I'm willing to listen to suggestions.""]","['SOCIAL CONVERSATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244635,Tagging articles using old markup on VE,"(In reply to comment #18)
+kwwilliams: Unrelated to agreeing or disagreeing with others, could you please assume that people mean well instead of calling names, to keep Bugzilla a friendly place? High-level debates on general development priorities are better placed on https://en.wikipedia.org/wiki/Wikipedia:VE/F instead of a bug report which is only meant to be about a *specific* problem *in the code*. Thanks!",task_subcomment,"['(In reply to comment #18)\nkwwilliams: Unrelated to agreeing or disagreeing with others, could you please assume that people mean well instead of calling names, to keep Bugzilla a friendly place?', 'High-level debates on general development priorities are better placed on URL instead of a bug report which is only meant to be about a *specific* problem *in the code*.', 'Thanks!']","['SOCIAL CONVERSATION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION']"
+244628,Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+Closely related problems, Kevin Norris: if they would *fix* 49686, this one would go away. This one can't really be fixed because the base condition that causes it should be prevented, not reported.",task_subcomment,"['**kwwilliams** wrote:\n\nClosely related problems, Kevin Norris: if they would *fix* 49686, this one would go away.', ""This one can't really be fixed because the base condition that causes it should be prevented, not reported.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+244623,Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+(In reply to comment #17)
+> Instead, James Forrester and Erik Moller have decreed that the bug not be
+> fixed, and that volunteers should eagerly flock to monitoring the output of
+> an
+> edit filter that detects each and every time this happens to that these
+> volunteers can fix it. That's repulsive. That's a level of disregard for the
+> volunteers that work on this project that is breathtaking. It's the *reason*
+> that the VE team can fix dozens of bugs each hour and the Wikipedia community
+> still complains that they are non-responsive.
+
+That is bug 49686, not this one.  Why are we discussing it here?",task_subcomment,"['**nykevin.norris** wrote:\n\n(In reply to comment #17)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat is bug 49686, not this one.', 'Why are we discussing it here?']","['OBSERVED BUG BEHAVIOR', 'SOCIAL CONVERSATION']"
+244618,Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+(In reply to comment #15)
+> Chris, could you add a link to that comment. Im interested in why the nowiki
+> edit filter isnt sufficient.
+
+It isn't sufficient because it disappoints the first human involved, this hypothetical new editor that is so confused by all of our existing material that he's errantly typing wikitext into a source window. VE could *help* him, but instead it pops a warning. The warning obviously isn't working, because we see saves of this material happening constantly. He goes ahead and saves it anyway, and he's bewildered and confused: he did just what the little cheat sheet he got from a friend told him to do, and it didn't work.
+
+It's insufficient because it requires a second human being to then review the change, figure out what it was that the first human was actually attempting, and then correct it if he can. 
+
+It's insufficient because it's in support of a use-case that doesn't exist: there's no reason to put something like [[New York City|the Big Apple]] into articles. If there *were*, it's coming from an editor that is quite skilled enough to go into the source editor. If we need to support putting such things in using the visual editor, a workflow can be designed with a ""nowiki"" button to do it intentionally.
+
+Instead, James Forrester and Erik Moller have decreed that the bug not be fixed, and that volunteers should eagerly flock to monitoring the output of an edit filter that detects each and every time this happens to that these volunteers can fix it. That's repulsive. That's a level of disregard for the volunteers that work on this project that is breathtaking. It's the *reason* that the VE team can fix dozens of bugs each hour and the Wikipedia community still complains that they are non-responsive.",task_subcomment,"[""**kwwilliams** wrote:\n\n(In reply to comment #15)\nQUOTE\nQUOTE\n\nIt isn't sufficient because it disappoints the first human involved, this hypothetical new editor that is so confused by all of our existing material that he's errantly typing wikitext into a source window."", 'VE could *help* him, but instead it pops a warning.', ""The warning obviously isn't working, because we see saves of this material happening constantly."", ""He goes ahead and saves it anyway, and he's bewildered and confused: he did just what the little cheat sheet he got from a friend told him to do, and it didn't work."", ""It's insufficient because it requires a second human being to then review the change, figure out what it was that the first human was actually attempting, and then correct it if he can."", ""It's insufficient because it's in support of a use-case that doesn't exist: there's no reason to put something like [[New York City|the Big Apple]] into articles."", ""If there *were*, it's coming from an editor that is quite skilled enough to go into the source editor."", 'If we need to support putting such things in using the visual editor, a workflow can be designed with a ""nowiki"" button to do it intentionally.', 'Instead, James Forrester and Erik Moller have decreed that the bug not be fixed, and that volunteers should eagerly flock to monitoring the output of an edit filter that detects each and every time this happens to that these volunteers can fix it.', ""That's repulsive."", ""That's a level of disregard for the volunteers that work on this project that is breathtaking."", ""It's the *reason* that the VE team can fix dozens of bugs each hour and the Wikipedia community still complains that they are non-responsive.""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOCIAL CONVERSATION', 'SOCIAL CONVERSATION', 'OBSERVED BUG BEHAVIOR']"
+244614,Tagging articles using old markup on VE,"(In reply to comment #15)
+> Chris, could you add a link to that comment. 
+It's the second comment by VQuakr at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=566546550#WONTFIX_on_nowiki.27s (that's a permalink to the present version of the page but the discussion may not have concluded yet).",task_subcomment,"[""(In reply to comment #15)\nQUOTE\nIt's the second comment by VQuakr at URL (that's a permalink to the present version of the page but the discussion may not have concluded yet).""]",['MOTIVATION']
+244610,Tagging articles using old markup on VE,"Chris, could you add a link to that comment. Im interested in why the nowiki edit filter isnt sufficient.
+Preventing the VE nowiki edit is a bit rude, and is sticky tape of the problem with the VE causing these nowikis. In VE, the user cant _see_ the nowiki causing problem all the time. E.g. A space at the beginning of the line isnt obviously the cause of the nowiki. unless VE explicitly tells them where the nowiki is happening, how can we expect the newbie to figure it out.",task_subcomment,"['Chris, could you add a link to that comment.', 'Im interested in why the nowiki edit filter isnt sufficient.', 'Preventing the VE nowiki edit is a bit rude, and is sticky tape of the problem with the VE causing these nowikis.', 'In VE, the user cant _see_ the nowiki causing problem all the time.', 'E.g.', 'A space at the beginning of the line isnt obviously the cause of the nowiki.', 'unless VE explicitly tells them where the nowiki is happening, how can we expect the newbie to figure it out.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+244606,Tagging articles using old markup on VE,"A user at en.wp comments that if this bug remains unfixed that cleaning up the live wiki using AWB will take ""about maybe an hour of experienced editor time to manage this, every day forever, because WMF is unwilling to accept feedback on how the software is actually used.""",task_subcomment,"['A user at en.wp comments that if this bug remains unfixed that cleaning up the live wiki using AWB will take ""about maybe an hour of experienced editor time to manage this, every day forever, because WMF is unwilling to accept feedback on how the software is actually used.""']",['OBSERVED BUG BEHAVIOR']
+244603,Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+(In reply to comment #11)
+> (In reply to comment #10)
+> > (In reply to comment #7)
+> > > Adding a  to an article (as opposed to a template or something) is
+> > > generally unnecessary and probably in need of a second look, regardless of
+> > > whether VE added it or the editor added it manually.  Wikimarkup simply
+> > > *doesn't look like* real punctuation, so it's uncommon to need to escape it
+> > > in
+> > > running text.
+> > > 
+> > > As such, I tentatively agree with James here: A VE-only filter would be
+> > > unnecessary since the broader case is really what we need to go after anyway.
+> > 
+> > You miss the point: in an edit-filter, I would advocate simply blocking the
+> > edit if it was VE and not allow it to be saved. If a human being consciously
+> > did it, there's at least a remote chance that it was a good edit worthy of
+> > examination.
+> 
+> I think that would be an exceptionally-bad thing to do to fellow editors and
+> thus to the wiki at large
+
+As was making VE the default editor in the first place, so it's obvious we don't agree some fundamental points.
+
+> 
+> > There *are* legitimate uses of nowiki, usually things involving bolded and
+> > italicized possessives, pipe characters inside of text. It's just that none
+> > of the ones created by VE have any merit.
+> 
+> None? None ever? Not even when a user of VisualEditor creates a bolded or
+> italicised possessive? :-)
+
+True enough. Which is why you should fix the root bug in the first place instead of pushing it downstream for everyone else to deal with: warning newbies about inserting explicit wikimarkup is obviously still inadequate, as this edit filter still fires.",task_subcomment,"[""**kwwilliams** wrote:\n\n(In reply to comment #11)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAs was making VE the default editor in the first place, so it's obvious we don't agree some fundamental points."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nTrue enough.', 'Which is why you should fix the root bug in the first place instead of pushing it downstream for everyone else to deal with: warning newbies about inserting explicit wikimarkup is obviously still inadequate, as this edit filter still fires.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+244599,Tagging articles using old markup on VE,"(In reply to comment #6)
+> Tell me how an abuse filter can even detect that Visual Editor was involved
+> in the edit before you attempt to close this, please.
+
+That would be bug 51421 (which is a bug against AbuseFilter); you should follow-up there.",task_subcomment,['(In reply to comment #6)\nQUOTE\nQUOTE\n\nThat would be bug 51421 (which is a bug against AbuseFilter); you should follow-up there.'],['ACTION ON ISSUE']
+244594,Tagging articles using old markup on VE,"(In reply to comment #10)
+> (In reply to comment #7)
+> > Adding a  to an article (as opposed to a template or something) is
+> > generally unnecessary and probably in need of a second look, regardless of
+> > whether VE added it or the editor added it manually.  Wikimarkup simply
+> > *doesn't look like* real punctuation, so it's uncommon to need to escape it
+> > in
+> > running text.
+> > 
+> > As such, I tentatively agree with James here: A VE-only filter would be
+> > unnecessary since the broader case is really what we need to go after anyway.
+> 
+> You miss the point: in an edit-filter, I would advocate simply blocking the
+> edit if it was VE and not allow it to be saved. If a human being consciously
+> did it, there's at least a remote chance that it was a good edit worthy of
+> examination.
+
+I think that would be an exceptionally-bad thing to do to fellow editors and thus to the wiki at large, but that's a decision for local wikis' communities to make, and not appropriate for the developers to rule on.
+
+> There *are* legitimate uses of nowiki, usually things involving bolded and
+> italicized possessives, pipe characters inside of text. It's just that none
+> of the ones created by VE have any merit.
+
+None? None ever? Not even when a user of VisualEditor creates a bolded or italicised possessive? :-)",task_subcomment,"[""(In reply to comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI think that would be an exceptionally-bad thing to do to fellow editors and thus to the wiki at large, but that's a decision for local wikis' communities to make, and not appropriate for the developers to rule on."", 'QUOTE\nQUOTE\nQUOTE\n\nNone?', 'None ever?', 'Not even when a user of VisualEditor creates a bolded or italicised possessive?', ':-)']","['MOTIVATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244590,Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+(In reply to comment #7)
+> Adding a  to an article (as opposed to a template or something) is
+> generally unnecessary and probably in need of a second look, regardless of
+> whether VE added it or the editor added it manually.  Wikimarkup simply
+> *doesn't look like* real punctuation, so it's uncommon to need to escape it
+> in
+> running text.
+> 
+> As such, I tentatively agree with James here: A VE-only filter would be
+> unnecessary since the broader case is really what we need to go after anyway.
+
+You miss the point: in an edit-filter, I would advocate simply blocking the edit if it was VE and not allow it to be saved. If a human being consciously did it, there's at least a remote chance that it was a good edit worthy of examination.
+
+There *are* legitimate uses of nowiki, usually things involving bolded and italicized possessives, pipe characters inside of text. It's just that none of the ones created by VE have any merit.",task_subcomment,"['**kwwilliams** wrote:\n\n(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYou miss the point: in an edit-filter, I would advocate simply blocking the edit if it was VE and not allow it to be saved.', ""If a human being consciously did it, there's at least a remote chance that it was a good edit worthy of examination."", 'There *are* legitimate uses of nowiki, usually things involving bolded and italicized possessives, pipe characters inside of text.', ""It's just that none of the ones created by VE have any merit.""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+244584,Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+But code samples and template documentation won't be in mainspace, which the current filter checks for.  Legitimate uses of  in mainspace are quite rare, so far as I know.  I suppose the articles on e.g. [[MediaWiki]] might use nowiki'd wikitext to show the readers what wikitext looks like, but other than that...",task_subcomment,"[""**nykevin.norris** wrote:\n\nBut code samples and template documentation won't be in mainspace, which the current filter checks for."", 'Legitimate uses of  in mainspace are quite rare, so far as I know.', 'I suppose the articles on e.g.', ""[[MediaWiki]] might use nowiki'd wikitext to show the readers what wikitext looks like, but other than that...""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR']"
+244577,Tagging articles using old markup on VE,"Its possible the abusefilter could be made to detect veaction=edit, then the abuse filter could be made more discriminating, and probably block ve edits with nowiki's.
+
+There are many cases where nowiki's are ment from the wikitext. In code samples documentation of templates etc. they always explicitly typed indication an intention from the user.",task_subcomment,"[""Its possible the abusefilter could be made to detect veaction=edit, then the abuse filter could be made more discriminating, and probably block ve edits with nowiki's."", ""There are many cases where nowiki's are ment from the wikitext."", 'In code samples documentation of templates etc.', 'they always explicitly typed indication an intention from the user.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244571,Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+Adding a  to an article (as opposed to a template or something) is generally unnecessary and probably in need of a second look, regardless of whether VE added it or the editor added it manually.  Wikimarkup simply *doesn't look like* real punctuation, so it's uncommon to need to escape it in running text.
+
+As such, I tentatively agree with James here: A VE-only filter would be unnecessary since the broader case is really what we need to go after anyway.",task_subcomment,"['**nykevin.norris** wrote:\n\nAdding a  to an article (as opposed to a template or something) is generally unnecessary and probably in need of a second look, regardless of whether VE added it or the editor added it manually.', ""Wikimarkup simply *doesn't look like* real punctuation, so it's uncommon to need to escape it in running text."", 'As such, I tentatively agree with James here: A VE-only filter would be unnecessary since the broader case is really what we need to go after anyway.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+244564,Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+Tell me how an abuse filter can even detect that Visual Editor was involved in the edit before you attempt to close this, please.",task_subcomment,"['**kwwilliams** wrote:\n\nTell me how an abuse filter can even detect that Visual Editor was involved in the edit before you attempt to close this, please.']",['BUG REPRODUCTION']
+244555,Tagging articles using old markup on VE,"As mentioned, there is now a local AbuseFilter running on enwiki that flags any edit that adds a  tag (whether in VisualEditor or wikitext editor; whether accidental or deliberate; whether due to using wikitext markup or because of a bug).
+
+I think a global AbuseFilter might make sense to do this globally, but certainly this feels like something better done using AbuseFilter than heavy-handedly inserted by VisualEditor itself, if that makes sense, so I'm going to close this as a WONTFIX - but very happy to reopen if people feel it would be better in VE.",task_subcomment,"['As mentioned, there is now a local AbuseFilter running on enwiki that flags any edit that adds a  tag (whether in VisualEditor or wikitext editor; whether accidental or deliberate; whether due to using wikitext markup or because of a bug).', ""I think a global AbuseFilter might make sense to do this globally, but certainly this feels like something better done using AbuseFilter than heavy-handedly inserted by VisualEditor itself, if that makes sense, so I'm going to close this as a WONTFIX - but very happy to reopen if people feel it would be better in VE.""]","['MOTIVATION', 'ACTION ON ISSUE']"
+244546,Tagging articles using old markup on VE,"Maybe this is something that should be tested with global filters[1] now that they are available?
+
+[1] http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070253.html",task_subcomment,"['Maybe this is something that should be tested with global filters[1] now that they are available?', '[1] URL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244537,Tagging articles using old markup on VE,"There is now an edit filter to detect insertion of nowiki's
+http://en.wikipedia.org/w/index.php?title=Special:AbuseLog&offset=&limit=500&wpSearchFilter=550",task_subcomment,"[""There is now an edit filter to detect insertion of nowiki's\nURL""]",['INVESTIGATION AND EXPLORATION']
+244529,Tagging articles using old markup on VE,"FYI, in the meantime, I've requested an edit filter to be added to identify nowiki tags in the main namespace on the English Wikipedia:
+https://en.wikipedia.org/w/index.php?title=Wikipedia:Edit_filter/Requested&oldid=562811538#nowiki_in_main_namespace
+
+There's now also one on the French Wikipedia.",task_subcomment,"[""FYI, in the meantime, I've requested an edit filter to be added to identify nowiki tags in the main namespace on the English Wikipedia:\nURL\n\nThere's now also one on the French Wikipedia.""]",['FUTURE PLAN']
+244521,Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+Here's an example of an edit which we'd like to be tagged in the future:
+
+https://en.wikipedia.org/w/index.php?title=Richard_Rich,_1st_Baron_Rich&diff=562587470&oldid=562435942
+
+In this case, the user didn't even realize they were using the VisualEditor and came to the help desk, confused:
+
+https://en.wikipedia.org/wiki/Wikipedia:Help_desk#Problems_editing_with_beta_versions.3F",task_subcomment,"[""**nykevin.norris** wrote:\n\nHere's an example of an edit which we'd like to be tagged in the future:\n\nURL\n\nIn this case, the user didn't even realize they were using the VisualEditor and came to the help desk, confused:\n\nURL""]",['INVESTIGATION AND EXPLORATION']
+52524,Buttons not showing up,"http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#.22Submit.22_button_doesn.27t_show_up
+
+Epicgenius reports the buttons not showing up, I have his same config and was not able to reproduce the issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Buttons not showing up\n\nURL\n\nEpicgenius reports the buttons not showing up, I have his same config and was not able to reproduce the issue.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+244399,Buttons not showing up,"Given that it's been 25 days without further reports or information about the original issue, I'm marking this as INVALID.",task_subcomment,"[""Given that it's been 25 days without further reports or information about the original issue, I'm marking this as INVALID.""]",['ACTION ON ISSUE']
+244391,Buttons not showing up,Can they take a screenshot and attach to this bug? It'd be helpful to understand what it now showing up looks like.,task_subcomment,"['Can they take a screenshot and attach to this bug?', ""It'd be helpful to understand what it now showing up looks like.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52521,Ghost references in VisualEditor?,"Pamd reports:
+If I open [[Queen Anne Grammar School]] in VE, I can see two superscripts linking to references - and 29 references in the reflist. Some of them perhaps most, are the refs which were deleted in a [http://en.wikipedia.org/w/index.php?title=Queen_Anne_Grammar_School&diff=562382386&oldid=562381869 series of edits] 9 hours ago while the article was being moved from AFC to mainspace. If I open it in Edit Source, it's a respectable little stub with two refs and no sign of the other stuff.
+
+Full report at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_picking_up_old_version_of_file.3F_-_27_ghost_references.21 .
+
+It does the same for me (Vector on Chrome).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Ghost references in VisualEditor?', 'Pamd reports:\nIf I open [[Queen Anne Grammar School]] in VE, I can see two superscripts linking to references - and 29 references in the reflist.', 'Some of them perhaps most, are the refs which were deleted in a [URL series of edits] 9 hours ago while the article was being moved from AFC to mainspace.', ""If I open it in Edit Source, it's a respectable little stub with two refs and no sign of the other stuff."", 'Full report at URL .', 'It does the same for me (Vector on Chrome).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244210,Ghost references in VisualEditor?,"Yes, same issue as bug 50380.
+
+*** This bug has been marked as a duplicate of bug 50380 ***",task_subcomment,"['Yes, same issue as bug 50380.', '*** This bug has been marked as a duplicate of bug 50380 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244204,Ghost references in VisualEditor?,"I cant reproduce this using the example given.
+
+It looks like this may be a dup of bug 50380.",task_subcomment,"['I cant reproduce this using the example given.', 'It looks like this may be a dup of bug 50380.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52519,VisualEditor: Deleting all content removes input marker,"When marking all content on a page, and hit «delete», then, while the content is removed, also the input marker is removed, so you can't input anything new directly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Deleting all content removes input marker\n\nWhen marking all content on a page, and hit «delete», then, while the content is removed, also the input marker is removed, so you can't input anything new directly."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244066,VisualEditor: Deleting all content removes input marker,"(In reply to comment #1)
+> Is this the same as Bug 50947 and/or Bug 51169?
+
+Yes; merging.
+
+*** This bug has been marked as a duplicate of bug 50947 ***",task_subcomment,"['(In reply to comment #1)\nQUOTE\n\nYes; merging.', '*** This bug has been marked as a duplicate of bug 50947 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+244061,VisualEditor: Deleting all content removes input marker,Is this the same as Bug 50947 and/or Bug 51169?,task_subcomment,['Is this the same as Bug 50947 and/or Bug 51169?'],['BUG REPRODUCTION']
+52507,Unexpected editing behavior for typing Malayalam text,"**Author:** `harshanh1979`
+
+**Description:**
+I have tested VisualEditor at ml.wikipedia at the following page
+
+https://ml.wikipedia.org/wiki/%E0%B4%AC%E0%B5%BC%E0%B4%A4%E0%B5%8D%E0%B4%A4%E0%B4%B2%E0%B5%8B%E0%B4%AE%E0%B4%BF%E0%B4%AF%E0%B5%8B_%E0%B4%A1%E0%B4%AF%E0%B4%B8%E0%B5%8D
+
+I tried to correct the text ൻറെ to ന്റെ. But the editor doesnt allow to input the characters ് െ etc. Unwanted changes happens somewhere else in the paragraph while trying to input the above mentioned characters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50566",task_description,"['Unexpected editing behavior for typing Malayalam text\n\n**Author:** CODE\n\n**Description:**\nI have tested VisualEditor at ml.wikipedia at the following page\n\nURL\n\nI tried to correct the text ൻറെ to ന്റെ.', 'But the editor doesnt allow to input the characters ് െ etc.', 'Unwanted changes happens somewhere else in the paragraph while trying to input the above mentioned characters.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**OS**: Linux\n**Platform**: PC\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+243373,Unexpected editing behavior for typing Malayalam text,I had this problem earlier with Ubuntu/Firefox 22. Now it is found that the problem was rectified.,task_subcomment,"['I had this problem earlier with Ubuntu/Firefox 22.', 'Now it is found that the problem was rectified.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52468,VisualEditor: thick line appearing,"Screenshot
+
+See screenshot, from https://en.wikipedia.org/wiki/Jitter_%28disambiguation%29?veaction=edit - that line near the top shouldn't be there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11385}",task_description,"[""VisualEditor: thick line appearing\n\nScreenshot\n\nSee screenshot, from URL - that line near the top shouldn't be there."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11385}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240951,VisualEditor: thick line appearing,"Created attachment 13766
+No thick line
+
+**Attached**: {F11386}",task_subcomment,['Created attachment 13766\nNo thick line\n\n**Attached**: {F11386}'],['BUG REPRODUCTION']
+240942,VisualEditor: thick line appearing,"The thick line is not appearing now near the top of this page.Checked in both FireFox 20 and chrome Version 26.0.1410.65 using MAC OS X 10.8.5
+
+See the screenshots attached.
+
+Therefore changing the status to Resolved-worksforme for now,if you get this problem again,please do reopen the bug.",task_subcomment,"['The thick line is not appearing now near the top of this page.Checked in both FireFox 20 and chrome Version 26.0.1410.65 using MAC OS X 10.8.5\n\nSee the screenshots attached.', 'Therefore changing the status to Resolved-worksforme for now,if you get this problem again,please do reopen the bug.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+52467,VisualEditor: Text wrongly being given pre-formatted format,"Screenshot
+
+See screenshot - from https://en.wikipedia.org/wiki/Iphigenia?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11382}",task_description,['VisualEditor: Text wrongly being given pre-formatted format\n\nScreenshot\n\nSee screenshot - from URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11382}'],['OBSERVED BUG BEHAVIOR']
+240899,VisualEditor: Text wrongly being given pre-formatted format,Fixed for some time due to changes in Parsoid. Sorry for the slowness of updating.,task_subcomment,"['Fixed for some time due to changes in Parsoid.', 'Sorry for the slowness of updating.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+52466,VisualEditor: Links created in the userspace are treated as links to subpages,"If I open the VisualEditor and add a link to say, ""Edward Coke (politician)"" in my sandbox, and then right click on the link and open it in a new tab, it takes me to https://en.wikipedia.org/wiki/User:Okeyes_%28WMF%29/Edward_Coke_%28politician%29
+
+This seems somewhat suboptimal.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Links created in the userspace are treated as links to subpages\n\nIf I open the VisualEditor and add a link to say, ""Edward Coke (politician)"" in my sandbox, and then right click on the link and open it in a new tab, it takes me to URL\n\nThis seems somewhat suboptimal.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+240855,VisualEditor: Links created in the userspace are treated as links to subpages,"
+
+*** This bug has been marked as a duplicate of bug 48915 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 48915 ***'],['ACTION ON ISSUE']
+52463,VisualEditor: Error saving data to server: Failed request: error.,"We have users reporting errors when trying to save on https://en.wikipedia.org/wiki/Colorado_14ers - can someone take a look at the log and work out what's happening? They were only adding text and a reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Error saving data to server: Failed request: error.', ""We have users reporting errors when trying to save on URL - can someone take a look at the log and work out what's happening?"", 'They were only adding text and a reference.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240730,VisualEditor: Error saving data to server: Failed request: error.,"Performance issue, fixed some time ago; sorry for slowness in replying.",task_subcomment,"['Performance issue, fixed some time ago; sorry for slowness in replying.']",['ACTION ON ISSUE']
+240721,VisualEditor: Error saving data to server: Failed request: error.,"It should be the same happening here http://en.wikipedia.org/w/index.php?title=U.S._Route_377_in_Texas&diff=562454441&oldid=506596182 although the user reports seeing the message _and_ still, the edit was saved.
+
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Received_error_though_edit_was_saved",task_subcomment,"['It should be the same happening here URL although the user reports seeing the message _and_ still, the edit was saved.', 'URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52456,"VE feature request: visual ""tell"" when editing","Can something - perhaps a faint background color or an outline - be added to make clear when one is in editing mode?
+
+Copied from http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Make_editing_view_more_distinctive_from_article
+
+I like the visual editor, and I predict that more people will edit WP when it's introduced. However, there is one thing that bugs me: After I clicked the ""Edit"" Tab, the view of the article does change only slightly - so sometimes I do not know that I am already editing, especially when I scroll down the article. I'd suggest a visual hint: A modal popup, a slim outline of the editing area or a more distinctive design of the tool bar, for example. Mateng (talk) 12:00, 30 June 2013 (UTC)
+
+Hear, hear! Perhaps a (faint) background colour? There needs to be some visual clue. JohnCD (talk) 12:17, 30 June 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VE feature request: visual ""tell"" when editing\n\nCan something - perhaps a faint background color or an outline - be added to make clear when one is in editing mode?', ""Copied from URL\n\nI like the visual editor, and I predict that more people will edit WP when it's introduced."", 'However, there is one thing that bugs me: After I clicked the ""Edit"" Tab, the view of the article does change only slightly - so sometimes I do not know that I am already editing, especially when I scroll down the article.', ""I'd suggest a visual hint: A modal popup, a slim outline of the editing area or a more distinctive design of the tool bar, for example."", 'Mateng (talk) 12:00, 30 June 2013 (UTC)\n\nHear, hear!', 'Perhaps a (faint) background colour?', 'There needs to be some visual clue.', 'JohnCD (talk) 12:17, 30 June 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOCIAL CONVERSATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+240291,"VE feature request: visual ""tell"" when editing","These are already covered by bug 48008 (""There is not enough UI difference between reading and editing mode"").
+
+*** This bug has been marked as a duplicate of bug 48008 ***",task_subcomment,"['These are already covered by bug 48008 (""There is not enough UI difference between reading and editing mode"").', '*** This bug has been marked as a duplicate of bug 48008 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240287,"VE feature request: visual ""tell"" when editing","Another related request: 
+
+It would be very nice to show changed text in a different font and/or color (or bg color), while editing. It helps seeing what you are editing. --Wickey-nl (talk) 09:34, 5 July 2013 (UTC)",task_subcomment,"['Another related request: \n\nIt would be very nice to show changed text in a different font and/or color (or bg color), while editing.', 'It helps seeing what you are editing.', '--Wickey-nl (talk) 09:34, 5 July 2013 (UTC)']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+240280,"VE feature request: visual ""tell"" when editing","Another editor suggests:
+
+I think various editors have said this before, but I'm feeling tired right now and have found it more of a problem than usually: a page open in VE needs to look much more distinctive. Otherwise it would be too easy to forget to Save Page and then absentmindedly close the tab on a page of edits. (Especially when juggling several tabs because checking different pages - even more so because Navigation Popups don't work in VE!). Even the header bar is almost monochrome. Could we have something like a red line all the way down the left-hand margin? Perhaps it would need to be an option, as some people would hate it. But I'd certainly find it helpful and I know I'm not alone. PamD 22:00, 4 July 2013 (UTC)",task_subcomment,"[""Another editor suggests:\n\nI think various editors have said this before, but I'm feeling tired right now and have found it more of a problem than usually: a page open in VE needs to look much more distinctive."", 'Otherwise it would be too easy to forget to Save Page and then absentmindedly close the tab on a page of edits.', ""(Especially when juggling several tabs because checking different pages - even more so because Navigation Popups don't work in VE!)."", 'Even the header bar is almost monochrome.', 'Could we have something like a red line all the way down the left-hand margin?', 'Perhaps it would need to be an option, as some people would hate it.', ""But I'd certainly find it helpful and I know I'm not alone."", 'PamD 22:00, 4 July 2013 (UTC)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52455,VisualEditor: Insert media dialog is borked,"screenshot
+
+It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11359}",task_description,"['VisualEditor: Insert media dialog is borked\n\nscreenshot\n\nIt was working fine previously.', 'I can reproduce this on both fr.wp and en.wp.', 'See screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11359}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240255,VisualEditor: Insert media dialog is borked,"
+
+*** This bug has been marked as a duplicate of bug 50471 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50471 ***'],['ACTION ON ISSUE']
+52437,"VisualEditor: ""Error saving data to server"" but actually successful, and spurious diff","I twice got the error alert box when saving.  However, it turns out that it did save both times.  The first time, it did the intended edit (https://en.wikipedia.org/w/index.php?title=Participants_in_World_War_II&diff=562174851&oldid=561500927).  The second time, it did a dirty diff for a pipe character (| -> |) in a section of the page I didn't edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: ""Error saving data to server"" but actually successful, and spurious diff\n\nI twice got the error alert box when saving.', 'However, it turns out that it did save both times.', ""The first time, it did the intended edit (URL  The second time, it did a dirty diff for a pipe character (| -> |) in a section of the page I didn't edit."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239309,"VisualEditor: ""Error saving data to server"" but actually successful, and spurious diff",We have tweaked the time-out code so this shouldn't happen in future; sorry for the disruption. Please re-open if it recurs…,task_subcomment,"[""We have tweaked the time-out code so this shouldn't happen in future; sorry for the disruption."", 'Please re-open if it recurs…']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+52428,Preserve wiki link href with ././ prefix,"The following HTML does not seem to properly round-trip through VE:
+
+
                ./Foo
                
+
+While the ././ prefix is not ideal (see Parsoid bug 50426) VE should still preserve the href on unmodified content. Instead, it seems to prefix another ./, which then results in diffs like this one:
+
+https://en.wikipedia.org/w/index.php?title=DreamWorks_Animation&curid=1509817&diff=562129988&oldid=562129729
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Preserve wiki link href with ././ prefix\n\nThe following HTML does not seem to properly round-trip through VE:\n\n
                ./Foo
                \n\nWhile the ././ prefix is not ideal (see Parsoid bug 50426) VE should still preserve the href on unmodified content.', 'Instead, it seems to prefix another ./, which then results in diffs like this one:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+238558,Preserve wiki link href with ././ prefix,"My problem is still occurring. I've now created bug 50720 for the specific issue I'm seeing. The latest occurrence was 05:07, 4 July 2013 
+https://en.wikipedia.org/w/index.php?title=Austropotamobius_pallipes&curid=3945333&diff=562783871&oldid=545518009",task_subcomment,"['My problem is still occurring.', ""I've now created bug 50720 for the specific issue I'm seeing."", 'The latest occurrence was 05:07, 4 July 2013 \nURL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+238555,Preserve wiki link href with ././ prefix,Note that I also deployed a fix for bug 50426 just before I closed this bug. That will avoid triggering this in VE even if there is still a bug.,task_subcomment,"['Note that I also deployed a fix for bug 50426 just before I closed this bug.', 'That will avoid triggering this in VE even if there is still a bug.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+238552,Preserve wiki link href with ././ prefix,"WORKSFORME is not good enough for a resolution for this bug. This seems to be quite a rare bug which I've only seen in edits with the visualeditor-needcheck tag
+
+https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=visualeditor-needcheck 
+
+Looking thorough that this edit
+https://en.wikipedia.org/w/index.php?title=Ron_Davies_(songwriter)&curid=31118393&diff=562723238&oldid=553701771
+
+introduced the bad markup and that was only a couple of hours ago.",task_subcomment,"['WORKSFORME is not good enough for a resolution for this bug.', ""This seems to be quite a rare bug which I've only seen in edits with the visualeditor-needcheck tag\n\nURL \n\nLooking thorough that this edit\nURL\n\nintroduced the bad markup and that was only a couple of hours ago.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+238548,Preserve wiki link href with ././ prefix,"It worked at http://en.wikipedia.org/wiki/User:Catrope/Shrek?veaction=edit though, so closing as working.",task_subcomment,"['It worked at URL though, so closing as working.']",['ACTION ON ISSUE']
+238541,Preserve wiki link href with ././ prefix,"This seems to also seem to replace spaces with underscores, and mangles category links. EG changing [[Category:House (season 7) episodes]] to [[./Category:House_(season_7)_episodes]]
+https://en.wikipedia.org/w/index.php?title=Out_of_the_Chute&diff=prev&oldid=562623071",task_subcomment,"['This seems to also seem to replace spaces with underscores, and mangles category links.', 'EG changing [[Category:House (season 7) episodes]] to [[./Category:House_(season_7)_episodes]]\nURL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238533,Preserve wiki link href with ././ prefix,"Those prefixes actually seem to have been inserted by VE:
+https://en.wikipedia.org/w/index.php?title=DreamWorks_Animation&curid=1509817&diff=562129729&oldid=562106766",task_subcomment,['Those prefixes actually seem to have been inserted by VE:\nURL'],['OBSERVED BUG BEHAVIOR']
+52421,Feature request: permit copy-paste of templates from history,"Taken from VisualEditor feedback page:
+
+Trying when editing articles to think ""Could I use VE for this?"" I came on an article where the {{AfD}} template had been removed and needed to be restored. The easiest way to get that right is to call up from the history a version with the template in place, and copy it from there to the current version. This doesn't seem possible in VE: after selecting the template so that it is highlighted, Ctrl-C doesn't copy it, and right-click doesn't offer a ""Copy"" option. JohnCD (talk) 21:29, 28 June 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Feature request: permit copy-paste of templates from history\n\nTaken from VisualEditor feedback page:\n\nTrying when editing articles to think ""Could I use VE for this?""', 'I came on an article where the {{AfD}} template had been removed and needed to be restored.', 'The easiest way to get that right is to call up from the history a version with the template in place, and copy it from there to the current version.', 'This doesn\'t seem possible in VE: after selecting the template so that it is highlighted, Ctrl-C doesn\'t copy it, and right-click doesn\'t offer a ""Copy"" option.', 'JohnCD (talk) 21:29, 28 June 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+238111,Feature request: permit copy-paste of templates from history,"This will be solved by bug 41193 when that is fixed; merging to that.
+
+*** This bug has been marked as a duplicate of bug 41193 ***",task_subcomment,"['This will be solved by bug 41193 when that is fixed; merging to that.', '*** This bug has been marked as a duplicate of bug 41193 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238106,Feature request: permit copy-paste of templates from history,"I believe Maggie means copying the VisualEditor representation of a template, not copying wikitext.",task_subcomment,"['I believe Maggie means copying the VisualEditor representation of a template, not copying wikitext.']",['SOLUTION DISCUSSION']
+238102,Feature request: permit copy-paste of templates from history,"Even if you could paste it in, that wouldn't do any good as the VE would surround the template with  tags. Entering any form of wikisyntax in the VE currently results in the editor thinking that you want the literal text to be displayed. This bug therefore (partly) depends on that bug being fixed too.",task_subcomment,"[""Even if you could paste it in, that wouldn't do any good as the VE would surround the template with  tags."", 'Entering any form of wikisyntax in the VE currently results in the editor thinking that you want the literal text to be displayed.', 'This bug therefore (partly) depends on that bug being fixed too.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52418,VisualEditor: Backspace from header line into empty paragraph changes header format into paragraph,"If a header line is preceded by an empty line, and one tries to remove that empty line by placing the cursor at the beginning of the header line and hitting Delete, the empty line is removed as expected, but the header line turns into Paragraph formatting, which is unexpected and incorrect.
+
+Note that the behavior is correct if the line preceding the header line is *not* empty: in that case we want to merge the header line with the previous line, and the header formatting should be removed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50995",task_description,"['VisualEditor: Backspace from header line into empty paragraph changes header format into paragraph\n\nIf a header line is preceded by an empty line, and one tries to remove that empty line by placing the cursor at the beginning of the header line and hitting Delete, the empty line is removed as expected, but the header line turns into Paragraph formatting, which is unexpected and incorrect.', 'Note that the behavior is correct if the line preceding the header line is *not* empty: in that case we want to merge the header line with the previous line, and the header formatting should be removed.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237967,VisualEditor: Backspace from header line into empty paragraph changes header format into paragraph,"The initial behaviour was, I believe, fixed some time ago; the rest of the bug (as now stated in the title) is intentional behaviour. Marking as FIXED.",task_subcomment,"['The initial behaviour was, I believe, fixed some time ago; the rest of the bug (as now stated in the title) is intentional behaviour.', 'Marking as FIXED.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']"
+237959,VisualEditor: Backspace from header line into empty paragraph changes header format into paragraph,"Sorry: I should have said ""Backspace"", not ""Delete"".",task_subcomment,"['Sorry: I should have said ""Backspace"", not ""Delete"".']",['OBSERVED BUG BEHAVIOR']
+52417,VisualEditor does not load on Opera when debugging with Dragonfly,"Would you believe that.
+
+[6/29/2013 1:44:17 PM] JavaScript - https://pl.wikipedia.org/wiki/Gródek_(obwód_lwowski)?veaction=edit
+Event thread: readystatechange
+Uncaught exception: Error: WRONG_ARGUMENTS_ERRError thrown at line 39, column 4 in (domElement) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.visibleText%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130629T021004Z&*:
+    return doc ? doc.importNode(domElement, true) : domElement.cloneNode(true);
+called from line 38, column 3 in (domElements, doc) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.visibleText%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130629T021004Z&*:
+    return domElements.map(function(domElement) {
+called from line 9721, column 3 in () in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    this.$.empty().append(ve.copyDomElements(store.value(index), doc));
+called from line 9711, column 2 in VeCeGeneratedContentNode() in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    this.onUpdate();
+called via Function.prototype.call() from line 10325, column 2 in VeCeMWTransclusionNode(model, config) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    ve.ce.GeneratedContentNode.call(this);
+called via Function.prototype.call() from line 10366, column 2 in VeCeMWTransclusionBlockNode(model) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    ve.ce.MWTransclusionNode.call(this, model);
+called via Function.prototype.apply() from line 50, column 2 in (name) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    constructor.apply(obj, args);
+called from line 8132, column 4 in (index) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    args[i] = ve.ce.nodeFactory.create(args[i].getType(), args[i]);
+called via Function.prototype.apply() from line 8089, column 2 in VeCeBranchNode(model, config) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    this.onSplice.apply(this, [0, 0].concat(model.getChildren()));
+called via Function.prototype.call() from line 9824, column 2 in VeCeDocumentNode(model, surface, config) in https://bits.wikimedia.org/pl.wikipedia.org/load.php?debug=false&lang=pl&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130629T021004Z&*:
+    ve.ce.BranchNode.call(this, model, config);
+
+At this point `store.value(index)` is [undefined, undefined] on Opera, but [, ] on Firefox. Since `index` is not undefined, this would indicate some sort of an internal inconsistency.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor does not load on Opera when debugging with Dragonfly\n\nWould you believe that.', '[6/29/2013 1:44:17 PM] JavaScript - URL\nEvent thread: readystatechange\nUncaught exception: Error: WRONG_ARGUMENTS_ERRError thrown at line 39, column 4 in (domElement) in URL\n    return doc ?', 'doc.importNode(domElement, true) : domElement.cloneNode(true);\ncalled from line 38, column 3 in (domElements, doc) in URL\n    return domElements.map(function(domElement) {\ncalled from line 9721, column 3 in () in URL\n    this.$.empty().append(ve.copyDomElements(store.value(index), doc));\ncalled from line 9711, column 2 in VeCeGeneratedContentNode() in URL\n    this.onUpdate();\ncalled via Function.prototype.call() from line 10325, column 2 in VeCeMWTransclusionNode(model, config) in URL\n    ve.ce.GeneratedContentNode.call(this);\ncalled via Function.prototype.call() from line 10366, column 2 in VeCeMWTransclusionBlockNode(model) in URL\n    ve.ce.MWTransclusionNode.call(this, model);\ncalled via Function.prototype.apply() from line 50, column 2 in (name) in URL\n    constructor.apply(obj, args);\ncalled from line 8132, column 4 in (index) in URL\n    args[i] = ve.ce.nodeFactory.create(args[i].getType(), args[i]);\ncalled via Function.prototype.apply() from line 8089, column 2 in VeCeBranchNode(model, config) in URL\n    this.onSplice.apply(this, [0, 0].concat(model.getChildren()));\ncalled via Function.prototype.call() from line 9824, column 2 in VeCeDocumentNode(model, surface, config) in URL\n    ve.ce.BranchNode.call(this, model, config);\n\nAt this point CODE is [undefined, undefined] on Opera, but [, ] on Firefox.', 'Since CODE is not undefined, this would indicate some sort of an internal inconsistency.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOCIAL CONVERSATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237907,VisualEditor does not load on Opera when debugging with Dragonfly,"Change 71174 merged by jenkins-bot:
+Make loading VE work on Opera again, attempt two
+
+https://gerrit.wikimedia.org/r/71174",task_subcomment,"['Change 71174 merged by jenkins-bot:\nMake loading VE work on Opera again, attempt two\n\nGERRIT_URL']",['ACTION ON ISSUE']
+237902,VisualEditor does not load on Opera when debugging with Dragonfly,"Change 71174 had a related patch set uploaded by Matmarex:
+Make loading VE work on Opera again, attempt two
+
+https://gerrit.wikimedia.org/r/71174",task_subcomment,"['Change 71174 had a related patch set uploaded by Matmarex:\nMake loading VE work on Opera again, attempt two\n\nGERRIT_URL']",['ACTION ON ISSUE']
+237896,VisualEditor does not load on Opera when debugging with Dragonfly,I know why it only fails when debugging: because the fix in https://gerrit.wikimedia.org/r/#/c/61560/ is only applied when not debugging. Apparently the document there is *still* not a document evenif it appears to be one.,task_subcomment,"['I know why it only fails when debugging: because the fix in URL is only applied when not debugging.', 'Apparently the document there is *still* not a document evenif it appears to be one.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237889,VisualEditor does not load on Opera when debugging with Dragonfly,"And that is because #cloneNode is returning `undefined` for those elements (probably because they come from some weird dynamically-generated document). Which is clearly an Opera bug, but it'd be nice to work around it somehow.",task_subcomment,"['And that is because #cloneNode is returning CODE for those elements (probably because they come from some weird dynamically-generated document).', ""Which is clearly an Opera bug, but it'd be nice to work around it somehow.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+237882,VisualEditor does not load on Opera when debugging with Dragonfly,"And this is because ve.copyArray() is losing data, always returning an array of undefineds there.",task_subcomment,"['And this is because ve.copyArray() is losing data, always returning an array of undefineds there.']",['OBSERVED BUG BEHAVIOR']
+237874,VisualEditor does not load on Opera when debugging with Dragonfly,"Hey, it's even better – all of the arrays in store.valueStore apparently consist only of varying number of undefineds.",task_subcomment,"[""Hey, it's even better – all of the arrays in store.valueStore apparently consist only of varying number of undefineds.""]",['OBSERVED BUG BEHAVIOR']
+52416,"Text covered up by infobox when editing, if image in infobox is large","If an infobox contains an image that is wider than the infobox's natural size, then editing the page cause the infobox to expand, without properly wrapping the adjacent text.  The result is that the infobox covers up the adjacent text.
+
+See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Text_appearing_behind_infobox_.2F_behaviour_after_editing on 28 June 2013 for the initial report.  The report came from a user running Chrome (version 27.0.1453.116) on Windows XP; I confirmed it in the en.wp article on Southampton using Safari 6.0.5 (7536.30.1) and Firefox 22.0 on Mac OS 10.7.5.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Text covered up by infobox when editing, if image in infobox is large\n\nIf an infobox contains an image that is wider than the infobox's natural size, then editing the page cause the infobox to expand, without properly wrapping the adjacent text."", 'The result is that the infobox covers up the adjacent text.', 'See URL on 28 June 2013 for the initial report.', 'The report came from a user running Chrome (version 27.0.1453.116) on Windows XP; I confirmed it in the en.wp article on Southampton using Safari 6.0.5 (7536.30.1) and Firefox 22.0 on Mac OS 10.7.5.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237836,"Text covered up by infobox when editing, if image in infobox is large","Congrats on your first bug report; sadly it is a dupe. Took me a while to find  bug 49925 though, so you are forgiven :)
+
+*** This bug has been marked as a duplicate of bug 49925 ***",task_subcomment,"['Congrats on your first bug report; sadly it is a dupe.', 'Took me a while to find  bug 49925 though, so you are forgiven :)\n\n*** This bug has been marked as a duplicate of bug 49925 ***']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+52380,VisualEditor: massively duplicating references on render,"https://en.wikipedia.org/wiki/Birbal has 3 references; https://en.wikipedia.org/wiki/Birbal?veaction=edit has 24.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: massively duplicating references on render\n\nURL has 3 references; URL has 24.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235754,VisualEditor: massively duplicating references on render,*** Bug 50521 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50521 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235749,VisualEditor: massively duplicating references on render,Fixed a few months ago; sorry for late reply.,task_subcomment,['Fixed a few months ago; sorry for late reply.'],['ACTION ON ISSUE']
+235743,VisualEditor: massively duplicating references on render,"They both have 21 references now. :P
+
+I see there were three references around the time of the bug entry
+https://en.wikipedia.org/w/index.php?title=Birbal&oldid=561978332
+
+We need to figure out how to make this problem reproducible.
+
+(bug 50521 looks similar, and might provide some clues on how to cause the renderer to get into this odd state)",task_subcomment,"['They both have 21 references now.', ':P\n\nI see there were three references around the time of the bug entry\nURL\n\nWe need to figure out how to make this problem reproducible.', '(bug 50521 looks similar, and might provide some clues on how to cause the renderer to get into this odd state)']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52364,"VisualEditor: Toolbar shows on top of Save dialog, prevents saving","screenshot
+
+I'm not sure if this is bug 49514 ; feel free to dupe if it is.
+
+See attached screenshot: the toolbar appears on top of the save dialog, which makes it difficult or impossible to save changes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11157}",task_description,"[""VisualEditor: Toolbar shows on top of Save dialog, prevents saving\n\nscreenshot\n\nI'm not sure if this is bug 49514 ; feel free to dupe if it is."", 'See attached screenshot: the toolbar appears on top of the save dialog, which makes it difficult or impossible to save changes.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11157}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234639,"VisualEditor: Toolbar shows on top of Save dialog, prevents saving","I think this is 50324 instead.
+
+*** This bug has been marked as a duplicate of bug 50324 ***",task_subcomment,"['I think this is 50324 instead.', '*** This bug has been marked as a duplicate of bug 50324 ***']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+52361,VisualEditor: modifying some templates causes them to collapse in on themselves in edit mode,"Screenshot
+
+Try modifying the infobox in https://en.wikipedia.org/wiki/Defiance_%28TV_series%29?veaction=edit for example - see the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11137}",task_description,"['VisualEditor: modifying some templates causes them to collapse in on themselves in edit mode\n\nScreenshot\n\nTry modifying the infobox in URL for example - see the screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11137}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234513,VisualEditor: modifying some templates causes them to collapse in on themselves in edit mode,"
+
+*** This bug has been marked as a duplicate of bug 49854 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49854 ***'],['ISSUE CONTENT MANAGEMENT']
+52359,"VisualEditor: Can't drag and drop transclusions, text, references","Users expect to be able to select, drag and drop most elements of the page, including snippets of text, templates & other transclusions, and references, just like they can do with images.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Can't drag and drop transclusions, text, references\n\nUsers expect to be able to select, drag and drop most elements of the page, including snippets of text, templates & other transclusions, and references, just like they can do with images."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234439,"VisualEditor: Can't drag and drop transclusions, text, references","Actually, bug 49981 is meant to cover everything; merging.
+
+*** This bug has been marked as a duplicate of bug 49981 ***",task_subcomment,"['Actually, bug 49981 is meant to cover everything; merging.', '*** This bug has been marked as a duplicate of bug 49981 ***']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+234431,"VisualEditor: Can't drag and drop transclusions, text, references","While for text there's 49981 open, itwp users also request this for templates.",task_subcomment,"[""While for text there's 49981 open, itwp users also request this for templates.""]",['POTENTIAL NEW ISSUES AND REQUESTS']
+52331,VisualEditor throws  next to any square bracket [,"It is usual to use [square brackets], [...] inside quotes to cut or complete sentences in quotes. As for today, VisualEditor will add  tags like this:
+
+[Square brackets]
+
+[...]
+
+This is not a big deal since the users will keep seeing the same in the published article, but it adds unnecessary cruft in edit source mode and it's wrong.
+
+Also, according to Bug 47678 this means that editors won't be able to edit the content inside those brackets with VisualEditor, because of the  tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T54268}",task_description,"['VisualEditor throws  next to any square bracket [\n\nIt is usual to use [square brackets], [...] inside quotes to cut or complete sentences in quotes.', ""As for today, VisualEditor will add  tags like this:\n\n[Square brackets]\n\n[...]\n\nThis is not a big deal since the users will keep seeing the same in the published article, but it adds unnecessary cruft in edit source mode and it's wrong."", ""Also, according to Bug 47678 this means that editors won't be able to edit the content inside those brackets with VisualEditor, because of the  tags."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\n{T54268}']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232663,VisualEditor throws  next to any square bracket [,"This bug was about single square brackets ([ ... ]), not wikitext links. 
+
+Entering [[Foo]] as text will practically always need to be escaped as the rules for valid page titles are less restrictive than those for absolute URLs. Same is true for linking parts of a word where the remainder of the word would become part of the link via the link trail mechanism (aka- less precisely- 'piped links'). Or entering any other random wikitext in the VE. Not escaping such wikitext would break the WYSIWYG promise.",task_subcomment,"['This bug was about single square brackets ([ ... ]), not wikitext links.', 'Entering [[Foo]] as text will practically always need to be escaped as the rules for valid page titles are less restrictive than those for absolute URLs.', ""Same is true for linking parts of a word where the remainder of the word would become part of the link via the link trail mechanism (aka- less precisely- 'piped links')."", 'Or entering any other random wikitext in the VE.', 'Not escaping such wikitext would break the WYSIWYG promise.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232654,VisualEditor throws  next to any square bracket [,"Not really sure if this applies as well, but will leave it here: http://en.wikipedia.org/w/index.php?title=Ingress_(game)&diff=prev&oldid=562432188 
+
+from
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Strange_result_with_a_.3C.2Fnowiki.3E_tag_inserted .
+Thanks.",task_subcomment,"['Not really sure if this applies as well, but will leave it here: URL \n\nfrom\nURL .', 'Thanks.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+232646,VisualEditor throws  next to any square bracket [,"Looks like we are either still have a problem or it may have resurfaced; last section of:
+
+http://en.wikipedia.org/w/index.php?title=Raphael_Sch%C3%A4fer&diff=prev&oldid=562506378
+
+and follow up edits.",task_subcomment,['Looks like we are either still have a problem or it may have resurfaced; last section of:\n\nURL\n\nand follow up edits.'],['OBSERVED BUG BEHAVIOR']
+232640,VisualEditor throws  next to any square bracket [,We have refined the nowiki escaping in Parsoid so that external link like syntax that does not have a valid target is no longer escaped.,task_subcomment,['We have refined the nowiki escaping in Parsoid so that external link like syntax that does not have a valid target is no longer escaped.'],['INVESTIGATION AND EXPLORATION']
+52313,VisualEditor: Cutting the text of a header leaves a blank header line behind,"Fairly self-explanatory.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Cutting the text of a header leaves a blank header line behind\n\nFairly self-explanatory.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231451,VisualEditor: Cutting the text of a header leaves a blank header line behind,"This is bug 50100.
+
+*** This bug has been marked as a duplicate of bug 50100 ***",task_subcomment,"['This is bug 50100.', '*** This bug has been marked as a duplicate of bug 50100 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231443,VisualEditor: Cutting the text of a header leaves a blank header line behind,"Removing a paragraph and header does the same - https://en.wikipedia.org/w/index.php?title=Idlib_Governorate_clashes_%28June_2012%E2%80%93present%29&curid=39240723&diff=562677456&oldid=562663343
+
+Can this please be prioritised and assigned?",task_subcomment,['Removing a paragraph and header does the same - URL\n\nCan this please be prioritised and assigned?'],['ACTION ON ISSUE']
+52312,VisualEditor: edit link on the history page needs updating,"The history page of any article has an 'edit' link on it; this currently takes you to source editing, which seems highly likely to confuse users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: edit link on the history page needs updating\n\nThe history page of any article has an 'edit' link on it; this currently takes you to source editing, which seems highly likely to confuse users."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+231398,VisualEditor: edit link on the history page needs updating,"How very strange. Slightly slower loading time giving a false impression, probably; thanks :).",task_subcomment,"['How very strange.', 'Slightly slower loading time giving a false impression, probably; thanks :).']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+231391,VisualEditor: edit link on the history page needs updating,"Do you mean the diff page - e.g. https://en.wikipedia.org/w/index.php?title=Barack_Obama&diff=561813443&oldid=561813311 - the history page e.g. https://en.wikipedia.org/wiki/Barack_Obama?action=history - or the oldid page - e.g. https://en.wikipedia.org/w/index.php?title=Barack_Obama&oldid=561813443 ?
+
+'Cos the second two work for me; the first one isn't a history page, though. :-)",task_subcomment,"['Do you mean the diff page - e.g.', 'URL - the history page e.g.', 'URL - or the oldid page - e.g.', 'URL ?', ""'Cos the second two work for me; the first one isn't a history page, though."", ':-)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+52295,Carriage return shows up among text,"This is what Alberobello looks like under VE
+
+When trying to edit http://it.wikipedia.org/wiki/Alberobello (tested with MonoBook on FF and Vector on Chrome) a few ""carriage returns"" appear in the first lines. I'd also add that I spot these in https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet : the line which says ""Test split on multiple lines""? It isn't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11918}",task_description,"['Carriage return shows up among text\n\nThis is what Alberobello looks like under VE\n\nWhen trying to edit URL (tested with MonoBook on FF and Vector on Chrome) a few ""carriage returns"" appear in the first lines.', 'I\'d also add that I spot these in URL : the line which says ""Test split on multiple lines""?', ""It isn't."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11918}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255695,Carriage return shows up among text,"(In reply to comment #0)
+> Created attachment 12662 [details]
+> This is what Alberobello looks like under VE
+> 
+> When trying to edit http://it.wikipedia.org/wiki/Alberobello (tested with
+> MonoBook on FF and Vector on Chrome) a few ""carriage returns"" appear in the
+> first lines.
+
+This is because the blank line is a 'slug' - see bug 47790 for further discussion.
+
+> I'd also add that I spot these in
+> https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet : the
+> line
+> which says ""Test split on multiple lines""? It isn't.
+
+It's a test of whether you can edit the caption with multiple lines for it to display correctly; it's not meant to actually end up on multiple lines, which is why it shows up with '↵'s instead.
+
+*** This bug has been marked as a duplicate of bug 47790 ***
+
+**Attached**: {F11918}",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis is because the blank line is a 'slug' - see bug 47790 for further discussion."", ""QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIt's a test of whether you can edit the caption with multiple lines for it to display correctly; it's not meant to actually end up on multiple lines, which is why it shows up with '↵'s instead."", '*** This bug has been marked as a duplicate of bug 47790 ***\n\n**Attached**: {F11918}']","['MOTIVATION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+52293,ULS doesn't work while using VisualEditor,"When VisualEditor is enabled there is no option to enable ULS, where I could type in Odia in the search bar using ULS.
+
+When VIsualEditor is enabled there typing is possible only in English. There is no option to change the language using ULS where as it works normally in the search bar. I have tested it for Odia Wikipedia for the article on Colombo: https://or.wikipedia.org/wiki/Colombo on Mac OS X 10.7.5 using browser Firefox 21.0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11913}",task_description,"[""ULS doesn't work while using VisualEditor\n\nWhen VisualEditor is enabled there is no option to enable ULS, where I could type in Odia in the search bar using ULS."", 'When VIsualEditor is enabled there typing is possible only in English.', 'There is no option to change the language using ULS where as it works normally in the search bar.', 'I have tested it for Odia Wikipedia for the article on Colombo: URL on Mac OS X 10.7.5 using browser Firefox 21.0.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11913}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255613,ULS doesn't work while using VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 49569 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49569 ***'],['ISSUE CONTENT MANAGEMENT']
+52290,VisualEditor: not permitting interaction with some media files (and formatting them weirdly),"See https://en.wikipedia.org/wiki/Mitochondrial_DNA?veaction=edit - the links appear, via source editing, to be perfectly normal, and yet you can't interact with them and they display oddly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: not permitting interaction with some media files (and formatting them weirdly)\n\nSee URL - the links appear, via source editing, to be perfectly normal, and yet you can't interact with them and they display oddly."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255457,VisualEditor: not permitting interaction with some media files (and formatting them weirdly),"This would have been bug 48900 in Parsoid.
+
+*** This bug has been marked as a duplicate of bug 48900 ***",task_subcomment,"['This would have been bug 48900 in Parsoid.', '*** This bug has been marked as a duplicate of bug 48900 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52283,VisualEditor: references cannot be copied and pasted without losing formatting,"Fairly self-explanatory. The reason this is important; being able to copy references across is crucial when using multiple references from one source item. If I have a book by Jones, from 2003, and I have a reference that reads Jones (2003) p.23 for one statement, and want to cite page 57 for another, it's a lot easier to change the page number than it is to type everything out again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: references cannot be copied and pasted without losing formatting\n\nFairly self-explanatory.', 'The reason this is important; being able to copy references across is crucial when using multiple references from one source item.', ""If I have a book by Jones, from 2003, and I have a reference that reads Jones (2003) p.23 for one statement, and want to cite page 57 for another, it's a lot easier to change the page number than it is to type everything out again."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+254975,VisualEditor: references cannot be copied and pasted without losing formatting,"This should be addressed when bug 33105 is fixed.
+
+*** This bug has been marked as a duplicate of bug 33105 ***",task_subcomment,"['This should be addressed when bug 33105 is fixed.', '*** This bug has been marked as a duplicate of bug 33105 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52278,VisualEditor: Page settings dialog adds categories with [[:Category:xyz]] syntax,"When you add a category to a page using the page settings dialog, it gets added as a wikilink [[:Category:xyz]], not a category inclusion [[Category:xyz]].
+
+Seen on testwiki and enwiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Page settings dialog adds categories with [[:Category:xyz]] syntax\n\nWhen you add a category to a page using the page settings dialog, it gets added as a wikilink [[:Category:xyz]], not a category inclusion [[Category:xyz]].', 'Seen on testwiki and enwiki.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254768,VisualEditor: Page settings dialog adds categories with [[:Category:xyz]] syntax,"This was a Parsoid bug, since fixed.",task_subcomment,"['This was a Parsoid bug, since fixed.']",['OBSERVED BUG BEHAVIOR']
+52276,VisualEditor: Toolbar obscures save dialog when scrolled down the page,"Screenshot of bug
+
+When scrolled down the page, the top of the save dialog is obscured by the toolbar. See screenshot.
+
+See also other z-index bugs: bug 49514 and bug 49275.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11882}",task_description,"['VisualEditor: Toolbar obscures save dialog when scrolled down the page\n\nScreenshot of bug\n\nWhen scrolled down the page, the top of the save dialog is obscured by the toolbar.', 'See screenshot.', 'See also other z-index bugs: bug 49514 and bug 49275.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11882}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254685,VisualEditor: Toolbar obscures save dialog when scrolled down the page,"
+
+*** This bug has been marked as a duplicate of bug 50324 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50324 ***'],['ISSUE CONTENT MANAGEMENT']
+52267,VisualEditor: not adhering to column numbers when rendering,"See https://en.wikipedia.org/wiki/Microorganism?veaction=edit#See_also for example; that should be divided into 3 columns.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: not adhering to column numbers when rendering\n\nSee URL for example; that should be divided into 3 columns.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254255,VisualEditor: not adhering to column numbers when rendering,"This is almost certainly the same as bug 50036.
+
+*** This bug has been marked as a duplicate of bug 50036 ***",task_subcomment,"['This is almost certainly the same as bug 50036.', '*** This bug has been marked as a duplicate of bug 50036 ***']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+52258,Unwanted Removal of text formatting,"In this edit:https://en.wikipedia.org/w/index.php?title=Blepsias_cirrhosus&diff=next&oldid=561719692
+
+Bold/italic formatting was removed by an unrelated action (addition of text).  See editor's description here:http://en.wikipedia.org/wiki/User_talk:PBASH607#VE_issues.3F
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['Unwanted Removal of text formatting\n\nIn this edit:URL\n\nBold/italic formatting was removed by an unrelated action (addition of text).', ""See editor's description here:URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253767,Unwanted Removal of text formatting,"Hey, yeah, this is a really irritating bug in Parsoid - bug 50068 - so marking this as a duplicate of that bug. Thanks for highlighting it, though - really important we try to fix this ASAP, and being reminded helps focus us!
+
+*** This bug has been marked as a duplicate of bug 50068 ***",task_subcomment,"['Hey, yeah, this is a really irritating bug in Parsoid - bug 50068 - so marking this as a duplicate of that bug.', 'Thanks for highlighting it, though - really important we try to fix this ASAP, and being reminded helps focus us!', '*** This bug has been marked as a duplicate of bug 50068 ***']","['BUG REPRODUCTION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+253759,Unwanted Removal of text formatting,Duplicated here: http://test.wikipedia.org/w/index.php?title=VisualEditor%3ATestingGrounds&diff=174932&oldid=174931,task_subcomment,['Duplicated here: URL'],['OBSERVED BUG BEHAVIOR']
+52249,'become' doesn't load ~/.bashrc,"When you use 'become' to log into a shared account, ~/.bashrc isn't run.
+
+catrope@tools-login:~$ become visualeditor
+local-visualeditor@tools-login:~$ cat ~/.bashrc
+# Shortcuts
+alias ..='cd ..'
+alias ll='ls -ahlF --color=auto'
+alias l='ll'
+
+# Environment
+export PATH=$HOME/bin:$PATH;
+
+local-visualeditor@tools-login:~$ echo $PATH
+/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
+local-visualeditor@tools-login:~$ . ~/.bashrc
+local-visualeditor@tools-login:~$ echo $PATH
+/data/project/visualeditor/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
+
+Adding $HOME/bin to $PATH would probably be a nice thing to do in general.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""'become' doesn't load ~/.bashrc\n\nWhen you use 'become' to log into a shared account, ~/.bashrc isn't run."", ""catrope@tools-login:~$ become visualeditor\nlocal-visualeditor@tools-login:~$ cat ~/.bashrc\n# Shortcuts\nalias ..='cd ..'\nalias ll='ls -ahlF --color=auto'\nalias l='ll'\n\n# Environment\nexport PATH=$HOME/bin:$PATH;\n\nlocal-visualeditor@tools-login:~$ echo $PATH\n/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin\nlocal-visualeditor@tools-login:~$ ."", '~/.bashrc\nlocal-visualeditor@tools-login:~$ echo $PATH\n/data/project/visualeditor/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin\n\nAdding $HOME/bin to $PATH would probably be a nice thing to do in general.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+253307,'become' doesn't load ~/.bashrc,"Works as designed.
+
+become, through sudo, creates an interactive login shell.  To quote from the bash info page:
+
+"" When Bash is invoked as an interactive login shell, or as a
+  non-interactive shell with the `--login' option, it first reads and
+  executes commands from the file `/etc/profile', if that file exists.
+  After reading that file, it looks for `~/.bash_profile',
+  `~/.bash_login', and `~/.profile', in that order, and reads and
+  executes commands from the first one that exists and is readable.""
+
+A thing many users may want to do to simplify things is to have a ~/.profile that sources ~/.bashrc (in addition or instead of login-specific behaviour) so that the latter gets sourced regardless of how the shell was invoked.",task_subcomment,"['Works as designed.', 'become, through sudo, creates an interactive login shell.', 'To quote from the bash info page:\n\n"" When Bash is invoked as an interactive login shell, or as a\n  non-interactive shell with the CODE/etc/profile\', if that file exists.', 'After reading that file, it looks for CODE~/.bash_login\', and `~/.profile\', in that order, and reads and\n  executes commands from the first one that exists and is readable.""', 'A thing many users may want to do to simplify things is to have a ~/.profile that sources ~/.bashrc (in addition or instead of login-specific behaviour) so that the latter gets sourced regardless of how the shell was invoked.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52248,screen doesn't work from within 'become',"catrope@tools-login:~$ become visualeditor
+local-visualeditor@tools-login:~$ screen
+Cannot open your terminal '/dev/pts/97' - please check.
+
+
+However, running screen as myself and then running 'become visualeditor' in each screen window does work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""screen doesn't work from within 'become'\n\ncatrope@tools-login:~$ become visualeditor\nlocal-visualeditor@tools-login:~$ screen\nCannot open your terminal '/dev/pts/97' - please check."", ""However, running screen as myself and then running 'become visualeditor' in each screen window does work."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253280,screen doesn't work from within 'become',"valhallasw@tools-login:~$ chown valhallasw:tools.tsreports /dev/pts/164
+valhallasw@tools-login:~$ chmod g+r /dev/pts/164
+valhallasw@tools-login:~$ become tsreports
+tools.tsreports@tools-login:~$ screen
+
+This works for me. I suppose there still is some security impact with this (I guess all tsreports users can now read my TTY? but that might already be possible when I 'become tsreports'?) but it's somewhat less extreme. 
+
+
+Alternatively, could log_input be used to redirect to /dev/null, thus mitigating the risk of log files?",task_subcomment,"['valhallasw@tools-login:~$ chown valhallasw:tools.tsreports /dev/pts/164\nvalhallasw@tools-login:~$ chmod g+r /dev/pts/164\nvalhallasw@tools-login:~$ become tsreports\ntools.tsreports@tools-login:~$ screen\n\nThis works for me.', 'I suppose there still is some security impact with this (I guess all tsreports users can now read my TTY?', ""but that might already be possible when I 'become tsreports'?)"", ""but it's somewhat less extreme."", 'Alternatively, could log_input be used to redirect to /dev/null, thus mitigating the risk of log files?']","['SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+253273,screen doesn't work from within 'become',"That will not be changed from the current method; automatically logging I/O is an unacceptable security risk, especially if it happens unconditionally and without the user's knowledge/consent.
+
+Run screen from your own user, or use screen to created a tty for the task.",task_subcomment,"[""That will not be changed from the current method; automatically logging I/O is an unacceptable security risk, especially if it happens unconditionally and without the user's knowledge/consent."", 'Run screen from your own user, or use screen to created a tty for the task.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+253268,screen doesn't work from within 'become',".bash_history records the commands you typed at the shell prompt that were actually submitted; recording the stream would include everything sent and/or received, including keystrokes to applications, typed passwords, etc.  For instance, if you mistakenly start to type a password in your ssh session because your focus was on the wrong window then backspace over it, .bash_history would not record it, log_input and log_output would.
+
+Another difference is that you can manage (delete, edit, verify) your .bash_history, whereas logged I/O is neither visible nor under your control.
+
+The logged I/O would only be available to roots; but much of that is stuff that I wouldn't want to exist on disk even granted perfect trust in everyone involved.  An accident that leaves /var/log/sudo-io/ accessible or a security flaw that allows escalation would expose that data -- on the instance or even the host.
+
+Key recording is just too much of an exposure, especially since the only putative benefit is the very marginal convenience of being able to start a screen session after sudo rather than just before it.",task_subcomment,"['.bash_history records the commands you typed at the shell prompt that were actually submitted; recording the stream would include everything sent and/or received, including keystrokes to applications, typed passwords, etc.', 'For instance, if you mistakenly start to type a password in your ssh session because your focus was on the wrong window then backspace over it, .bash_history would not record it, log_input and log_output would.', 'Another difference is that you can manage (delete, edit, verify) your .bash_history, whereas logged I/O is neither visible nor under your control.', ""The logged I/O would only be available to roots; but much of that is stuff that I wouldn't want to exist on disk even granted perfect trust in everyone involved."", 'An accident that leaves /var/log/sudo-io/ accessible or a security flaw that allows escalation would expose that data -- on the instance or even the host.', 'Key recording is just too much of an exposure, especially since the only putative benefit is the very marginal convenience of being able to start a screen session after sudo rather than just before it.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+253264,screen doesn't work from within 'become',"(In reply to comment #6)
+> ... at the cost of, you know, logging all the input and output of your
+> session.
+> 
+> Needless to say, that will not happen in Tool Labs -- even having the
+> capability to replay users' sessions (including passwords typed and all!)
+> would be a *massive* violation of privacy.
+
+Would it? What's the difference between this and .bash_history?
+
+Is the logged input/output available to all users or only to roots (and the session owner)?",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWould it?', ""What's the difference between this and .bash_history?"", 'Is the logged input/output available to all users or only to roots (and the session owner)?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+253260,screen doesn't work from within 'become',"Oh!  I figured out how they do it:  they have turned on log_input, log_output or both in their sudo configuration -- this causes the creation of a pty (like script does), and thus neatly circumvents the problem; the tty of the sudo-ed user is brand new and owned by the user.
+
+... at the cost of, you know, logging all the input and output of your session.
+
+Needless to say, that will not happen in Tool Labs -- even having the capability to replay users' sessions (including passwords typed and all!) would be a *massive* violation of privacy.
+
+I'm forced to wonder whether users of toolserver are aware that their sessions are logged in this way.",task_subcomment,"['Oh!', 'I figured out how they do it:  they have turned on log_input, log_output or both in their sudo configuration -- this causes the creation of a pty (like script does), and thus neatly circumvents the problem; the tty of the sudo-ed user is brand new and owned by the user.', '... at the cost of, you know, logging all the input and output of your session.', ""Needless to say, that will not happen in Tool Labs -- even having the capability to replay users' sessions (including passwords typed and all!)"", 'would be a *massive* violation of privacy.', ""I'm forced to wonder whether users of toolserver are aware that their sessions are logged in this way.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+253257,screen doesn't work from within 'become',"I can't tell; I don't have a MMP on the toolserver, and a cursory inspection of nightshade shows that screen isn't suid to root, which means that it should not be possible for it to open the tty when invoked from a sudo-ed user:
+
+crw--w---- 1 marc tty 136, 31 Sep  5 04:39 /dev/pts/31
+
+Whereas:
+
+-rwxr-sr-x 1 root utmp 364088 Jul 29  2009 /usr/bin/screen
+
+meaning that screen runs with the privileges of the invoking user, who would not have permission to open the terminal.  Can you switch to an MMP account and do a ""ls -l `tty`"" to see if something funky is going on with the terminal's permissions?  That might give me a hint.
+
+The hack with script is exactly that -- a hack: it creates a new shell, a new terminal pair, and has a process running busy shuffling the data between both sides of the pipe, with a copy to /dev/null.  At best, it is horribly wasteful and doubles context switches.",task_subcomment,"[""I can't tell; I don't have a MMP on the toolserver, and a cursory inspection of nightshade shows that screen isn't suid to root, which means that it should not be possible for it to open the tty when invoked from a sudo-ed user:\n\ncrw--w---- 1 marc tty 136, 31 Sep  5 04:39 /dev/pts/31\n\nWhereas:\n\n-rwxr-sr-x 1 root utmp 364088 Jul 29  2009 /usr/bin/screen\n\nmeaning that screen runs with the privileges of the invoking user, who would not have permission to open the terminal."", 'Can you switch to an MMP account and do a ""ls -l CODE"" to see if something funky is going on with the terminal\'s permissions?', 'That might give me a hint.', 'The hack with script is exactly that -- a hack: it creates a new shell, a new terminal pair, and has a process running busy shuffling the data between both sides of the pipe, with a copy to /dev/null.', 'At best, it is horribly wasteful and doubles context switches.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+253253,screen doesn't work from within 'become',"According to , it is possible on the Linux hosts, but not on the Solaris hosts. I just confirmed: dbreps@willow.toolserver.org (Solaris) gets the same error as above while dbreps@nightshade.toolserver.org (Linux) has no issue starting screen.
+
+The Toolserver folks had a workaround for Solaris hosts (using `ttyallow`), but now we've reached a new question: what did the Toolserver do on its Linux hosts to resolve this issue that Labs hasn't done?",task_subcomment,"['According to  to no avail. On IRC, I was told (by a bot, no less) that running ""script /dev/null"" is a workaround. It seems Roan found another workaround.
+
+At a minimum, this needs to be documented (which I'll do momentarily) and the error message could be hacked to be clearer what the hell is happening (""check /dev/pts/50"" is pretty much an online equivalent of ""go fuck yourself""). Re-opening this for further thought and consideration.",task_subcomment,"[""I don't remember the Toolserver having this issue."", ""This doesn't seem like a wontfix to me."", 'This is pretty awful behavior currently.', 'Surely we can do better.', ""local-dbreps@tools-login:~$ screen\nCannot open your terminal '/dev/pts/50' - please check."", 'I kept getting this.', 'I checked  (In reply to comment #0)
+> > Adding a template to a page (say, https://en.wikipedia.org/wiki/Eugene_Lies )
+> > for some reason blocks the opening of the page settings dialogue.
+> 
+> Is this in Monobook or in Vector? AFAICS this works for me in Vector fine; in
+> Monobook, there's the bug 50241 issue but that's it.
+
+Aha, tracked it down:
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 136 ve.ce.Document.js:187
+ve.ce.Document.getNodeAndOffset ve.ce.Document.js:187
+ve.ce.Surface.showSelection ve.ce.Surface.js:1296
+ve.ce.Surface.onChange ve.ce.Surface.js:745
+oo.EventEmitter.emit oo.js:421
+ve.dm.Surface.change ve.dm.Surface.js:402
+ve.dm.SurfaceFragment.insertContent ve.dm.SurfaceFragment.js:581
+ve.ui.MWTransclusionDialog.onClose ve.ui.MWTransclusionDialog.js:110
+ve.ui.Window.close ve.ui.Window.js:328
+(anonymous function) ve.ui.Dialog.js:118
+proxy load.php:775
+
+
+This is bug 47947 - which we really need to fix now. :-(
+
+*** This bug has been marked as a duplicate of bug 47947 ***",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAha, tracked it down:\n\nUncaught Error: Offset could not be translated to a DOM element and offset: 136 ve.ce.Document.js:187\nve.ce.Document.getNodeAndOffset ve.ce.Document.js:187\nve.ce.Surface.showSelection ve.ce.Surface.js:1296\nve.ce.Surface.onChange ve.ce.Surface.js:745\noo.EventEmitter.emit oo.js:421\nve.dm.Surface.change ve.dm.Surface.js:402\nve.dm.SurfaceFragment.insertContent ve.dm.SurfaceFragment.js:581\nve.ui.MWTransclusionDialog.onClose ve.ui.MWTransclusionDialog.js:110\nve.ui.Window.close ve.ui.Window.js:328\n(anonymous function) ve.ui.Dialog.js:118\nproxy load.php:775\n\n\nThis is bug 47947 - which we really need to fix now.', ':-(\n\n*** This bug has been marked as a duplicate of bug 47947 ***']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+252966,VisualEditor: Dialogs won't open after adding a template at the end of the page,"(In reply to comment #0)
+> Adding a template to a page (say, https://en.wikipedia.org/wiki/Eugene_Lies )
+> for some reason blocks the opening of the page settings dialogue.
+
+Is this in Monobook or in Vector? AFAICS this works for me in Vector fine; in Monobook, there's the bug 50241 issue but that's it.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\n\nIs this in Monobook or in Vector?', ""AFAICS this works for me in Vector fine; in Monobook, there's the bug 50241 issue but that's it.""]","['ACTION ON ISSUE', 'BUG REPRODUCTION']"
+52226,VisualEditor not working due to unflushed ResourceLoader cache?,"What ""not working"" means is that templates, links, references and images cannot be interacted with, at all. References and templates don't acknowledge they're there, images bug out, and the link inspector does not appear for links. I've had a group of users test this, and they've all reported wildly inconsistent results; this is happening for some but not for others, with no correlation in OS, browser or even skin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**Whiteboard**: aklapper-moreinfo",task_description,"['VisualEditor not working due to unflushed ResourceLoader cache?', 'What ""not working"" means is that templates, links, references and images cannot be interacted with, at all.', ""References and templates don't acknowledge they're there, images bug out, and the link inspector does not appear for links."", ""I've had a group of users test this, and they've all reported wildly inconsistent results; this is happening for some but not for others, with no correlation in OS, browser or even skin."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**Whiteboard**: aklapper-moreinfo']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251967,VisualEditor not working due to unflushed ResourceLoader cache?,"(In reply to comment #2)
+> I assume this is obsolete now?
+
+Sorry, yes, we got this fixed; thanks Sam, and thanks for the follow-up, Andre.",task_subcomment,"['(In reply to comment #2)\nQUOTE\n\nSorry, yes, we got this fixed; thanks Sam, and thanks for the follow-up, Andre.']",['SOLUTION USAGE']
+251961,VisualEditor not working due to unflushed ResourceLoader cache?,I assume this is obsolete now?,task_subcomment,['I assume this is obsolete now?'],['SOLUTION DISCUSSION']
+251955,VisualEditor not working due to unflushed ResourceLoader cache?,"I think we fixed this with a touch on ve.js by Reedy - please confirm? (Gah, forgot to say this 3 hours ago.)",task_subcomment,"['I think we fixed this with a touch on ve.js by Reedy - please confirm?', '(Gah, forgot to say this 3 hours ago.)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52213,VisualEditor: Extra bullet point before template containing bulleted list,"VE rendering of [[WUEC#External_links]] does not match MW rendering.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Extra bullet point before template containing bulleted list\n\nVE rendering of [[WUEC#External_links]] does not match MW rendering.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+251257,VisualEditor: Extra bullet point before template containing bulleted list,"This is a slightly-faulty use of wikitext on the page - it dereferences to
+
+*[http://www.wpr.org/ Wisconsin Public Radio]
+*{{FM station data|WUEC}}
+
+->
+
+*[http://www.wpr.org/ Wisconsin Public Radio]
+*
+*{{FMQ|WUEC}}
+*{{FML|WUEC}}
+*{{FMARB|WUEC}}
+
+… and gets displayed as such, in case you want to edit that otherwise-inexpliably-hidden bullet. Marking as INVALID (but yeah, eww at that wikitext).",task_subcomment,"['This is a slightly-faulty use of wikitext on the page - it dereferences to\n\n*[URL Wisconsin Public Radio]\n*{{FM station data|WUEC}}\n\n->\n\n*[URL Wisconsin Public Radio]\n*\n*{{FMQ|WUEC}}\n*{{FML|WUEC}}\n*{{FMARB|WUEC}}\n\n… and gets displayed as such, in case you want to edit that otherwise-inexpliably-hidden bullet.', 'Marking as INVALID (but yeah, eww at that wikitext).']","['SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+52211,VisualEditor: References prevent floats from being selected and edited,"screenshot
+
+When floats (like images or templates) are located at the same level as references, the blue rectangle of the references prevents the user from selecting (and editing) the floats. See attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11749}",task_description,"['VisualEditor: References prevent floats from being selected and edited\n\nscreenshot\n\nWhen floats (like images or templates) are located at the same level as references, the blue rectangle of the references prevents the user from selecting (and editing) the floats.', 'See attached screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11749}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251151,VisualEditor: References prevent floats from being selected and edited,"Entirely-confusingly, this is the same as bug 50395 (which is more detailed, so I'll up-merge this into that one). Sorry for the slow update.
+
+*** This bug has been marked as a duplicate of bug 50395 ***",task_subcomment,"[""Entirely-confusingly, this is the same as bug 50395 (which is more detailed, so I'll up-merge this into that one)."", 'Sorry for the slow update.', '*** This bug has been marked as a duplicate of bug 50395 ***']","['BUG REPRODUCTION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+52210,VisualEditor: Opening Page settings dialog doesn't close heading format drop-down,"screenshot
+
+Steps to reproduce:
+* Click on the heading format drop-down menu. Don't close it.
+* Click on the Page settings menu.
+
+Expected result:
+* The heading format drop-down is closed before the Page settings dialog shows up.
+
+Actual result:
+* The heading format drop-down remains open (and selectable) on top of the Page settings dialog (see attached screenshot).
+
+Observed in Firefox 21.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11748}",task_description,"[""VisualEditor: Opening Page settings dialog doesn't close heading format drop-down\n\nscreenshot\n\nSteps to reproduce:\n* Click on the heading format drop-down menu."", ""Don't close it."", '* Click on the Page settings menu.', 'Expected result:\n* The heading format drop-down is closed before the Page settings dialog shows up.', 'Actual result:\n* The heading format drop-down remains open (and selectable) on top of the Page settings dialog (see attached screenshot).', 'Observed in Firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11748}']","['BUG REPRODUCTION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251095,VisualEditor: Opening Page settings dialog doesn't close heading format drop-down,"This is still true (and deliberate), but since our major re-vamp of how windows stack on top of one another, no longer an issue; closing as FIXED.",task_subcomment,"['This is still true (and deliberate), but since our major re-vamp of how windows stack on top of one another, no longer an issue; closing as FIXED.']",['ACTION ON ISSUE']
+52207,VisualEditor: Image size parameter with spaces is ignored,"See [[testwiki:VisualEditor:Little or big]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Image size parameter with spaces is ignored\n\nSee [[testwiki:VisualEditor:Little or big]].', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+250900,VisualEditor: Image size parameter with spaces is ignored,"
+
+*** This bug has been marked as a duplicate of bug 49696 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49696 ***'],['ISSUE CONTENT MANAGEMENT']
+52204,Logging broken for GettingStarted (page-save-success logged as page-impression),"**Author:** `swalling`
+
+**Description:**
+Looking at the logs for the latest GettingStarted schema (GettingStartedNavbar_5496876) I am not finding a page-save-success event since June 6th. 
+
+This may have something to do with the VisualEditor split test or maybe not. I am seeing very few events (28 total) of any kind being logged on enwiki after 2013-06-20 when logging for the VE split test was enabled. This is obviously wrong, since there were more than 150 revisions tagged as gettingstarted-edit yesterday alone.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Logging broken for GettingStarted (page-save-success logged as page-impression)\n\n**Author:** CODE\n\n**Description:**\nLooking at the logs for the latest GettingStarted schema (GettingStartedNavbar_5496876) I am not finding a page-save-success event since June 6th.', 'This may have something to do with the VisualEditor split test or maybe not.', 'I am seeing very few events (28 total) of any kind being logged on enwiki after 2013-06-20 when logging for the VE split test was enabled.', 'This is obviously wrong, since there were more than 150 revisions tagged as gettingstarted-edit yesterday alone.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250671,Logging broken for GettingStarted (page-save-success logged as page-impression),"Looks properly fixed with the 2013-07-18 rollout of wmf10 to enwiki that included this fix, plus and later that day the changes to restore GettingStarted after CentralAuth/SUL2 changed.
+
+SELECT LEFT( timestamp, 8), COUNT(*) FROM GettingStartedNavbar_5588671 WHERE wiki = ""enwiki"" AND event_action = ""page-save-success"" AND event_funnel = ""returnto"" GROUP BY 1;
+
++---------------------+----------+
+| LEFT( timestamp, 8) | COUNT(*) |
++---------------------+----------+
+| 20130702            |        1 |
+| 20130718            |       17 |
+| 20130719            |      235 |
++---------------------+----------+",task_subcomment,"['Looks properly fixed with the 2013-07-18 rollout of wmf10 to enwiki that included this fix, plus and later that day the changes to restore GettingStarted after CentralAuth/SUL2 changed.', 'SELECT LEFT( timestamp, 8), COUNT(*) FROM GettingStartedNavbar_5588671 WHERE wiki = ""enwiki"" AND event_action = ""page-save-success"" AND event_funnel = ""returnto"" GROUP BY 1;\n\n+---------------------+----------+\n| LEFT( timestamp, 8) | COUNT(*) |\n+---------------------+----------+\n| 20130702            |        1 |\n| 20130718            |       17 |\n| 20130719            |      235 |\n+---------------------+----------+']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250664,Logging broken for GettingStarted (page-save-success logged as page-impression),"**swalling** wrote:
+
+https://gerrit.wikimedia.org/r/#/c/71575/ was scheduled to be deployed last week, but we flubbed a bit and it did not go out to 1.22wmf9 until today. 
+
+I am still seeing only one page-save-success in the returnto funnel as of today, so the patch not getting deployed may be the likely culprit.",task_subcomment,"['**swalling** wrote:\n\nURL was scheduled to be deployed last week, but we flubbed a bit and it did not go out to 1.22wmf9 until today.', 'I am still seeing only one page-save-success in the returnto funnel as of today, so the patch not getting deployed may be the likely culprit.']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+250657,Logging broken for GettingStarted (page-save-success logged as page-impression),"There are still no page-save-success + returnto events in prod, so there may be an RL issue.
+
+Re-opening until we're sure it's fixed.
+
+A relevant query is:
+
+SELECT COUNT(*) FROM GettingStartedNavbar_5588671 WHERE wiki = ""enwiki""
+AND event_action = ""page-save-success"" AND event_funnel = ""returnto"";",task_subcomment,"['There are still no page-save-success + returnto events in prod, so there may be an RL issue.', ""Re-opening until we're sure it's fixed."", 'A relevant query is:\n\nSELECT COUNT(*) FROM GettingStartedNavbar_5588671 WHERE wiki = ""enwiki""\nAND event_action = ""page-save-success"" AND event_funnel = ""returnto"";']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+250652,Logging broken for GettingStarted (page-save-success logged as page-impression),*** Bug 51208 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51208 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250648,Logging broken for GettingStarted (page-save-success logged as page-impression),"S's patch fixes the post-edit issue locally, which I believe is the same one I mentioned in comment 1.",task_subcomment,"[""S's patch fixes the post-edit issue locally, which I believe is the same one I mentioned in comment 1.""]",['BUG REPRODUCTION']
+250644,Logging broken for GettingStarted (page-save-success logged as page-impression),"Change 71575 merged by jenkins-bot:
+postEdit needs to run before GS logging
+
+https://gerrit.wikimedia.org/r/71575",task_subcomment,['Change 71575 merged by jenkins-bot:\npostEdit needs to run before GS logging\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250641,Logging broken for GettingStarted (page-save-success logged as page-impression),"Change 71575 had a related patch set uploaded by Spage:
+postEdit module needs to run before openTask
+
+https://gerrit.wikimedia.org/r/71575",task_subcomment,['Change 71575 had a related patch set uploaded by Spage:\npostEdit module needs to run before openTask\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+250637,Logging broken for GettingStarted (page-save-success logged as page-impression),"GettingStarted only logs page-save-success if wgPostEdit is true. On my local wiki I printed log messages from the two routines, and they sometimes came out:
+   about to log returnto page-impression
+   postEdit.js set wgPostEdit true!
+
+So the postEdit.js is running *after* openTask.js and that's why the wrong event is logged. On enwiki with resourceLoaderDebug cookie it did log a page-save-success event (go look at GettingStartedNavbar_5588671 where event_userId = 19275523), but without the RL debug in regular operation GS logs page-impression.
+
+RL loads postEdit first in its mw.loader.load() call at the end of the page body, but I don't know what RL's guarantee of code execution ordering is.
+
+Adding a dependency to ext.gettingstarted.openTask:
+        'mediawiki.action.view.postEdit', // need this to run prior
+
+seemed to fix it locally; another fix would be to use 
+        mw.hook( 'postEdit' ).add( function ()
+as VE does instead of changing the action from page-impression to page-save-success.
+
+I don't know how VE affects this, this was all clicking [Edit source].",task_subcomment,"['GettingStarted only logs page-save-success if wgPostEdit is true.', 'On my local wiki I printed log messages from the two routines, and they sometimes came out:\n   about to log returnto page-impression\n   postEdit.js set wgPostEdit true!', ""So the postEdit.js is running *after* openTask.js and that's why the wrong event is logged."", 'On enwiki with resourceLoaderDebug cookie it did log a page-save-success event (go look at GettingStartedNavbar_5588671 where event_userId = 19275523), but without the RL debug in regular operation GS logs page-impression.', ""RL loads postEdit first in its mw.loader.load() call at the end of the page body, but I don't know what RL's guarantee of code execution ordering is."", ""Adding a dependency to ext.gettingstarted.openTask:\n        'mediawiki.action.view.postEdit', // need this to run prior\n\nseemed to fix it locally; another fix would be to use \n        mw.hook( 'postEdit' ).add( function ()\nas VE does instead of changing the action from page-impression to page-save-success."", ""I don't know how VE affects this, this was all clicking [Edit source].""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250632,Logging broken for GettingStarted (page-save-success logged as page-impression),"**swalling** wrote:
+
+(In reply to comment #1)
+> The latest GettingStartedNavbar table is GettingStartedNavbar_5588671
+> (easiest
+> way to see is SHOW TABLES).
+> 
+> However, that doesn't convincingly explain why the latest (by timestamp)
+> enwiki
+> entries in GettingStartedNavbar_5496876 are a long string of
+> page-save-attempt
+> (the last of which is on 2013-06-26), but the latest page-save-success is
+> 2013-06-06.
+> 
+> It could be a coincidence, but it's worth looking into.
+
+Okay, you were correct, this is worth looking in to. In the most recent logs (GettingStartedNavbar_5588671) it seems we are not logging any page-save-success events for the returnto funnel. Logging for other events in the returnto funnel seem normal, and page saves all gettingstarted funnels (copyedit, clarify, addlinks) are normal.",task_subcomment,"['**swalling** wrote:\n\n(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOkay, you were correct, this is worth looking in to.', 'In the most recent logs (GettingStartedNavbar_5588671) it seems we are not logging any page-save-success events for the returnto funnel.', 'Logging for other events in the returnto funnel seem normal, and page saves all gettingstarted funnels (copyedit, clarify, addlinks) are normal.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250627,Logging broken for GettingStarted (page-save-success logged as page-impression),"**swalling** wrote:
+
+(In reply to comment #1)
+> The latest GettingStartedNavbar table is GettingStartedNavbar_5588671
+> (easiest
+> way to see is SHOW TABLES).
+> 
+
+Resolving as not a bug, accordingly, because there's no RESOLVED STEVENISDUMB. ;)",task_subcomment,"[""**swalling** wrote:\n\n(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nResolving as not a bug, accordingly, because there's no RESOLVED STEVENISDUMB."", ';)']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+250622,Logging broken for GettingStarted (page-save-success logged as page-impression),"The latest GettingStartedNavbar table is GettingStartedNavbar_5588671 (easiest way to see is SHOW TABLES).
+
+However, that doesn't convincingly explain why the latest (by timestamp) enwiki entries in GettingStartedNavbar_5496876 are a long string of page-save-attempt (the last of which is on 2013-06-26), but the latest page-save-success is 2013-06-06.
+
+It could be a coincidence, but it's worth looking into.",task_subcomment,"['The latest GettingStartedNavbar table is GettingStartedNavbar_5588671 (easiest way to see is SHOW TABLES).', ""However, that doesn't convincingly explain why the latest (by timestamp) enwiki entries in GettingStartedNavbar_5496876 are a long string of page-save-attempt (the last of which is on 2013-06-26), but the latest page-save-success is 2013-06-06."", ""It could be a coincidence, but it's worth looking into.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52181,VisualEditor: weird behaviour on reload following save (JS not loading?),"Specifically, a lot of JS-dependent things simply don't seem to work. Mostly those are gadgets (no big deal) but on reload, section edit links take you to the source editor. This is probably the most critical; I can imagine a workflow in which a newbie makes a change in the VE, saves, sees something else to tweak, goes to edit...ack! Broken the site!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: weird behaviour on reload following save (JS not loading?)', ""Specifically, a lot of JS-dependent things simply don't seem to work."", 'Mostly those are gadgets (no big deal) but on reload, section edit links take you to the source editor.', 'This is probably the most critical; I can imagine a workflow in which a newbie makes a change in the VE, saves, sees something else to tweak, goes to edit...ack!', 'Broken the site!', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249455,VisualEditor: weird behaviour on reload following save (JS not loading?),"Yeah, sorry about this bug, and my tardiness in replying; this was bug 49620, which we fixed just before you posted this, but only deployed the next day.
+
+*** This bug has been marked as a duplicate of bug 49620 ***",task_subcomment,"['Yeah, sorry about this bug, and my tardiness in replying; this was bug 49620, which we fixed just before you posted this, but only deployed the next day.', '*** This bug has been marked as a duplicate of bug 49620 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+52168,VisualEditor: Odd behavior using arrow keys for cursor movement,"Normally I would rewrite the bug description for bz, but JohnCD has given a very good demonstration on-wiki of strange cursor movements when navigating using arrow keys:
+
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=561499916#Some_funnies
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=561499916#Some_funnies",task_description,"['VisualEditor: Odd behavior using arrow keys for cursor movement\n\nNormally I would rewrite the bug description for bz, but JohnCD has given a very good demonstration on-wiki of strange cursor movements when navigating using arrow keys:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",['OBSERVED BUG BEHAVIOR']
+248776,VisualEditor: Odd behavior using arrow keys for cursor movement,"This is a duplicate of bug 48847, which we fixed last week; sorry for not getting to this bug until now.
+
+*** This bug has been marked as a duplicate of bug 48847 ***",task_subcomment,"['This is a duplicate of bug 48847, which we fixed last week; sorry for not getting to this bug until now.', '*** This bug has been marked as a duplicate of bug 48847 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52147," tags added to (valid) list in a template parameter, corrupting them","In general,
+
+{{foo
+bar = 
+* 1
+* 2
+* 3
+}}
+
+… is RT'ing to 
+
+{{foo
+bar = * 1
+* 2
+* 3
+}}
+
+Examples: 
+
+* https://en.wikipedia.org/w/index.php?title=Riddler&diff=561149660&oldid=561096940
+* https://en.wikipedia.org/w/index.php?title=Schuylar_Oordt&diff=561438828&oldid=561406705
+
+VisualEditor bug (to prevent dirty-DOMing and so hide this bug on RT) is bug 50070, but this will still occur when users edit the template unless this is recognised as valid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50070",task_description,"["" tags added to (valid) list in a template parameter, corrupting them\n\nIn general,\n\n{{foo\nbar = \n* 1\n* 2\n* 3\n}}\n\n… is RT'ing to \n\n{{foo\nbar = * 1\n* 2\n* 3\n}}\n\nExamples: \n\n* URL\n* URL\n\nVisualEditor bug (to prevent dirty-DOMing and so hide this bug on RT) is bug 50070, but this will still occur when users edit the template unless this is recognised as valid."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+247575," tags added to (valid) list in a template parameter, corrupting them","
+
+*** This bug has been marked as a duplicate of bug 50144 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50144 ***'],['ISSUE CONTENT MANAGEMENT']
+52143,Missing root git config file when cloning,"After modifying site.pp and provisioning, I got:
+
+notice: /Stage[main]/Role::Eventlogging/Mediawiki::Extension[EventLogging]/Git::Clone[mediawiki/extensions/EventLogging]/Exec[git clone mediawiki/extensions/EventLogging]/returns: fatal: unable to access '/root/.config/git/config': Permission denied                                                                                                                       
+resulting in:
+
+err: /Stage[main]/Role::Eventlogging/Mediawiki::Extension[EventLogging]/Git::Clone[mediawiki/extensions/EventLogging]/Exec[git clone mediawiki/extensions/EventLogging]/returns: change from notrun to 0 failed: git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/EventLogging.git /vagrant/mediawiki/extensions/EventLogging returned 128 instead of one of [0] at /tmp/vagrant-puppet/modules-0/git/manifests/clone.pp:40
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Missing root git config file when cloning\n\nAfter modifying site.pp and provisioning, I got:\n\nnotice: /Stage[main]/Role::Eventlogging/Mediawiki::Extension[EventLogging]/Git::Clone[mediawiki/extensions/EventLogging]/Exec[git clone mediawiki/extensions/EventLogging]/returns: fatal: unable to access '/root/.config/git/config': Permission denied                                                                                                                       \nresulting in:\n\nerr: /Stage[main]/Role::Eventlogging/Mediawiki::Extension[EventLogging]/Git::Clone[mediawiki/extensions/EventLogging]/Exec[git clone mediawiki/extensions/EventLogging]/returns: change from notrun to 0 failed: git clone URL /vagrant/mediawiki/extensions/EventLogging returned 128 instead of one of [0] at /tmp/vagrant-puppet/modules-0/git/manifests/clone.pp:40\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]",['OBSERVED BUG BEHAVIOR']
+247419,Missing root git config file when cloning,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],task_subcomment,"['[mass-moving from Tools>MediaWiki-Vagrant to separate product.', 'See bug 54041.', 'Filter bugmail on this comment.]']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+247414,Missing root git config file when cloning,"As of git 1.8.1.1 and above, if the home directory can't be accessed, it results in a fatal error. That was the cause of the error. I fixed it in gerrit change 71165.",task_subcomment,"[""As of git 1.8.1.1 and above, if the home directory can't be accessed, it results in a fatal error."", 'That was the cause of the error.', 'I fixed it in gerrit change 71165.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247409,Missing root git config file when cloning,"Change 71165 had a related patch set uploaded by Ori.livneh:
+Set $HOME when git-cloning
+
+https://gerrit.wikimedia.org/r/71165",task_subcomment,['Change 71165 had a related patch set uploaded by Ori.livneh:\nSet $HOME when git-cloning\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+247403,Missing root git config file when cloning,"Happens to me too. I did `git pull --ff-only` on my host, added ""include role::visualeditor"" to puppet/manifests/site.pp, and tried to run vagrant for the first time in weeks. I tried vagrant up, vagrant reload, and vagrant provision, and all failed early on with variations of the same error as above:
+
+[default] Running provisioner: puppet...
+Running Puppet with site.pp...
+info: Applying configuration version '1372472629'
+notice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Git::Clone[mediawiki/extensions/VisualEditor]/Exec[git clone mediawiki/extensions/VisualEditor]/returns: fatal: unable to access '/root/.config/git/config': Permission denied
+
+I can `vagrant ssh` and the wiki is running on http://127.0.0.1:8080/ , but Special:Version says I don't have VisualEditor installed. I'm running Ubuntu 13.04.",task_subcomment,"['Happens to me too.', 'I did CODE on my host, added ""include role::visualeditor"" to puppet/manifests/site.pp, and tried to run vagrant for the first time in weeks.', ""I tried vagrant up, vagrant reload, and vagrant provision, and all failed early on with variations of the same error as above:\n\n[default] Running provisioner: puppet...\nRunning Puppet with site.pp...\ninfo: Applying configuration version '1372472629'\nnotice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Git::Clone[mediawiki/extensions/VisualEditor]/Exec[git clone mediawiki/extensions/VisualEditor]/returns: fatal: unable to access '/root/.config/git/config': Permission denied\n\nI can CODE and the wiki is running on URL , but Special:Version says I don't have VisualEditor installed."", ""I'm running Ubuntu 13.04.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52142,"Images: Frameless images should not emit the ""caption"" as a 
                 even when it's set","[Not urgent.]
+
+Frameless images are special; the caption is meant to be the alt text, unless alt= is also set, in which case it's ignored - but Parsoid outputs a 
                 for images regardless of type (thumb, framed or frameless) - and doesn't output the alt at all, which is bug 45208.
+
+There's a hack in VisualEditor to ignore 
                s for these as part of bug 50113, but Parsoid should fix these in due course.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['Images: Frameless images should not emit the ""caption"" as a 
                 even when it\'s set\n\n[Not urgent.]', ""Frameless images are special; the caption is meant to be the alt text, unless alt= is also set, in which case it's ignored - but Parsoid outputs a 
                 for images regardless of type (thumb, framed or frameless) - and doesn't output the alt at all, which is bug 45208."", ""There's a hack in VisualEditor to ignore 
                s for these as part of bug 50113, but Parsoid should fix these in due course."", '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+247370,"Images: Frameless images should not emit the ""caption"" as a 
                 even when it's set",[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+247366,"Images: Frameless images should not emit the ""caption"" as a 
                 even when it's set",This is by design. See http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images for documentation and rationales.,task_subcomment,"['This is by design.', 'See URL for documentation and rationales.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+52116,VisualEditor adding spurious pipe separators to image syntax,"https://en.wikipedia.org/w/index.php?title=History_of_Delta_Air_Lines&curid=38607247&diff=561387547&oldid=557734729
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor adding spurious pipe separators to image syntax\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+245599,VisualEditor adding spurious pipe separators to image syntax,"
+
+*** This bug has been marked as a duplicate of bug 50012 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50012 ***'],['ISSUE CONTENT MANAGEMENT']
+245594,VisualEditor adding spurious pipe separators to image syntax,"[[File:Delta logo.svg|right|200px]] --> [[File:Delta logo.svg|right|200px|]]
+
+I've seen this in a few other diffs as well.",task_subcomment,"[""[[File:Delta logo.svg|right|200px]] --> [[File:Delta logo.svg|right|200px|]]\n\nI've seen this in a few other diffs as well.""]",['BUG REPRODUCTION']
+52108,VisualEditor template parameter normalization results in dirty diffs,"https://en.wikipedia.org/w/index.php?title=Laura_Pannack&diff=561375041&oldid=561336738
+
+The change should have only italicized a few publication names. Instead it changed...
+
+* Winner, Magenta Foundation award{{cite book |last= Pritchard | first= Lisa |authorlink= Lisa Pritchard|title= Setting Up a Successful Photography Business: How to be a Professional Photographer |url= http://books.google.co.uk/books?id=Nn4Zt5SBcswC&pg=PA134&lpg=PA134&dq=laura+pannack++Setting+up+a+Successful+Photography+Business&source=bl&ots=jPQTB9IuYE&sig=7xtX-t9WFQYB76Xo_ZlU06BnIrE&hl=en&sa=X&ei=QehaUZGZCJSa1AWR_oCICw&ved=0CC8Q6AEwAA#v=onepage&q=laura%20pannack%20%20Setting%20up%20a%20Successful%20Photography%20Business&f=false|accessdate= 2 April 2013 |year= |publisher= A & C Black Publishers Ltd|location= London|isbn= 978-1-408125-77-9|page= 134| quote = Laura Pannack ... twice winner of the Magenta Foundation Award}}
+
+to...
+
+* Winner, Magenta Foundation award{{cite book |last=Pritchard | first=Lisa |authorlink=Lisa Pritchard|title=Setting Up a Successful Photography Business: How to be a Professional Photographer |url=http://books.google.co.uk/books?id=Nn4Zt5SBcswC&pg=PA134&lpg=PA134&dq=laura+pannack++Setting+up+a+Successful+Photography+Business&source=bl&ots=jPQTB9IuYE&sig=7xtX-t9WFQYB76Xo_ZlU06BnIrE&hl=en&sa=X&ei=QehaUZGZCJSa1AWR_oCICw&ved=0CC8Q6AEwAA#v=onepage&q=laura%20pannack%20%20Setting%20up%20a%20Successful%20Photography%20Business&f=false|accessdate=2 April 2013 |year=|publisher=A & C Black Publishers Ltd|location=London|isbn=978-1-408125-77-9|page=134| quote =Laura Pannack ... twice winner of the Magenta Foundation Award}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor template parameter normalization results in dirty diffs\n\nURL\n\nThe change should have only italicized a few publication names.', 'Instead it changed...\n\n* Winner, Magenta Foundation award{{cite book |last= Pritchard | first= Lisa |authorlink= Lisa Pritchard|title= Setting Up a Successful Photography Business: How to be a Professional Photographer |url= URL 2 April 2013 |year= |publisher= A & C Black Publishers Ltd|location= London|isbn= 978-1-408125-77-9|page= 134| quote = Laura Pannack ... twice winner of the Magenta Foundation Award}}\n\nto...\n\n* Winner, Magenta Foundation award{{cite book |last=Pritchard | first=Lisa |authorlink=Lisa Pritchard|title=Setting Up a Successful Photography Business: How to be a Professional Photographer |url=URL April 2013 |year=|publisher=A & C Black Publishers Ltd|location=London|isbn=978-1-408125-77-9|page=134| quote =Laura Pannack ... twice winner of the Magenta Foundation Award}}\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'ISSUE CONTENT MANAGEMENT']"
+245113,VisualEditor template parameter normalization results in dirty diffs,"Closing ""bugs"" which consist of multiple issues.",task_subcomment,"['Closing ""bugs"" which consist of multiple issues.']",['ISSUE CONTENT MANAGEMENT']
+245110,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Save_Rock_and_Roll&curid=38419944&diff=561416388&oldid=561387755,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245105,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Ivan_Tan&curid=39767321&diff=561408770&oldid=561406619,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245101,VisualEditor template parameter normalization results in dirty diffs,"(In reply to comment #9)
+> This remains a duplicate of bug 50066; that is merged on VE end. There are
+> some artefacts due to Parsoid which are different bugs (which are also fixed
+> and being deployed this afternoon, hopefully) [...]
+
+Let's do this: mark this bug as resolved when it's actually resolved. Not when it may be hopefully resolved in the future.",task_subcomment,"[""(In reply to comment #9)\nQUOTE\nQUOTE\nQUOTE\n\nLet's do this: mark this bug as resolved when it's actually resolved."", 'Not when it may be hopefully resolved in the future.']","['ACTION ON ISSUE', 'FUTURE PLAN']"
+245096,VisualEditor template parameter normalization results in dirty diffs,"https://en.wikipedia.org/w/index.php?title=United_States_presidential_election,_1844&curid=40514&diff=561407211&oldid=559883253",task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245093,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Sela_(Saudi_Arabia)&curid=26371208&diff=561403748&oldid=561269241,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245090,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Kamelot&curid=1161493&diff=561402036&oldid=560661945,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245086,VisualEditor template parameter normalization results in dirty diffs,"This remains a duplicate of bug 50066; that is merged on VE end. There are some artefacts due to Parsoid which are different bugs (which are also fixed and being deployed this afternoon, hopefully), but Bugzilla doesn't have ""dupe of these seven bugs"" as an option.
+
+*** This bug has been marked as a duplicate of bug 50066 ***",task_subcomment,"['This remains a duplicate of bug 50066; that is merged on VE end.', 'There are some artefacts due to Parsoid which are different bugs (which are also fixed and being deployed this afternoon, hopefully), but Bugzilla doesn\'t have ""dupe of these seven bugs"" as an option.', '*** This bug has been marked as a duplicate of bug 50066 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245082,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=19th_Virginia_Infantry&curid=25759369&diff=561398799&oldid=561398641,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245079,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Dan_Penteado&curid=13006822&diff=561396894&oldid=561392351,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245076,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Low_Orbit_Ion_Cannon&curid=28240388&diff=561396775&oldid=560499820,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245071,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=MTV&curid=18856&diff=561395466&oldid=561389102,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245068,VisualEditor template parameter normalization results in dirty diffs,"https://en.wikipedia.org/w/index.php?title=Wappingers_Falls,_New_York&curid=126391&diff=561394799&oldid=561394670",task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245063,VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Wild_Pack&curid=29143457&diff=561394555&oldid=561394449,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+245059,VisualEditor template parameter normalization results in dirty diffs,"Re-opening this for now. This doesn't appear to be fixed:
+
+https://en.wikipedia.org/w/index.php?title=Paul_Evans_(footballer_born_1973)&curid=15575267&diff=561390930&oldid=561390588",task_subcomment,"['Re-opening this for now.', ""This doesn't appear to be fixed:\n\nURL""]","['ACTION ON ISSUE', 'BUG REPRODUCTION']"
+245057,VisualEditor template parameter normalization results in dirty diffs,"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50066 ***'],['ISSUE CONTENT MANAGEMENT']
+52106,VisualEditor ref weirdness,"https://en.wikipedia.org/w/index.php?title=Laura_Pannack&diff=561336738&oldid=557984097
+
+ --> 
+
+Weird.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor ref weirdness\n\nURL\n\n --> \n\nWeird.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244928,VisualEditor ref weirdness,https://en.wikipedia.org/w/index.php?title=Save_Rock_and_Roll&curid=38419944&diff=561416388&oldid=561387755,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+244922,VisualEditor ref weirdness,https://en.wikipedia.org/w/index.php?title=Daniel_Kahneman&curid=165492&diff=561411461&oldid=560179630,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+244916,VisualEditor ref weirdness,"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50066 ***'],['ISSUE CONTENT MANAGEMENT']
+52101,VisualEditor spurious attribute normalization (resulting in dirty diffs),"https://en.wikipedia.org/w/index.php?title=Christopher_Walken&curid=167790&diff=561335042&oldid=560573850
+
+https://en.wikipedia.org/w/index.php?title=Complement_fixation_test&diff=561335484&oldid=540954235
+
+https://en.wikipedia.org/w/index.php?title=List_of_first-class_cricket_records&curid=5507023&diff=561342472&oldid=560120426
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor spurious attribute normalization (resulting in dirty diffs)\n\nURL\n\nURL\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+244653,VisualEditor spurious attribute normalization (resulting in dirty diffs),"Closing ""bugs"" which consist of multiple issues.",task_subcomment,"['Closing ""bugs"" which consist of multiple issues.']",['ISSUE CONTENT MANAGEMENT']
+244648,VisualEditor spurious attribute normalization (resulting in dirty diffs),"This is still happening:
+
+https://en.wikipedia.org/w/index.php?title=Wappingers_Falls,_New_York&curid=126391&diff=561392322&oldid=560081821",task_subcomment,['This is still happening:\n\nURL'],['OBSERVED BUG BEHAVIOR']
+244641,VisualEditor spurious attribute normalization (resulting in dirty diffs),"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50066 ***'],['ISSUE CONTENT MANAGEMENT']
+52099,VisualEditor dirty diff,"https://en.wikipedia.org/w/index.php?title=Paula_Deen&diff=561368754&oldid=561308417
+
+I did a section edit to link ""Food Network"". This was the resulting diff.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor dirty diff\n\nURL\n\nI did a section edit to link ""Food Network"".', 'This was the resulting diff.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244489,VisualEditor dirty diff,"Sorry about this; fixed by bug 50066 which we'll deploy in a few minutes.
+
+*** This bug has been marked as a duplicate of bug 50066 ***",task_subcomment,"[""Sorry about this; fixed by bug 50066 which we'll deploy in a few minutes."", '*** This bug has been marked as a duplicate of bug 50066 ***']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+52086,VisualEditor: Impossible to review or save changes in IE10,"Screenshot of bug
+
+The ""review changes"" flyout looks broken and doesn't actually do anything.
+
+There's a script error:
+
+SCRIPT70: Permission denied 
+load.php, line 18 character 453
+
+With ""format JavaScript"" enabled (a real godsend of IE's dev tools) we see that the error is occurring on the first line of this for statement:
+
+for(i=0,len=oldDoc.head.childNodes.length;
+        i
+Projects:
+  mediawiki/extensions/VisualEditor
+     ^master$
+  operations/mediawiki-config
+     ^master$ 
+  test/mediawiki
+    
+  analytics/wikistats
+    
+  analytics/udp-filters
+    
+  operations/puppet
+    
+  analytics/webstatscollector
+    
+  analytics/libanon
+    
+  mediawiki/extensions/Parsoid
+    
+  mediawiki/core
+     (?!REL1_19)^(\.jshint|.*\.(js|json)$)
+    
+     ^(REL1_21|master)$^.*\.(js|json)$
+     ^master$
+     ^REL1_19$
+     ^REL1_20$
+     ^REL1_21
+    
+       
+  mediawiki/extensions/Math
+    
+  integration/docroot
+     ^master$
+
+Some of those jobs are shared with over pipelines (such as mediawiki-core-lint) and are thus meaningless.  The only candidates would be:
+
+
+mwext-VisualEditor-doc-publish
+beta-mediawiki-config-update
+beta-recompile-math-texvc
+test-mediawiki-docgen
+operations-puppet-doc
+parsoid-regressions
+mediawiki-core-regression-*
+integration-docroot-deploy
+
+
+If we wanted to do that for other repositories (such as mediawiki extensions), we will need to have JJB to create a new job and edit the Zuul template 'extensions-unittests' to have a postmerge pipeline.
+
+
+ I need to restart Jenkins next week, so I will look at installing the plugin.",task_subcomment,"['As Timo said, this will only be useful for Jobs triggering only on merge events.', ""In Zuul that is the 'postmerge' pipeline, its configuration is currently:\n\n\nConfigured Pipeline Manager postmerge\nEvents:\n  \nProjects:\n  mediawiki/extensions/VisualEditor\n     ^master$\n  operations/mediawiki-config\n     ^master$ \n  test/mediawiki\n    \n  analytics/wikistats\n    \n  analytics/udp-filters\n    \n  operations/puppet\n    \n  analytics/webstatscollector\n    \n  analytics/libanon\n    \n  mediawiki/extensions/Parsoid\n    \n  mediawiki/core\n     (?!REL1_19)^(\\.jshint|.*\\."", '(js|json)$)\n    \n     ^(REL1_21|master)$^.*\\.', '(js|json)$\n     ^master$\n     ^REL1_19$\n     ^REL1_20$\n     ^REL1_21\n    \n       \n  mediawiki/extensions/Math\n    \n  integration/docroot\n     ^master$\n\nSome of those jobs are shared with over pipelines (such as mediawiki-core-lint) and are thus meaningless.', ""The only candidates would be:\n\n\nmwext-VisualEditor-doc-publish\nbeta-mediawiki-config-update\nbeta-recompile-math-texvc\ntest-mediawiki-docgen\noperations-puppet-doc\nparsoid-regressions\nmediawiki-core-regression-*\nintegration-docroot-deploy\n\n\nIf we wanted to do that for other repositories (such as mediawiki extensions), we will need to have JJB to create a new job and edit the Zuul template 'extensions-unittests' to have a postmerge pipeline."", 'I need to restart Jenkins next week, so I will look at installing the plugin.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'WORKAROUNDS']"
+239941,Jenkins: Provide build status images,"Note that due to the way we currently separate larger build steps into separate jobs, you'd need to display about a dozen status badges to have the complete picture (e.g. mediawiki-core-lint, mediawiki-core-jslint, mediawiki-core-phpunit-groupA, mediawiki-core-phpunit-groupB, mediawiki-core-databaseless etc.).
+
+
+If we do want to display this somewhere (for the unlikely event that someone bypassed Jenkins), we would need to have a post-merge job that runs on master only (so that it isn't affected by failing tests from proposed changes in Gerrit).
+
+The closest we have for that is the post-merge job for phpunit regressions:
+
+https://integration.wikimedia.org/ci/view/MediaWiki/job/mediawiki-core-regression-master/
+
+This one only runs for master and only post-merge.
+
+Note though that this doesn't include phplint, jshint and qunit. Only phpunit.",task_subcomment,"[""Note that due to the way we currently separate larger build steps into separate jobs, you'd need to display about a dozen status badges to have the complete picture (e.g."", 'mediawiki-core-lint, mediawiki-core-jslint, mediawiki-core-phpunit-groupA, mediawiki-core-phpunit-groupB, mediawiki-core-databaseless etc.).', ""If we do want to display this somewhere (for the unlikely event that someone bypassed Jenkins), we would need to have a post-merge job that runs on master only (so that it isn't affected by failing tests from proposed changes in Gerrit)."", 'The closest we have for that is the post-merge job for phpunit regressions:\n\nURL\n\nThis one only runs for master and only post-merge.', ""Note though that this doesn't include phplint, jshint and qunit."", 'Only phpunit.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239931,Jenkins: Provide build status images,"Installing that plugin won't be very useful because we use Jenkins pre-merge, not post-merge.
+
+The builds you see in Jenkins are for patch sets in Gerrit. The latest build of those jobs have no meaning in correlation to the state of a repository as those builds are just an arbitrary sequence of builds on proposed changes.
+
+The build status of our branches (incl. master) is always passing because you can't merge a change if it would result in the build failing.
+
+Thus we don't need a status badge because our workflow (unlike most typical projects with e.g. Travis-CI set up on GitHub) makes it impossible not to be passing because we force every change to be pushed for review first, and is only merged after it is Verified by a passing build[1].
+
+[1] Unless someone with the appropriate user permissions bypasses Jenkins manually, which is frowned upon and would break Jenkins for every submitted patch set after that.",task_subcomment,"[""Installing that plugin won't be very useful because we use Jenkins pre-merge, not post-merge."", 'The builds you see in Jenkins are for patch sets in Gerrit.', 'The latest build of those jobs have no meaning in correlation to the state of a repository as those builds are just an arbitrary sequence of builds on proposed changes.', 'The build status of our branches (incl.', ""master) is always passing because you can't merge a change if it would result in the build failing."", ""Thus we don't need a status badge because our workflow (unlike most typical projects with e.g."", 'Travis-CI set up on GitHub) makes it impossible not to be passing because we force every change to be pushed for review first, and is only merged after it is Verified by a passing build[1].', '[1] Unless someone with the appropriate user permissions bypasses Jenkins manually, which is frowned upon and would break Jenkins for every submitted patch set after that.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+52019,Parametr adds =,"I have tryed to add {{Commonscat|Saint Robert of Molesme}} to the article w:cs:Robert z Molesme using VE. VE adds ""="" behind parametr in the code. See this revision: https://cs.wikipedia.org/w/index.php?title=Robert_z_Molesme&oldid=10436403
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://cs.wikipedia.org/w/index.php?title=Robert_z_Molesme&diff=10436403&oldid=10436394",task_description,"['Parametr adds =\n\nI have tryed to add {{Commonscat|Saint Robert of Molesme}} to the article w:cs:Robert z Molesme using VE.', 'VE adds ""="" behind parametr in the code.', 'See this revision: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239811,Parametr adds =,"But anyway, thx for explanation and sorry for disturbing!",task_subcomment,"['But anyway, thx for explanation and sorry for disturbing!']",['ACTION ON ISSUE']
+239806,Parametr adds =,"(In reply to comment #1)
+> ...the parameter name in this case is ""1""...
+
+Isnt this tricky? How the newbie should know, that ""parametr name is 1""?",task_subcomment,"['(In reply to comment #1)\nQUOTE\n\nIsnt this tricky?', 'How the newbie should know, that ""parametr name is 1""?']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+239800,Parametr adds =,"This was caused by you adding ""Saint Robert of Molesme"" as the parameter name rather than value - the parameter name in this case is ""1"", which wikitext can hide (the formal wikitext you were intending to add was ""{{Commonscat|1=Saint Robert of Molesme}}"".
+
+In English the label () is ""Parameter name"", which I believe is shown as ""Jméno parametru"" in Czech. I think the addition of the help documentation at https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide and linked from the help menu in the interface will reduce this occurring, but sorry for the confusion in the first place. :-(",task_subcomment,"['This was caused by you adding ""Saint Robert of Molesme"" as the parameter name rather than value - the parameter name in this case is ""1"", which wikitext can hide (the formal wikitext you were intending to add was ""{{Commonscat|1=Saint Robert of Molesme}}"".', 'In English the label () is ""Parameter name"", which I believe is shown as ""Jméno parametru"" in Czech.', 'I think the addition of the help documentation at URL and linked from the help menu in the interface will reduce this occurring, but sorry for the confusion in the first place.', ':-(']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+52016,Uncaught TypeError: Cannot read property 'description' of undefined,"After loading the Visual Editor on
+https://pt.wikipedia.org/wiki/Quadrado?veaction=edit&debug=1&uselang=pt&useskin=vector
+and clicking in the template which shows the text ""Wikicionário"", in the bottom right corner of the page, I get the following error on console (Google Chrome 28.0.1500.52):
+----
+Uncaught TypeError: Cannot read property 'description' of undefined 
+----
+
+It comes from the line 
+----
+if ( data.description !== null ) {
+----
+
+of the following script:
+https://bits.wikimedia.org/static-1.22wmf7/extensions/VisualEditor/modules/ve/dm/models/ve.dm.MWTemplateSpecModel.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Uncaught TypeError: Cannot read property \'description\' of undefined\n\nAfter loading the Visual Editor on\nURL\nand clicking in the template which shows the text ""Wikicionário"", in the bottom right corner of the page, I get the following error on console (Google Chrome 28.0.1500.52):\n----\nUncaught TypeError: Cannot read property \'description\' of undefined \n----\n\nIt comes from the line \n----\nif ( data.description !== null ) {\n----\n\nof the following script:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR']
+239680,Uncaught TypeError: Cannot read property 'description' of undefined,"This is the same as bug 49493 which is fixed in master and now in production; sorry for the disruption.
+
+*** This bug has been marked as a duplicate of bug 49493 ***",task_subcomment,"['This is the same as bug 49493 which is fixed in master and now in production; sorry for the disruption.', '*** This bug has been marked as a duplicate of bug 49493 ***']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+51986,Provide ability to alternate between visual and source editing,"A user suggested at
+https://pt.wikipedia.org/wiki/WP:Editor_Visual/Coment%C3%A1rios?oldid=36175459#Alternar_entre_editores_sem_sair_da_p.C3.A1gina
+which there should be a way to alternate between the two edit methods (visual/source), to avoid having to do two edits, when e.g. we are not able to finish our edit using the Visual Editor (maybe because we underestimate its difficulty, and changed our mind while using VisualEditor).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Provide ability to alternate between visual and source editing\n\nA user suggested at\nURL\nwhich there should be a way to alternate between the two edit methods (visual/source), to avoid having to do two edits, when e.g.', 'we are not able to finish our edit using the Visual Editor (maybe because we underestimate its difficulty, and changed our mind while using VisualEditor).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237997,Provide ability to alternate between visual and source editing,"Already suggested as bug 47779.
+
+*** This bug has been marked as a duplicate of bug 47779 ***",task_subcomment,"['Already suggested as bug 47779.', '*** This bug has been marked as a duplicate of bug 47779 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+51984,VisualEditor: Insecure image links on https,"When I open
+https://pt.wikipedia.org/wiki/Jorge_VI_do_Reino_Unido?veaction=edit
+I see several warnings like this on Google Chrome:
+
+The page at https://pt.wikipedia.org/wiki/Jorge_VI_do_Reino_Unido?veaction=edit displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/4/4a/Commons-logo.svg/22px-Commons-logo.svg.png.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor: Insecure image links on https\n\nWhen I open\nURL\nI see several warnings like this on Google Chrome:\n\nThe page at URL displayed insecure content from URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+237865,VisualEditor: Insecure image links on https,"
+
+*** This bug has been marked as a duplicate of bug 43015 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 43015 ***'],['ISSUE CONTENT MANAGEMENT']
+51960,VisualEditor: not functioning on it.wiki,"Screenshot
+
+See associated screenshot; that's the VE, in edit mode, on it.wiki. You can apparently still type into the window, but aren't given the toolbar or, for that matter, the ability to save. Erica is currently testing it.wiki's default gadgets one by one to see if any of those are causing the problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11224}",task_description,"[""VisualEditor: not functioning on it.wiki\n\nScreenshot\n\nSee associated screenshot; that's the VE, in edit mode, on it.wiki."", ""You can apparently still type into the window, but aren't given the toolbar or, for that matter, the ability to save."", ""Erica is currently testing it.wiki's default gadgets one by one to see if any of those are causing the problem."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11224}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236220,VisualEditor: not functioning on it.wiki,"Cool; marking as resolved. I'd suggest speaking to the QE author quickfast, then :D.",task_subcomment,"['Cool; marking as resolved.', ""I'd suggest speaking to the QE author quickfast, then :D.""]","['SOLUTION USAGE', 'ACTION ON ISSUE']"
+236215,VisualEditor: not functioning on it.wiki,"Confirming it's QE's fault, http://it.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FCommenti&diff=59583884&oldid=59583801",task_subcomment,"[""Confirming it's QE's fault, URL""]",['OBSERVED BUG BEHAVIOR']
+236212,VisualEditor: not functioning on it.wiki,"I need to point out that I'm testing gadgets I added, I'm pretty sure defaults are ok :) http://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox&diff=59583614&oldid=59581474 tells me QuickEdit might cause the trouble here, since I managed to edit with VE without it.",task_subcomment,"[""I need to point out that I'm testing gadgets I added, I'm pretty sure defaults are ok :) URL tells me QuickEdit might cause the trouble here, since I managed to edit with VE without it.""]",['OBSERVED BUG BEHAVIOR']
+51950,Required 'Edit Source' at Sections,"At present, VisualEditor is invoked when clicking on the Edit link of sections. Please provide 'Edit Source' link in addition to that for each section.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Required 'Edit Source' at Sections\n\nAt present, VisualEditor is invoked when clicking on the Edit link of sections."", ""Please provide 'Edit Source' link in addition to that for each section."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+235627,Required 'Edit Source' at Sections,"This is a duplicate of bug 49666 which we hope to do very soon.
+
+*** This bug has been marked as a duplicate of bug 49666 ***",task_subcomment,"['This is a duplicate of bug 49666 which we hope to do very soon.', '*** This bug has been marked as a duplicate of bug 49666 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+51939,VisualEditor translates templates into Uzbek language,"When I edit https://en.wikipedia.org/wiki/Golden_tortoise_beetle in VE, the template names at the top and bottom are suddenly in Uzbek (""Turkum:Biologik turlar"" and ""Andoza:Chrysomelidae-stub"") and parts of the contents of the rendered infobox are in Uzbek as well (""Kingdom:"" becomes ""Olam:"" etc.).
+
+More evidence of VE's growing self-awareness? Caffeine-induced hallucination on the reporter's part? Inquiring minds want to know.
+
+Chrome/Ubuntu and FF/Ubuntu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor translates templates into Uzbek language\n\nWhen I edit URL in VE, the template names at the top and bottom are suddenly in Uzbek (""Turkum:Biologik turlar"" and ""Andoza:Chrysomelidae-stub"") and parts of the contents of the rendered infobox are in Uzbek as well (""Kingdom:"" becomes ""Olam:"" etc.).', ""More evidence of VE's growing self-awareness?"", ""Caffeine-induced hallucination on the reporter's part?"", 'Inquiring minds want to know.', 'Chrome/Ubuntu and FF/Ubuntu.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235015,VisualEditor translates templates into Uzbek language,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+235007,VisualEditor translates templates into Uzbek language,"Caffeine-induced hallucination on the reporter's part would have been a better explanation.  Yes, 49411 again.
+
+*** This bug has been marked as a duplicate of bug 49411 ***",task_subcomment,"[""Caffeine-induced hallucination on the reporter's part would have been a better explanation."", 'Yes, 49411 again.', '*** This bug has been marked as a duplicate of bug 49411 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235001,VisualEditor translates templates into Uzbek language,Looks like a Parsoid caching issue: bug 49411 again?,task_subcomment,['Looks like a Parsoid caching issue: bug 49411 again?'],['OBSERVED BUG BEHAVIOR']
+51919,"VisualEditor: Internal wiki link using ""pipe trick"" [[/Foo/]] to link to sub page broken","Screenshot of problem. Compares VE view and MWParser view.
+
+Wikitext [[/Foo/]] should be interpreted as a link to ./Foo with label ""Foo"". This is likely a bug in Parsoid but I'm filing it in VisualEditor for now (feel free to make dependant on a Parsoid bug, or if it requires no action from our end, re-purpose and move there).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11096}",task_description,"['VisualEditor: Internal wiki link using ""pipe trick"" [[/Foo/]] to link to sub page broken\n\nScreenshot of problem.', 'Compares VE view and MWParser view.', 'Wikitext [[/Foo/]] should be interpreted as a link to ./Foo with label ""Foo"".', ""This is likely a bug in Parsoid but I'm filing it in VisualEditor for now (feel free to make dependant on a Parsoid bug, or if it requires no action from our end, re-purpose and move there)."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11096}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+233418,"VisualEditor: Internal wiki link using ""pipe trick"" [[/Foo/]] to link to sub page broken","
+
+*** This bug has been marked as a duplicate of bug 48081 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 48081 ***'],['ACTION ON ISSUE']
+51891,Parsoid: full sized images are displayed regardless of a |pictured parameter,"In particular it appears that the |pictured parameter in a file link is not being recognised. Take a look at https://en.wikipedia.org/wiki/User:PamD in the VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Parsoid: full sized images are displayed regardless of a |pictured parameter\n\nIn particular it appears that the |pictured parameter in a file link is not being recognised.', 'Take a look at URL in the VisualEditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231505,Parsoid: full sized images are displayed regardless of a |pictured parameter,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+231499,Parsoid: full sized images are displayed regardless of a |pictured parameter,"This is a dupe of bug 48387 which is fixed and deployed as of a few minutes ago but Parsoid's cache needs to be purged for this to show up.
+
+*** This bug has been marked as a duplicate of bug 48387 ***",task_subcomment,"[""This is a dupe of bug 48387 which is fixed and deployed as of a few minutes ago but Parsoid's cache needs to be purged for this to show up."", '*** This bug has been marked as a duplicate of bug 48387 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+231493,Parsoid: full sized images are displayed regardless of a |pictured parameter,"Aha,",task_subcomment,"['Aha,']",['OBSERVED BUG BEHAVIOR']
+231488,Parsoid: full sized images are displayed regardless of a |pictured parameter,"No, it's the : in front of the Image:name, that isn't being recognized.",task_subcomment,"[""No, it's the : in front of the Image:name, that isn't being recognized.""]",['OBSERVED BUG BEHAVIOR']
+51877,VisualEditor: Pawn ♙ appears when bolding multiple list items at same time,"If one creates two list items and then tries to bold them at the same time, the items are removed and replaced with a pawn symbol. This is reproducible on the version currently deployed on the English Wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Pawn ♙ appears when bolding multiple list items at same time\n\nIf one creates two list items and then tries to bold them at the same time, the items are removed and replaced with a pawn symbol.', 'This is reproducible on the version currently deployed on the English Wikipedia.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+230629,VisualEditor: Pawn ♙ appears when bolding multiple list items at same time,"Dupe of bug 49732 which is fixed in master and wmf8; will get that pushed to production wmf7 tonight.
+
+*** This bug has been marked as a duplicate of bug 49732 ***",task_subcomment,"['Dupe of bug 49732 which is fixed in master and wmf8; will get that pushed to production wmf7 tonight.', '*** This bug has been marked as a duplicate of bug 49732 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+51824,Existing image inclusions are duplicated and truncated by VisualEditor,"In the following edits, images that were already in the article were duplicated on save, and the duplicate was truncated:
+
+https://fr.wikipedia.org/w/index.php?diff=94163829
+https://www.mediawiki.org/w/index.php?diff=713109
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Existing image inclusions are duplicated and truncated by VisualEditor\n\nIn the following edits, images that were already in the article were duplicated on save, and the duplicate was truncated:\n\nURL\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR']
+252856,Existing image inclusions are duplicated and truncated by VisualEditor,"This is 49729.
+
+*** This bug has been marked as a duplicate of bug 49729 ***",task_subcomment,"['This is 49729.', '*** This bug has been marked as a duplicate of bug 49729 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252852,Existing image inclusions are duplicated and truncated by VisualEditor,"(sorry, just saw the first edit.)",task_subcomment,"['(sorry, just saw the first edit.)']",['OBSERVED BUG BEHAVIOR']
+252845,Existing image inclusions are duplicated and truncated by VisualEditor,One more: https://www.mediawiki.org/w/index.php?title=VisualEditor%2FFAQ&diff=713663&oldid=713655,task_subcomment,['One more: URL'],['SOLUTION DISCUSSION']
+51810,Parsoid cannot parse some wikimarkup,"See https://en.wikipedia.org/wiki/User:Kephir/acid
+
+In the VE: https://en.wikipedia.org/wiki/File:MediaWiki_acid_markup_-_VisualEditor.png
+In the normal, rendered page: https://en.wikipedia.org/wiki/File:MediaWiki_acid_markup_-_native_rendering.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Parsoid cannot parse some wikimarkup\n\nSee URL\n\nIn the VE: URL\nIn the normal, rendered page: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR']
+251855,Parsoid cannot parse some wikimarkup,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+251846,Parsoid cannot parse some wikimarkup,"Note that the use of HTML comments mid-token was WONTFIXed: bug 49750.
+
+*** This bug has been marked as a duplicate of bug 49753 ***",task_subcomment,"['Note that the use of HTML comments mid-token was WONTFIXed: bug 49750.', '*** This bug has been marked as a duplicate of bug 49753 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51802,VisualEditor: IE8 support,"Tracking bug; the VisualEditor doesn't seem to work in IE8 (this may be a feature as well as a bug). I'm going to recommend that people upgrade, and mark this as an enhancement, but: it would be nice to have an official statement on if this is coming, if so, when, if not, why, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: IE8 support\n\nTracking bug; the VisualEditor doesn't seem to work in IE8 (this may be a feature as well as a bug)."", ""I'm going to recommend that people upgrade, and mark this as an enhancement, but: it would be nice to have an official statement on if this is coming, if so, when, if not, why, etc."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+251182,VisualEditor: IE8 support,Great! Thanks.,task_subcomment,"['Great!', 'Thanks.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251178,VisualEditor: IE8 support,"(In reply to comment #4)
+> Makes a lot of sense. Any specific technologies that are problematic? Just
+> so I can avoid coming off as ""we're not doing it, it's hard"".
+
+Primary technologies:
+* HTML 5, most notably with ContentEditable (IE8 has basic support; IE in general has major issues with elements that aren't editable inside ones that are - e.g. templates inside pages - though we've found a way to hack around it in IE9&10 for now)
+* Javascript (ECMAScript) 5 (not all of it, which is good as IE9 doesn't do that either, but more than IE8 supports)
+* Selection interaction (IE's support is... Quixotic, to be polite)
+* Key detection/over-riding (same as for selection)",task_subcomment,"[""(In reply to comment #4)\nQUOTE\nQUOTE\n\nPrimary technologies:\n* HTML 5, most notably with ContentEditable (IE8 has basic support; IE in general has major issues with elements that aren't editable inside ones that are - e.g."", ""templates inside pages - though we've found a way to hack around it in IE9&10 for now)\n* Javascript (ECMAScript) 5 (not all of it, which is good as IE9 doesn't do that either, but more than IE8 supports)\n* Selection interaction (IE's support is... Quixotic, to be polite)\n* Key detection/over-riding (same as for selection)""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+251175,VisualEditor: IE8 support,"Makes a lot of sense. Any specific technologies that are problematic? Just so I can avoid coming off as ""we're not doing it, it's hard"".",task_subcomment,"['Makes a lot of sense.', 'Any specific technologies that are problematic?', 'Just so I can avoid coming off as ""we\'re not doing it, it\'s hard"".']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+251169,VisualEditor: IE8 support,"This is a WONTFIX; Internet Explorer in general doesn't support many of the key technologies that VisualEditor relies upon, and this becomes more acute the further back from IE10 you get.
+
+Supporting ""just"" IE9 and IE10 has been approximately 90% of our browser-specific workload; for IE8 support, we would need to write an entirely parallel implementation of VisualEditor just for that (and even then, most things wouldn't work).
+
+We cannot justify spending a very significant amount of donors' funds on IE8, which is (as of May) less than 5% of all our readers, and likely even less than that for editors. See [[mw:VisualEditor/Target browser matrix]] (which needs to be updated) for detail about which browsers we actively support.",task_subcomment,"[""This is a WONTFIX; Internet Explorer in general doesn't support many of the key technologies that VisualEditor relies upon, and this becomes more acute the further back from IE10 you get."", 'Supporting ""just"" IE9 and IE10 has been approximately 90% of our browser-specific workload; for IE8 support, we would need to write an entirely parallel implementation of VisualEditor just for that (and even then, most things wouldn\'t work).', ""We cannot justify spending a very significant amount of donors' funds on IE8, which is (as of May) less than 5% of all our readers, and likely even less than that for editors."", 'See [[mw:VisualEditor/Target browser matrix]] (which needs to be updated) for detail about which browsers we actively support.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+251164,VisualEditor: IE8 support,That's an en_INTERNET idiom. Do you want me to sic the internationalisation team on you? Cuz I will.,task_subcomment,"[""That's an en_INTERNET idiom."", 'Do you want me to sic the internationalisation team on you?', 'Cuz I will.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+251158,VisualEditor: IE8 support,Kill it with fire!,task_subcomment,['Kill it with fire!'],['INVESTIGATION AND EXPLORATION']
+51795,VisualEditor: Insert media create link to undefined,"https://en.wikipedia.org/?diff=560548908
+
+Step to reproduce:
+1. Click on the ""Media"" button on VisualEditor toolbar
+2. Choose a media to insert
+3. Click ""Insert media""
+4. Save page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Insert media create link to undefined\n\nURL\n\nStep to reproduce:\n1.', 'Click on the ""Media"" button on VisualEditor toolbar\n2.', 'Choose a media to insert\n3.', 'Click ""Insert media""\n4.', 'Save page\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250757,VisualEditor: Insert media create link to undefined,"Same thing?
+
+*** This bug has been marked as a duplicate of bug 49596 ***",task_subcomment,"['Same thing?', '*** This bug has been marked as a duplicate of bug 49596 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51768,VisualEditor: strange artefact in monobook when resizing images,"Screenshot
+
+Check out the top left of the screen; interacting with an image, in a resize-y way, causes resize-like highlighting to appear in monobook.
+
+Windows 7, Firefox 21.0
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11696}",task_description,"['VisualEditor: strange artefact in monobook when resizing images\n\nScreenshot\n\nCheck out the top left of the screen; interacting with an image, in a resize-y way, causes resize-like highlighting to appear in monobook.', 'Windows 7, Firefox 21.0\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11696}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+249272,VisualEditor: strange artefact in monobook when resizing images,"This is a duplicate of bug 50074 (despite the naming, it was a wider issue with phantoms), which is now fixed.
+
+*** This bug has been marked as a duplicate of bug 50074 ***",task_subcomment,"['This is a duplicate of bug 50074 (despite the naming, it was a wider issue with phantoms), which is now fixed.', '*** This bug has been marked as a duplicate of bug 50074 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51756,"VisualEditor: VE providing unasked-for removal of ""duplicate"" formatting","See (ferinstance) https://en.wikipedia.org/w/index.php?title=User:JohnCD/draft&diff=560430675&oldid=560430611
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: VE providing unasked-for removal of ""duplicate"" formatting\n\nSee (ferinstance) URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR']
+248519,"VisualEditor: VE providing unasked-for removal of ""duplicate"" formatting","
+
+%%%*** This bug has been marked as a duplicate of bug 49755 ***%%%",task_subcomment,['\n\n%%%*** This bug has been marked as a duplicate of bug 49755 ***%%%'],['ACTION ON ISSUE']
+51739,Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them,"If you explicitly declare positional parameters in a template, and then edit it with the Visual Editor, the Template Inspector converts it to implicitly declared positional parameters - i.e. {{some template|1= foo |2= bar }} becomes {{some template|foo|bar}}.
+
+Now, if an explicit positional parameter contains an equals sign, then the Template Inspector puts nowiki tags around it. So {{some template|1= foo=bar |2= baz }} becomes {{some template|foo=bar|baz}}. However, ""foo=bar"" and ""foo=bar"" are not equivalent wikitext. For example, nowiki tags will break wikilinks.
+
+There's an example of the difference in this diff:
+https://www.mediawiki.org/w/index.php?title=VisualEditor:Template_test&diff=712906&oldid=712905
+
+See the effects for the revisions before and after (look at the ""Inline template"" section).
+
+Before: https://www.mediawiki.org/w/index.php?title=VisualEditor:Template_test&oldid=712905
+After: https://www.mediawiki.org/w/index.php?title=VisualEditor:Template_test&oldid=712906
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them\n\nIf you explicitly declare positional parameters in a template, and then edit it with the Visual Editor, the Template Inspector converts it to implicitly declared positional parameters - i.e."", '{{some template|1= foo |2= bar }} becomes {{some template|foo|bar}}.', 'Now, if an explicit positional parameter contains an equals sign, then the Template Inspector puts nowiki tags around it.', 'So {{some template|1= foo=bar |2= baz }} becomes {{some template|foo=bar|baz}}.', 'However, ""foo=bar"" and ""foo=bar"" are not equivalent wikitext.', 'For example, nowiki tags will break wikilinks.', 'There\'s an example of the difference in this diff:\nURL\n\nSee the effects for the revisions before and after (look at the ""Inline template"" section).', 'Before: URL\nAfter: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+247573,Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them,"Change 72876 merged by jenkins-bot:
+Bug 49739: Use named parameter if value contains '='
+
+https://gerrit.wikimedia.org/r/72876",task_subcomment,"[""Change 72876 merged by jenkins-bot:\nBug 49739: Use named parameter if value contains '='\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+247568,Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them,"Change 72876 had a related patch set uploaded by GWicke:
+Bug 49739: Use named parameter if value contains '='
+
+https://gerrit.wikimedia.org/r/72876",task_subcomment,"[""Change 72876 had a related patch set uploaded by GWicke:\nBug 49739: Use named parameter if value contains '='\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+247564,Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them,"This feels like a Parsoid bug, but I'm not sure? The user creating the equivalent of {{foo|1=foo|2=bar=foo}} should serialise to {{foo|foo|2=bar=foo}} instead of  {{foo|foo|bar=foo}}.",task_subcomment,"[""This feels like a Parsoid bug, but I'm not sure?"", 'The user creating the equivalent of {{foo|1=foo|2=bar=foo}} should serialise to {{foo|foo|2=bar=foo}} instead of  {{foo|foo|bar=foo}}.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+247559,Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them,See also bug 49743.,task_subcomment,['See also bug 49743.'],['OBSERVED BUG BEHAVIOR']
+51730,VisualEditor: visual representation of template breaks on 'apply changes',"Screenshot
+
+See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11624}",task_description,"[""VisualEditor: visual representation of template breaks on 'apply changes'\n\nScreenshot\n\nSee associated screenshot."", 'This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11624}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247136,VisualEditor: visual representation of template breaks on 'apply changes',"This is a dupe of bug 49854.
+
+*** This bug has been marked as a duplicate of bug 49854 ***",task_subcomment,"['This is a dupe of bug 49854.', '*** This bug has been marked as a duplicate of bug 49854 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51728,Enable voting in VisualEditor product,"If I want to track a bug, I can just vote for it. This is pretty common practice, as I understand it. 
+
+But voting seems to be disabled in the VisualEditor product. Can we have it please?
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",task_description,"['Enable voting in VisualEditor product\n\nIf I want to track a bug, I can just vote for it.', 'This is pretty common practice, as I understand it.', 'But voting seems to be disabled in the VisualEditor product.', 'Can we have it please?', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+246940,Enable voting in VisualEditor product,"The voting system is worse than valueless; it has absolutely impact on prioritisation (we use judgement and actually talking to the community for that), which is bad enough, but it gives users the entirely-false expectation that we even notice, let alone act upon, their ""votes"".
+
+The ""voting"" system should be removed from Wikimedia's Bugzilla instance for all products, but at the very least, I think it's dangerously disrespectful to our users - who can't be expected to know this works in practice - to add its rot to any more places.
+
+Marking as WONTFIX.",task_subcomment,"['The voting system is worse than valueless; it has absolutely impact on prioritisation (we use judgement and actually talking to the community for that), which is bad enough, but it gives users the entirely-false expectation that we even notice, let alone act upon, their ""votes"".', 'The ""voting"" system should be removed from Wikimedia\'s Bugzilla instance for all products, but at the very least, I think it\'s dangerously disrespectful to our users - who can\'t be expected to know this works in practice - to add its rot to any more places.', 'Marking as WONTFIX.']","['FUTURE PLAN', 'FUTURE PLAN', 'ACTION ON ISSUE']"
+246937,Enable voting in VisualEditor product,"(In reply to comment #1)
+> Voting is not for tracking a bug, voting is to express that you'd like to
+> see a
+> bug fixed. The CC field is for tracking a bug.
+
+See some of the comments in bug 25321 and bug 28385...",task_subcomment,['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\n\nSee some of the comments in bug 25321 and bug 28385...'],['MOTIVATION']
+246934,Enable voting in VisualEditor product,"Voting is not for tracking a bug, voting is to express that you'd like to see a bug fixed. The CC field is for tracking a bug.
+
+
+It's correct that some products have it enabled, others have not.
+
+In general (not a topic for this bug report), if voting is NOT used as an input channel for planning by developers (and hence part of the process to define priorities), it should be disabled.
+I cannot make that decision for another team, hence CC'ing James.
+My personal preference currently is to completely disable voting for above reasons (not used by management as one input channel to set priorities).",task_subcomment,"[""Voting is not for tracking a bug, voting is to express that you'd like to see a bug fixed."", 'The CC field is for tracking a bug.', ""It's correct that some products have it enabled, others have not."", 'In general (not a topic for this bug report), if voting is NOT used as an input channel for planning by developers (and hence part of the process to define priorities), it should be disabled.', ""I cannot make that decision for another team, hence CC'ing James."", 'My personal preference currently is to completely disable voting for above reasons (not used by management as one input channel to set priorities).']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+51724,VisualEditor: Possible to insert empty DEFAULTSORT,"Go to .
+
+Click ""Page settings"", enter ""hello"" for the default sort key, click ""Apply changes"".
+
+Click ""Page settings"", clear the default sort key, click ""Apply changes"".
+
+Review your changes. VisualEditor wants to insert ""{{DEFAULTSORT:}}"" into the page. I don't think we want this behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Possible to insert empty DEFAULTSORT\n\nGo to 
+
+--------------------------
+**Version**: master
+**Severity**: major
+**URL**: https://en.wikipedia.org/w/index.php?limit=500&tagfilter=visualeditor&title=Special%3AContributions&contribs=newbie&target=&namespace=&tagfilter=visualeditor&year=2013&month=-1",task_description,"['Special:Contributions lists spurious AFT entries and takes 20 more seconds to load\n\nThe URL was served for me in 22.766 s and contain spurious entries (without visualeditor tag) like\n    21:47, 17 June 2013 .', '.', '(0)\u200e .', '.', 'Feedback: Wikipedia:File Upload Wizard .', '.', 'DenakiPanos70 (talk) \n\nThis practically equivalent search was served in 1.645 s: , where he just meant to delete a sentence. However the content was duplicated and templates were substituted in this duplicated version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Edit with VisualEditor duplicates content with subst'd version of the content\n\nA user reported this edit\n at their end display it, confusing users","See https://en.wikipedia.org/wiki/Daryle_Singletary?veaction=edit - the first three (but strangely, not the last) discography tables.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Tables with a faulty
    got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Extra tags got inserted causing infobox layout to be broken\n\nURL\n\nAll change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically.', 'Where\'s that ""partial serialization"" mentioned before?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +213878,VisualEditor: Extra tags got inserted causing infobox layout to be broken,"The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",task_subcomment,"[""The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May."", 'The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor).', 'Marking as a dupe.', '*** This bug has been marked as a duplicate of bug 47737 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +49816,VisualEditor: Unread message notification will not mark itself read,"I have ""1 notice"", ""You are using an alpha version...."". + +1. Clicking the notice, it pops up. +2. Click the message contents, the popup hides. + +""1 notice"" remains. Maybe it will go away when I save the page I'm editing? + +3. Save the page, and edit again. + +The notice is still there, and even expands when the editor is started. Blargh! + +-------------------------- +**Version**: unspecified +**Severity**: minor",task_description,"['VisualEditor: Unread message notification will not mark itself read\n\nI have ""1 notice"", ""You are using an alpha version...."".', '1.', 'Clicking the notice, it pops up.', '2.', 'Click the message contents, the popup hides.', '""1 notice"" remains.', ""Maybe it will go away when I save the page I'm editing?"", '3.', 'Save the page, and edit again.', 'The notice is still there, and even expands when the editor is started.', 'Blargh!', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +211213,VisualEditor: Unread message notification will not mark itself read,"(In reply to comment #0) +> I have ""1 notice"", ""You are using an alpha version...."". +> +> 1. Clicking the notice, it pops up. +> 2. Click the message contents, the popup hides. +> +> ""1 notice"" remains. Maybe it will go away when I save the page I'm editing? +> +> 3. Save the page, and edit again. +> +> The notice is still there, and even expands when the editor is started. +> Blargh! + +The notices are urgent notifications about the page, not about the user. They're intended to always display, just like the editnotices they replace. + +Theoretically we could have per-user nullification of these, but that'd be messy. Another idea (perhaps?) is to not auto-display the OMG-this-is-so-important-all-users-must-acknowledge nature of editnotices and the like. However, this seems to fly against the underlying purpose of the notices. + +Marking as WONTFIX.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe notices are urgent notifications about the page, not about the user.', ""They're intended to always display, just like the editnotices they replace."", ""Theoretically we could have per-user nullification of these, but that'd be messy."", 'Another idea (perhaps?)', 'is to not auto-display the OMG-this-is-so-important-all-users-must-acknowledge nature of editnotices and the like.', 'However, this seems to fly against the underlying purpose of the notices.', 'Marking as WONTFIX.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +49814,RTL Support for VisualEditor,"Add RTL support for page-, paragraph- and block-level elements in VisualEditor, as well as support for multi-language use in articles. + +Full proposal (GSoC2013 project) is available here: http://www.mediawiki.org/wiki/User:Mooeypoo/GSOC_2013_Proposal:_RTL_Support_in_VisualEditor + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['RTL Support for VisualEditor\n\nAdd RTL support for page-, paragraph- and block-level elements in VisualEditor, as well as support for multi-language use in articles.', 'Full proposal (GSoC2013 project) is available here: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['FUTURE PLAN', 'BUG REPRODUCTION']" +211126,RTL Support for VisualEditor,"This is indeed a duplicate of bug 33126. mooeypoo please update your proposal linking to that bug. + +No worries, these things happen to veteran bug submitters as well. :) + +*** This bug has been marked as a duplicate of bug 33126 ***",task_subcomment,"['This is indeed a duplicate of bug 33126. mooeypoo please update your proposal linking to that bug.', 'No worries, these things happen to veteran bug submitters as well.', ':)\n\n*** This bug has been marked as a duplicate of bug 33126 ***']","['ACTION ON ISSUE', 'SOCIAL CONVERSATION', 'ISSUE CONTENT MANAGEMENT']" +211122,RTL Support for VisualEditor,"I'll tentatively reopen it and mark it as blocking 33126 instead. +Not sure though, maybe James knows. :)",task_subcomment,"[""I'll tentatively reopen it and mark it as blocking 33126 instead."", 'Not sure though, maybe James knows.', ':)']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']" +211118,RTL Support for VisualEditor,It's a bug for tracking a GSoC proposal. I think that it should be reopened.,task_subcomment,"[""It's a bug for tracking a GSoC proposal."", 'I think that it should be reopened.']","['POTENTIAL NEW ISSUES AND REQUESTS', 'BUG REPRODUCTION']" +211113,RTL Support for VisualEditor,"As this seems to be a tracking bug covering several aspects, marking as duplicate of bug 33126. + +Please see the list of specific issues blocking bug 33126 in the ""Depends on:"" section of bug 33126, and if some of the specific issues that you mention are not covered (means: do not have a bug report), please file separate bug reports for each item. Thanks! + +*** This bug has been marked as a duplicate of bug 33126 ***",task_subcomment,"['As this seems to be a tracking bug covering several aspects, marking as duplicate of bug 33126.', 'Please see the list of specific issues blocking bug 33126 in the ""Depends on:"" section of bug 33126, and if some of the specific issues that you mention are not covered (means: do not have a bug report), please file separate bug reports for each item.', 'Thanks!', '*** This bug has been marked as a duplicate of bug 33126 ***']","['ACTION ON ISSUE', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +49768,[VisualEditor] CSS and JS pages should only be editable using the source editor,"CSS and JS pages shouldn't be editable using the VisualEditor, but only using the regular source editor. These pages should only have the ""Edit source"" tab. + +(It may make sense to have them editable using the source code editor that is used for Lua, but that's a separate issue.) + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""[VisualEditor] CSS and JS pages should only be editable using the source editor\n\nCSS and JS pages shouldn't be editable using the VisualEditor, but only using the regular source editor."", 'These pages should only have the ""Edit source"" tab.', ""(It may make sense to have them editable using the source code editor that is used for Lua, but that's a separate issue.)"", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +207992,[VisualEditor] CSS and JS pages should only be editable using the source editor," + +*** This bug has been marked as a duplicate of bug 47456 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 47456 ***'],['ACTION ON ISSUE'] +49755,Feedback is broken,"**Author:** `benedix` + +**Description:** +One of the feedback-mechanisms in the VisualEditor is broken: + +'visual editor' -> 'review and save' -> 'something is wrong' -> 'report problem' + +I made a little test: +http://www.youtube.com/watch?v=Zzt_2CBfTNI (35 seconds) + +The feedback is sent to http://parsoid.wmflabs.org/_bugs/ but the request is canceled after a few seconds. + + +Btw. There is no visual feedback to the user that shows him to wait while the request is pending. + + +Lukas + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""Feedback is broken\n\n**Author:** CODE\n\n**Description:**\nOne of the feedback-mechanisms in the VisualEditor is broken:\n\n'visual editor' -> 'review and save' -> 'something is wrong' -> 'report problem'\n\nI made a little test:\nURL (35 seconds)\n\nThe feedback is sent to URL but the request is canceled after a few seconds."", 'Btw.', 'There is no visual feedback to the user that shows him to wait while the request is pending.', 'Lukas\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +207265,Feedback is broken,"Not actually broken, see bug 42974.",task_subcomment,"['Not actually broken, see bug 42974.']",['OBSERVED BUG BEHAVIOR'] +49751,A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page,"See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",task_description,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page\n\nSee the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +233225,A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page,"Confirm that this is intentional behaviour. There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.",task_subcomment,"['Confirm that this is intentional behaviour.', ""There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +233217,A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page,As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level. James - please confirm (and reopen if I'm wrong).,task_subcomment,"[""As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level."", ""James - please confirm (and reopen if I'm wrong).""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +49546,VisualEditor: Adding a hyperlink to an exsisting page deletes the line. The link doesn't get inserted (undefined),"**Author:** `mh87` + +**Description:** +I tried to add a link to a word. The page containing this word already exsists so the Editor tells me ""Matching pages"" and lists the word. + +When I click the matching word to add the Hyperlink the word says ""undefined"". After clicking ok the whole line gets deleted + +MediaWiki Alpha 1.22 +VisualEditor 0.1.0 (latest snapshot) +Chrome 26.0.1410.64 m + +-------------------------- +**Version**: unspecified +**Severity**: major +**OS**: Windows 7 +**Platform**: PC",task_description,"['VisualEditor: Adding a hyperlink to an exsisting page deletes the line.', ""The link doesn't get inserted (undefined)\n\n**Author:** CODE\n\n**Description:**\nI tried to add a link to a word."", 'The page containing this word already exsists so the Editor tells me ""Matching pages"" and lists the word.', 'When I click the matching word to add the Hyperlink the word says ""undefined"".', 'After clicking ok the whole line gets deleted\n\nMediaWiki Alpha 1.22\nVisualEditor 0.1.0 (latest snapshot)\nChrome 26.0.1410.64 m\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**OS**: Windows 7\n**Platform**: PC']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']" +219973,VisualEditor: Adding a hyperlink to an exsisting page deletes the line. The link doesn't get inserted (undefined)," + +*** This bug has been marked as a duplicate of bug 47413 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 47413 ***'],['ACTION ON ISSUE'] +219969,VisualEditor: Adding a hyperlink to an exsisting page deletes the line. The link doesn't get inserted (undefined),"**mh87** wrote: + +After click on the matching link item it says undefined + +**Attached**: {F10658}",task_subcomment,['**mh87** wrote:\n\nAfter click on the matching link item it says undefined\n\n**Attached**: {F10658}'],['OBSERVED BUG BEHAVIOR'] +49419,"VisualEditor: Dirty diffs with FF, but not in Chrome on pages with citations","Performing small edits on pages with citations like http://en.wikipedia.org/wiki/JRuby results in a clean diff in Chrome, but produces a dirty diff when using Firefox. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Dirty diffs with FF, but not in Chrome on pages with citations\n\nPerforming small edits on pages with citations like URL results in a clean diff in Chrome, but produces a dirty diff when using Firefox.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +212180,"VisualEditor: Dirty diffs with FF, but not in Chrome on pages with citations"," + +*** This bug has been marked as a duplicate of bug 47417 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 47417 ***'],['ACTION ON ISSUE'] +212174,"VisualEditor: Dirty diffs with FF, but not in Chrome on pages with citations","Example edit: +https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&curid=37842561&diff=551148728&oldid=551148307",task_subcomment,['Example edit:\nURL'],['SOLUTION DISCUSSION'] +49258,VisualEditor: Problem with placing cursor inside slug (inline|block) with mouse,"Cursor correctly appear and blinks in slug, but surface completely does not know about it, so when user start typing it does not convert slug into paragraph (for block level slug) or delete slug (for inline slug). + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Problem with placing cursor inside slug (inline|block) with mouse\n\nCursor correctly appear and blinks in slug, but surface completely does not know about it, so when user start typing it does not convert slug into paragraph (for block level slug) or delete slug (for inline slug).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']" +228421,VisualEditor: Problem with placing cursor inside slug (inline|block) with mouse,Fixed here: https://gerrit.wikimedia.org/r/#/c/59199/,task_subcomment,['Fixed here: URL'],['SOLUTION DISCUSSION'] +48794,VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,"Currently we can't use the UnicodeJS.wordbreak library to emulate word skipping (ctrl+arrow / alt+arrow) functionality as wordbreaks appear either side of whitespace and between multiple whitespaces: + +|One| |Two| | |Three| + +Moving forwards we expect the cursor to stop in the following positions: +One| Two| Three| + +Moving backwards we expect: +|One |Two |Three + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"[""VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality\n\nCurrently we can't use the UnicodeJS.wordbreak library to emulate word skipping (ctrl+arrow / alt+arrow) functionality as wordbreaks appear either side of whitespace and between multiple whitespaces:\n\n|One| |Two| | |Three|\n\nMoving forwards we expect the cursor to stop in the following positions:\nOne| Two| Three|\n\nMoving backwards we expect:\n|One |Two |Three\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]",['OBSERVED BUG BEHAVIOR'] +225500,VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Now fixed.,task_subcomment,['Now fixed.'],['SOLUTION DISCUSSION'] +225490,VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Related URL: https://gerrit.wikimedia.org/r/58868 (Gerrit Change I6b2700d65476c4d34ba4a01a88382d7af8e736fb),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I6b2700d65476c4d34ba4a01a88382d7af8e736fb)'],['OBSERVED BUG BEHAVIOR'] +225481,VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Actually Ed is still working on it.,task_subcomment,['Actually Ed is still working on it.'],['WORKAROUNDS'] +225476,VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,I have added better support for skipping white spaces in 4th patch set: https://gerrit.wikimedia.org/r/#/c/57076/,task_subcomment,['I have added better support for skipping white spaces in 4th patch set: URL'],['SOLUTION DISCUSSION'] +225473,VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,"Looking at other implementations, sepcifically OpenOffice, they have an ""ignore whitespace"" mode in their nextWord function: + +https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk/main/i18npool/source/breakiterator/breakiterator_unicode.cxx + +which calls an is_whitepsace function, which is defined as: +http://www.icu-project.org/apiref/icu4c/uchar_8h.html#a5cef869b23e8d8e649963457cccca68e",task_subcomment,"['Looking at other implementations, sepcifically OpenOffice, they have an ""ignore whitespace"" mode in their nextWord function:\n\nURL\n\nwhich calls an is_whitepsace function, which is defined as:\nURL']",['OBSERVED BUG BEHAVIOR'] +48619,VisualEditor: Allow nodes to handle their own children,"DM nodes should be able to handle their own children, rather than having the converter do it for them. + +This means we need a .static.handlesOwnChildren flag or something similar, and a way for .toDataElement to recursively invoke the converter to convert a sub-DOM to a sub-linmod. + +Reflecting this, CE nodes should be able to take control of the rendering of their children as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['VisualEditor: Allow nodes to handle their own children\n\nDM nodes should be able to handle their own children, rather than having the converter do it for them.', 'This means we need a .static.handlesOwnChildren flag or something similar, and a way for .toDataElement to recursively invoke the converter to convert a sub-DOM to a sub-linmod.', 'Reflecting this, CE nodes should be able to take control of the rendering of their children as well.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +214760,VisualEditor: Allow nodes to handle their own children,Done in https://gerrit.wikimedia.org/r/#/c/58645/ and related commits.,task_subcomment,['Done in URL and related commits.'],['BUG REPRODUCTION'] +48520,VisualEditor to edit infobox text fields,"Currently VisualEditor users can't touch infoboxes. It would be great to have edit access to the text fields of infoboxes. + +Being able to update images would be a plus. + +Modification of the infobox itself (e.g. addition of new fields) is out of scope here. + + +I'm filing this request in relation to + +""Wikidata provides data for Wikipedia's infoboxes. The goal of this project is easy editing of the data for a given infobox on the Wikipedia, without having to go to Wikidata."" +http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#On-site_editing + +By the time those Wikipedia infoboxes would be filled with Wikidata data, +""easy editing"" should be provided by VisualEditor. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",task_description,"[""VisualEditor to edit infobox text fields\n\nCurrently VisualEditor users can't touch infoboxes."", 'It would be great to have edit access to the text fields of infoboxes.', 'Being able to update images would be a plus.', 'Modification of the infobox itself (e.g.', 'addition of new fields) is out of scope here.', 'I\'m filing this request in relation to \n\n""Wikidata provides data for Wikipedia\'s infoboxes.', 'The goal of this project is easy editing of the data for a given infobox on the Wikipedia, without having to go to Wikidata.""', 'URL\n\nBy the time those Wikipedia infoboxes would be filled with Wikidata data, \n""easy editing"" should be provided by VisualEditor.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +208358,VisualEditor to edit infobox text fields,"Very much on the roadmap already. + +The Wikidata integration is another issue; will talk with Denny and see about opening distinct bugs for that stuff. + +*** This bug has been marked as a duplicate of bug 39598 ***",task_subcomment,"['Very much on the roadmap already.', 'The Wikidata integration is another issue; will talk with Denny and see about opening distinct bugs for that stuff.', '*** This bug has been marked as a duplicate of bug 39598 ***']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +48516,Generalise the Parsoid structure and internal representations.,"So Molly and I are at LibrePlanet talking about bug 37933. + +We decided that while Wikitext --> HTML --> LaTeX is possible, it's not terribly useful and doesn't really take advantage of the structure of Parsoid - we see it as adding an extra stage to the parse, which will potentially add to the time the parse takes, as opposed to having a generalized token stream and only starting to convert to a format after the token stream is actually ready. + +Obviously this means a few of big things, potentially: + +1. The DOM post processor needs to either run before the HTML5 tree builder, on tokens or some other structure, or it needs to be emulated for each format. I'm leaning towards the former, because if we're going to export to multiple formats it would make more sense to have one file for each format that builds the export from a token structure, rather than two files each, which build the export and do the postprocessing. + +2. Because we aren't actually dealing with HTML, necessarily, in the end, we shouldn't be talking about tokens with HTML-specific tag names. Probably we could just use canonical Parsoid-specific names - something like http://www.mediawiki.org/wiki/Parsoid/RDFa_vocabulary - or maybe something similar to the *_NODE attributes in DOM nodes, with a mapper to some canonical integer values that are defined in the base Token class. + +Footnote: As I was thinking about this and trying to come up with how I wanted it to look, I realized that the problem was that I was looking at it as wanting to convert between WT and either LaTeX or HTML, but if we wound up following our long term plan, ""LaTeX export"" would also require HTML-to-LaTeX, because HTML would be our storage mechanism. So I think it might be better to rewrite each bit of our system to convert each format to and from a canonical internal representation, rather than to and from any one other format. + +I'm posting here because I want thoughts and feedback. It should be noted that bug 37934 would also benefit from any of the work we did on the generalisation problem - and we could probably open a tracking bug to figure out all of these things more generally. + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,"['Generalise the Parsoid structure and internal representations.', 'So Molly and I are at LibrePlanet talking about bug 37933.', ""We decided that while Wikitext --> HTML --> LaTeX is possible, it's not terribly useful and doesn't really take advantage of the structure of Parsoid - we see it as adding an extra stage to the parse, which will potentially add to the time the parse takes, as opposed to having a generalized token stream and only starting to convert to a format after the token stream is actually ready."", 'Obviously this means a few of big things, potentially:\n\n1.', 'The DOM post processor needs to either run before the HTML5 tree builder, on tokens or some other structure, or it needs to be emulated for each format.', ""I'm leaning towards the former, because if we're going to export to multiple formats it would make more sense to have one file for each format that builds the export from a token structure, rather than two files each, which build the export and do the postprocessing."", '2.', ""Because we aren't actually dealing with HTML, necessarily, in the end, we shouldn't be talking about tokens with HTML-specific tag names."", 'Probably we could just use canonical Parsoid-specific names - something like URL - or maybe something similar to the *_NODE attributes in DOM nodes, with a mapper to some canonical integer values that are defined in the base Token class.', 'Footnote: As I was thinking about this and trying to come up with how I wanted it to look, I realized that the problem was that I was looking at it as wanting to convert between WT and either LaTeX or HTML, but if we wound up following our long term plan, ""LaTeX export"" would also require HTML-to-LaTeX, because HTML would be our storage mechanism.', 'So I think it might be better to rewrite each bit of our system to convert each format to and from a canonical internal representation, rather than to and from any one other format.', ""I'm posting here because I want thoughts and feedback."", 'It should be noted that bug 37934 would also benefit from any of the work we did on the generalisation problem - and we could probably open a tracking bug to figure out all of these things more generally.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +208160,Generalise the Parsoid structure and internal representations.,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +208157,Generalise the Parsoid structure and internal representations.,"**molly.white5** wrote: + +From my brief look at pandoc, it appears that it can do it. As always, it's roundtripping that's the issue.",task_subcomment,"['**molly.white5** wrote:\n\nFrom my brief look at pandoc, it appears that it can do it.', ""As always, it's roundtripping that's the issue.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']" +208153,Generalise the Parsoid structure and internal representations.,"I agree. If we wind up supporting Markdown, it will be because we've found a way to do HTML <--> Markdown, or at least one direction or t'other. Converting to HTML is simple enough, at least.",task_subcomment,"['I agree.', ""If we wind up supporting Markdown, it will be because we've found a way to do HTML <--> Markdown, or at least one direction or t'other."", 'Converting to HTML is simple enough, at least.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +208148,Generalise the Parsoid structure and internal representations.,"**molly.white5** wrote: + +I agree that LaTeX to wikitext would not be terribly useful. I wonder if the community would benefit from having some other formats be two-way, though. I'm sure there are people out there who would rather write their articles using Markdown... Then again, if we're trying to make the switch to the VisualEditor anyway, the ability to write articles in Markdown would be of only temporary value.",task_subcomment,"['**molly.white5** wrote:\n\nI agree that LaTeX to wikitext would not be terribly useful.', 'I wonder if the community would benefit from having some other formats be two-way, though.', ""I'm sure there are people out there who would rather write their articles using Markdown... Then again, if we're trying to make the switch to the VisualEditor anyway, the ability to write articles in Markdown would be of only temporary value.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +208142,Generalise the Parsoid structure and internal representations.,"I think we could call that ""of dubious usefulness"", but you're the one who's going to have to implement it, so I probably shouldn't dictate anything. In any case I think LaTeX and HTML have a much closer 1:1 ratio than WT and HTML, so it should be much easier to add in, even if it winds up being an afterthought. + +And as ever, we're in IRC if you'd like any help or guidance :)",task_subcomment,"['I think we could call that ""of dubious usefulness"", but you\'re the one who\'s going to have to implement it, so I probably shouldn\'t dictate anything.', 'In any case I think LaTeX and HTML have a much closer 1:1 ratio than WT and HTML, so it should be much easier to add in, even if it winds up being an afterthought.', ""And as ever, we're in IRC if you'd like any help or guidance :)""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']" +208135,Generalise the Parsoid structure and internal representations.,"**molly.white5** wrote: + +Alright, that sounds fine as long as you're not concerned with the speed. I'm not familiar with pandoc, but I'll read up on it. I'm curious to see how they perform wikitext <-> LaTeX and HTML <-> LaTeX. + +Have you discussed whether or not we'll want to be able to roundtrip wikitext and LaTeX?",task_subcomment,"[""**molly.white5** wrote:\n\nAlright, that sounds fine as long as you're not concerned with the speed."", ""I'm not familiar with pandoc, but I'll read up on it."", ""I'm curious to see how they perform wikitext <-> LaTeX and HTML <-> LaTeX."", ""Have you discussed whether or not we'll want to be able to roundtrip wikitext and LaTeX?""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +208128,Generalise the Parsoid structure and internal representations.,"We're chatting on IRC currently, and I think the rough consensus is something like...""HTML should be the common format, and the rest can deal with it."" This makes some amount of sense, though it does mean that, temporarily at least, we'll have to deal with parsing WT to HTML before going to other formats. Since anything beyond that is relatively fast, in terms of performance, we can live with that issue for now. + +So Molly, we'll throw out the insane charts and maps we've drawn up (which really just consists of one chalk scribble at Harvard) and see what HTML can offer as an intermediary format - to that end, I guess gwicke's suggestion of pandoc is a good place to start.",task_subcomment,"['We\'re chatting on IRC currently, and I think the rough consensus is something like...""HTML should be the common format, and the rest can deal with it.""', ""This makes some amount of sense, though it does mean that, temporarily at least, we'll have to deal with parsing WT to HTML before going to other formats."", 'Since anything beyond that is relatively fast, in terms of performance, we can live with that issue for now.', ""So Molly, we'll throw out the insane charts and maps we've drawn up (which really just consists of one chalk scribble at Harvard) and see what HTML can offer as an intermediary format - to that end, I guess gwicke's suggestion of pandoc is a good place to start.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +208121,Generalise the Parsoid structure and internal representations.,"Reg. 1. the DOM post processor cannot run before the DOM is built, it requires information that is available only after the DOM is fully built.",task_subcomment,"['Reg.', '1. the DOM post processor cannot run before the DOM is built, it requires information that is available only after the DOM is fully built.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +208110,Generalise the Parsoid structure and internal representations.,"I just ran a quick serialize to see what the timing was like in comparison to a parse - in case we decide to convert HTML into an intermediary format that would translate into whatever other format we want to use. I think the two seconds that it takes to serialize wouldn't be greatly affected by an extra step in the serializer process, and I think the benefits of having a general solution for converting between formats would be greatly useful.",task_subcomment,"['I just ran a quick serialize to see what the timing was like in comparison to a parse - in case we decide to convert HTML into an intermediary format that would translate into whatever other format we want to use.', ""I think the two seconds that it takes to serialize wouldn't be greatly affected by an extra step in the serializer process, and I think the benefits of having a general solution for converting between formats would be greatly useful.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +48506,"Just added single character, but at review all content is replaced","Steps: + +1) Go to http://en.wikipedia.org/wiki/Jean_Nicolas +2) Click VisualEditor +3) Without moving the cursor or anything, enter the following character: a +4) Click ""Review and save"" +5) The whole content of the article has been replaced with just the character. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['Just added single character, but at review all content is replaced\n\nSteps:\n\n1) Go to URL\n2) Click VisualEditor\n3) Without moving the cursor or anything, enter the following character: a\n4) Click ""Review and save""\n5) The whole content of the article has been replaced with just the character.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'BUG REPRODUCTION']" +207494,"Just added single character, but at review all content is replaced"," + +*** This bug has been marked as a duplicate of bug 43103 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 43103 ***'],['ISSUE CONTENT MANAGEMENT'] +48505,Clicking outside of link edition popup removes link,"Steps: + +1) Go to http://en.wikipedia.org/wiki/Nicolas +2) Click VisualEditor +3) Left-click any link +4) A small popup with only one item appears, click on it +5) Click outside of the popup, for instance on a blank area of the article behind +6) Link has disappeared + +Step 5 is what many users do to cancel. + +-------------------------- +**Version**: unspecified +**Severity**: major",task_description,"['Clicking outside of link edition popup removes link\n\nSteps:\n\n1) Go to URL\n2) Click VisualEditor\n3) Left-click any link\n4) A small popup with only one item appears, click on it\n5) Click outside of the popup, for instance on a blank area of the article behind\n6) Link has disappeared\n\nStep 5 is what many users do to cancel.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'BUG REPRODUCTION']" +207443,Clicking outside of link edition popup removes link,"This was fixed in bug 46025 which is bundled in MediaWiki 1.21wmf12 which should be deployed to enwiki tomorrow. Sorry for the delay! + +*** This bug has been marked as a duplicate of bug 46025 ***",task_subcomment,"['This was fixed in bug 46025 which is bundled in MediaWiki 1.21wmf12 which should be deployed to enwiki tomorrow.', 'Sorry for the delay!', '*** This bug has been marked as a duplicate of bug 46025 ***']","['BUG REPRODUCTION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']" +48320,VisualEditor: store annotations in a document-wide index/value store and serialize as integer indexes," + +-------------------------- +**Version**: unspecified +**Severity**: normal",task_description,['VisualEditor: store annotations in a document-wide index/value store and serialize as integer indexes\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR'] +220341,VisualEditor: store annotations in a document-wide index/value store and serialize as integer indexes,Related URL: https://gerrit.wikimedia.org/r/54991 (Gerrit Patch-Set: I249a5d48726093d1cb3e36351893f4bff85f52e2/1),task_subcomment,['Related URL: GERRIT_URL (Gerrit Patch-Set: I249a5d48726093d1cb3e36351893f4bff85f52e2/1)'],['OBSERVED BUG BEHAVIOR'] +220336,VisualEditor: store annotations in a document-wide index/value store and serialize as integer indexes,"Before I go breaking things, I've added tests for AnnotationSet: https://gerrit.wikimedia.org/r/54640",task_subcomment,"[""Before I go breaking things, I've added tests for AnnotationSet: GERRIT_URL""]",['BUG REPRODUCTION'] +48296,Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors),"We have a job that sanity-checks our API server, which is a primary part of our ability to communicate with the VisualEditor. It fails because the process forks off several workers to handle requests, which sets off big red blinking alarms in Jenkins. + +Do we need to add in an option to not fork? Do we need to add in some other method of doing this (like a ""start a background process"" Jenkins builder)? Or can we work around the file descriptor issue? + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://integration.mediawiki.org/ci/view/All/job/parsoid-server-sanity-check/",task_description,"[""Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors)\n\nWe have a job that sanity-checks our API server, which is a primary part of our ability to communicate with the VisualEditor."", 'It fails because the process forks off several workers to handle requests, which sets off big red blinking alarms in Jenkins.', 'Do we need to add in an option to not fork?', 'Do we need to add in some other method of doing this (like a ""start a background process"" Jenkins builder)?', 'Or can we work around the file descriptor issue?', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']" +218511,Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors),"Job got deleted, I guess we can forget this bug for now.",task_subcomment,"['Job got deleted, I guess we can forget this bug for now.']",['WORKAROUNDS'] +218504,Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors),"Yeah, we disabled it because there was no point in keeping it around. + +There's some hacky workaround, but it seemed really complicated and not worth the work at that time.",task_subcomment,"['Yeah, we disabled it because there was no point in keeping it around.', ""There's some hacky workaround, but it seemed really complicated and not worth the work at that time.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +218497,Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors),"The tests seem to be working now. Has this been fixed or have certain testing paths been disabled? + +Is there something we can do on our end?",task_subcomment,"['The tests seem to be working now.', 'Has this been fixed or have certain testing paths been disabled?', 'Is there something we can do on our end?']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +218491,Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors),"daemon seems to have broken it further, though I'm not sure why. I tried letting the server get set up, and I tried making sure my options were correct, but the parsoid server doesn't seem to like being run with daemon.",task_subcomment,"[""daemon seems to have broken it further, though I'm not sure why."", ""I tried letting the server get set up, and I tried making sure my options were correct, but the parsoid server doesn't seem to like being run with daemon.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +218484,Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors),"The job dashboard is https://integration.mediawiki.org/ci/view/All/job/parsoid-server-sanity-check/ + +An example console is https://integration.mediawiki.org/ci/view/All/job/parsoid-server-sanity-check/65/console + +After the worker have been forked, Jenkins detects some file descriptor leakage and cancel the build: + +Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information + +They point to http://software.clapper.org/daemonize/ . But maybe we can use /usr/bin/daemon for the same effect.",task_subcomment,"['The job dashboard is URL\n\nAn example console is URL \n\nAfter the worker have been forked, Jenkins detects some file descriptor leakage and cancel the build:\n\nProcess leaked file descriptors.', 'See URL for more information\n\nThey point to URL .', 'But maybe we can use /usr/bin/daemon for the same effect.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']" +47341,Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Screenshot of {{disambiguation}} on [[Loco]] at en.wikipedia.org + +Using {{disambiguation}} on a page and editing it with VisualEditor shows an incorrect rendering. + +Attached are screenshots and dumps of the active DOM for the PHP parser and Parsoid/VisualEditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F10462}",task_description,"['Parsoid: Incorrect rendering for [[Template:Disambiguation]]\n\nScreenshot of {{disambiguation}} on [[Loco]] at en.wikipedia.org\n\nUsing {{disambiguation}} on a page and editing it with VisualEditor shows an incorrect rendering.', 'Attached are screenshots and dumps of the active DOM for the PHP parser and Parsoid/VisualEditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F10462}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']" +212897,Parsoid: Incorrect rendering for [[Template:Disambiguation]],A reasonable resolution of this issue. :),task_subcomment,"['A reasonable resolution of this issue.', ':)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']" +212890,Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Indeed. The following edit by me fixed it for Parsoid: + +https://en.wikipedia.org/w/index.php?title=Template%3ADmbox&diff=540384230&oldid=466538335 + +Seems like a reasonable change to make. Not sure how common this is but I think in most cases editors will understand as in most cases this is already how it is. Leading space after a line break causes a 

    . The reason the line break is there is probably by mistake, and nothing broke so it was forgotten/left.
+
+Lets hope it is not too common.",task_subcomment,"['Indeed.', 'The following edit by me fixed it for Parsoid:\n\nURL\n\nSeems like a reasonable change to make.', 'Not sure how common this is but I think in most cases editors will understand as in most cases this is already how it is.', 'Leading space after a line break causes a 
    .', 'The reason the line break is there is probably by mistake, and nothing broke so it was forgotten/left.', 'Lets hope it is not too common.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+212883,Parsoid: Incorrect rendering for [[Template:Disambiguation]],"This can be narrowed down to the difference between these two table cells.  Look at PHP parser output for these two tds in the table:
+
+
+
+
+
+
+
    
+  a
+ b
+
    
+
+""a"" is not wrapped in a pre-tag, but ""b"" is.  
+
+http://www.mediawiki.org/wiki/User:Ssastry/Tests:Odd_pre_in_td_behavior
+
+Parsoid wraps both in a pre-tag which is the reason why Parsoid output is different from PHP output.  This seems a PHP parser bug to me, not a Parsoid bug.  I imagine we want to be bug-to-bug compatible, but I am not sure what the correct behavior for this is.",task_subcomment,"['This can be narrowed down to the difference between these two table cells.', 'Look at PHP parser output for these two tds in the table:\n\n\n\n\n\n\n
    \n  a\n b\n
    \n\n""a"" is not wrapped in a pre-tag, but ""b"" is.', 'URL\n\nParsoid wraps both in a pre-tag which is the reason why Parsoid output is different from PHP output.', 'This seems a PHP parser bug to me, not a Parsoid bug.', 'I imagine we want to be bug-to-bug compatible, but I am not sure what the correct behavior for this is.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+212875,Parsoid: Incorrect rendering for [[Template:Disambiguation]],"This might be a bug in https://gerrit.wikimedia.org/r/#/c/32405/ or a regression.  The 
     is coming from an #if parser function which should not have as per that commit message.
+
+Will investigate.",task_subcomment,"['This might be a bug in URL or a regression.', 'The 
     is coming from an #if parser function which should not have as per that commit message.', 'Will investigate.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+212867,Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11841
+HTML of {{disambiguation}} from Parsoid
+
+The main problem is the presence of a 
     that shouldn't be there.
+
+**Attached**: {F10465}",task_subcomment,"[""Created attachment 11841\nHTML of {{disambiguation}} from Parsoid\n\nThe main problem is the presence of a 
     that shouldn't be there."", '**Attached**: {F10465}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+212862,Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11840
+Screenshot of {{disambiguation}} from Parsoid
+
+**Attached**: {F10464}",task_subcomment,['Created attachment 11840\nScreenshot of {{disambiguation}} from Parsoid\n\n**Attached**: {F10464}'],['INVESTIGATION AND EXPLORATION']
+212856,Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11839
+HTML of {{disambiguation}} on [[Loco]] at en.wikipedia.org
+
+**Attached**: {F10463}",task_subcomment,['Created attachment 11839\nHTML of {{disambiguation}} on [[Loco]] at en.wikipedia.org\n\n**Attached**: {F10463}'],['INVESTIGATION AND EXPLORATION']
+47024,Parsoid: Tables don't round-trip cleanly,"See http://parsoid.wmflabs.org/_rt/mw/VisualEditor/Node_types for example. (This URL currently doesn't work because the /mw prefix disappeared in a recent change.)
+
+* border=""1"" is normalized to border=1, but only in the table's attributes, not in the rows' attributes
+* | rowspan=""3"" is normalized to |rowspan=""3""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Parsoid: Tables don't round-trip cleanly\n\nSee URL for example."", ""(This URL currently doesn't work because the /mw prefix disappeared in a recent change.)"", '* border=""1"" is normalized to border=1, but only in the table\'s attributes, not in the rows\' attributes\n* | rowspan=""3"" is normalized to |rowspan=""3""\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+219694,Parsoid: Tables don't round-trip cleanly,"The first normalization is actually the other way around: border=1 is normalized to border=""1"".
+
+This is the expected degree of normalization for non-selective serialization, so closing as wontfix. Selective serialization is becoming smarter, and will soon only normalize a table cell or even only a part of a table cell's content, which will hide this issue normally.",task_subcomment,"['The first normalization is actually the other way around: border=1 is normalized to border=""1"".', 'This is the expected degree of normalization for non-selective serialization, so closing as wontfix.', ""Selective serialization is becoming smarter, and will soon only normalize a table cell or even only a part of a table cell's content, which will hide this issue normally.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+46969,Parsoid crashes when serializing page with colon in title,"Send a POST request with any content at all to a Parsoid URL containing a colon, and you'll get strange crashes. Strangely, the behavior differs between localhost and enwiki:
+
+POST /localhost/VisualEditor%3AMetastuff HTTP/1.0
+Host: localhost:8000
+Content-Length: 3
+
+HTTP/1.1 500 Internal Server Error
+X-Powered-By: Express
+Content-Type: text/html; charset=utf-8
+Content-Length: 66
+Connection: close
+
+ParserError: Failed to parse the JSON response for Page Fetch null
+
+(Note that I didn't even get a chance to send the POST body, the 500 occurs as soon as I send the double newline that terminates the request header.)
+
+For this case, the Parsoid log shows:
+ParserError: Failed to parse the JSON response for Page Fetch null
+worker 10132 died, restarting.
+
+
+POST /en/Talk%3AWQKO HTTP/1.0
+Host: localhost:8000
+Content-Length: 3
+
+Foo
+
+[Parsoid closes the connection without sending anything]
+
+Parsoid log:
+There was an error in the HTML5 parser! Sending it back to the editor.
+Error: No source to parse
+    at EventEmitter.parse (/var/lib/parsoid/Parsoid/js/node_modules/html5/lib/html5/parser.js:44:20)
+    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:579:6
+    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:284:4
+    at /var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:185:3
+    at [object Object]. (/var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:209:4)
+    at Array.1 (/var/lib/parsoid/Parsoid/js/lib/mediawiki.ApiRequest.js:60:4)
+    at EventEmitter._tickCallback (node.js:192:40)
+TypeError: Cannot read property 'childNodes' of undefined
+    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:597:34
+    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:284:4
+    at /var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:185:3
+    at [object Object]. (/var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:209:4)
+    at Array.1 (/var/lib/parsoid/Parsoid/js/lib/mediawiki.ApiRequest.js:60:4)
+    at EventEmitter._tickCallback (node.js:192:40)
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",task_description,"[""Parsoid crashes when serializing page with colon in title\n\nSend a POST request with any content at all to a Parsoid URL containing a colon, and you'll get strange crashes."", ""Strangely, the behavior differs between localhost and enwiki:\n\nPOST /localhost/VisualEditor%3AMetastuff HTTP/1.0\nHost: localhost:8000\nContent-Length: 3\n\nHTTP/1.1 500 Internal Server Error\nX-Powered-By: Express\nContent-Type: text/html; charset=utf-8\nContent-Length: 66\nConnection: close\n\nParserError: Failed to parse the JSON response for Page Fetch null\n\n(Note that I didn't even get a chance to send the POST body, the 500 occurs as soon as I send the double newline that terminates the request header.)"", 'For this case, the Parsoid log shows:\nParserError: Failed to parse the JSON response for Page Fetch null\nworker 10132 died, restarting.', 'POST /en/Talk%3AWQKO HTTP/1.0\nHost: localhost:8000\nContent-Length: 3\n\nFoo\n\n[Parsoid closes the connection without sending anything]\n\nParsoid log:\nThere was an error in the HTML5 parser!', 'Sending it back to the editor.', ""Error: No source to parse\n    at EventEmitter.parse (/var/lib/parsoid/Parsoid/js/node_modules/html5/lib/html5/parser.js:44:20)\n    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:579:6\n    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:284:4\n    at /var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:185:3\n    at [object Object]. (/var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:209:4)\n    at Array.1 (/var/lib/parsoid/Parsoid/js/lib/mediawiki.ApiRequest.js:60:4)\n    at EventEmitter._tickCallback (node.js:192:40)\nTypeError: Cannot read property 'childNodes' of undefined\n    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:597:34\n    at /var/lib/parsoid/Parsoid/js/api/ParserService.js:284:4\n    at /var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:185:3\n    at [object Object]. (/var/lib/parsoid/Parsoid/js/lib/mediawiki.parser.environment.js:209:4)\n    at Array.1 (/var/lib/parsoid/Parsoid/js/lib/mediawiki.ApiRequest.js:60:4)\n    at EventEmitter._tickCallback (node.js:192:40)\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+216497,Parsoid crashes when serializing page with colon in title,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+216490,Parsoid crashes when serializing page with colon in title,"(In reply to comment #0)
+> POST /localhost/VisualEditor%3AMetastuff HTTP/1.0
+> Host: localhost:8000
+> Content-Length: 3
+> 
+> HTTP/1.1 500 Internal Server Error
+> X-Powered-By: Express
+> Content-Type: text/html; charset=utf-8
+> Content-Length: 66
+> Connection: close
+> 
+> ParserError: Failed to parse the JSON response for Page Fetch null
+> 
+Ignore this one, this is due to a misconfiguration on my end.
+
+> POST /en/Talk%3AWQKO HTTP/1.0
+> Host: localhost:8000
+> Content-Length: 3
+> 
+> Foo
+> 
+> [Parsoid closes the connection without sending anything]
+> 
+> Parsoid log:
+> There was an error in the HTML5 parser! Sending it back to the editor.
+And this behavior occurs on the command line but not from my browser, for some reason.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nIgnore this one, this is due to a misconfiguration on my end.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nAnd this behavior occurs on the command line but not from my browser, for some reason.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+46927,VisualEditor: VE chokes on unexpected redirect response from Parsoid,"**Author:** `phil`
+
+**Description:**
+I created a page using the normal editor that was
+
+
+
+File:Example.jpg|Caption1
+#REDIRECT [[Target page name]]
+
+
+
+Trying to load this page in VE gives an error message
+"" Error loading data from server: Server error. Would you like to retry? ""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: VE chokes on unexpected redirect response from Parsoid\n\n**Author:** CODE\n\n**Description:**\nI created a page using the normal editor that was\n\n\n\nFile:Example.jpg|Caption1\n#REDIRECT [[Target page name]]\n\n\n\nTrying to load this page in VE gives an error message\n"" Error loading data from server: Server error.', 'Would you like to retry? ""', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+214053,VisualEditor: VE chokes on unexpected redirect response from Parsoid,"Phil,
+
+I've checked and this is now fixed (in part - there's the wider question of Parsoid and redirection which is covered in bug 45808) - am marking as closed. Thank you again for your bug report!
+
+James.",task_subcomment,"[""Phil,\n\nI've checked and this is now fixed (in part - there's the wider question of Parsoid and redirection which is covered in bug 45808) - am marking as closed."", 'Thank you again for your bug report!', 'James.']","['ACTION ON ISSUE', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+214045,VisualEditor: VE chokes on unexpected redirect response from Parsoid,"**phil** wrote:
+
+Selecting the OK option to Retry brings the error dialog back up so the only option is to Cancel unless you want to spend all day pressing OK
+
+thanks for the extra info on how redirect works - or is meant to work",task_subcomment,['**phil** wrote:\n\nSelecting the OK option to Retry brings the error dialog back up so the only option is to Cancel unless you want to spend all day pressing OK\n\nthanks for the extra info on how redirect works - or is meant to work'],['OBSERVED BUG BEHAVIOR']
+214038,VisualEditor: VE chokes on unexpected redirect response from Parsoid,"Phil, did this happen when you retried? That error message (which sucks, and we're going to fix as part of bug 44354) just means that it couldn't hail the Parsoid server at the time, and normally means that nothing went wrong other than the server availability.
+
+More generally, when you edit a page which as has a redirect OR a redirect-like string that isn't a redirect because it's not at the top of the page, Parsoid follows the redirect and returns the document that the redirect points to, which is a pair of bugs (we'll need to be able to edit #REDIRECT statements, so it shouldn't return the redirected page, and it should behave the same way as the PHP parser with regard to what is considered a redirect).",task_subcomment,"['Phil, did this happen when you retried?', ""That error message (which sucks, and we're going to fix as part of bug 44354) just means that it couldn't hail the Parsoid server at the time, and normally means that nothing went wrong other than the server availability."", ""More generally, when you edit a page which as has a redirect OR a redirect-like string that isn't a redirect because it's not at the top of the page, Parsoid follows the redirect and returns the document that the redirect points to, which is a pair of bugs (we'll need to be able to edit #REDIRECT statements, so it shouldn't return the redirected page, and it should behave the same way as the PHP parser with regard to what is considered a redirect).""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+46838,VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,"**Author:** `mwalker`
+
+**Description:**
+On chrome 24 and firefox 18.0.2 -- rapid switching between the edit tab and the view tab will cause multiple toolbars to be displayed on both the edit tab and view tab.
+
+I note that the page DOM becomes more and more unusable as I keep switching.
+
+As I am switching when I still see the 'loading' indicator; I am guessing that this is caused by a non complete initialization of the editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Multiple toolbars created if tabs switched before initialization is complete\n\n**Author:** CODE\n\n**Description:**\nOn chrome 24 and firefox 18.0.2 -- rapid switching between the edit tab and the view tab will cause multiple toolbars to be displayed on both the edit tab and view tab.', 'I note that the page DOM becomes more and more unusable as I keep switching.', ""As I am switching when I still see the 'loading' indicator; I am guessing that this is caused by a non complete initialization of the editor."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+208579,VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Now merged.,task_subcomment,['Now merged.'],['SOLUTION DISCUSSION']
+208575,VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,"Whoops, not yet merged.",task_subcomment,"['Whoops, not yet merged.']",['ACTION ON ISSUE']
+208571,VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Merged.,task_subcomment,['Merged.'],['SOLUTION DISCUSSION']
+208567,VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Patch in: https://gerrit.wikimedia.org/r/48491,task_subcomment,['Patch in: GERRIT_URL'],['SOLUTION DISCUSSION']
+46780,VisualEditor: What Heading levels are offered should flex based,"**Author:** `phil`
+
+**Description:**
+Selecting some text and applying Header 6 to it has no affect
+
+The normal editor does not offer this option so it seems inconsistent for it to be an option in the Visual Editor
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor: What Heading levels are offered should flex based\n\n**Author:** CODE\n\n**Description:**\nSelecting some text and applying Header 6 to it has no affect\n\nThe normal editor does not offer this option so it seems inconsistent for it to be an option in the Visual Editor\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['INVESTIGATION AND EXPLORATION']
+231156,VisualEditor: What Heading levels are offered should flex based,"Levels of headings available will need to be tweakable for local integrations - for example, we probably don't want to allow H1s in the article namespace on our content wikis.
+
+However, H6s do in fact work and should be made available in general to HTML editors; not sure whether we should provide them in article space.
+
+Am marking this as a duplicate of bug 43334 which talks about H1s; will adjust that one.
+
+*** This bug has been marked as a duplicate of bug 43334 ***",task_subcomment,"[""Levels of headings available will need to be tweakable for local integrations - for example, we probably don't want to allow H1s in the article namespace on our content wikis."", 'However, H6s do in fact work and should be made available in general to HTML editors; not sure whether we should provide them in article space.', 'Am marking this as a duplicate of bug 43334 which talks about H1s; will adjust that one.', '*** This bug has been marked as a duplicate of bug 43334 ***']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+231149,VisualEditor: What Heading levels are offered should flex based,"Created attachment 11760
+Screenshot showing H1 to H6 in VisualEditor mode
+
+**Attached**: {F11017}",task_subcomment,['Created attachment 11760\nScreenshot showing H1 to H6 in VisualEditor mode\n\n**Attached**: {F11017}'],['ATTACHMENT']
+231140,VisualEditor: What Heading levels are offered should flex based,"Created attachment 11759
+Screenshot showing H1 to H6 in read mode
+
+**Attached**: {F11015}",task_subcomment,['Created attachment 11759\nScreenshot showing H1 to H6 in read mode\n\n**Attached**: {F11015}'],['ATTACHMENT']
+46779,Parsoid: Linktrails should get a  added on serialisation,"**Author:** `phil`
+
+**Description:**
+Link includes the word 'and'
+
+I edited the space after a link so that the word following was right next to the link. I then realised this was not what I wanted so added the space back
+The preview indicated all was well with the space included but after saving the word after the link became part of the link
+
+Example:
+The text I had was
+""A page about a test pilot and his job""
+'test pilot' was a link
+
+I edited the page and put the cursor before the 'a' in 'and' and pressed delete.
+I then pressed Space to move the word back to its original position
+Saved - the preview indicated all was well
+After saving - 'and' had become part of the link
+
+Looking at the page in the normal editor it seems the space has not been put back - the Visual Editor display indicates that it has
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11010}",task_description,"[""Parsoid: Linktrails should get a  added on serialisation\n\n**Author:** CODE\n\n**Description:**\nLink includes the word 'and'\n\nI edited the space after a link so that the word following was right next to the link."", 'I then realised this was not what I wanted so added the space back\nThe preview indicated all was well with the space included but after saving the word after the link became part of the link\n\nExample:\nThe text I had was\n""A page about a test pilot and his job""\n\'test pilot\' was a link\n\nI edited the page and put the cursor before the \'a\' in \'and\' and pressed delete.', ""I then pressed Space to move the word back to its original position\nSaved - the preview indicated all was well\nAfter saving - 'and' had become part of the link\n\nLooking at the page in the normal editor it seems the space has not been put back - the Visual Editor display indicates that it has\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11010}""]","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION']"
+231072,Parsoid: Linktrails should get a  added on serialisation,"Ah, couldn't find the bug; thanks, Gabriel.
+
+*** This bug has been marked as a duplicate of bug 33091 ***",task_subcomment,"[""Ah, couldn't find the bug; thanks, Gabriel."", '*** This bug has been marked as a duplicate of bug 33091 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231068,Parsoid: Linktrails should get a  added on serialisation,"To me it seems that the VE should produce a DOM including the space: 
+
+bar baz
+
+If that is not the case, then this is a bug in VE. Escaping for legitimate link trails was fixed in bug 33091, which is not yet deployed.
+
+So either way, I don't think there is a bug in Parsoid here.",task_subcomment,"['To me it seems that the VE should produce a DOM including the space: \n\nbar baz\n\nIf that is not the case, then this is a bug in VE.', 'Escaping for legitimate link trails was fixed in bug 33091, which is not yet deployed.', ""So either way, I don't think there is a bug in Parsoid here.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231063,Parsoid: Linktrails should get a  added on serialisation,"This appears to be a problem in Parsoid.
+
+In VisualEditor the user has (effectively) created barbaz; it is unexpectedly converted into [[foo|bar]]baz instead of [[foo|bar]]baz, hence the confusion.
+
+Gabriel, thoughts?",task_subcomment,"['This appears to be a problem in Parsoid.', 'In VisualEditor the user has (effectively) created barbaz; it is unexpectedly converted into [[foo|bar]]baz instead of [[foo|bar]]baz, hence the confusion.', 'Gabriel, thoughts?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+46686,VisualEditor: Opening link inspector without selection in stand alone instance throws error.,"Open stand alone editor.  Trigger LinkInspector with cmd/ctrl+k or LinkInspector button.
+
+Uncaught TypeError: Cannot read property 'data' of undefined ve.ui.LinkTargetInputWidget.js:84
+ve.ui.LinkTargetInputWidget.getTargetFromAnnotation ve.ui.LinkTargetInputWidget.js:84
+ve.ui.LinkTargetInputWidget.setAnnotation ve.ui.LinkTargetInputWidget.js:63
+ve.ui.LinkInspector.onOpen ve.ui.LinkInspector.js:95
+ve.ui.Inspector.open ve.ui.Inspector.js:206
+ve.ui.Context.openInspector ve.ui.Context.js:355
+ve.InspectorAction.open ve.InspectorAction.js:44
+ve.Surface.execute ve.Surface.js:193
+ve.Surface.execute ve.Surface.js:186
+ve.ce.Surface.onDocumentKeyDown ve.ce.Surface.js:330
+proxy jquery.js:775
+jQuery.event.dispatch jquery.js:3063
+elemData.handle.eventHandle
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Opening link inspector without selection in stand alone instance throws error.', 'Open stand alone editor.', 'Trigger LinkInspector with cmd/ctrl+k or LinkInspector button.', ""Uncaught TypeError: Cannot read property 'data' of undefined ve.ui.LinkTargetInputWidget.js:84\nve.ui.LinkTargetInputWidget.getTargetFromAnnotation ve.ui.LinkTargetInputWidget.js:84\nve.ui.LinkTargetInputWidget.setAnnotation ve.ui.LinkTargetInputWidget.js:63\nve.ui.LinkInspector.onOpen ve.ui.LinkInspector.js:95\nve.ui.Inspector.open ve.ui.Inspector.js:206\nve.ui.Context.openInspector ve.ui.Context.js:355\nve.InspectorAction.open ve.InspectorAction.js:44\nve.Surface.execute ve.Surface.js:193\nve.Surface.execute ve.Surface.js:186\nve.ce.Surface.onDocumentKeyDown ve.ce.Surface.js:330\nproxy jquery.js:775\njQuery.event.dispatch jquery.js:3063\nelemData.handle.eventHandle\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+225462,VisualEditor: Opening link inspector without selection in stand alone instance throws error.,Now merged.,task_subcomment,['Now merged.'],['SOLUTION DISCUSSION']
+225460,VisualEditor: Opening link inspector without selection in stand alone instance throws error.,Patched in https://gerrit.wikimedia.org/r/#/c/47615/,task_subcomment,['Patched in URL'],['SOLUTION DISCUSSION']
+46478,VisualEditor: Unexpected behavior when line starts with space,"nowiki tags
+
+edit a line in VE such that it starts with a space
+
+VE unexpectedly inserts  tags on the text of the line
+
+edit a line in VE such that it starts with a text, and add bold or italic to the middle of the line somewhere
+
+VE inserts  tags up to the formatted character and leaves the rest of the line alone
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10444}",task_description,"['VisualEditor: Unexpected behavior when line starts with space\n\nnowiki tags\n\nedit a line in VE such that it starts with a space\n\nVE unexpectedly inserts  tags on the text of the line\n\nedit a line in VE such that it starts with a text, and add bold or italic to the middle of the line somewhere\n\nVE inserts  tags up to the formatted character and leaves the rest of the line alone\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F10444}']",['OBSERVED BUG BEHAVIOR']
+212656,VisualEditor: Unexpected behavior when line starts with space,"... but when you save "" le'''''adi'''''ing space"" in the wikitext editor, you get 
    le'''''adi'''''ing space
    , not 
     le'''''adi'''''ing space
    . The  tags are necessary to get the latter, which is what the VE user actually typed.
+
+Closing as WONTFIX.",task_subcomment,"['... but when you save "" le\'\'\'\'\'adi\'\'\'\'\'ing space"" in the wikitext editor, you get 
    le\'\'\'\'\'adi\'\'\'\'\'ing space
    , not 
     le\'\'\'\'\'adi\'\'\'\'\'ing space
    .', 'The  tags are necessary to get the latter, which is what the VE user actually typed.', 'Closing as WONTFIX.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+212649,VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11719
+normal editor vs. VE on save
+
+**Attached**: {F10447}",task_subcomment,"['Created attachment 11719\nnormal editor vs.', 'VE on save\n\n**Attached**: {F10447}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+212641,VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11718
+normal editor vs. VE preview
+
+**Attached**: {F10446}",task_subcomment,"['Created attachment 11718\nnormal editor vs.', 'VE preview\n\n**Attached**: {F10446}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+212634,VisualEditor: Unexpected behavior when line starts with space,"
+Maybe I'm missing something. 
+
+I've attached a screen shot comparing preview in the normal editor to preview in VE where both are doing exactly the same operation:  editing the string "" leading space"" where the ""adi"" part of the string is made both bold and italic. 
+
+The normal editor does not add  tags to this string.  VE adds  tags. 
+
+The normal editor does not save the text with  tags.  VE saves the text with  tags. 
+
+It may be that VE adds  tags by design, but they seem unnecessary.  Again, I could be wrong.",task_subcomment,"[""\nMaybe I'm missing something."", 'I\'ve attached a screen shot comparing preview in the normal editor to preview in VE where both are doing exactly the same operation:  editing the string "" leading space"" where the ""adi"" part of the string is made both bold and italic.', 'The normal editor does not add  tags to this string.', 'VE adds  tags.', 'The normal editor does not save the text with  tags.', 'VE saves the text with  tags.', 'It may be that VE adds  tags by design, but they seem unnecessary.', 'Again, I could be wrong.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+212630,VisualEditor: Unexpected behavior when line starts with space,"No, this is expected behaviour. A line that starts with "" "" in wikitext is a pre-formatted block. If VE just let users save 
     Foo
     as "" Foo"" they'd get very unexpected results.
+
+We don't (and won't) expect users to understand that certain characters are magic and can't be used in certain places, and instead we need to escape character sequences they've entered that happen to be 'magic'.
+
+Unless I'm missing something?",task_subcomment,"['No, this is expected behaviour.', 'A line that starts with "" "" in wikitext is a pre-formatted block.', 'If VE just let users save 
     Foo
     as "" Foo"" they\'d get very unexpected results.', ""We don't (and won't) expect users to understand that certain characters are magic and can't be used in certain places, and instead we need to escape character sequences they've entered that happen to be 'magic'."", ""Unless I'm missing something?""]","['EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+212627,VisualEditor: Unexpected behavior when line starts with space,look what happens in the regular editor.  I think VE is doing something really strange here.,task_subcomment,"['look what happens in the regular editor.', 'I think VE is doing something really strange here.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+212625,VisualEditor: Unexpected behavior when line starts with space,I'm not entirely convinced what the expected behaviour is - should it be just the leading ' ' character that is wrapped in  elements?,task_subcomment,"[""I'm not entirely convinced what the expected behaviour is - should it be just the leading ' ' character that is wrapped in  elements?""]",['OBSERVED BUG BEHAVIOR']
+212622,VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11706
+nowiki tags with formatted text
+
+**Attached**: {F10445}",task_subcomment,['Created attachment 11706\nnowiki tags with formatted text\n\n**Attached**: {F10445}'],['INVESTIGATION AND EXPLORATION']
+46313,Parsoid should support passing on an authenticated user's read right (when MW API supports that),"**Author:** `mail`
+
+**Description:**
+Hi,
+
+when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:
+
+    {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}
+
+My config is as following:
+
+    require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");
+    define( 'NS_VISUALEDITOR', 2500 );
+    define( 'NS_VISUALEDITOR_TALK', 2501 );
+    $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor';
+    $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk';
+    $wgVisualEditorNamespaces = array( NS_MAIN );
+    $wgVisualEditorNamespaces = array();
+    $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;
+    $wgDefaultUserOptions['visualeditor-enable'] = 1;
+    $wgHiddenPrefs[] = 'visualeditor-enable';
+    $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/';
+
+I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC
+**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",task_description,"['Parsoid should support passing on an authenticated user\'s read right (when MW API supports that)\n\n**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n    {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n    require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n    define( \'NS_VISUALEDITOR\', 2500 );\n    define( \'NS_VISUALEDITOR_TALK\', 2501 );\n    $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n    $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n    $wgVisualEditorNamespaces = array( NS_MAIN );\n    $wgVisualEditorNamespaces = array();\n    $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n    $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n    $wgHiddenPrefs[] = \'visualeditor-enable\';\n    $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+226815,Parsoid should support passing on an authenticated user's read right (when MW API supports that),"
+
+*** This bug has been marked as a duplicate of bug 44483 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 44483 ***'],['ACTION ON ISSUE']
+226812,Parsoid should support passing on an authenticated user's read right (when MW API supports that),"**mail** wrote:
+
+http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html
+
+Solved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE.
+I hope there will be the possibility to have it FALSE in the future :)",task_subcomment,"[""**mail** wrote:\n\nURL\n\nSolved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE."", 'I hope there will be the possibility to have it FALSE in the future :)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+45925,SMW: Refresh tab (purge) is always collapsed when using the Vector skin,"Just very recently I started to work with semantic wikis intensely which use the Vector skin as a standard and where it does not make sense to switch back to MonoBook. 
+
+Having said this, I would like to suggest that the ""Refresh"" tab (purge) of the action menu at the top of a page is not collapsed with miscellaneous other tabs but always displayed expanded between the ""Edit"" and ""View history"" tabs.
+
+Especially for beginners it would be very helpful to make them aware of the possible need to refresh a page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['SMW: Refresh tab (purge) is always collapsed when using the Vector skin\n\nJust very recently I started to work with semantic wikis intensely which use the Vector skin as a standard and where it does not make sense to switch back to MonoBook.', 'Having said this, I would like to suggest that the ""Refresh"" tab (purge) of the action menu at the top of a page is not collapsed with miscellaneous other tabs but always displayed expanded between the ""Edit"" and ""View history"" tabs.', 'Especially for beginners it would be very helpful to make them aware of the possible need to refresh a page.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+420024,SMW: Refresh tab (purge) is always collapsed when using the Vector skin,"The Semantic MediaWiki developers requested in https://phabricator.wikimedia.org/T64114 to move their task tracking to https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues and to close remaining tasks in Wikimedia Phabricator.  If you still face the problem reported in this task in a supported version of SMW, please feel free to transfer your report to https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues .  We are sorry for the inconvenience.",task_subcomment,"['The Semantic MediaWiki developers requested in URL to move their task tracking to URL and to close remaining tasks in Wikimedia Phabricator.', 'If you still face the problem reported in this task in a supported version of SMW, please feel free to transfer your report to URL .', 'We are sorry for the inconvenience.']","['INVESTIGATION AND EXPLORATION', 'WORKAROUNDS', 'INVESTIGATION AND EXPLORATION']"
+229648,SMW: Refresh tab (purge) is always collapsed when using the Vector skin,"Removing relation to Vector skin issues. This is the default behaviour indeed, but individual menu items can indicate whether or not Vector should allow them to ""come out  of the menu"" and onto the horizontal menu bar when space is available.
+
+The navigation links array in PHP (exposed via the SkinTemplateNavigation hook[1]) contains an array for each tab. Setting property 'primary' to boolean true will instruct Vector to apply class ""collapsible"".
+
+Example:
+ https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/1f136f9d1d/VisualEditor.hooks.php#L96-L101
+
+
+[1] https://www.mediawiki.org/wiki/Manual:Hooks/SkinTemplateNavigation",task_subcomment,"['Removing relation to Vector skin issues.', 'This is the default behaviour indeed, but individual menu items can indicate whether or not Vector should allow them to ""come out  of the menu"" and onto the horizontal menu bar when space is available.', 'The navigation links array in PHP (exposed via the SkinTemplateNavigation hook[1]) contains an array for each tab.', 'Setting property \'primary\' to boolean true will instruct Vector to apply class ""collapsible"".', 'Example:\n URL\n\n\n[1] URL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', '1] URL']"
+45841,"VisualEditor: Make link inspector aware of annotations, rather than just target strings","The link inspector currently depends on a function which decides whether a target is an internal or external link, making it impossible to link to a new or existing page named like a URL.
+
+This is related to bug 43063.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43063",task_description,"['VisualEditor: Make link inspector aware of annotations, rather than just target strings\n\nThe link inspector currently depends on a function which decides whether a target is an internal or external link, making it impossible to link to a new or existing page named like a URL.', 'This is related to bug 43063.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+224674,"VisualEditor: Make link inspector aware of annotations, rather than just target strings",Made it to master for the 2013-01-16 branch.,task_subcomment,['Made it to master for the 2013-01-16 branch.'],['SOLUTION USAGE']
+224670,"VisualEditor: Make link inspector aware of annotations, rather than just target strings",Addressed in gerrit 43028.,task_subcomment,['Addressed in gerrit 43028.'],['SOLUTION USAGE']
+45566,"VisualEditor: Fix ""Error loading data from server: error. Would you like to retry?""","**Author:** `Coiby.Xu`
+
+**Description:**
+I'm testing VE and meet such error: ""Error loading data from server: Server error. Would you like to retry"". And the output of Parsoid says: ""non-200 response: 404 undefined"". According to http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2012_12#Error_loading_data_from_server:_Server_error._Would_you_like_to_retry.3F_2, the bug should have be fixed. 
+P.S. I'm using latest VE and Parsoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**OS**: Linux",task_description,"['VisualEditor: Fix ""Error loading data from server: error.', 'Would you like to retry?""', '**Author:** CODE\n\n**Description:**\nI\'m testing VE and meet such error: ""Error loading data from server: Server error.', 'Would you like to retry"".', 'And the output of Parsoid says: ""non-200 response: 404 undefined"".', 'According to URL the bug should have be fixed.', 'P.S.', ""I'm using latest VE and Parsoid."", '--------------------------\n**Version**: unspecified\n**Severity**: critical\n**OS**: Linux']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+208325,"VisualEditor: Fix ""Error loading data from server: error. Would you like to retry?""","**Coiby.Xu** wrote:
+
+I'm sorry, this should be a bug. It occurs due to the wrong setting in js/api/localsettings.js
+env.setInterwiki( 'localhost', 'http://' );",task_subcomment,"[""**Coiby.Xu** wrote:\n\nI'm sorry, this should be a bug."", ""It occurs due to the wrong setting in js/api/localsettings.js\nenv.setInterwiki( 'localhost', 'URL );""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+208320,"VisualEditor: Fix ""Error loading data from server: error. Would you like to retry?""","**blue.snow013** wrote:
+
+(In reply to comment #4)
+> (In reply to comment #3)
+> > I have the same problems on the latest VE and Parsoid,too.
+> > could someone help me?
+> Could you tell us:
+> * What $wgVisualEditorParsoidURL and $wgVisualEditorParsoidPrefix are set to
+> in
+> your LocalSettings.php
+> * the contents of Parsoid's localsettings.js file
+> * where Parsoid is running
+
+Here is my LocalSettings.php
+
+require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");
+ 
+// Allow using VisualEditor in the main namespace only (default)
+$wgVisualEditorNamespaces = array( NS_MAIN );
+ 
+// Enable by default for everybody
+$wgDefaultUserOptions['visualeditor-enable'] = 1;
+ 
+// Don't allow users to disable it
+$wgHiddenPrefs[] = 'visualeditor-enable';
+
+$wgVisualEditorParsoidURL = 'http://localhost:8000/';
+
+
+And my localsettings.js:
+
+exports.setup = function( config, env ) {
+        // The URL here is supposed to be your MediaWiki installation root
+        env.setInterwiki( 'localhost', 'http://localhost/wiki' );
+
+        // Use the PHP preprocessor to expand templates via the MW API
+        env.usePHPPreProcessor = false;
+};
+
+// Use selective serialization
+exports.useSelser = false;
+                      
+I run the Parsoid in the background using node on my own server.
+
+Thanks!",task_subcomment,"['**blue.snow013** wrote:\n\n(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nHere is my LocalSettings.php\n\nrequire_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n \n// Allow using VisualEditor in the main namespace only (default)\n$wgVisualEditorNamespaces = array( NS_MAIN );\n \n// Enable by default for everybody\n$wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n \n// Don\'t allow users to disable it\n$wgHiddenPrefs[] = \'visualeditor-enable\';\n\n$wgVisualEditorParsoidURL = \'URL\n\n\nAnd my localsettings.js:\n\nexports.setup = function( config, env ) {\n        // The URL here is supposed to be your MediaWiki installation root\n        env.setInterwiki( \'localhost\', \'URL );\n\n        // Use the PHP preprocessor to expand templates via the MW API\n        env.usePHPPreProcessor = false;\n};\n\n// Use selective serialization\nexports.useSelser = false;\n                      \nI run the Parsoid in the background using node on my own server.', 'Thanks!']","['SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+208311,"VisualEditor: Fix ""Error loading data from server: error. Would you like to retry?""","(In reply to comment #3)
+> I have the same problems on the latest VE and Parsoid,too.
+> could someone help me?
+Could you tell us:
+* What $wgVisualEditorParsoidURL and $wgVisualEditorParsoidPrefix are set to in your LocalSettings.php
+* the contents of Parsoid's localsettings.js file
+* where Parsoid is running",task_subcomment,"[""(In reply to comment #3)\nQUOTE\nQUOTE\nCould you tell us:\n* What $wgVisualEditorParsoidURL and $wgVisualEditorParsoidPrefix are set to in your LocalSettings.php\n* the contents of Parsoid's localsettings.js file\n* where Parsoid is running""]",['INVESTIGATION AND EXPLORATION']
+208304,"VisualEditor: Fix ""Error loading data from server: error. Would you like to retry?""","**blue.snow013** wrote:
+
+I have the same problems on the latest VE and Parsoid,too.
+could someone help me?",task_subcomment,"['**blue.snow013** wrote:\n\nI have the same problems on the latest VE and Parsoid,too.', 'could someone help me?']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+208297,"VisualEditor: Fix ""Error loading data from server: error. Would you like to retry?""","**Coiby.Xu** wrote:
+
+I'm running it on my own server.
+Here's the address for testing: wiki.aiesec.cn/index.php?title=Test.
+If you click ""VisualEditor"", the above error will occur.
+> (In reply to comment #0)
+> > P.S. I'm using latest VE and Parsoid.
+> 
+> Are you saying you're running it on your own server? Or are you using
+> Wikipedia?",task_subcomment,"[""**Coiby.Xu** wrote:\n\nI'm running it on my own server."", ""Here's the address for testing: wiki.aiesec.cn/index.php?title=Test."", 'If you click ""VisualEditor"", the above error will occur.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+208293,"VisualEditor: Fix ""Error loading data from server: error. Would you like to retry?""","(In reply to comment #0)
+> P.S. I'm using latest VE and Parsoid.
+
+Are you saying you're running it on your own server? Or are you using Wikipedia?",task_subcomment,"[""(In reply to comment #0)\nQUOTE\n\nAre you saying you're running it on your own server?"", 'Or are you using Wikipedia?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+45460,VisualEditor: Empty editnotices appear as notices,"The VisualEditor toolbar has a section for ""notices"" between the ""Leave feedback"" and ""Cancel"" buttons. This includes the ""You are using an alpha version of the VisualEditor. It may be slow and make erroneous changes - please check each edit that you make."" notice, as well as a relevant edit notice where one exists, separated by a gray line. However, when there is no edit notice, the section still says ""2 notices"" and places an empty div resulting in a gray line at the bottom.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Empty editnotices appear as notices\n\nThe VisualEditor toolbar has a section for ""notices"" between the ""Leave feedback"" and ""Cancel"" buttons.', 'This includes the ""You are using an alpha version of the VisualEditor.', 'It may be slow and make erroneous changes - please check each edit that you make.""', 'notice, as well as a relevant edit notice where one exists, separated by a gray line.', 'However, when there is no edit notice, the section still says ""2 notices"" and places an empty div resulting in a gray line at the bottom.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+202768,VisualEditor: Empty editnotices appear as notices,"This is due to English Wikipedia's self-invented system for edit notices where their [[MediaWiki:Editnotice-0]] / [[Template:Editnotice load]] displays an html structure even when there is no edit notice created (namely the link to ""create"" the edit notice, hidden/shown with usergroup css).
+
+Although that system is rather unhandy (as it means there will always be an edit notice even when this is not intended), it is possible to work around it by parsing the edit notice client side in javascript and applying the local stylesheet and check whether there are any non-hidden nodes.
+
+This was done and fixed in master. It will be deployed in the next branch.
+
+*** This bug has been marked as a duplicate of bug 43013 ***",task_subcomment,"['This is due to English Wikipedia\'s self-invented system for edit notices where their [[MediaWiki:Editnotice-0]] / [[Template:Editnotice load]] displays an html structure even when there is no edit notice created (namely the link to ""create"" the edit notice, hidden/shown with usergroup css).', 'Although that system is rather unhandy (as it means there will always be an edit notice even when this is not intended), it is possible to work around it by parsing the edit notice client side in javascript and applying the local stylesheet and check whether there are any non-hidden nodes.', 'This was done and fixed in master.', 'It will be deployed in the next branch.', '*** This bug has been marked as a duplicate of bug 43013 ***']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'WORKAROUNDS', 'OBSERVED BUG BEHAVIOR']"
+45429,Removing link trail doesn't affect the output,"In investigating bug 43089, we found that removing a link trail (i.e. [[Link]]s --> [[Link]]) is impossible in the VisualEditor. This is a Parsoid bug, can be reproduced with this command:
+
+echo ""[[Link]]s"" | node parse.js | sed 's/Links/blah/;' | node parse.js --html2wt
+
+This is a further result of our steadfast approach of ""if the tests aren't broken, it's working"" -- we didn't consider changes for a long time, and now that changes are possible, our hacks for roundtripping don't always work....
+
+Suggested solution:
+
+1. First try to find the initial link text (sans trail) in the current link text. If it's there, the new trail is whatever is left.
+
+2. If that failed, try to find the old trail in the current text with a regex like /s$/. If you find it, emit it.
+
+3. If both of those fail, don't emit a link trail. The trail has been modified enough that it's probably just within the text of the link now, and we won't lose meaning by just using the [[link|text]] syntax.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Removing link trail doesn't affect the output\n\nIn investigating bug 43089, we found that removing a link trail (i.e."", '[[Link]]s --> [[Link]]) is impossible in the VisualEditor.', 'This is a Parsoid bug, can be reproduced with this command:\n\necho ""[[Link]]s"" | node parse.js | sed \'s/Links/blah/;\' | node parse.js --html2wt\n\nThis is a further result of our steadfast approach of ""if the tests aren\'t broken, it\'s working"" -- we didn\'t consider changes for a long time, and now that changes are possible, our hacks for roundtripping don\'t always work....', 'Suggested solution:\n\n1.', 'First try to find the initial link text (sans trail) in the current link text.', ""If it's there, the new trail is whatever is left."", '2.', 'If that failed, try to find the old trail in the current text with a regex like /s$/.', 'If you find it, emit it.', '3.', ""If both of those fail, don't emit a link trail."", ""The trail has been modified enough that it's probably just within the text of the link now, and we won't lose meaning by just using the [[link|text]] syntax."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+200760,Removing link trail doesn't affect the output,Finally squashed in https://gerrit.wikimedia.org/r/#/c/43985/.,task_subcomment,['Finally squashed in URL'],['SOLUTION DISCUSSION']
+200752,Removing link trail doesn't affect the output,Change I126116de should fix this.,task_subcomment,['Change I126116de should fix this.'],['SOLUTION DISCUSSION']
+200743,Removing link trail doesn't affect the output,"You can replicate this in VisualEditor in fact by removing the trailing 's' when the linked 's' came via a link-trail in the original wikitext.    
+
+We record information about original wikitext in html-attributes.  Recording source information in attributes and using it is not a hack -- it is necessary to preserve original wikitext when it is unmodified (which is going to be more often than not).  We now need to fix our serialization to detect modifications in cases like this where we are currently not.",task_subcomment,"[""You can replicate this in VisualEditor in fact by removing the trailing 's' when the linked 's' came via a link-trail in the original wikitext."", 'We record information about original wikitext in html-attributes.', 'Recording source information in attributes and using it is not a hack -- it is necessary to preserve original wikitext when it is unmodified (which is going to be more often than not).', 'We now need to fix our serialization to detect modifications in cases like this where we are currently not.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+45323,PHP Fatal error:  Call to undefined method Title::getEditNotices() in extensions/VisualEditor/ApiVisualEditor.php,"**Author:** `aderumier`
+
+**Description:**
+Hello,
+I'm trying VisualEditor, last git version (21 december), and I got an error 500 on POST /api.php, when I try to edit/create a page with visualeditor
+
+php-fpm error log give me
+
+Call to undefined method Title::getEditNotices() in extensions/VisualEditor/ApiVisualEditor.php
+
+
+Any idea ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""PHP Fatal error:  Call to undefined method Title::getEditNotices() in extensions/VisualEditor/ApiVisualEditor.php\n\n**Author:** CODE\n\n**Description:**\nHello,\nI'm trying VisualEditor, last git version (21 december), and I got an error 500 on POST /api.php, when I try to edit/create a page with visualeditor\n\nphp-fpm error log give me\n\nCall to undefined method Title::getEditNotices() in extensions/VisualEditor/ApiVisualEditor.php\n\n\nAny idea ?"", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+194880,PHP Fatal error:  Call to undefined method Title::getEditNotices() in extensions/VisualEditor/ApiVisualEditor.php,This method was added into MediaWiki core in Gerrit change 36240. You'll need to update to that.,task_subcomment,"['This method was added into MediaWiki core in Gerrit change 36240.', ""You'll need to update to that.""]","['MOTIVATION', 'SOLUTION DISCUSSION']"
+45258,VisualEditor: Tooltip broken on outdent button,"https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=modules/ve/ui/tools/buttons/ve.ui.OutdentButtonTool.js;h=ccb5e6cfbf8edc3b5f8326941fe50db8417dd85e;hb=HEAD#l29
+
+Change
+visualeditor-outdentationbutton-outdent-tooltip
+to
+visualeditor-indentationbutton-outdent-tooltip
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor: Tooltip broken on outdent button\n\nURL\n\nChange\nvisualeditor-outdentationbutton-outdent-tooltip\nto\nvisualeditor-indentationbutton-outdent-tooltip\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['BUG REPRODUCTION']
+190926,VisualEditor: Tooltip broken on outdent button,Thanks for the report.  This was patched in. https://gerrit.wikimedia.org/r/#/c/38810/,task_subcomment,"['Thanks for the report.', 'This was patched in.', 'URL']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+45119,Reporter missing in IRC announcement of new issue,"The reporter is missing in the IRC announcements of new issues in #mediawiki.
+
+Observed IRC output:
+
+(NEW) VisualEditor: Support  extension - https://bugzilla.wikimedia.org/43118 normal; VisualEditor: General; ()
+(NEW) File will not change from original version - https://bugzilla.wikimedia.org/43117 normal; MediaWiki: File management; ()
+(NEW) prevent update.php from updating database schemata of wgSharedTables - https://bugzilla.wikimedia.org/43116 enhancement; MediaWiki: Installer; ()
+
+Expected IRC output: ""()"" replaced by ""(UserName)"":
+
+(NEW) VisualEditor: Support  extension - https://bugzilla.wikimedia.org/43118 normal; VisualEditor: General; (Raimond Spekking)
+(NEW) File will not change from original version - https://bugzilla.wikimedia.org/43117 normal; MediaWiki: File management; (Adam Cuerden)
+(NEW) prevent update.php from updating database schemata of wgSharedTables - https://bugzilla.wikimedia.org/43116 enhancement; MediaWiki: Installer; (Gregor Hagedorn)
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",task_description,"['Reporter missing in IRC announcement of new issue\n\nThe reporter is missing in the IRC announcements of new issues in #mediawiki.', 'Observed IRC output:\n\n(NEW) VisualEditor: Support  extension - URL normal; VisualEditor: General; ()\n(NEW) File will not change from original version - URL normal; MediaWiki: File management; ()\n(NEW) prevent update.php from updating database schemata of wgSharedTables - URL enhancement; MediaWiki: Installer; ()\n\nExpected IRC output: ""()"" replaced by ""(UserName)"":\n\n(NEW) VisualEditor: Support  extension - URL normal; VisualEditor: General; (Raimond Spekking)\n(NEW) File will not change from original version - URL normal; MediaWiki: File management; (Adam Cuerden)\n(NEW) prevent update.php from updating database schemata of wgSharedTables - URL enhancement; MediaWiki: Installer; (Gregor Hagedorn)\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+183160,Reporter missing in IRC announcement of new issue,"
+
+*** This bug has been marked as a duplicate of bug 42774 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 42774 ***'],['ACTION ON ISSUE']
+45078,VisualEditor never loads,"After enabling the VisualEditor editing interface, as usual in the Vector skin, the tab appears but then the page actually never loads for editing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker
+**OS**: Windows XP
+**Platform**: PC",task_description,"['VisualEditor never loads\n\nAfter enabling the VisualEditor editing interface, as usual in the Vector skin, the tab appears but then the page actually never loads for editing.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker\n**OS**: Windows XP\n**Platform**: PC']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+205134,VisualEditor never loads,Wth?! Why does it take so much time to load. But then it atlast worked.,task_subcomment,"['Wth?!', 'Why does it take so much time to load.', 'But then it atlast worked.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+45064,VisualEditor: Skip the inspector menu on links,"The correctness of a Wikipedia article to a great extent depends on the correctness of the link targets. Presently, Visual Editors give no Visual feedback of the target.
+
+Enhancement 1: provide a tooltip for the target when hovering with the mouse over a link. This will be helpful for mouse-based computing devices.
+
+Enhancement 2: Open the link editing dialogue box directly when clicking the link. Presently when clicking on existing links, only a small chain-link icon appears, which has to be clicked again to open the dialogue which shows the link target and allows editing it.
+
+I believe the link-chain-icon step can be skipped.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Skip the inspector menu on links\n\nThe correctness of a Wikipedia article to a great extent depends on the correctness of the link targets.', 'Presently, Visual Editors give no Visual feedback of the target.', 'Enhancement 1: provide a tooltip for the target when hovering with the mouse over a link.', 'This will be helpful for mouse-based computing devices.', 'Enhancement 2: Open the link editing dialogue box directly when clicking the link.', 'Presently when clicking on existing links, only a small chain-link icon appears, which has to be clicked again to open the dialogue which shows the link target and allows editing it.', 'I believe the link-chain-icon step can be skipped.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+204232,VisualEditor: Skip the inspector menu on links,"What you explain is pretty depressing. Just the necessity to learn all the icons for all the rare-to-be-used ""inspectors"" that will accumulate over time sounds like it may continue to prevent a majority of people from editing ... I fear it is dangerous if programmers try to design the user interface for normal people.
+
+The method used by Google docs works really well for me: when clicking on an existing link, it directly shows the link target and offers ""change"" and ""remove"". Nice, simple, accessible, intuitive. And all the other non-context sensitive options for normal text stay in the menu and button and can be accessed from there. No toolbar full of accessor/inspector items that moves with the cursor and prevents reading.",task_subcomment,"['What you explain is pretty depressing.', 'Just the necessity to learn all the icons for all the rare-to-be-used ""inspectors"" that will accumulate over time sounds like it may continue to prevent a majority of people from editing ...', 'I fear it is dangerous if programmers try to design the user interface for normal people.', 'The method used by Google docs works really well for me: when clicking on an existing link, it directly shows the link target and offers ""change"" and ""remove"".', 'Nice, simple, accessible, intuitive.', 'And all the other non-context sensitive options for normal text stay in the menu and button and can be accessed from there.', 'No toolbar full of accessor/inspector items that moves with the cursor and prevents reading.']","['SOCIAL CONVERSATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+204226,VisualEditor: Skip the inspector menu on links,"(In reply to comment #2)
+> I remain unconvinced. What other ""inspectors"" do you want to call on a link?
+
+It's not ""on a link"", it's ""on some text"" - yes, this includes links if one is set, but there will be quite a few annotation inspectors; in complex cases, we may need to come up with a new interface if it ever got about half a dozen or so. What you're seeing is an artefact that we haven't written the other annotation inspectors yet - not that they aren't applicable. For example, we'll be creating (or helping others create) annotation inspectors for setting the selection's language (as used on the English Wikipedia through a template, but invaluable to our multi-lingual wikis), modifying text colour and other funky formatting, marking up the content as an address (as used through an extension in Wikivoyage) or as a status update (used on MediaWiki.org), and no-doubt several others that we haven't even thought of yet.
+
+Note that this menu (which is purely about annotation inspectors) doesn't trigger on text that isn't already a link, as we don't show it when there are no appropriate annotation inspectors for the context.
+
+There will also be a bunch of object inspectors for ""complex"" things like references, templates, images and other media, galleries, Wikidata transclusions and queries, music annotations, maths equations, EasyTimeline uses, code blocks with syntax highlighting, poems, and dozens of other things that are block-level parser hooks of some kind, as tailored to the wiki and within that to the context. And, of course, this list will expand over time as the number of things that can be created and edited through the VisualEditor approaches completeness for Wikimedia's cluster install, and for third parties using MediaWiki in their own situations.
+
+Finally, there will be a page-level inspector for page-level meta-data - like categories and language links, the ""magic words"" that perform title over-rides, redirects, suppression of the table of contents, etc.
+
+[Snip]
+
+> I fear it will be an even worse user experience if users have to choose
+> between various ""inspectors"" for a link. And I fear the choices will be
+> hard to make until they have read a couple of help pages. This is not what
+> I hope the VE will achieve...
+
+Certainly, part of our job is to make a complex task as simple as possible - but, to steal the phrase, no simpler. I fear that we haven't explained the concept of annotation inspectors in the design language well enough for the above to be clear, for which I apologise.
+
+> I would prefer a bit of object-oriented context smartness. Perhaps, to
+> satisfy the generic design (I can imagine some alternative choices for some
+> other objects...): why not skip the ""choose an inspector"" step if there is
+> only one choice for a given object in a given context? This would easily
+> support cases where an object may truly need a choice of inspectors, but
+> avoid the clumsiness of the current approach.
+
+This would mean that, as you move the cursor through the text, every time you hit a link, the link inspector would load, filling the screen (and triggering a wasteful and unwanted API request to get the suggested list of pages for the link text). Clearly for you, this would be appropriate, but I don't agree that it's an interface paradigm that would work for most users.
+
+> (Note that the tooltip enhancement does not help on modern touch devices, so
+> making the interaction with links to check link correctness painless remains
+> an issue.)
+
+Sorry, but this is not true. In an iPad or Android tablet or mobile 'phone, press and hold on a link to be informed of the link's title attribute; voilà, the link destination is revealed. Yes, this is messy, but our job is to be as seemless as possible in integrating with users' operating systems' existing workflows, not inventing our own.",task_subcomment,"['(In reply to comment #2)\nQUOTE\n\nIt\'s not ""on a link"", it\'s ""on some text"" - yes, this includes links if one is set, but there will be quite a few annotation inspectors; in complex cases, we may need to come up with a new interface if it ever got about half a dozen or so.', ""What you're seeing is an artefact that we haven't written the other annotation inspectors yet - not that they aren't applicable."", ""For example, we'll be creating (or helping others create) annotation inspectors for setting the selection's language (as used on the English Wikipedia through a template, but invaluable to our multi-lingual wikis), modifying text colour and other funky formatting, marking up the content as an address (as used through an extension in Wikivoyage) or as a status update (used on MediaWiki.org), and no-doubt several others that we haven't even thought of yet."", ""Note that this menu (which is purely about annotation inspectors) doesn't trigger on text that isn't already a link, as we don't show it when there are no appropriate annotation inspectors for the context."", 'There will also be a bunch of object inspectors for ""complex"" things like references, templates, images and other media, galleries, Wikidata transclusions and queries, music annotations, maths equations, EasyTimeline uses, code blocks with syntax highlighting, poems, and dozens of other things that are block-level parser hooks of some kind, as tailored to the wiki and within that to the context.', ""And, of course, this list will expand over time as the number of things that can be created and edited through the VisualEditor approaches completeness for Wikimedia's cluster install, and for third parties using MediaWiki in their own situations."", 'Finally, there will be a page-level inspector for page-level meta-data - like categories and language links, the ""magic words"" that perform title over-rides, redirects, suppression of the table of contents, etc.', '[Snip]\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nCertainly, part of our job is to make a complex task as simple as possible - but, to steal the phrase, no simpler.', ""I fear that we haven't explained the concept of annotation inspectors in the design language well enough for the above to be clear, for which I apologise."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis would mean that, as you move the cursor through the text, every time you hit a link, the link inspector would load, filling the screen (and triggering a wasteful and unwanted API request to get the suggested list of pages for the link text).', ""Clearly for you, this would be appropriate, but I don't agree that it's an interface paradigm that would work for most users."", 'QUOTE\nQUOTE\nQUOTE\n\nSorry, but this is not true.', ""In an iPad or Android tablet or mobile 'phone, press and hold on a link to be informed of the link's title attribute; voilà, the link destination is revealed."", ""Yes, this is messy, but our job is to be as seemless as possible in integrating with users' operating systems' existing workflows, not inventing our own.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+204220,VisualEditor: Skip the inspector menu on links,"I remain unconvinced. What other ""inspectors"" do you want to call on a link? (An ""Open link in new tab"" inspector? If yes I propose to integrate such special case functions in the link inspector itself to keep things simple and avoid decisions steps up front). 
+
+I fear it will be an even worse user experience if users have to choose between various ""inspectors"" for a link. And I fear the choices will be hard to make until they have read a couple of help pages. This is not what I hope the VE will achieve...
+
+I would prefer a bit of object-oriented context smartness. Perhaps, to satisfy the generic design (I can imagine some alternative choices for some other objects...): why not skip the ""choose an inspector"" step if there is only one choice for a given object in a given context? This would easily support cases where an object may truly need a choice of inspectors, but avoid the clumsiness of the current approach.
+
+(Note that the tooltip enhancement does not help on modern touch devices, so making the interaction with links to check link correctness painless remains an issue.)",task_subcomment,"['I remain unconvinced.', 'What other ""inspectors"" do you want to call on a link?', '(An ""Open link in new tab"" inspector?', 'If yes I propose to integrate such special case functions in the link inspector itself to keep things simple and avoid decisions steps up front).', 'I fear it will be an even worse user experience if users have to choose between various ""inspectors"" for a link.', 'And I fear the choices will be hard to make until they have read a couple of help pages.', 'This is not what I hope the VE will achieve...', 'I would prefer a bit of object-oriented context smartness.', 'Perhaps, to satisfy the generic design (I can imagine some alternative choices for some other objects...): why not skip the ""choose an inspector"" step if there is only one choice for a given object in a given context?', 'This would easily support cases where an object may truly need a choice of inspectors, but avoid the clumsiness of the current approach.', '(Note that the tooltip enhancement does not help on modern touch devices, so making the interaction with links to check link correctness painless remains an issue.)']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+204212,VisualEditor: Skip the inspector menu on links,"This mis-understands the menu - the ""chain icon"" launches the link inspector, but there are potentially quite a few icons in the user's context at this point. We only have the link inspector created at this stage, but we will have more before the VisualEditor is ""finished"".
+
+For the first enhancement, this was fixed in bug 37904 but that has regressed - have re-opened that one.",task_subcomment,"['This mis-understands the menu - the ""chain icon"" launches the link inspector, but there are potentially quite a few icons in the user\'s context at this point.', 'We only have the link inspector created at this stage, but we will have more before the VisualEditor is ""finished"".', 'For the first enhancement, this was fixed in bug 37904 but that has regressed - have re-opened that one.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+45056,VisualEditor: Things are sometimes alienated as block when they should be inline,"""phantoms"" text is wrapped into a ""div class=""ve-ce-phantoms"" "" which adds a linebreak because div is a  block element, see https://en.wikipedia.org/wiki/User:Raymond/nowiki
+
+Better to use a span I think.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Things are sometimes alienated as block when they should be inline\n\n""phantoms"" text is wrapped into a ""div class=""ve-ce-phantoms"" "" which adds a linebreak because div is a  block element, see URL\n\nBetter to use a span I think.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+203706,VisualEditor: Things are sometimes alienated as block when they should be inline,Merged; code will be deployed as part of the 2013-01-16 release cycle.,task_subcomment,['Merged; code will be deployed as part of the 2013-01-16 release cycle.'],['SOLUTION DISCUSSION']
+203700,VisualEditor: Things are sometimes alienated as block when they should be inline,https://gerrit.wikimedia.org/r/39846,task_subcomment,['GERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+203693,VisualEditor: Things are sometimes alienated as block when they should be inline,"Fixing summary. Editable nodes are called ""aliens"". The ""phantom"" is the green hatched-out overlay that appears when mousing over an alien. It's an absolutely positioned 
     that exists outside of the main editor DOM. Because of the mouseover effect, you can't actually inspect the aliens themselves easily, but when you do, you'll find that the actual uneditable content is in 
     or  as appropriate.
+
+The issue here is that some things (nowikis in Raymond's example, and I've seen some references do it in the wild) are alienated as alienBlock nodes by ve.dm.Converter when they should really be alienInline nodes.",task_subcomment,"['Fixing summary.', 'Editable nodes are called ""aliens"".', 'The ""phantom"" is the green hatched-out overlay that appears when mousing over an alien.', ""It's an absolutely positioned 
     that exists outside of the main editor DOM."", 'Because of the mouseover effect, you can\'t actually inspect the aliens themselves easily, but when you do, you\'ll find that the actual uneditable content is in 
     or  as appropriate.', ""The issue here is that some things (nowikis in Raymond's example, and I've seen some references do it in the wild) are alienated as alienBlock nodes by ve.dm.Converter when they should really be alienInline nodes.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+45055,VisualEditor: Escape from LinkAnnotation editor closes annotation editor but leaves suggestion box floating,"Screenshot of state after escape
+
+Steps to reproduce problem:
+1. Open link editor for a link on a page
+2. Enter a new page type
+3. Hit Escape
+
+Expected:
+Annotation editor closes.
+
+
+Actual:
+ve-ui-inspector hides, ve-ui-context-menu re-appears. But ve-ui-context-frame-overlay (and thus ve-ui-suggest-select) stay visible and interactive (taking hover and clicks). Though interaction is ignored at this point (clicking a different suggestion does not affect the actual link anymore).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10181}",task_description,"['VisualEditor: Escape from LinkAnnotation editor closes annotation editor but leaves suggestion box floating\n\nScreenshot of state after escape\n\nSteps to reproduce problem:\n1.', 'Open link editor for a link on a page\n2.', 'Enter a new page type\n3.', 'Hit Escape\n\nExpected:\nAnnotation editor closes.', 'Actual:\nve-ui-inspector hides, ve-ui-context-menu re-appears.', 'But ve-ui-context-frame-overlay (and thus ve-ui-suggest-select) stay visible and interactive (taking hover and clicks).', 'Though interaction is ignored at this point (clicking a different suggestion does not affect the actual link anymore).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F10181}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+203667,VisualEditor: Escape from LinkAnnotation editor closes annotation editor but leaves suggestion box floating,"
+
+%%%*** This bug has been marked as a duplicate of bug 43051 ***%%%",task_subcomment,['\n\n%%%*** This bug has been marked as a duplicate of bug 43051 ***%%%'],['ACTION ON ISSUE']
+45051,VisualEditor: Suggestion tool fails to close when escaping out of context menu.,"Pressing escape while editing a link with the suggestion tool open causes the context menu to close without ever hiding the suggestion tool in the dom.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Suggestion tool fails to close when escaping out of context menu.', 'Pressing escape while editing a link with the suggestion tool open causes the context menu to close without ever hiding the suggestion tool in the dom.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+203460,VisualEditor: Suggestion tool fails to close when escaping out of context menu.,Add to deployment milestone.,task_subcomment,['Add to deployment milestone.'],['ACTION ON ISSUE']
+203454,VisualEditor: Suggestion tool fails to close when escaping out of context menu.,%%%*** Bug 43055 has been marked as a duplicate of this bug. ***%%%,task_subcomment,"['%%%*** Bug 43055 has been marked as a duplicate of this bug.', '***%%%']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+203450,VisualEditor: Suggestion tool fails to close when escaping out of context menu.,"Escape was normally handled by calling onInput, until yesterday I simplified the close logic.  This slipped through the cracks pre-release.
+
+Patched in https://gerrit.wikimedia.org/r/38468",task_subcomment,"['Escape was normally handled by calling onInput, until yesterday I simplified the close logic.', 'This slipped through the cracks pre-release.', 'Patched in GERRIT_URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+45036,"VisualEditor: For initial deployment, do not over-ride edit-section links","Right now, VE grabs a hold of the edit-section links. However, for current deployment this should not be the case - they should remain pointing to the wikitext editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: For initial deployment, do not over-ride edit-section links\n\nRight now, VE grabs a hold of the edit-section links.', 'However, for current deployment this should not be the case - they should remain pointing to the wikitext editor.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+202693,"VisualEditor: For initial deployment, do not over-ride edit-section links",This appears to have missed the deploy-train; moving.,task_subcomment,['This appears to have missed the deploy-train; moving.'],['ACTION ON ISSUE']
+202689,"VisualEditor: For initial deployment, do not over-ride edit-section links",Now merged into master.,task_subcomment,['Now merged into master.'],['SOLUTION DISCUSSION']
+202684,"VisualEditor: For initial deployment, do not over-ride edit-section links",Fixed by https://gerrit.wikimedia.org/r/#/c/38451/,task_subcomment,['Fixed by URL'],['SOLUTION DISCUSSION']
+45033,VisualEditor: Undo just after load of the editor causes JS error.,"Open the editor, Hit Control/Command U.
+Throws Exception:
+Uncaught TypeError: Cannot read property 'start' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Undo just after load of the editor causes JS error.', 'Open the editor, Hit Control/Command U.', ""Throws Exception:\nUncaught TypeError: Cannot read property 'start' of null\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+202552,VisualEditor: Undo just after load of the editor causes JS error.,"Also happens for redo.
+Patched in: https://gerrit.wikimedia.org/r/#/c/38349/",task_subcomment,"['Also happens for redo.', 'Patched in: URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+44983,VisualEditor:  message is missing,"Seen on the VE-editing interface of https://www.mediawiki.org/wiki/VisualEditor:Test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor:  message is missing\n\nSeen on the VE-editing interface of URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+199407,VisualEditor:  message is missing,Add to deployment milestone.,task_subcomment,['Add to deployment milestone.'],['ACTION ON ISSUE']
+199404,VisualEditor:  message is missing,Working for me now after a hard refresh.,task_subcomment,['Working for me now after a hard refresh.'],['SOLUTION USAGE']
+199402,VisualEditor:  message is missing,"The messages are certainly in the i18n file, it probably just needs a l10n cache rebuild. Doing that now.",task_subcomment,"['The messages are certainly in the i18n file, it probably just needs a l10n cache rebuild.', 'Doing that now.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+199398,VisualEditor:  message is missing,"visualeditor-savedialog-title-review is in the i18n file the others aren't..
+
+visualeditor-toolbar-savedialog is also showing as missing...
+
+
+
+Certainly, for starters, having all the messages actually defined, and also ""exported"" to JS where necessary would be useful",task_subcomment,"[""visualeditor-savedialog-title-review is in the i18n file the others aren't..\n\nvisualeditor-toolbar-savedialog is also showing as missing..."", 'Certainly, for starters, having all the messages actually defined, and also ""exported"" to JS where necessary would be useful']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+199391,VisualEditor:  message is missing,"Confirming that this is a bug on mediawiki.org. I was about to file a bug and include a screenshot, but I think this should be pretty easy to spot in the interface on mediawiki.org.
+
+This may not be a VisualEditor bug, per se. It could be an issue with localisation cache.",task_subcomment,"['Confirming that this is a bug on mediawiki.org.', 'I was about to file a bug and include a screenshot, but I think this should be pretty easy to spot in the interface on mediawiki.org.', 'This may not be a VisualEditor bug, per se.', 'It could be an issue with localisation cache.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+199387,VisualEditor:  message is missing,"Also messages in that dialog, like , ,  etc",task_subcomment,"['Also messages in that dialog, like , ,  etc']",['OBSERVED BUG BEHAVIOR']
+44935,"VisualEditor: While using link inspector, transaction hangs and page eventually explodes.","Reproduce by create a new article with VisualEditor.
+
+Return down about 10 lines.
+Type some text, hit command+k (open link inspector)
+Select an item in the dropdown. Hit enter.
+
+Page may freeze but will eventually produce this stack error:
+
+Uncaught TypeError: Cannot read property 'type' of undefined ve.dm.Transaction.js:214
+ve.dm.Transaction.newFromAnnotation ve.dm.Transaction.js:214
+ve.dm.SurfaceFragment.annotateContent ve.dm.SurfaceFragment.js:450
+ve.ui.LinkInspector.onClose ve.ui.LinkInspector.js:172
+ve.ui.Inspector.close ve.ui.Inspector.js:204
+ve.ui.Context.closeInspector ve.ui.Context.js:341
+ve.ui.Context.hide ve.ui.Context.js:255
+ve.ui.Context.update ve.ui.Context.js:196
+ve.ui.Context.onChange ve.ui.Context.js:86
+(anonymous function) ve.EventEmitter.js:96
+ve.EventEmitter.emit ve.EventEmitter.js:43
+ve.dm.Surface.change ve.dm.Surface.js:278
+ve.ce.Surface.onSelectionChange ve.ce.Surface.js:293
+(anonymous function) ve.EventEmitter.js:96
+ve.EventEmitter.emit ve.EventEmitter.js:43
+ve.ce.SurfaceObserver.poll ve.ce.SurfaceObserver.js:178
+ve.ce.SurfaceObserver.start ve.ce.SurfaceObserver.js:67
+ve.ce.Surface.onUnlock ve.ce.Surface.js:313
+(anonymous function) ve.EventEmitter.js:96
+ve.EventEmitter.emit ve.EventEmitter.js:43
+ve.dm.Surface.undo ve.dm.Surface.js:322
+ve.HistoryAction.undo ve.HistoryAction.js:43
+ve.Surface.execute ve.Surface.js:162
+ve.ui.LinkInspector.onClose ve.ui.LinkInspector.js:161
+ve.ui.Inspector.close ve.ui.Inspector.js:204
+ve.ui.Inspector.onFormSubmit ve.ui.Inspector.js:102
+proxy load.php:775
+jQuery.event.dispatch load.php:3058
+elemData.handle.eventHandle
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: While using link inspector, transaction hangs and page eventually explodes.', 'Reproduce by create a new article with VisualEditor.', 'Return down about 10 lines.', 'Type some text, hit command+k (open link inspector)\nSelect an item in the dropdown.', 'Hit enter.', ""Page may freeze but will eventually produce this stack error:\n\nUncaught TypeError: Cannot read property 'type' of undefined ve.dm.Transaction.js:214\nve.dm.Transaction.newFromAnnotation ve.dm.Transaction.js:214\nve.dm.SurfaceFragment.annotateContent ve.dm.SurfaceFragment.js:450\nve.ui.LinkInspector.onClose ve.ui.LinkInspector.js:172\nve.ui.Inspector.close ve.ui.Inspector.js:204\nve.ui.Context.closeInspector ve.ui.Context.js:341\nve.ui.Context.hide ve.ui.Context.js:255\nve.ui.Context.update ve.ui.Context.js:196\nve.ui.Context.onChange ve.ui.Context.js:86\n(anonymous function) ve.EventEmitter.js:96\nve.EventEmitter.emit ve.EventEmitter.js:43\nve.dm.Surface.change ve.dm.Surface.js:278\nve.ce.Surface.onSelectionChange ve.ce.Surface.js:293\n(anonymous function) ve.EventEmitter.js:96\nve.EventEmitter.emit ve.EventEmitter.js:43\nve.ce.SurfaceObserver.poll ve.ce.SurfaceObserver.js:178\nve.ce.SurfaceObserver.start ve.ce.SurfaceObserver.js:67\nve.ce.Surface.onUnlock ve.ce.Surface.js:313\n(anonymous function) ve.EventEmitter.js:96\nve.EventEmitter.emit ve.EventEmitter.js:43\nve.dm.Surface.undo ve.dm.Surface.js:322\nve.HistoryAction.undo ve.HistoryAction.js:43\nve.Surface.execute ve.Surface.js:162\nve.ui.LinkInspector.onClose ve.ui.LinkInspector.js:161\nve.ui.Inspector.close ve.ui.Inspector.js:204\nve.ui.Inspector.onFormSubmit ve.ui.Inspector.js:102\nproxy load.php:775\njQuery.event.dispatch load.php:3058\nelemData.handle.eventHandle\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+196646,"VisualEditor: While using link inspector, transaction hangs and page eventually explodes.",Fixed in https://gerrit.wikimedia.org/r/#/c/38004/,task_subcomment,['Fixed in URL'],['BUG REPRODUCTION']
+44925,VisualEditor: Inspector doesn't open properly,"When you select backwards, the inspector doesn't open when you make something a link (using toolbar or command+k) and when it does open (by clicking the link icon in the context menu) the link suggestions show up in the wrong place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"[""VisualEditor: Inspector doesn't open properly\n\nWhen you select backwards, the inspector doesn't open when you make something a link (using toolbar or command+k) and when it does open (by clicking the link icon in the context menu) the link suggestions show up in the wrong place."", '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+196092,VisualEditor: Inspector doesn't open properly,*** Bug 37856 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 37856 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+196086,VisualEditor: Inspector doesn't open properly,Fixed in gerrit 37945.,task_subcomment,['Fixed in gerrit 37945.'],['SOLUTION USAGE']
+44920,VisualEditor: Re-enable the feedback tool for deployment,"Point to [[Project:VisualEditor/Feedback]] for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Re-enable the feedback tool for deployment\n\nPoint to [[Project:VisualEditor/Feedback]] for now.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['PROJECT:VISUALEDITOR/FEEDBACK', 'OBSERVED BUG BEHAVIOR']"
+195743,VisualEditor: Re-enable the feedback tool for deployment,See also https://gerrit.wikimedia.org/r/#/c/32700/ for usage.,task_subcomment,['See also URL for usage.'],['SOLUTION USAGE']
+44919,VisualEditor: Toolbar tooltips should also suggest key-commands,"Toolbar tooltips should also suggest key-commands - e.g. the bold button's tooltip should be ""Bold (Cmd+B)"". Not hard-coded but created live, though there may be i18n issues.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44012",task_description,"['VisualEditor: Toolbar tooltips should also suggest key-commands\n\nToolbar tooltips should also suggest key-commands - e.g.', 'the bold button\'s tooltip should be ""Bold (Cmd+B)"".', 'Not hard-coded but created live, though there may be i18n issues.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+195707,VisualEditor: Toolbar tooltips should also suggest key-commands,"Now merged, will go out in 2013-02-04 release cycle.",task_subcomment,"['Now merged, will go out in 2013-02-04 release cycle.']",['SOLUTION USAGE']
+195705,VisualEditor: Toolbar tooltips should also suggest key-commands,Patched in https://gerrit.wikimedia.org/r/#/c/44347/,task_subcomment,['Patched in URL'],['SOLUTION DISCUSSION']
+44848,VisualEditor: Notifications should not use db-variant of page titles,"Via viewPage.pageName (mw.config wgRelevantPageName)
+
+Creating or editing pages, the mw.notify send uses the db-variant straight from wgRelevantPageName.
+
+Should mw.Title.textify it for proper localisation and normalisation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Notifications should not use db-variant of page titles\n\nVia viewPage.pageName (mw.config wgRelevantPageName)\n\nCreating or editing pages, the mw.notify send uses the db-variant straight from wgRelevantPageName.', 'Should mw.Title.textify it for proper localisation and normalisation.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+191994,VisualEditor: Notifications should not use db-variant of page titles,"(In reply to comment #1)
+> Change-Id: Ie84168cd2509a17c180c6143a87a18ae8bbb3d0a
+Merged.",task_subcomment,['(In reply to comment #1)\nQUOTE\nMerged.'],['SOLUTION USAGE']
+191987,VisualEditor: Notifications should not use db-variant of page titles,Change-Id: Ie84168cd2509a17c180c6143a87a18ae8bbb3d0a,task_subcomment,['Change-Id: Ie84168cd2509a17c180c6143a87a18ae8bbb3d0a'],['OBSERVED BUG BEHAVIOR']
+44847,VisualEditor: Support Internet Explorer,"Right now we have Internet Explorer support removed because it fails to support a number of features, mostly around ContentEditable. However, as a major browser we need to find a way around these shortcomings.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Support Internet Explorer\n\nRight now we have Internet Explorer support removed because it fails to support a number of features, mostly around ContentEditable.', 'However, as a major browser we need to find a way around these shortcomings.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+191955,VisualEditor: Support Internet Explorer,"This is close-enough to done that I'm going to make this as complete. No doubt there will remain bugs, but those are within the framework of VE generally ""working"".",task_subcomment,"[""This is close-enough to done that I'm going to make this as complete."", 'No doubt there will remain bugs, but those are within the framework of VE generally ""working"".']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+191951,VisualEditor: Support Internet Explorer,Please see Bug 41233,task_subcomment,['Please see Bug 41233'],['OBSERVED BUG BEHAVIOR']
+191947,VisualEditor: Support Internet Explorer,"Argh, ignore that; an at-least partial fix in gerrit 37592.",task_subcomment,"['Argh, ignore that; an at-least partial fix in gerrit 37592.']",['OBSERVED BUG BEHAVIOR']
+191939,VisualEditor: Support Internet Explorer,Attempted fixes in gerrit 37566 and gerrit 37570.,task_subcomment,['Attempted fixes in gerrit 37566 and gerrit 37570.'],['BUG REPRODUCTION']
+44842,VisualEditor: Create a link at the beginning of the document throws rangy error,"Create a link at the beginning of the document, select it and open inspector.
+
+Uncaught TypeError: Cannot read property 'left' of undefined rangy-position.js:215
+(anonymous function) rangy-position.js:215
+(anonymous function) rangy-position.js:295
+(anonymous function) rangy-position.js:348
+ve.ce.Surface.getSelectionRect ve.ce.Surface.js:1190
+.......
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Create a link at the beginning of the document throws rangy error\n\nCreate a link at the beginning of the document, select it and open inspector.', ""Uncaught TypeError: Cannot read property 'left' of undefined rangy-position.js:215\n(anonymous function) rangy-position.js:215\n(anonymous function) rangy-position.js:295\n(anonymous function) rangy-position.js:348\nve.ce.Surface.getSelectionRect ve.ce.Surface.js:1190\n.......\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+191722,VisualEditor: Create a link at the beginning of the document throws rangy error,Related URL: https://gerrit.wikimedia.org/r/69707 (Gerrit Change I8bcdea0f7a6951216bf8368865d23ef6246880ea),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I8bcdea0f7a6951216bf8368865d23ef6246880ea)'],['OBSERVED BUG BEHAVIOR']
+191717,VisualEditor: Create a link at the beginning of the document throws rangy error,Fix in gerrit 37603,task_subcomment,['Fix in gerrit 37603'],['SOLUTION DISCUSSION']
+44764,"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['INVESTIGATION AND EXPLORATION']
+187052,"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language",Merged.,task_subcomment,['Merged.'],['SOLUTION DISCUSSION']
+187047,"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language",Change-Id: I84fee641162cdeed290092e56fb0e1d2562d833d,task_subcomment,['Change-Id: I84fee641162cdeed290092e56fb0e1d2562d833d'],['OBSERVED BUG BEHAVIOR']
+44670,VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken,"The VisualEditorMessagesModule class does not implement a ::getModifiedTime() method, and the default falls back to timestamp 1 (Thu Jan 01 1970 00:00:01), which, together with the max() with global MediaWiki Epoch is stuck on Wikimedia servers on 20120908T000000Z[1].
+
+
+> > mw.loader.getVersion('ext.visualEditor.specialMessages')
+> < ""20120908T000000Z""
+
+
+https://gerrit.wikimedia.org/r/gitweb?p=operations/mediawiki-config.git;a=blob;f=wmf-config/CommonSettings.php;h=8481e9b30130288b187cac5ebd7a6993320c91c4;hb=HEAD#l1347
+
+Assigning to self, being worked on. Filing as reminder and as future reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken\n\nThe VisualEditorMessagesModule class does not implement a ::getModifiedTime() method, and the default falls back to timestamp 1 (Thu Jan 01 1970 00:00:01), which, together with the max() with global MediaWiki Epoch is stuck on Wikimedia servers on 20120908T000000Z[1].', 'QUOTE\nQUOTE\n\n\nURL\n\nAssigning to self, being worked on.', 'Filing as reminder and as future reference.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+181694,VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken,Now merged into master.,task_subcomment,['Now merged into master.'],['SOLUTION DISCUSSION']
+181687,VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken,Change-Id: I7f26b47e9467e850c08b9c217c4f1098590de109,task_subcomment,['Change-Id: I7f26b47e9467e850c08b9c217c4f1098590de109'],['OBSERVED BUG BEHAVIOR']
+44456,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),"Fatal error:  Call to undefined method Title::getRedirectTarget() in /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php on line 305
+
+No stack trace currently as it seems the fatal log is empty...
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,['LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget()\n\nFatal error:  Call to undefined method Title::getRedirectTarget() in /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php on line 305\n\nNo stack trace currently as it seems the fatal log is empty...\n\n--------------------------\n**Version**: unspecified\n**Severity**: major'],['OBSERVED BUG BEHAVIOR']
+194167,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),"I added tests in https://gerrit.wikimedia.org/r/#/c/35388/, which should catch future regressions.",task_subcomment,['I added tests in URL which should catch future regressions.'],['BUG REPRODUCTION']
+194165,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),"It helps when I actually read the error message, hence the first folic.
+
+Said method can return null, though whether it will for your use case... So it shouldn't do any harm at least",task_subcomment,"['It helps when I actually read the error message, hence the first folic.', 'Said method can return null, though whether it will for your use case...', ""So it shouldn't do any harm at least""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+194161,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),"Thanks for fixing this, Sam (also for the wfProfileOuts).
+
+Apparently this was not caught by a parser test, so I'll create some tests for #REDIRECT behavior.
+
+I'll also check whether the ""if ( $target )"" is redundant or not. In any case, it shouldn't do any harm keeping it there.",task_subcomment,"['Thanks for fixing this, Sam (also for the wfProfileOuts).', ""Apparently this was not caught by a parser test, so I'll create some tests for #REDIRECT behavior."", 'I\'ll also check whether the ""if ( $target )"" is redundant or not.', ""In any case, it shouldn't do any harm keeping it there.""]","['SOLUTION USAGE', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+194157,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),https://gerrit.wikimedia.org/r/#/c/35327/,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+194150,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),"Basic fix in https://gerrit.wikimedia.org/r/#/c/35316/
+
+Not sure if further work also needed",task_subcomment,['Basic fix in URL\n\nNot sure if further work also needed'],['INVESTIGATION AND EXPLORATION']
+194143,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),"http://p.defau.lt/?hOOnMmL6voQcgnoX4_1Gpw
+
+[26-Nov-2012 22:14:15] Fatal error: Call to undefined method Title::getRedirectTarget() at /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php on line 305
+Server: mw11
+URL: http://[unknown-host]
+Backtrace:
+#0 /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php(305): LabeledSectionTransclusion->getWikiPageDom()
+#1 /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php(367): LabeledSectionTransclusion::getWikiPageDom(Object(Title), Array)
+#2 /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php(438): LabeledSectionTransclusion::setupPfunc12(Object(Parser), Object(PPTemplateFrame_DOM), Array, 'lst')
+#3 [internal function]: LabeledSectionTransclusion::pfuncIncludeObj(Object(Parser), Object(PPTemplateFrame_DOM), Array)
+#4 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3286): call_user_func_array(Array, Array)
+#5 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#6 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3452): PPFrame_DOM->expand(Object(PPNode_DOM))
+#7 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#8 /usr/local/apache/common-local/php-1.21wmf5/extensions/ParserFunctions/ParserFunctions_body.php(400): PPFrame_DOM->expand(Object(PPNode_DOM))
+#9 [internal function]: ExtParserFunctions::ifexistObj(Object(Parser), Object(PPTemplateFrame_DOM), Array)
+#10 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3286): call_user_func_array('ExtParserFuncti...', Array)
+#11 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#12 /usr/local/apache/common-local/php-1.21wmf5/extensions/ParserFunctions/ParserFunctions_body.php(400): PPFrame_DOM->expand(Object(PPNode_DOM))
+#13 [internal function]: ExtParserFunctions::ifexistObj(Object(Parser), Object(PPTemplateFrame_DOM), Array)
+#14 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3286): call_user_func_array('ExtParserFuncti...', Array)
+#15 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#16 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3452): PPFrame_DOM->expand(Object(PPNode_DOM))
+#17 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPFrame_DOM))
+#18 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3073): PPFrame_DOM->expand(Object(PPNode_DOM), 0)
+#19 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(1157): Parser->replaceVariables('The Wikimedia F...')
+#20 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(385): Parser->internalParse('The Wikimedia F...')
+#21 [internal function]: Parser->parse('The Wikimedia F...', Object(Title), Object(ParserOptions), true, true, NULL)
+#22 /usr/local/apache/common-local/php-1.21wmf5/includes/StubObject.php(79): call_user_func_array(Array, Array)
+#23 /usr/local/apache/common-local/php-1.21wmf5/includes/StubObject.php(99): StubObject->_call('parse', Array)
+#24 /usr/local/apache/common-local/php-1.21wmf5/includes/content/WikitextContent.php(290): StubObject->__call('parse', Array)
+#25 /usr/local/apache/common-local/php-1.21wmf5/includes/content/WikitextContent.php(290): StubObject->parse('The Wikimedia F...', Object(Title), Object(ParserOptions), true, true, NULL)
+#26 /usr/local/apache/common-local/php-1.21wmf5/includes/content/AbstractContent.php(234): WikitextContent->getParserOutput(Object(Title), NULL, NULL, false)
+#27 /usr/local/apache/common-local/php-1.21wmf5/includes/job/jobs/RefreshLinksJob.php(81): AbstractContent->getSecondaryDataUpdates(Object(Title), NULL, false)
+#28 /usr/local/apache/common-local/php-1.21wmf5/includes/job/jobs/RefreshLinksJob.php(193): RefreshLinksJob::runForTitleInternal(Object(Title), Object(Revision), 'RefreshLinksJob...')
+#29 /usr/local/apache/common-local/php-1.21wmf5/maintenance/runJobs.php(83): RefreshLinksJob2->run()
+#30 /usr/local/apache/common-local/php-1.21wmf5/maintenance/doMaintenance.php(110): RunJobs->execute()
+#31 /usr/local/apache/common-local/php-1.21wmf5/maintenance/runJobs.php(116): require_once('/usr/local/apac...')
+#32 /usr/local/apache/common-local/multiversion/MWScript.php(68): require_once('/usr/local/apac...')
+#33 {main}",task_subcomment,"[""URL\n\n[26-Nov-2012 22:14:15] Fatal error: Call to undefined method Title::getRedirectTarget() at /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php on line 305\nServer: mw11\nURL: URL\nBacktrace:\n#0 /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php(305): LabeledSectionTransclusion->getWikiPageDom()\n#1 /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php(367): LabeledSectionTransclusion::getWikiPageDom(Object(Title), Array)\n#2 /usr/local/apache/common-local/php-1.21wmf5/extensions/LabeledSectionTransclusion/lst.php(438): LabeledSectionTransclusion::setupPfunc12(Object(Parser), Object(PPTemplateFrame_DOM), Array, 'lst')\n#3 [internal function]: LabeledSectionTransclusion::pfuncIncludeObj(Object(Parser), Object(PPTemplateFrame_DOM), Array)\n#4 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3286): call_user_func_array(Array, Array)\n#5 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))\n#6 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3452): PPFrame_DOM->expand(Object(PPNode_DOM))\n#7 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))\n#8 /usr/local/apache/common-local/php-1.21wmf5/extensions/ParserFunctions/ParserFunctions_body.php(400): PPFrame_DOM->expand(Object(PPNode_DOM))\n#9 [internal function]: ExtParserFunctions::ifexistObj(Object(Parser), Object(PPTemplateFrame_DOM), Array)\n#10 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3286): call_user_func_array('ExtParserFuncti...', Array)\n#11 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))\n#12 /usr/local/apache/common-local/php-1.21wmf5/extensions/ParserFunctions/ParserFunctions_body.php(400): PPFrame_DOM->expand(Object(PPNode_DOM))\n#13 [internal function]: ExtParserFunctions::ifexistObj(Object(Parser), Object(PPTemplateFrame_DOM), Array)\n#14 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3286): call_user_func_array('ExtParserFuncti...', Array)\n#15 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))\n#16 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3452): PPFrame_DOM->expand(Object(PPNode_DOM))\n#17 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Preprocessor_DOM.php(1084): Parser->braceSubstitution(Array, Object(PPFrame_DOM))\n#18 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(3073): PPFrame_DOM->expand(Object(PPNode_DOM), 0)\n#19 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(1157): Parser->replaceVariables('The Wikimedia F...')\n#20 /usr/local/apache/common-local/php-1.21wmf5/includes/parser/Parser.php(385): Parser->internalParse('The Wikimedia F...')\n#21 [internal function]: Parser->parse('The Wikimedia F...', Object(Title), Object(ParserOptions), true, true, NULL)\n#22 /usr/local/apache/common-local/php-1.21wmf5/includes/StubObject.php(79): call_user_func_array(Array, Array)\n#23 /usr/local/apache/common-local/php-1.21wmf5/includes/StubObject.php(99): StubObject->_call('parse', Array)\n#24 /usr/local/apache/common-local/php-1.21wmf5/includes/content/WikitextContent.php(290): StubObject->__call('parse', Array)\n#25 /usr/local/apache/common-local/php-1.21wmf5/includes/content/WikitextContent.php(290): StubObject->parse('The Wikimedia F...', Object(Title), Object(ParserOptions), true, true, NULL)\n#26 /usr/local/apache/common-local/php-1.21wmf5/includes/content/AbstractContent.php(234): WikitextContent->getParserOutput(Object(Title), NULL, NULL, false)\n#27 /usr/local/apache/common-local/php-1.21wmf5/includes/job/jobs/RefreshLinksJob.php(81): AbstractContent->getSecondaryDataUpdates(Object(Title), NULL, false)\n#28 /usr/local/apache/common-local/php-1.21wmf5/includes/job/jobs/RefreshLinksJob.php(193): RefreshLinksJob::runForTitleInternal(Object(Title), Object(Revision), 'RefreshLinksJob...')\n#29 /usr/local/apache/common-local/php-1.21wmf5/maintenance/runJobs.php(83): RefreshLinksJob2->run()\n#30 /usr/local/apache/common-local/php-1.21wmf5/maintenance/doMaintenance.php(110): RunJobs->execute()\n#31 /usr/local/apache/common-local/php-1.21wmf5/maintenance/runJobs.php(116): require_once('/usr/local/apac...')\n#32 /usr/local/apache/common-local/multiversion/MWScript.php(68): require_once('/usr/local/apac...')\n#33 {main}""]",['BUG REPRODUCTION']
+194137,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),Caused by https://gerrit.wikimedia.org/r/#/c/31330/,task_subcomment,['Caused by URL'],['OBSERVED BUG BEHAVIOR']
+194130,LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),"Seems to be causing:
+
+* Fatal error where directly on page: https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&oldid=597441
+* Blank section where transcluded via a Template: https://www.mediawiki.org/w/index.php?title=VisualEditor&oldid=598709",task_subcomment,['Seems to be causing:\n\n* Fatal error where directly on page: URL\n* Blank section where transcluded via a Template: URL'],['OBSERVED BUG BEHAVIOR']
+44335,VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",task_description,['VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: blocker'],['BUG REPRODUCTION']
+186736,VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient,https://gerrit.wikimedia.org/r/#/c/34584/,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+44123,VisualEditor: i18n for alien tooltip,"The tooltip on aliens (""Sorry, you can't edit this with the Visual Editor"" or whatever) should be i18ned.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: i18n for alien tooltip\n\nThe tooltip on aliens (""Sorry, you can\'t edit this with the Visual Editor"" or whatever) should be i18ned.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+199634,VisualEditor: i18n for alien tooltip,Fixed in gerrit 33851,task_subcomment,['Fixed in gerrit 33851'],['SOLUTION USAGE']
+199628,VisualEditor: i18n for alien tooltip,"Also it's VisualEditor not ""Visual Editor"". :-)",task_subcomment,"['Also it\'s VisualEditor not ""Visual Editor"".', ':-)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+44120,VisualEditor: Change markers don't propagate when generated paragraphs are unwrapped,"When editing the text of a list item, a change marker is set on the paragraph, but that paragraph has .internal.generated=='wrapper', so it's unwrapped by the data->DOM converter. This unwrapping step destroys the change marker; instead, it should be merged into the list item.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Change markers don't propagate when generated paragraphs are unwrapped\n\nWhen editing the text of a list item, a change marker is set on the paragraph, but that paragraph has .internal.generated=='wrapper', so it's unwrapped by the data->DOM converter."", 'This unwrapping step destroys the change marker; instead, it should be merged into the list item.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+199486,VisualEditor: Change markers don't propagate when generated paragraphs are unwrapped,"
+
+*** This bug has been marked as a duplicate of bug 41947 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 41947 ***'],['ISSUE CONTENT MANAGEMENT']
+44111,[Regression] Parsoid now wrongly santising wikitext of tables,"See https://www.mediawiki.org/w/index.php?title=VisualEditor:Templates&diff=605499&oldid=605498 - previously this was edited without incident, but now we've switched from the 19 August build to the 12 November one, it's now changing the wikitext of this table.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""[Regression] Parsoid now wrongly santising wikitext of tables\n\nSee URL - previously this was edited without incident, but now we've switched from the 19 August build to the 12 November one, it's now changing the wikitext of this table."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+199059,[Regression] Parsoid now wrongly santising wikitext of tables,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+199056,[Regression] Parsoid now wrongly santising wikitext of tables,"This is not a regression, and is already tracked. So closing as duplicate.
+
+*** This bug has been marked as a duplicate of bug 39564 ***",task_subcomment,"['This is not a regression, and is already tracked.', 'So closing as duplicate.', '*** This bug has been marked as a duplicate of bug 39564 ***']","['ACTION ON ISSUE', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+199052,[Regression] Parsoid now wrongly santising wikitext of tables,"Are you sure this was edited without us introducing quotes before? Selective serialization is designed to handle this, but so far we have always normalized inter-attribute spacing and quoting.",task_subcomment,"['Are you sure this was edited without us introducing quotes before?', 'Selective serialization is designed to handle this, but so far we have always normalized inter-attribute spacing and quoting.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+56802,"VisualEditor: In the save dialog, ""characters left"" is under the ""pending changes"" text","When saving some page using VisualEditor, ""characters left"" (e.g. 255) is under the text which comes from the Pending changes extension.
+
+I have a picture to explain more. It's taken from the Finnish Wikipedia where is the Pending changes extension.
+
+https://commons.wikimedia.org/wiki/File:To_explain_a_bug_with_VisualEditor_and_Pending_changes.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: In the save dialog, ""characters left"" is under the ""pending changes"" text\n\nWhen saving some page using VisualEditor, ""characters left"" (e.g.', '255) is under the text which comes from the Pending changes extension.', 'I have a picture to explain more.', ""It's taken from the Finnish Wikipedia where is the Pending changes extension."", 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+270182,"VisualEditor: In the save dialog, ""characters left"" is under the ""pending changes"" text","Merging with bug 52175; this is happily already fixed in the re-written save dialog that will be coming shortly. Sorry for the disruption.
+
+*** This bug has been marked as a duplicate of bug 52175 ***",task_subcomment,"['Merging with bug 52175; this is happily already fixed in the re-written save dialog that will be coming shortly.', 'Sorry for the disruption.', '*** This bug has been marked as a duplicate of bug 52175 ***']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+270177,"VisualEditor: In the save dialog, ""characters left"" is under the ""pending changes"" text",Confirmed bug on de.wp.  Support for flagged revs was added on bug 49699.,task_subcomment,"['Confirmed bug on de.wp.', 'Support for flagged revs was added on bug 49699.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+56728,VisualEditor: Copying a heading's text doesn't copy its format (unless the entire node is copied),"From T56721 comment 2:
+
+> When I copy a portion of content beginning with a header, then paste it
+> elsewhere in the same document, everything is retained  /except/ the header.
+> However, if I begin before the header (the paragraph before the header, for
+> example) the header is retained.
+>
+> For example, copy everything from 'Start' to 'Finish' on this test page:
+> https://www.mediawiki.org/wiki/VisualEditor:Test1234567
+>
+> Everything is retained except the H2 formatting on 'Start'. See this
+> screenshot as an example too:
+> http://images.wikia.com/trevortest/images/5/54/Header_is_lost.png
+> {F16005520}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Copying a heading's text doesn't copy its format (unless the entire node is copied)\n\nFrom T56721 comment 2:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]",['INVESTIGATION AND EXPLORATION']
+265880,VisualEditor: Copying a heading's text doesn't copy its format (unless the entire node is copied),"
+
+*** This bug has been marked as a duplicate of bug 50126 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50126 ***'],['ISSUE CONTENT MANAGEMENT']
+56727,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Currently on MediaWiki.org, categories cannot be removed from the 'Page Settings' modal. This is true of new categories added and existing categories.
+
+https://www.mediawiki.org/wiki/VisualEditor:Test1234567?veaction=edit
+
+Inez says he's working on a fix now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"[""VisualEditor: Can't remove categories from 'Page Settings' modal in latest build\n\nCurrently on MediaWiki.org, categories cannot be removed from the 'Page Settings' modal."", 'This is true of new categories added and existing categories.', ""URL\n\nInez says he's working on a fix now."", '--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+265842,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Change 86674 merged by jenkins-bot:
+removedItems[i] is already an item, no need to pass removedItems[i].item
+
+https://gerrit.wikimedia.org/r/86674",task_subcomment,"['Change 86674 merged by jenkins-bot:\nremovedItems[i] is already an item, no need to pass removedItems[i].item\n\nGERRIT_URL']",['ACTION ON ISSUE']
+265838,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Change 86673 merged by jenkins-bot:
+removedItems[i] is already an item, no need to pass removedItems[i].item
+
+https://gerrit.wikimedia.org/r/86673",task_subcomment,"['Change 86673 merged by jenkins-bot:\nremovedItems[i] is already an item, no need to pass removedItems[i].item\n\nGERRIT_URL']",['ACTION ON ISSUE']
+265834,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Change 86674 had a related patch set uploaded by Jforrester:
+removedItems[i] is already an item, no need to pass removedItems[i].item
+
+https://gerrit.wikimedia.org/r/86674",task_subcomment,"['Change 86674 had a related patch set uploaded by Jforrester:\nremovedItems[i] is already an item, no need to pass removedItems[i].item\n\nGERRIT_URL']",['ACTION ON ISSUE']
+265830,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Change 86673 had a related patch set uploaded by Jforrester:
+removedItems[i] is already an item, no need to pass removedItems[i].item
+
+https://gerrit.wikimedia.org/r/86673",task_subcomment,"['Change 86673 had a related patch set uploaded by Jforrester:\nremovedItems[i] is already an item, no need to pass removedItems[i].item\n\nGERRIT_URL']",['ACTION ON ISSUE']
+265824,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Marking as ""FIXED""; have removed ""or change sort key"" from title per discussion with Inez.",task_subcomment,"['Marking as ""FIXED""; have removed ""or change sort key"" from title per discussion with Inez.']",['ACTION ON ISSUE']
+265817,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Change 86341 merged by jenkins-bot:
+removedItems[i] is already an item, no need to pass removedItems[i].item
+
+https://gerrit.wikimedia.org/r/86341",task_subcomment,"['Change 86341 merged by jenkins-bot:\nremovedItems[i] is already an item, no need to pass removedItems[i].item\n\nGERRIT_URL']",['ACTION ON ISSUE']
+265813,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Change 86341 had a related patch set uploaded by Catrope:
+(bug 54727) item itself is an item, there is no need to try to pass item of that item
+
+https://gerrit.wikimedia.org/r/86341",task_subcomment,"['Change 86341 had a related patch set uploaded by Catrope:\n(bug 54727) item itself is an item, there is no need to try to pass item of that item\n\nGERRIT_URL']",['BUG REPRODUCTION']
+265807,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,Bugfix for removal is waiting for review. Sortkey still not fixed - Trevor: Can you split it into separated bug?,task_subcomment,"['Bugfix for removal is waiting for review.', 'Sortkey still not fixed - Trevor: Can you split it into separated bug?']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+265799,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Change 86341 had a related patch set uploaded by Inez:
+(bug 54727) item itself is an item, there is no need to try to pass item of that item
+
+https://gerrit.wikimedia.org/r/86341",task_subcomment,"['Change 86341 had a related patch set uploaded by Inez:\n(bug 54727) item itself is an item, there is no need to try to pass item of that item\n\nGERRIT_URL']",['BUG REPRODUCTION']
+265792,VisualEditor: Can't remove categories from 'Page Settings' modal in latest build,"Also just checked editing a sort key — that functionality is no longer working as well. You can enter text into the field and close the inspector, but when it is reopened the text is not retained.",task_subcomment,"['Also just checked editing a sort key — that functionality is no longer working as well.', 'You can enter text into the field and close the inspector, but when it is reopened the text is not retained.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+56721,VisualEditor: Header formatting is stripped when copying (or cutting) and pasting inside a single article in Firefox,"Comparison of content
+
+I am on Mac OSX 10.8.5 on Firefox 24.0
+
+Steps to reproduce:
+
+1. Navigate to any article and open the VisualEditor (https://en.wikipedia.org/wiki/Kitten?veaction=edit)
+2. Copy any selection of text that has formatting (bold, italics, link, header, references)
+3. Paste the content elsewhere in the same VE document.
+4. You will see that all formatting has been stripped. See the attached file.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12231}",task_description,"['VisualEditor: Header formatting is stripped when copying (or cutting) and pasting inside a single article in Firefox\n\nComparison of content\n\nI am on Mac OSX 10.8.5 on Firefox 24.0\n\nSteps to reproduce:\n\n1.', 'Navigate to any article and open the VisualEditor (URL\n2.', 'Copy any selection of text that has formatting (bold, italics, link, header, references)\n3.', 'Paste the content elsewhere in the same VE document.', '4.', 'You will see that all formatting has been stripped.', 'See the attached file.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F12231}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+265480,VisualEditor: Header formatting is stripped when copying (or cutting) and pasting inside a single article in Firefox,"Making this a new bug as it's actually present in all browsers and has been around for a while, unlike this one - bug 54728.",task_subcomment,"[""Making this a new bug as it's actually present in all browsers and has been around for a while, unlike this one - bug 54728.""]",['BUG REPRODUCTION']
+265475,VisualEditor: Header formatting is stripped when copying (or cutting) and pasting inside a single article in Firefox,"Oh, it is fixed!  But now I see a more minor issue:
+
+When I copy a portion of content beginning with a header, then paste it elsewhere in the same document, everything is retained  /except/ the header. However, if I begin before the header (the paragraph before the header, for example) the header is retained.
+
+For example, copy everything from 'Start' to 'Finish' on this test page: https://www.mediawiki.org/wiki/VisualEditor:Test1234567
+
+Everything is retained except the H2 formatting on 'Start'. See this screenshot as an example too: http://images.wikia.com/trevortest/images/5/54/Header_is_lost.png
+
+I can create a new ticket if you need me to, but I think this one may suffice with a name change.",task_subcomment,"['Oh, it is fixed!', 'But now I see a more minor issue:\n\nWhen I copy a portion of content beginning with a header, then paste it elsewhere in the same document, everything is retained  /except/ the header.', 'However, if I begin before the header (the paragraph before the header, for example) the header is retained.', ""For example, copy everything from 'Start' to 'Finish' on this test page: URL\n\nEverything is retained except the H2 formatting on 'Start'."", 'See this screenshot as an example too: URL\n\nI can create a new ticket if you need me to, but I think this one may suffice with a name change.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+265469,VisualEditor: Header formatting is stripped when copying (or cutting) and pasting inside a single article in Firefox,"Aha - yes, sorry, I *can* re-create this in wmf18 (en.wikipedia.org) but not wmf19 (mediawiki.org). I think we fixed this is in gerrit 85213, but closing as FIXED for now. If you can reproduce on MediaWiki.org (or master), please re-open.",task_subcomment,"['Aha - yes, sorry, I *can* re-create this in wmf18 (en.wikipedia.org) but not wmf19 (mediawiki.org).', 'I think we fixed this is in gerrit 85213, but closing as FIXED for now.', 'If you can reproduce on MediaWiki.org (or master), please re-open.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'BUG REPRODUCTION']"
+56706,VisualEditor: Sometimes the edit link for VE does not appear,"Edit link for VE missing in automated test
+
+Seen on mw.o and test2wiki, with examples from automated tests and manual operations, but I do not have a consistent repro. 
+
+Seems to happen more frequently for Chrome than Firefox. 
+
+The lack of an edit link causes automated tests to fail from time to time.  I had thought it might be an artifact of the automation, but one of our candidates for VE QA also encountered the issue and conveniently provided a screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12179}",task_description,"['VisualEditor: Sometimes the edit link for VE does not appear\n\nEdit link for VE missing in automated test\n\nSeen on mw.o and test2wiki, with examples from automated tests and manual operations, but I do not have a consistent repro.', 'Seems to happen more frequently for Chrome than Firefox.', 'The lack of an edit link causes automated tests to fail from time to time.', 'I had thought it might be an artifact of the automation, but one of our candidates for VE QA also encountered the issue and conveniently provided a screen shot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F12179}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+264484,VisualEditor: Sometimes the edit link for VE does not appear,No recent reports.,task_subcomment,['No recent reports.'],['OBSERVED BUG BEHAVIOR']
+264482,VisualEditor: Sometimes the edit link for VE does not appear,"Have you seen this issue recently? If not, this could probably be closed...",task_subcomment,"['Have you seen this issue recently?', 'If not, this could probably be closed...']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+264480,VisualEditor: Sometimes the edit link for VE does not appear,*** Bug 60359 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 60359 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+264477,VisualEditor: Sometimes the edit link for VE does not appear,"probably worth a look but this might be WORKSFORME, I don't think we've encountered this issue in at least a month",task_subcomment,"[""probably worth a look but this might be WORKSFORME, I don't think we've encountered this issue in at least a month""]",['WORKAROUNDS']
+264475,VisualEditor: Sometimes the edit link for VE does not appear,"Created attachment 13393
+Edit link for VE missing in manual operation
+
+**Attached**: {F12180}",task_subcomment,['Created attachment 13393\nEdit link for VE missing in manual operation\n\n**Attached**: {F12180}'],['INVESTIGATION AND EXPLORATION']
+56675,VisualEditor: Render lock when changing selection prevents inspectors' changes from rendering,"This is the root cause of bug 54335. Basically, you open the language inspector (or the link inspector, for that matter), make a change, then close the inspector by clicking elsewhere into the document (as opposed to by using the arrow or by pressing enter or escape in the link inspector's text input).
+
+Narrated call stack:
+* A mouseup event fires on the document
+* ve.ce.Surface.onDocumentMouseUp() starts the observer and polls
+* The observer notices that the selection has changed and emits a selectionChange event, which ends up invoking ve.ce.Surface.onSelectionChange
+* onSelectionChange sets a render lock and changes the model selection
+* ve.dm.Surface.change() emits a change event
+* ve.ui.Context.onChange() notices that the selection changed while an inspector was visible, so it closes the inspector
+* ve.ui.AnnotationInspector.onClose() saves the changes the user made to the model, by indirectly calling ve.dm.Surface.change()
+* (at this point, we have a change() call stack frame nested inside another change() frame, which is always a bad sign)
+* The transaction processed by onClose() annotates text, which causes an update event to be emitted
+* ve.ce.ContentBranchNode.onChildUpdate() responds to this event and calls renderContents()
+* renderContents() checks to see if the surface is locked for rendering; it is, so it bails and doesn't render the change
+
+When I briefly talked to Trevor about this issue, he said something about emitting an event asynchronously. I dismissed it at the time, because it would just move both problems (having to lock to prevent the model normalizing the selection / event storms, but having to not lock to allow inspector changes to render), but now I think about it I think it has merit. We could have ve.ui.Context.onChange() asynchronously close the inspector, from a setTimeout(). That would avoid the nested change() thing, and it would allow the render lock to be lifted before the inspector is closed.
+
+Alternatively, onSelectionChange could only lock against selection changes and still allow transactions. But the nested change() seems like a code smell anyway, the order of event handlers might get messed up for instance, and the caller would observe multiple changes from calling change() once (that's the root of the problem here).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Render lock when changing selection prevents inspectors' changes from rendering\n\nThis is the root cause of bug 54335."", ""Basically, you open the language inspector (or the link inspector, for that matter), make a change, then close the inspector by clicking elsewhere into the document (as opposed to by using the arrow or by pressing enter or escape in the link inspector's text input)."", ""Narrated call stack:\n* A mouseup event fires on the document\n* ve.ce.Surface.onDocumentMouseUp() starts the observer and polls\n* The observer notices that the selection has changed and emits a selectionChange event, which ends up invoking ve.ce.Surface.onSelectionChange\n* onSelectionChange sets a render lock and changes the model selection\n* ve.dm.Surface.change() emits a change event\n* ve.ui.Context.onChange() notices that the selection changed while an inspector was visible, so it closes the inspector\n* ve.ui.AnnotationInspector.onClose() saves the changes the user made to the model, by indirectly calling ve.dm.Surface.change()\n* (at this point, we have a change() call stack frame nested inside another change() frame, which is always a bad sign)\n* The transaction processed by onClose() annotates text, which causes an update event to be emitted\n* ve.ce.ContentBranchNode.onChildUpdate() responds to this event and calls renderContents()\n* renderContents() checks to see if the surface is locked for rendering; it is, so it bails and doesn't render the change\n\nWhen I briefly talked to Trevor about this issue, he said something about emitting an event asynchronously."", 'I dismissed it at the time, because it would just move both problems (having to lock to prevent the model normalizing the selection / event storms, but having to not lock to allow inspector changes to render), but now I think about it I think it has merit.', 'We could have ve.ui.Context.onChange() asynchronously close the inspector, from a setTimeout().', 'That would avoid the nested change() thing, and it would allow the render lock to be lifted before the inspector is closed.', 'Alternatively, onSelectionChange could only lock against selection changes and still allow transactions.', ""But the nested change() seems like a code smell anyway, the order of event handlers might get messed up for instance, and the caller would observe multiple changes from calling change() once (that's the root of the problem here)."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+263009,VisualEditor: Render lock when changing selection prevents inspectors' changes from rendering,"Change 90957 merged by jenkins-bot:
+Defer selection-triggered updates in ve.ui.Context
+
+https://gerrit.wikimedia.org/r/90957",task_subcomment,['Change 90957 merged by jenkins-bot:\nDefer selection-triggered updates in ve.ui.Context\n\nGERRIT_URL'],['ACTION ON ISSUE']
+263005,VisualEditor: Render lock when changing selection prevents inspectors' changes from rendering,"Change 90957 had a related patch set uploaded by Catrope:
+Defer selection-triggered updates in ve.ui.Context
+
+https://gerrit.wikimedia.org/r/90957",task_subcomment,['Change 90957 had a related patch set uploaded by Catrope:\nDefer selection-triggered updates in ve.ui.Context\n\nGERRIT_URL'],['ACTION ON ISSUE']
+263002,VisualEditor: Render lock when changing selection prevents inspectors' changes from rendering,"From #mediawiki-visualeditor IRC with RoanKattouw:
+
+* It seems wrong to implement click-out-to-close by detecting a selection change.
+* Should we bind to document mousedown instead? We need to avoid tripping over other mouse handling of course.
+
+Aside from this,
+
+* In general DM selection changes should emit something less drastic than 'change', because we don't want them to get back to the CE layer (which has a somewhat different set of possible cursor positions).
+* I (David) am currently working on a fairly big refactor of ve.ce.Surface will include this.",task_subcomment,"['From #mediawiki-visualeditor IRC with RoanKattouw:\n\n* It seems wrong to implement click-out-to-close by detecting a selection change.', '* Should we bind to document mousedown instead?', 'We need to avoid tripping over other mouse handling of course.', ""Aside from this,\n\n* In general DM selection changes should emit something less drastic than 'change', because we don't want them to get back to the CE layer (which has a somewhat different set of possible cursor positions)."", '* I (David) am currently working on a fairly big refactor of ve.ce.Surface will include this.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+56577,VisualEditor: Rendering of  MWExtensionNode is empty after the user edits it,"1. Create a page with some content here
+2. Edit the page in VE. Note that the  tag renders correctly
+3. Use the alien tag inspector to edit the contents of the  tag
+4. The  tag rerenders as an empty block
+
+This is because the HTML  tag is self-closing and cannot have any content. This leads to strange situations like:
+
+>>> extensionNode[0]
+​whee​​
+>>> extensionNode[0].outerHTML
+""""
+
+To avoid the HTML behavior for this and possibly other tag names, we should create an XML node rather than an HTML node to build the wikitext string for the preview.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57429",task_description,"['VisualEditor: Rendering of  MWExtensionNode is empty after the user edits it\n\n1.', 'Create a page with some content here\n2.', 'Edit the page in VE.', 'Note that the  tag renders correctly\n3.', 'Use the alien tag inspector to edit the contents of the  tag\n4.', 'The  tag rerenders as an empty block\n\nThis is because the HTML  tag is self-closing and cannot have any content.', 'This leads to strange situations like:\n\nQUOTE\n\u200bwhee\u200b\u200b\nQUOTE\n""""\n\nTo avoid the HTML behavior for this and possibly other tag names, we should create an XML node rather than an HTML node to build the wikitext string for the preview.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+257051,VisualEditor: Rendering of  MWExtensionNode is empty after the user edits it,"Change 98392 merged by jenkins-bot:
+Render MW extension node wikitext with XML
+
+https://gerrit.wikimedia.org/r/98392",task_subcomment,['Change 98392 merged by jenkins-bot:\nRender MW extension node wikitext with XML\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+257044,VisualEditor: Rendering of  MWExtensionNode is empty after the user edits it,"Change 98392 had a related patch set uploaded by Esanders:
+Render MW extension node wikitext with XML
+
+https://gerrit.wikimedia.org/r/98392",task_subcomment,['Change 98392 had a related patch set uploaded by Esanders:\nRender MW extension node wikitext with XML\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+56445,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","https://en.wikipedia.org/w/index.php?title=Daniel_Rowe_%28footballer%29&oldid=570278760&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54341",task_description,"['[Regression] VisualEditor: Attribute name="":0"" inserted into \n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']",['BUG REPRODUCTION']
+254458,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","Hey Roan :)
+I might be wrong, but I think it's still about name corruption (I think the user is complaining that he added or reused a reference, but after he saved the number in brackets was not pointing to the one he chose).
+Anyway, I'll contact the user to get more details, because it might also be not a bug at all. As I wrote elsewhere, I think it can be confusing that the name and the number of a reference do not match, although everything will still work as intended.
+See
+https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=575128343&oldid=575128003
+(the reference #2 gets a ref name:3).",task_subcomment,"[""Hey Roan :)\nI might be wrong, but I think it's still about name corruption (I think the user is complaining that he added or reused a reference, but after he saved the number in brackets was not pointing to the one he chose)."", ""Anyway, I'll contact the user to get more details, because it might also be not a bug at all."", 'As I wrote elsewhere, I think it can be confusing that the name and the number of a reference do not match, although everything will still work as intended.', 'See\nURL\n(the reference #2 gets a ref name:3).']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+254456,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","(In reply to comment #7)
+> Additional comments from Polish Wikipedia Kthaara:
+> 
+> ""Bug seems did not recognize references or not recognize their numbers. Ex.:
+> I
+> wrote some text in section about add-ons and need to make a reference to page
+> from Eve-community. I make one and VE, sure, did it, but aotomaticaly
+> redirects
+> to completely different reference, like: it make ref no. 50 and redirect it
+> to
+> no. 3 - which is different thing. After several tries I manage to get right
+> reference but it change another. In this moment I gave up."" 
+> 
+> And here is a diff:
+> https://pl.wikipedia.org/w/index.
+> php?title=Eve_Online&diff=37587971&oldid=37587957
+This looks like a similar bug, but it's not the same bug (the original report was about name corruption, not content corruption). Could you file a new bug for this?
+
+Additionally, an as detailed as possible explanation of what the user did to produce that diff (step-by-step instructions, if they remember) would be very helpful. It's theoretically possible for VE to produce that diff legitimately if the user did certain things, but I doubt that's what happened.",task_subcomment,"[""(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nThis looks like a similar bug, but it's not the same bug (the original report was about name corruption, not content corruption)."", 'Could you file a new bug for this?', 'Additionally, an as detailed as possible explanation of what the user did to produce that diff (step-by-step instructions, if they remember) would be very helpful.', ""It's theoretically possible for VE to produce that diff legitimately if the user did certain things, but I doubt that's what happened.""]","['MOTIVATION', 'ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+254454,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","Additional comments from Polish Wikipedia Kthaara:
+
+""Bug seems did not recognize references or not recognize their numbers. Ex.: I wrote some text in section about add-ons and need to make a reference to page from Eve-community. I make one and VE, sure, did it, but aotomaticaly redirects to completely different reference, like: it make ref no. 50 and redirect it to no. 3 - which is different thing. After several tries I manage to get right reference but it change another. In this moment I gave up."" 
+
+And here is a diff: https://pl.wikipedia.org/w/index.php?title=Eve_Online&diff=37587971&oldid=37587957",task_subcomment,"['Additional comments from Polish Wikipedia Kthaara:\n\n""Bug seems did not recognize references or not recognize their numbers.', 'Ex.', ': I wrote some text in section about add-ons and need to make a reference to page from Eve-community.', 'I make one and VE, sure, did it, but aotomaticaly redirects to completely different reference, like: it make ref no.', '50 and redirect it to no.', '3 - which is different thing.', 'After several tries I manage to get right reference but it change another.', 'In this moment I gave up.""', 'And here is a diff: URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254452,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","This problem was also reported happening on Polish Wikipedia (PL.WP) by User:Kthaara (using VE on Win 7, Mozilla Firefox (latest version)).
+
+https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#linki_i_przypisy 
+
+>> This bug appears when I edited Eve Online page:
+>> https://pl.wikipedia.org/wiki/Eve_Online",task_subcomment,"['This problem was also reported happening on Polish Wikipedia (PL.WP) by User:Kthaara (using VE on Win 7, Mozilla Firefox (latest version)).', 'URL \n\nQUOTE\nQUOTE']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+254448,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","I believe that this is the same as bug 54341 which was fixed last week and is live.
+
+*** This bug has been marked as a duplicate of bug 54341 ***",task_subcomment,"['I believe that this is the same as bug 54341 which was fixed last week and is live.', '*** This bug has been marked as a duplicate of bug 54341 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+254443,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","More from Red Fiona:
+<>",task_subcomment,"[""More from Red Fiona:\n<>""]",['OBSERVED BUG BEHAVIOR']
+254439,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","Worse, I just attempted to add an actual reference, and this bug just replaced the reference I tried to insert with a cross-reference to this new bogus :0 reference!
+
+It was a good thing Visual Editor got disabled by default recently - quality control seems to be lacking!!",task_subcomment,"['Worse, I just attempted to add an actual reference, and this bug just replaced the reference I tried to insert with a cross-reference to this new bogus :0 reference!', 'It was a good thing Visual Editor got disabled by default recently - quality control seems to be lacking!', '!']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254431,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","Created attachment 13346
+Screenshot of dirty diff on ""Turkey Hill (company)""
+
+https://en.wikipedia.org/w/index.php?title=Turkey_Hill_(company)&oldid=568325662&veaction=edit
+
+http://tools.wmflabs.org/visualeditor/dirtydiffs/2013-09-17_13-00/Turkey_Hill_-company-.png
+
+**Attached**: {F11869}",task_subcomment,"['Created attachment 13346\nScreenshot of dirty diff on ""Turkey Hill (company)""\n\nURL\n\nURL\n\n**Attached**: {F11869}']",['URL']
+254424,"[Regression] VisualEditor: Attribute name="":0"" inserted into ","Created attachment 13344
+Screenshot of dirty diff on ""Daniel Rowe (footballer)""
+
+http://tools.wmflabs.org/visualeditor/dirtydiffs/2013-09-17_13-00/Daniel_Rowe_-footballer-.png
+
+**Attached**: {F11868}",task_subcomment,"['Created attachment 13344\nScreenshot of dirty diff on ""Daniel Rowe (footballer)""\n\nURL\n\n**Attached**: {F11868}']",['BUG REPRODUCTION']
+56443,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,"**Author:** `swalling`
+
+**Description:**
+Steps to reproduce:
+
+1. Place your cursor in page text. 
+2. Navigate through the text with left-right arrow keys, until you get to a reference
+3. When the ref tool popup appears, you cannot move past it with arrow keys.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys\n\n**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Place your cursor in page text.', '2.', 'Navigate through the text with left-right arrow keys, until you get to a reference\n3.', 'When the ref tool popup appears, you cannot move past it with arrow keys.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+254347,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,"Change 86801 merged by Catrope:
+Make cursoring over a FocusableNode work again
+
+https://gerrit.wikimedia.org/r/86801",task_subcomment,['Change 86801 merged by Catrope:\nMake cursoring over a FocusableNode work again\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+254339,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,"Change 86800 merged by Catrope:
+Make cursoring over a FocusableNode work again
+
+https://gerrit.wikimedia.org/r/86800",task_subcomment,['Change 86800 merged by Catrope:\nMake cursoring over a FocusableNode work again\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+254336,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,Merged into master; we'll back-port and deploy tomorrow.,task_subcomment,"[""Merged into master; we'll back-port and deploy tomorrow.""]",['ACTION ON ISSUE']
+254332,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,"Change 86801 had a related patch set uploaded by Jforrester:
+Make cursoring over a FocusableNode work again
+
+https://gerrit.wikimedia.org/r/86801",task_subcomment,['Change 86801 had a related patch set uploaded by Jforrester:\nMake cursoring over a FocusableNode work again\n\nGERRIT_URL'],['ACTION ON ISSUE']
+254330,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,"Change 86800 had a related patch set uploaded by Jforrester:
+Make cursoring over a FocusableNode work again
+
+https://gerrit.wikimedia.org/r/86800",task_subcomment,['Change 86800 had a related patch set uploaded by Jforrester:\nMake cursoring over a FocusableNode work again\n\nGERRIT_URL'],['ACTION ON ISSUE']
+254326,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,"Change 86788 merged by jenkins-bot:
+Make cursoring over a FocusableNode work again
+
+https://gerrit.wikimedia.org/r/86788",task_subcomment,['Change 86788 merged by jenkins-bot:\nMake cursoring over a FocusableNode work again\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+254322,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,"Change 86788 had a related patch set uploaded by Catrope:
+Make cursoring over a FocusableNode work again
+
+https://gerrit.wikimedia.org/r/86788",task_subcomment,['Change 86788 had a related patch set uploaded by Catrope:\nMake cursoring over a FocusableNode work again\n\nGERRIT_URL'],['ACTION ON ISSUE']
+254318,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,*** Bug 54722 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54722 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254314,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,The events from the pasteTarget (which has focus when a focusableNode is selected) are not getting through to the document listener.,task_subcomment,['The events from the pasteTarget (which has focus when a focusableNode is selected) are not getting through to the document listener.'],['OBSERVED BUG BEHAVIOR']
+254307,VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,Updating priority to normal. Inability to move the cursor using arrows is definitely a bug.,task_subcomment,"['Updating priority to normal.', 'Inability to move the cursor using arrows is definitely a bug.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+56410,VisualEditor: [Regression] Copy/paste of existing templates and images broken (unformatted text pasted only),"Copy/pasting a template that existed prior to the current session only pastes, as literal text, the unformatted text output of the template. Template boxes, etc are ignored. Images are ignored unless they have alt-text, in which case the alt-text is pasted in the position the image would be if shown.
+
+Templates added in the current editing session can be copied and pasted as expected.
+
+Possibly this is a result of the fix to bug 49396?
+
+To reproduce:
+1. Load any page with 1 or more templates or images, e.g. https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=573844495
+
+2. select and copy a template or image
+3. Paste the somewhere else in the page.
+
+Expected behaviour: the full template or image is pasted
+Actual behaviour (templates): Only text output of the template is pasted, unformatted and unlinked.
+Actual behaviour (images): Only the image caption is pasted, unformatted and unlinked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49396",task_description,"['VisualEditor: [Regression] Copy/paste of existing templates and images broken (unformatted text pasted only)\n\nCopy/pasting a template that existed prior to the current session only pastes, as literal text, the unformatted text output of the template.', 'Template boxes, etc are ignored.', 'Images are ignored unless they have alt-text, in which case the alt-text is pasted in the position the image would be if shown.', 'Templates added in the current editing session can be copied and pasted as expected.', 'Possibly this is a result of the fix to bug 49396?', 'To reproduce:\n1.', 'Load any page with 1 or more templates or images, e.g.', 'URL\n\n2. select and copy a template or image\n3.', 'Paste the somewhere else in the page.', 'Expected behaviour: the full template or image is pasted\nActual behaviour (templates): Only text output of the template is pasted, unformatted and unlinked.', 'Actual behaviour (images): Only the image caption is pasted, unformatted and unlinked.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252365,VisualEditor: [Regression] Copy/paste of existing templates and images broken (unformatted text pasted only),This was fixed some time ago; sorry for the slow update.,task_subcomment,['This was fixed some time ago; sorry for the slow update.'],['ACTION ON ISSUE']
+56406,Parsoid jobs are not dequeued fast enough during heavy editing activity,"Parsoid is flooding the global job queue.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**Whiteboard**: [see comment 9]",task_description,"['Parsoid jobs are not dequeued fast enough during heavy editing activity\n\nParsoid is flooding the global job queue.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal\n**Whiteboard**: [see comment 9]']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+252161,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to James Forrester from comment #36)
+> Can we close this bug now? I believe this has been fixed.
+
+No feedback => Closing.",task_subcomment,['(In reply to James Forrester from comment #36)\nQUOTE\n\nNo feedback => Closing.'],['ACTION ON ISSUE']
+252157,Parsoid jobs are not dequeued fast enough during heavy editing activity,Can we close this bug now? I believe this has been fixed.,task_subcomment,"['Can we close this bug now?', 'I believe this has been fixed.']","['ACTION ON ISSUE', 'BUG REPRODUCTION']"
+252153,Parsoid jobs are not dequeued fast enough during heavy editing activity,"Change 86745 merged by Faidon Liambotis:
+Bug 54406: Speed up Parsoid job processing
+
+https://gerrit.wikimedia.org/r/86745",task_subcomment,['Change 86745 merged by Faidon Liambotis:\nBug 54406: Speed up Parsoid job processing\n\nGERRIT_URL'],['BUG REPRODUCTION']
+252150,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #30)
+> @MZMcBride: I think both the broader technical and the social issue have been
+> discussed sufficiently now. From now on I am not going to discuss anything
+> but the Parsoid job queue length in this bug.
+
+I was repeatedly called out (by you and others) on this bug for causing the increased job queue length when there's no evidence this was the case.
+
+(In reply to comment #32)
+> (I'm removing myself from cc as we don't even manage to get a fact-based
+> summary.)
+
+I wish I could remove myself, but Bugzilla doesn't allow the reporter to be changed. :-(",task_subcomment,"[""(In reply to comment #30)\nQUOTE\nQUOTE\nQUOTE\n\nI was repeatedly called out (by you and others) on this bug for causing the increased job queue length when there's no evidence this was the case."", ""(In reply to comment #32)\nQUOTE\nQUOTE\n\nI wish I could remove myself, but Bugzilla doesn't allow the reporter to be changed."", ':-(']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+252146,Parsoid jobs are not dequeued fast enough during heavy editing activity,"Change 86745 had a related patch set uploaded by GWicke:
+Bug 54406: Speed up Parsoid job processing
+
+https://gerrit.wikimedia.org/r/86745",task_subcomment,['Change 86745 had a related patch set uploaded by GWicke:\nBug 54406: Speed up Parsoid job processing\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+252143,Parsoid jobs are not dequeued fast enough during heavy editing activity,(I'm removing myself from cc as we don't even manage to get a fact-based summary.),task_subcomment,"[""(I'm removing myself from cc as we don't even manage to get a fact-based summary.)""]",['SOCIAL CONVERSATION']
+252140,Parsoid jobs are not dequeued fast enough during heavy editing activity,PS: There is no such thing as a global job queue. There are several independent queues which are stored on the same infrastructure and graphed as an aggregate.,task_subcomment,"['PS: There is no such thing as a global job queue.', 'There are several independent queues which are stored on the same infrastructure and graphed as an aggregate.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252136,Parsoid jobs are not dequeued fast enough during heavy editing activity,@MZMcBride: I think both the broader technical and the social issue have been discussed sufficiently now. From now on I am not going to discuss anything but the Parsoid job queue length in this bug. Please discuss other aspects elsewhere.,task_subcomment,"['SCREEN_NAME: I think both the broader technical and the social issue have been discussed sufficiently now.', 'From now on I am not going to discuss anything but the Parsoid job queue length in this bug.', 'Please discuss other aspects elsewhere.']","['FUTURE PLAN', 'FUTURE PLAN', 'ACTION ON ISSUE']"
+252132,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #3)
+> The main issue seems to be MZMcBride's null editing at a rate way beyond even
+> bot edit limits.
+
+It's difficult to look at these claims as being anything other than spurious. Attachment 13412 shows a continued increase in the global job queue (now exceeding 3.78 million jobs).
+
+I'm restoring the original bug summary, which was most accurate: Parsoid is flooding the global job queue. Nobody seems to be particularly concerned with this, however, so it may make sense to mark this bug as resolved/worksforme.",task_subcomment,"[""(In reply to comment #3)\nQUOTE\nQUOTE\n\nIt's difficult to look at these claims as being anything other than spurious."", 'Attachment 13412 shows a continued increase in the global job queue (now exceeding 3.78 million jobs).', ""I'm restoring the original bug summary, which was most accurate: Parsoid is flooding the global job queue."", 'Nobody seems to be particularly concerned with this, however, so it may make sense to mark this bug as resolved/worksforme.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+252125,Parsoid jobs are not dequeued fast enough during heavy editing activity,"Created attachment 13412
+Screenshot to accompany comment 3
+
+**Attached**: {F11775}",task_subcomment,['Created attachment 13412\nScreenshot to accompany comment 3\n\n**Attached**: {F11775}'],['ATTACHMENT']
+252118,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #23)
+> Just curious - is there anything actionable that can possibly come out of
+> this bug?
+
+This bug was filed under the assumption that job queues shouldn't contain millions of jobs.
+
+Gabriel seems to suggest throughout this bug report that the global job queue size is irrelevant (or rather, that he's apparently unconcerned with its size), so I'm not sure there is anything actionable here. This may be a wontfix.
+
+(In reply to comment #21)
+> For templates there is no way around the load this creates when they really
+> need to be edited. I have a hard time seeing a similarly good reason for
+> making 8 million null edits at a rate of ~4/second.
+
+There are a lot of pages to edit. If we edited one page per minute and edited 31,000,000 pages, that would take approximately 58.9 years. Obviously we're going to have to go a bit faster than that.
+
+Many pages have not been re-parsed or purged from cache in years (since 2005 for the oldest pages). This results in outdated or incorrect *links entries, stale HTML cache, etc., in addition to a number of lurking page text anomalies (incorrectly unsubstituted templates, incorrectly unexpanded user signatures, etc.). Null editing is built in to MediaWiki to address these issues on a per-page basis. You've yet to identify any issue with using this built-in feature.
+
+Other than a global job queue that's already flooded, were there any issues from null editing that you (Gabriel) or anyone else has found? If so, I'd like to learn more so that I can understand and grow as a contributor.",task_subcomment,"[""(In reply to comment #23)\nQUOTE\nQUOTE\n\nThis bug was filed under the assumption that job queues shouldn't contain millions of jobs."", ""Gabriel seems to suggest throughout this bug report that the global job queue size is irrelevant (or rather, that he's apparently unconcerned with its size), so I'm not sure there is anything actionable here."", 'This may be a wontfix.', '(In reply to comment #21)\nQUOTE\nQUOTE\nQUOTE\n\nThere are a lot of pages to edit.', 'If we edited one page per minute and edited 31,000,000 pages, that would take approximately 58.9 years.', ""Obviously we're going to have to go a bit faster than that."", 'Many pages have not been re-parsed or purged from cache in years (since 2005 for the oldest pages).', 'This results in outdated or incorrect *links entries, stale HTML cache, etc., in addition to a number of lurking page text anomalies (incorrectly unsubstituted templates, incorrectly unexpanded user signatures, etc.).', 'Null editing is built in to MediaWiki to address these issues on a per-page basis.', ""You've yet to identify any issue with using this built-in feature."", ""Other than a global job queue that's already flooded, were there any issues from null editing that you (Gabriel) or anyone else has found?"", ""If so, I'd like to learn more so that I can understand and grow as a contributor.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'CONTRIBUTION AND COMMITMENT']"
+252112,Parsoid jobs are not dequeued fast enough during heavy editing activity,"@Yuvi: For the technical part, see comment #9. The social / DoS prevention issue is probably better discussed elsewhere.",task_subcomment,"['SCREEN_NAME: For the technical part, see comment #9.', 'The social / DoS prevention issue is probably better discussed elsewhere.']","['SOLUTION DISCUSSION', 'ISSUE CONTENT MANAGEMENT']"
+252107,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #24)
+> Yes! I'm hoping for a definition of ""what is the problem"" to actually come
+> out
+> of it. It may take a hundred more comments though, given the current speed
+> we're approaching it at.
+
+May I suggest using something that's not bugzilla for that purpose? I understand the need for clarity, but honestly a bugzilla ticket is probably not the best way to do it. A mailing list post, perhaps?",task_subcomment,"[""(In reply to comment #24)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nMay I suggest using something that's not bugzilla for that purpose?"", 'I understand the need for clarity, but honestly a bugzilla ticket is probably not the best way to do it.', 'A mailing list post, perhaps?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252100,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #23)
+> Just curious - is there anything actionable that can possibly come out of
+> this
+> bug?
+
+Yes! I'm hoping for a definition of ""what is the problem"" to actually come out of it. It may take a hundred more comments though, given the current speed we're approaching it at.",task_subcomment,"['(In reply to comment #23)\nQUOTE\nQUOTE\nQUOTE\n\nYes!', 'I\'m hoping for a definition of ""what is the problem"" to actually come out of it.', ""It may take a hundred more comments though, given the current speed we're approaching it at.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+252093,Parsoid jobs are not dequeued fast enough during heavy editing activity,Just curious - is there anything actionable that can possibly come out of this bug?,task_subcomment,['Just curious - is there anything actionable that can possibly come out of this bug?'],['SOLUTION DISCUSSION']
+252088,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #21)
+> Popular templates are protected for a reason, and editors don't edit them
+> needlessly, as they know about the high load this causes. 
+> 
+> For templates there is no way around the load this creates when they really
+> need to be edited. 
+
+Ok, so people avoid things which cause overload but still in July we had about 2M additional job queue items. And it seems that's fine. What's not fine then, what is this bug about? Can we please identify the problem and the source of it? Otherwise I don't see how one can identify solutions.
+
+> I have a hard time seeing a similarly good reason for
+> making
+> 8 million null edits at a rate of ~4/second. 
+
+I'm having a hard time too. They are just speculations without answers to what above.
+
+> Especially without talking to
+> the
+> people responsible for keeping the site running 
+
+(This makes sense.)
+
+> and in contravention of the
+> bot
+> policy.
+
+Sigh. There isn't any contravention of the bot policy. The relevant local page is [[Wikipedia:Don't worry about performance]].
+Hint: the policies or pseudo-policies you are looking for are on wikitech, e.g. [[wikitech:Robot policy]]. I don't remember which one precisely but there is one written by Tim which explicitly says ""if you're causing problems/bringing the site down we'll block you"", period.
+In this case however, I still don't see what the problem is. Again, why is 2M not a problem but 3M yes?",task_subcomment,"['(In reply to comment #21)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOk, so people avoid things which cause overload but still in July we had about 2M additional job queue items.', ""And it seems that's fine."", ""What's not fine then, what is this bug about?"", 'Can we please identify the problem and the source of it?', ""Otherwise I don't see how one can identify solutions."", ""QUOTE\nQUOTE\nQUOTE\n\nI'm having a hard time too."", 'They are just speculations without answers to what above.', 'QUOTE\nQUOTE\nQUOTE\n\n(This makes sense.)', 'QUOTE\nQUOTE\nQUOTE\n\nSigh.', ""There isn't any contravention of the bot policy."", ""The relevant local page is [[Wikipedia:Don't worry about performance]]."", 'Hint: the policies or pseudo-policies you are looking for are on wikitech, e.g.', '[[wikitech:Robot policy]].', 'I don\'t remember which one precisely but there is one written by Tim which explicitly says ""if you\'re causing problems/bringing the site down we\'ll block you"", period.', ""In this case however, I still don't see what the problem is."", 'Again, why is 2M not a problem but 3M yes?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOCIAL CONVERSATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252082,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #20)
+> Can you then explain why ""the
+> second million was too much"", i.e. why reaching 2M job queue is in your
+> opinion
+> all fine and normal while 3 is something absolutely horrible and criminal?
+> Thanks.
+
+Popular templates are protected for a reason, and editors don't edit them needlessly, as they know about the high load this causes. 
+
+For templates there is no way around the load this creates when they really need to be edited. I have a hard time seeing a similarly good reason for making 8 million null edits at a rate of ~4/second. Especially without talking to the people responsible for keeping the site running and in contravention of the bot policy.",task_subcomment,"[""(In reply to comment #20)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nPopular templates are protected for a reason, and editors don't edit them needlessly, as they know about the high load this causes."", 'For templates there is no way around the load this creates when they really need to be edited.', 'I have a hard time seeing a similarly good reason for making 8 million null edits at a rate of ~4/second.', 'Especially without talking to the people responsible for keeping the site running and in contravention of the bot policy.']","['SOLUTION USAGE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252075,Parsoid jobs are not dequeued fast enough during heavy editing activity,"I'm not sure how familiar you are with the actual writing and enacting of those social rules, but surely here nothing was done against them. The social rules in the various variations of the global [[m:Bot policy]] are not about performance; the speed limit is typically driven by users not wanting their Special:RecentChanges and Special:WatchList to be flooded, which in this case obviously didn't happen (so let's not even start debating what's an ""edit"").
+
+Besides, I don't really have an answer yet to my question, though we're getting nearer; probably it would be faster if we avoided off-topic discussions on alleged abuse and similar stuff.
+
+(In reply to comment #19)
+> (In reply to comment #15)
+> > I still see no answer about what the spike on July 29 was: are you saying it
+> > wasn't about parsoid, but just a coincidence? Or that it was normal to queue
+> > over a million jobs in a couple of days (initial caching of all pages or
+> > something?) but the second million was too much?
+> 
+> Just editing a handful really popular templates (some are used in >7 million
+> articles) can enqueue a lot of jobs (10 titles per job, so ~700k jobs). As
+> can
+> editing content at high rates. Core happens to cap the number of titles to
+> re-render at 200k, while Parsoid re-renders all, albeit with a delay.
+
+Thanks, so I guess the answer is the second. Can you then explain why ""the second million was too much"", i.e. why reaching 2M job queue is in your opinion all fine and normal while 3 is something absolutely horrible and criminal? Thanks.",task_subcomment,"[""I'm not sure how familiar you are with the actual writing and enacting of those social rules, but surely here nothing was done against them."", 'The social rules in the various variations of the global [[m:Bot policy]] are not about performance; the speed limit is typically driven by users not wanting their Special:RecentChanges and Special:WatchList to be flooded, which in this case obviously didn\'t happen (so let\'s not even start debating what\'s an ""edit"").', ""Besides, I don't really have an answer yet to my question, though we're getting nearer; probably it would be faster if we avoided off-topic discussions on alleged abuse and similar stuff."", '(In reply to comment #19)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThanks, so I guess the answer is the second.', 'Can you then explain why ""the second million was too much"", i.e.', 'why reaching 2M job queue is in your opinion all fine and normal while 3 is something absolutely horrible and criminal?', 'Thanks.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOCIAL CONVERSATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+252069,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #15)
+> I still see no answer about what the spike on July 29 was: are you saying it
+> wasn't about parsoid, but just a coincidence? Or that it was normal to queue
+> over a million jobs in a couple of days (initial caching of all pages or
+> something?) but the second million was too much?
+
+Just editing a handful really popular templates (some are used in >7 million articles) can enqueue a lot of jobs (10 titles per job, so ~700k jobs). As can editing content at high rates. Core happens to cap the number of titles to re-render at 200k, while Parsoid re-renders all, albeit with a delay.
+
+Ideally we'd prioritize direct edits over template updates as only the former has any performance impact. Editing a page with slightly out-of-date template rendering will still yield correct results. Longer-term our goal is to reduce API requests further so that we can run the Parsoid cluster at capacity without taking out the API.
+
+And yes, I was referring to very straightforward social rules that are designed to prevent our users from overloading the site with expensive operations. We currently provide powerful API access that can easily be abused. If the attitude that everything that is not technically blocked must surely be ok becomes more popular we'll have to neuter those APIs significantly. Maybe it is actually time to technically enforce social rules more strictly, for example by automatically blocking abusers.",task_subcomment,"['(In reply to comment #15)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nJust editing a handful really popular templates (some are used in >7 million articles) can enqueue a lot of jobs (10 titles per job, so ~700k jobs).', 'As can editing content at high rates.', 'Core happens to cap the number of titles to re-render at 200k, while Parsoid re-renders all, albeit with a delay.', ""Ideally we'd prioritize direct edits over template updates as only the former has any performance impact."", 'Editing a page with slightly out-of-date template rendering will still yield correct results.', 'Longer-term our goal is to reduce API requests further so that we can run the Parsoid cluster at capacity without taking out the API.', 'And yes, I was referring to very straightforward social rules that are designed to prevent our users from overloading the site with expensive operations.', 'We currently provide powerful API access that can easily be abused.', ""If the attitude that everything that is not technically blocked must surely be ok becomes more popular we'll have to neuter those APIs significantly."", 'Maybe it is actually time to technically enforce social rules more strictly, for example by automatically blocking abusers.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+252065,Parsoid jobs are not dequeued fast enough during heavy editing activity,"No user in the ""bot"" user group was used to null edit. Just a standard and unprivileged (albeit autoconfirmed) account.
+
+On Wikimedia wikis, 'edit' is rate-limited only for 'ip' and 'newbie', but not for 'user' or 'bot' or any other group, as far as I can tell.",task_subcomment,"['No user in the ""bot"" user group was used to null edit.', 'Just a standard and unprivileged (albeit autoconfirmed) account.', ""On Wikimedia wikis, 'edit' is rate-limited only for 'ip' and 'newbie', but not for 'user' or 'bot' or any other group, as far as I can tell.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+252059,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #16)
+> (In reply to comment #14)
+> > Bots are explicitly not rate-limited.
+> 
+> https://en.wikipedia.org/wiki/Wikipedia:Bot_policy#Bot_requirements states
+> that
+> ""bots doing non-urgent tasks may edit approximately once every ten seconds"". 
+> Am I missing something?
+
+That requirement is imposed by the community, it is not necessarily a technical limit. If you look at https://en.wikipedia.org/wiki/Special:ListGroupRights, the 'bot' group is deliberately exempted from rate limits with the 'noratelimit' userright.",task_subcomment,"['(In reply to comment #16)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat requirement is imposed by the community, it is not necessarily a technical limit.', ""If you look at URL the 'bot' group is deliberately exempted from rate limits with the 'noratelimit' userright.""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+252051,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #14)
+> Bots are explicitly not rate-limited.
+
+https://en.wikipedia.org/wiki/Wikipedia:Bot_policy#Bot_requirements states that ""bots doing non-urgent tasks may edit approximately once every ten seconds"". 
+Am I missing something?",task_subcomment,"['(In reply to comment #14)\nQUOTE\n\nURL states that ""bots doing non-urgent tasks may edit approximately once every ten seconds"".', 'Am I missing something?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+252044,Parsoid jobs are not dequeued fast enough during heavy editing activity,"I still see no answer about what the spike on July 29 was: are you saying it wasn't about parsoid, but just a coincidence? Or that it was normal to queue over a million jobs in a couple of days (initial caching of all pages or something?) but the second million was too much?
+
+The new summary seems incorrect in two ways:
+1) ""fast enough"" might be incorrect, you say that it's not important if it's slow,
+2) ""during heavy bot activity"" is a possibly incorrect guess.
+What's sure is that we no longer seem to have any meaningful job queue data.",task_subcomment,"[""I still see no answer about what the spike on July 29 was: are you saying it wasn't about parsoid, but just a coincidence?"", 'Or that it was normal to queue over a million jobs in a couple of days (initial caching of all pages or something?)', 'but the second million was too much?', 'The new summary seems incorrect in two ways:\n1) ""fast enough"" might be incorrect, you say that it\'s not important if it\'s slow,\n2) ""during heavy bot activity"" is a possibly incorrect guess.', ""What's sure is that we no longer seem to have any meaningful job queue data.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252037,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #13)
+> Still, to avoid any misunderstandings: Null editing at rates way higher than
+> those allowed for bots is at best a very bad idea.
+
+Bots are explicitly not rate-limited.",task_subcomment,['(In reply to comment #13)\nQUOTE\nQUOTE\n\nBots are explicitly not rate-limited.'],['SOLUTION DISCUSSION']
+252030,Parsoid jobs are not dequeued fast enough during heavy editing activity,"Changed the subject to be more accurate. Some more clarification for those less familiar with the way Parsoid caching works:
+
+* Timely Parsoid cache refreshes are not needed for correctness. Delayed updates can result in a higher percentage of cache misses than usual, but will not result in incorrect edits.
+
+* Parsoid uses its own queue, so a backlog does not affect any other job queue.
+
+So in the bigger picture this is annoying, but not critical.
+
+Still, to avoid any misunderstandings: Null editing at rates way higher than those allowed for bots is at best a very bad idea.",task_subcomment,"['Changed the subject to be more accurate.', 'Some more clarification for those less familiar with the way Parsoid caching works:\n\n* Timely Parsoid cache refreshes are not needed for correctness.', 'Delayed updates can result in a higher percentage of cache misses than usual, but will not result in incorrect edits.', '* Parsoid uses its own queue, so a backlog does not affect any other job queue.', 'So in the bigger picture this is annoying, but not critical.', 'Still, to avoid any misunderstandings: Null editing at rates way higher than those allowed for bots is at best a very bad idea.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+252023,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #10)
+> (In reply to comment #9)
+> > Since
+> > that stopped yesterday, the enwiki Parsoid job queue has drained by 10% (200k
+> > jobs).
+> 
+> Did the other jobs increase then? 
+
+Jobs in other job queues (I see 26k refreshlinks2 jobs on enwiki for example), and/or Parsoid jobs on other wikis have likely slightly increased in number. Overall the queue size has slightly decreased since the null-editing was stopped.",task_subcomment,"['(In reply to comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nJobs in other job queues (I see 26k refreshlinks2 jobs on enwiki for example), and/or Parsoid jobs on other wikis have likely slightly increased in number.', 'Overall the queue size has slightly decreased since the null-editing was stopped.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252017,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #9)
+> It seems that the Parsoid dequeue rate was slightly lower than the average
+> enqueue rate since the end of July, which allowed the job backlog to build
+> up a bit.
+
+A bit? Looking at https://ganglia.wikimedia.org/latest/graph_all_periods.php?c=Miscellaneous%20pmtpa&h=hume.wikimedia.org&v=823574&m=Global_JobQueue_length&r=hour&z=default&jr=&js=&st=1365625056&z=large it seems like the queue went from 355,850 to 1,590,000 in the span of about six days (from July 29 to August 3). It grew by... 346%? That's what you're calling ""a bit""?",task_subcomment,"['(In reply to comment #9)\nQUOTE\nQUOTE\nQUOTE\n\nA bit?', 'Looking at URL it seems like the queue went from 355,850 to 1,590,000 in the span of about six days (from July 29 to August 3).', 'It grew by... 346%?', 'That\'s what you\'re calling ""a bit""?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252009,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #9)
+> Since
+> that stopped yesterday, the enwiki Parsoid job queue has drained by 10% (200k
+> jobs).
+
+Did the other jobs increase then? The total job queue was 3.01M and is now 2.94M (it generally goes down in European nights and so).",task_subcomment,"['(In reply to comment #9)\nQUOTE\nQUOTE\nQUOTE\n\nDid the other jobs increase then?', 'The total job queue was 3.01M and is now 2.94M (it generally goes down in European nights and so).']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252002,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #6)
+> (In reply to comment #3)
+> > We dequeue Parsoid jobs in a throttled manner to avoid overloading the API
+> > during edit spikes. This means that abnormal edit rates especially to
+> > templates can create a large backlog of jobs in the Parsoid queue.
+> 
+> Where does Parsoid fit in to the general MediaWiki ecosystem? Are Parsoid
+> jobs
+> generated on every edit? If so, why? 
+
+After an edit, the Parsoid HTML for each affected article is generated / updated with jobs that perform HTTP requests to the Parsoid cluster. This ensures that requests from VisualEditor and other users are normally served straight from cache. We have been processing all edits from all Wikipedias since June. As expected, VE deployments have not made a noticeable difference to the load on the Parsoid cluster.
+
+It seems that the Parsoid dequeue rate was slightly lower than the average enqueue rate since the end of July, which allowed the job backlog to build up a bit. During MZMcBride's null edit episode the backlog doubled in size. Since that stopped yesterday, the enwiki Parsoid job queue has drained by 10% (200k jobs).
+
+So overall, the Parsoid job dequeue rate is slightly too low to absorb abnormal edit rates in a timely manner. It might be sufficient to slightly de-throttle the Parsoid dequeue rate while keeping an eye on the API cluster load (https://ganglia.wikimedia.org/latest/?r=hour&cs=&ce=&m=cpu_report&s=by+name&c=API+application+servers+eqiad&h=&host_regex=&max_graphs=0&tab=m&vn=&sh=1&z=small&hc=4).",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAfter an edit, the Parsoid HTML for each affected article is generated / updated with jobs that perform HTTP requests to the Parsoid cluster.', 'This ensures that requests from VisualEditor and other users are normally served straight from cache.', 'We have been processing all edits from all Wikipedias since June.', 'As expected, VE deployments have not made a noticeable difference to the load on the Parsoid cluster.', 'It seems that the Parsoid dequeue rate was slightly lower than the average enqueue rate since the end of July, which allowed the job backlog to build up a bit.', ""During MZMcBride's null edit episode the backlog doubled in size."", 'Since that stopped yesterday, the enwiki Parsoid job queue has drained by 10% (200k jobs).', 'So overall, the Parsoid job dequeue rate is slightly too low to absorb abnormal edit rates in a timely manner.', 'It might be sufficient to slightly de-throttle the Parsoid dequeue rate while keeping an eye on the API cluster load (URL']","['MOTIVATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+251997,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #7)
+> Created attachment 13342 [details]
+> Screenshot to accompany comment 2
+
+The spike around July 29 is easy to see and most likely corresponds with the deployment mentioned in comment 2. There are also spikes around August 14 and September 8, neither of which have been accounted for yet.
+
+**Attached**: {F11772}",task_subcomment,"['(In reply to comment #7)\nQUOTE\nQUOTE\n\nThe spike around July 29 is easy to see and most likely corresponds with the deployment mentioned in comment 2.', 'There are also spikes around August 14 and September 8, neither of which have been accounted for yet.', '**Attached**: {F11772}']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251992,Parsoid jobs are not dequeued fast enough during heavy editing activity,"Created attachment 13342
+Screenshot to accompany comment 2
+
+**Attached**: {F11772}",task_subcomment,['Created attachment 13342\nScreenshot to accompany comment 2\n\n**Attached**: {F11772}'],['ATTACHMENT']
+251986,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #3)
+> We dequeue Parsoid jobs in a throttled manner to avoid overloading the API
+> during edit spikes. This means that abnormal edit rates especially to
+> templates can create a large backlog of jobs in the Parsoid queue.
+
+Where does Parsoid fit in to the general MediaWiki ecosystem? Are Parsoid jobs generated on every edit? If so, why? My understanding is that Parsoid is related to VisualEditor, so I have difficultly understanding how millions of Parsoid jobs would be queued unless they were all related to VisualEditor usage.
+
+> The main issue seems to be MZMcBride's null editing at a rate way beyond even
+> bot edit limits.
+
+What's a bot edit limit?
+
+> Do we have a product for DoS attack detection and -mitigation?
+
+DoS attack? I think it makes sense for all of us to focus on why and how Parsoid is flooding the global job queue. Suggesting anyone was performing a denial-of-service attack is both inappropriate and unhelpful. There are a number of anti-abuse measures built in to MediaWiki, to answer your question generally.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nWhere does Parsoid fit in to the general MediaWiki ecosystem?', 'Are Parsoid jobs generated on every edit?', 'If so, why?', 'My understanding is that Parsoid is related to VisualEditor, so I have difficultly understanding how millions of Parsoid jobs would be queued unless they were all related to VisualEditor usage.', ""QUOTE\nQUOTE\n\nWhat's a bot edit limit?"", 'QUOTE\n\nDoS attack?', 'I think it makes sense for all of us to focus on why and how Parsoid is flooding the global job queue.', 'Suggesting anyone was performing a denial-of-service attack is both inappropriate and unhelpful.', 'There are a number of anti-abuse measures built in to MediaWiki, to answer your question generally.']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+251982,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #2)
+> For the record, my null editing respected maxlag. It also started August 28
+> and
+> ended September 20.
+
+maxlag has actually little relevance as a metric on the task you were doing...",task_subcomment,['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nmaxlag has actually little relevance as a metric on the task you were doing...'],['INVESTIGATION AND EXPLORATION']
+251976,Parsoid jobs are not dequeued fast enough during heavy editing activity,"(In reply to comment #3)
+> The main issue seems to be MZMcBride's null editing at a rate way beyond even
+> bot edit limits.
+
+Can you please clarify how, in your opinion, the null editing retroactively caused a spike a month before its beginning? Thanks.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\n\nCan you please clarify how, in your opinion, the null editing retroactively caused a spike a month before its beginning?', 'Thanks.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+251971,Parsoid jobs are not dequeued fast enough during heavy editing activity,"We dequeue Parsoid jobs in a throttled manner to avoid overloading the API during edit spikes. This means that abnormal edit rates especially to templates can create a large backlog of jobs in the Parsoid queue. This is then slowly processed over time. Since this is a separate queue this won't hold up other job queues.
+
+The main issue seems to be MZMcBride's null editing at a rate way beyond even bot edit limits. Do we have a product for DoS attack detection and -mitigation?",task_subcomment,"['We dequeue Parsoid jobs in a throttled manner to avoid overloading the API during edit spikes.', 'This means that abnormal edit rates especially to templates can create a large backlog of jobs in the Parsoid queue.', 'This is then slowly processed over time.', ""Since this is a separate queue this won't hold up other job queues."", ""The main issue seems to be MZMcBride's null editing at a rate way beyond even bot edit limits."", 'Do we have a product for DoS attack detection and -mitigation?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'POTENTIAL NEW ISSUES AND REQUESTS']"
+251966,Parsoid jobs are not dequeued fast enough during heavy editing activity,"For the record, my null editing respected maxlag. It also started August 28 and ended September 20.
+
+The graph goes wild around July 29, which seems to correspond tightly with ""16:44 logmsgbot: catrope synchronized wmf-config/InitialiseSettings.php 'Enable VE for anons on es/fr/he/it/pl/ru/svwiki; set dewiki back to opt-in mode'"".",task_subcomment,"['For the record, my null editing respected maxlag.', 'It also started August 28 and ended September 20.', 'The graph goes wild around July 29, which seems to correspond tightly with ""16:44 logmsgbot: catrope synchronized wmf-config/InitialiseSettings.php \'Enable VE for anons on es/fr/he/it/pl/ru/svwiki; set dewiki back to opt-in mode\'"".']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+251960,Parsoid jobs are not dequeued fast enough during heavy editing activity,"https://ganglia.wikimedia.org/latest/graph_all_periods.php?c=Miscellaneous%20pmtpa&h=hume.wikimedia.org&v=823574&m=Global_JobQueue_length&r=hour&z=default&jr=&js=&st=1365625056&z=large
+
+06.11 < TimStarling> mostly parsoid
+06.11 < TimStarling> ParsoidCacheUpdateJob: 2413680 queued; 611 claimed (12 active, 599 abandoned)",task_subcomment,"['URL\n\n06.11 < TimStarling> mostly parsoid\n06.11 < TimStarling> ParsoidCacheUpdateJob: 2413680 queued; 611 claimed (12 active, 599 abandoned)']",['OBSERVED BUG BEHAVIOR']
+56379,"VisualEditor: Right half of toolbar disappears when 
     or 
     appears in image on first line of page","When a page has an image on the first line and the image caption contains a 
     tag or a 
     tag (where ... is ""left"", ""right"" or ""center"">, the right half of the VE toolbar (Beta, Page settings, Cancel and Save) are not visible. Obviously this means you cannot save any edits.
+
+Curiously, 
     does not exhibit this problem.
+
+Example from an article: https://en.wikipedia.org/w/index.php?title=Little_Tich&oldid=573770305
+
+Minimal test case: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=573786703
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54642",task_description,"['VisualEditor: Right half of toolbar disappears when 
     or 
     appears in image on first line of page\n\nWhen a page has an image on the first line and the image caption contains a 
     tag or a 
     tag (where ... is ""left"", ""right"" or ""center"">, the right half of the VE toolbar (Beta, Page settings, Cancel and Save) are not visible.', 'Obviously this means you cannot save any edits.', 'Curiously, 
     does not exhibit this problem.', 'Example from an article: URL\n\nMinimal test case: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250281,"VisualEditor: Right half of toolbar disappears when 
     or 
     appears in image on first line of page","This was fixed some time ago, I believe; sorry for the very slow triage.",task_subcomment,"['This was fixed some time ago, I believe; sorry for the very slow triage.']",['OBSERVED BUG BEHAVIOR']
+56377,VisualEditor: Paste validation fails for images in FF,"Because firefox converts path attributes to absolute URLs, the hashes don't match up, so VE pastes the plain-text equivalent content (empty string).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Paste validation fails for images in FF\n\nBecause firefox converts path attributes to absolute URLs, the hashes don't match up, so VE pastes the plain-text equivalent content (empty string)."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250158,VisualEditor: Paste validation fails for images in FF,"Change 85213 merged by jenkins-bot:
+Ignore all node attributes in clipboard hash
+
+https://gerrit.wikimedia.org/r/85213",task_subcomment,['Change 85213 merged by jenkins-bot:\nIgnore all node attributes in clipboard hash\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250153,VisualEditor: Paste validation fails for images in FF,"Change 85213 had a related patch set uploaded by Esanders:
+Clipboard hash should ignore all node attributes
+
+https://gerrit.wikimedia.org/r/85213",task_subcomment,['Change 85213 had a related patch set uploaded by Esanders:\nClipboard hash should ignore all node attributes\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+56335,VisualEditor: Surface isn't updated properly for Language annotations,"This is extremely weird, and is relatively new, and I am at a loss.
+
+Steps to reproduce:
+1. Put cursor on some word in the article.
+2. Select ""More -> Language"" in the toolbar
+3. Click ""Change Language"" button in the widget
+4. Choose any other language (for example, ""Hebrew"")
+5. Close the inspector by clicking anywhere else.
+6. Notice: The word is surrounded with a language span, but it has the initial en/ltr values instead of the chosen annotation.
+7. Save the article.
+8. Click on ""Edit Source"" --> the language span contains the *correct* annotation (he/rtl)
+
+Expansion on that:
+1. Repeat the above through step 6.
+2. Select a separate word and annotate it with some random link.
+3. Inspect the original language span -- *now* it's updated!
+
+One more weirdness:
+1. Repeat above through step 6.
+2. Put the cursor back on that annotation, and open the inspector
+3. Observe: While the surface shows the span as en/ltr, the inspector widget shows the correct annotation (hebrew/rtl)
+
+This happens in master and in the live mediawiki.org version.
+
+
+
+I've spent a while tracking what is wrong with the annotations, and they seem to be correct in the inspector itself. In the ""onClose"", the annotation is the correct he/rtl one, being then sent to AnnotationInspector onClose, and then to the SurfaceFragment for execution in the fragment.annotateContent( 'set', annotation )
+
+That annotation (the final one that's sent to the fragment) is the *correct* annotation. And yet, somewhere along the way the update stops. 
+
+I tried stepping into the code inside ve.ce.Surface onChange and the annotation remains the correct one. It then continues to ve.dm.Surface 'change' method where the annotation is still the correct one (he/rtl) 
+
+And yet somewhere it doesn't update the surface.
+
+Link Inspector seems to work properly, though, and both link and language inspector rely on AnnotationInspector, which makes me think there is an issue with Language specifically, or that perhaps something has changed with the definition that needs to be updated in the Language inspector.
+
+I'm not sure if the problem is in the Language Inspector (though that seems a bit odd, since the annotation remains correct throughout) or somewhere in the process of updating (and that seems weird too since *links* are working fine).
+
+I'm at a loss. Help is appreciated!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Surface isn't updated properly for Language annotations\n\nThis is extremely weird, and is relatively new, and I am at a loss."", 'Steps to reproduce:\n1.', 'Put cursor on some word in the article.', '2.', 'Select ""More -> Language"" in the toolbar\n3.', 'Click ""Change Language"" button in the widget\n4.', 'Choose any other language (for example, ""Hebrew"")\n5.', 'Close the inspector by clicking anywhere else.', '6.', 'Notice: The word is surrounded with a language span, but it has the initial en/ltr values instead of the chosen annotation.', '7.', 'Save the article.', '8.', 'Click on ""Edit Source"" --> the language span contains the *correct* annotation (he/rtl)\n\nExpansion on that:\n1.', 'Repeat the above through step 6.', '2.', 'Select a separate word and annotate it with some random link.', '3.', ""Inspect the original language span -- *now* it's updated!"", 'One more weirdness:\n1.', 'Repeat above through step 6.', '2.', 'Put the cursor back on that annotation, and open the inspector\n3.', 'Observe: While the surface shows the span as en/ltr, the inspector widget shows the correct annotation (hebrew/rtl)\n\nThis happens in master and in the live mediawiki.org version.', ""I've spent a while tracking what is wrong with the annotations, and they seem to be correct in the inspector itself."", 'In the ""onClose"", the annotation is the correct he/rtl one, being then sent to AnnotationInspector onClose, and then to the SurfaceFragment for execution in the fragment.annotateContent( \'set\', annotation )\n\nThat annotation (the final one that\'s sent to the fragment) is the *correct* annotation.', 'And yet, somewhere along the way the update stops.', 'I tried stepping into the code inside ve.ce.Surface onChange and the annotation remains the correct one.', ""It then continues to ve.dm.Surface 'change' method where the annotation is still the correct one (he/rtl) \n\nAnd yet somewhere it doesn't update the surface."", 'Link Inspector seems to work properly, though, and both link and language inspector rely on AnnotationInspector, which makes me think there is an issue with Language specifically, or that perhaps something has changed with the definition that needs to be updated in the Language inspector.', ""I'm not sure if the problem is in the Language Inspector (though that seems a bit odd, since the annotation remains correct throughout) or somewhere in the process of updating (and that seems weird too since *links* are working fine)."", ""I'm at a loss."", 'Help is appreciated!', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+247687,VisualEditor: Surface isn't updated properly for Language annotations,This was fixed in gerrit 90957.,task_subcomment,['This was fixed in gerrit 90957.'],['SOLUTION USAGE']
+247684,VisualEditor: Surface isn't updated properly for Language annotations,"The same also happens with Link annotation on MediaWiki.org and on Master.
+
+Since the dataModel seems to change, and the problem *seems* to be in the ce.Surface not changing, I am in dire need of help. 
+
+Based on advice from Roan, I've repeatedly checked the transaction history, and it shows a correct transaction on both meta/language annotation and link/mwInternal and link/mwExternal as it should, based on the annotation actions.
+
+And yet, while the datamodel seems to be updated, the ce.Surface does not.",task_subcomment,"['The same also happens with Link annotation on MediaWiki.org and on Master.', 'Since the dataModel seems to change, and the problem *seems* to be in the ce.Surface not changing, I am in dire need of help.', ""Based on advice from Roan, I've repeatedly checked the transaction history, and it shows a correct transaction on both meta/language annotation and link/mwInternal and link/mwExternal as it should, based on the annotation actions."", 'And yet, while the datamodel seems to be updated, the ce.Surface does not.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+56332,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"Following on from the reports at bug 51142 comments 5-9 
+
+In every case where the last character of a link is non-alphanumeric and any text is inserted before that character. It seems that the underscore behaves as an alphanumeric character, and that script is irrelevant. It doesn't matter if the link was added in the current editing session or not.
+
+e.g. [[Link|Link.]] → [[Link]]s[[Link|.]]
+but [[Links]] → [[Linkers]] (this is the expected behaviour for all situations)
+
+See https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox3&diff=573654600&oldid=573653290
+
+If due to this a non-alphanumeric character that was previously mid-link but now becomes the last character of the link, adding any character before it triggers the bug again.
+
+See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&diff=573655981&oldid=573654600
+
+In VE it is easy to include trailing punctuation (particularly commas and full stops) in a link without realising it (this is a side-effect of the WYSIWYG), meaning this occurs more often than might be expected (see comments at bug 51142).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51442",task_description,"['VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail\n\nFollowing on from the reports at bug 51142 comments 5-9 \n\nIn every case where the last character of a link is non-alphanumeric and any text is inserted before that character.', 'It seems that the underscore behaves as an alphanumeric character, and that script is irrelevant.', ""It doesn't matter if the link was added in the current editing session or not."", 'e.g.', '[[Link|Link.]]', '→ [[Link]]s[[Link|.]]', 'but [[Links]] → [[Linkers]] (this is the expected behaviour for all situations)\n\nSee URL\n\nIf due to this a non-alphanumeric character that was previously mid-link but now becomes the last character of the link, adding any character before it triggers the bug again.', 'See URL\n\nIn VE it is easy to include trailing punctuation (particularly commas and full stops) in a link without realising it (this is a side-effect of the WYSIWYG), meaning this occurs more often than might be expected (see comments at bug 51142).', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'MOTIVATION', 'BUG REPRODUCTION']"
+247577,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"Change 86235 merged by jenkins-bot:
+Typing into an annotation next to a word break keeps annotation
+
+https://gerrit.wikimedia.org/r/86235",task_subcomment,['Change 86235 merged by jenkins-bot:\nTyping into an annotation next to a word break keeps annotation\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247571,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"btw, the  is inserted by Parsoid to make sure the document we have (Foo/a>ish?) is translated properly into what the PHP parser understands as by default the PHP parser treats "" + adjecent text"" as a shortcut to extend the lable (e.g. [[book]]s becomes books).",task_subcomment,"['btw, the  is inserted by Parsoid to make sure the document we have (Foo/a>ish?) is translated properly into what the PHP parser understands as by default the PHP parser treats "" + adjecent text"" as a shortcut to extend the lable (e.g.', '[[book]]s becomes books).']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+247567,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"Change 86235 had a related patch set uploaded by Esanders:
+Typing into an annotation next to a word break
+
+https://gerrit.wikimedia.org/r/86235",task_subcomment,['Change 86235 had a related patch set uploaded by Esanders:\nTyping into an annotation next to a word break\n\nGERRIT_URL'],['BUG REPRODUCTION']
+247563,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"Yeah, this looks like an off-by-one error in the code for link annotations to not span ""word break"" characters.",task_subcomment,"['Yeah, this looks like an off-by-one error in the code for link annotations to not span ""word break"" characters.']",['OBSERVED BUG BEHAVIOR']
+247558,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"You are right, Chris. I just thought VE could easily recognize cases in which punctuation could just be included by mistake, because the wikilink would be something like [[Fun.]], not [[Fun|Fun.]] .",task_subcomment,"['You are right, Chris.', 'I just thought VE could easily recognize cases in which punctuation could just be included by mistake, because the wikilink would be something like [[Fun.', ']], not [[Fun|Fun.]]', '.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+247556,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"In some cases the non-alphnumeric is desired - [[Fun.]], [[Westward Ho!]] and [[C++]] are cases that spring immediately to mind.
+
+I think it is best that VE does what you ask it to, whether that is what you wanted or not. Anything typed in the middle of a link should be included in that link in all cases, which would make spotting that trailing punctuation is limited easier.",task_subcomment,"['In some cases the non-alphnumeric is desired - [[Fun.', ']], [[Westward Ho!]]', 'and [[C++]] are cases that spring immediately to mind.', 'I think it is best that VE does what you ask it to, whether that is what you wanted or not.', 'Anything typed in the middle of a link should be included in that link in all cases, which would make spotting that trailing punctuation is limited easier.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+247555,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"(I'd add that, at least for me, there is a desired outcome, which is that VE puts the non-alphanumeric character outside the link - of course, I am not sure this is doable or desirable, but this is why I had added my report to 51442.)",task_subcomment,"[""(I'd add that, at least for me, there is a desired outcome, which is that VE puts the non-alphanumeric character outside the link - of course, I am not sure this is doable or desirable, but this is why I had added my report to 51442.)""]",['INVESTIGATION AND EXPLORATION']
+247552,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"How to reproduce
+
+1. Load any page in VE
+2. Type any sequence of characters ending in one or more non-space characters followed by any non-alphanumeric character except space or underscore. For example: Foo?
+3. Link what you have written, including the last character, to any target (e.g. [[Wikipedia]].
+4. add any text immediately before the last character. eg. change Foo? to Fooish?
+5. Save and look at the diff.
+
+Expected wikitext:
+[[Wikipedia|Fooish?]]
+
+Actual wikitext:
+[[Wikipedia|Foo]]ish[[Wikipedia|?]]
+
+(In reply to comment #1)
+> I think you mean bug 51442
+
+I do. Dyslexia strikes again :(",task_subcomment,"['How to reproduce\n\n1.', 'Load any page in VE\n2.', 'Type any sequence of characters ending in one or more non-space characters followed by any non-alphanumeric character except space or underscore.', 'For example: Foo?', '3.', 'Link what you have written, including the last character, to any target (e.g.', '[[Wikipedia]].', '4. add any text immediately before the last character.', 'eg.', 'change Foo?', 'to Fooish?', '5.', 'Save and look at the diff.', 'Expected wikitext:\n[[Wikipedia|Fooish?]]', 'Actual wikitext:\n[[Wikipedia|Foo]]ish[[Wikipedia|?]]', '(In reply to comment #1)\nQUOTE\n\nI do.', 'Dyslexia strikes again :(']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+247547,VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,I think you mean bug 51442,task_subcomment,['I think you mean bug 51442'],['MOTIVATION']
+56322,VisualEditor: [Regression] Page settings dialog broken in Firefox,"Current VisualEditor-Version:
+commit c98a964d5f8495f0d16af9229abbeb0449042d1e
+Merge: 3d01a5b e7aed52
+Author: jenkins-bot 
+Date:   Wed Sep 18 01:11:46 2013 +0000
+Merge ""Fix check for preformatted when stripping whitespace""
+
+Browser: Firefox 24.0 on Windows 7 64bit
+
+
+Description:
+I updated my VisualEditor via git yesterday. Before that I didnt update for 4 weeks. Now when openening a page on my MediaWiki in VE-Editmode I cant assign a page category (See screenshot).
+
+I tried to debug with Firebug: When I click on categories the following error gets fired:
+
+TypeError: style is null
+http://XYZ/load.php?debug=false&lang=de&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T072806Z&*
+Line 9
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",task_description,"['VisualEditor: [Regression] Page settings dialog broken in Firefox\n\nCurrent VisualEditor-Version:\ncommit c98a964d5f8495f0d16af9229abbeb0449042d1e\nMerge: 3d01a5b e7aed52\nAuthor: jenkins-bot \nDate:   Wed Sep 18 01:11:46 2013 +0000\nMerge ""Fix check for preformatted when stripping whitespace""\n\nBrowser: Firefox 24.0 on Windows 7 64bit\n\n\nDescription:\nI updated my VisualEditor via git yesterday.', 'Before that I didnt update for 4 weeks.', 'Now when openening a page on my MediaWiki in VE-Editmode I cant assign a page category (See screenshot).', 'I tried to debug with Firebug: When I click on categories the following error gets fired:\n\nTypeError: style is null\nURL\nLine 9\n\n--------------------------\n**Version**: unspecified\n**Severity**: blocker']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247037,VisualEditor: [Regression] Page settings dialog broken in Firefox,Have split the new failure into bug 54928 and am re-closing this one.,task_subcomment,['Have split the new failure into bug 54928 and am re-closing this one.'],['BUG REPRODUCTION']
+247033,VisualEditor: [Regression] Page settings dialog broken in Firefox,"(In reply to comment #7)
+> This should be fixed in https://gerrit.wikimedia.org/r/#/c/85692 , which is
+> in
+> wmf19 but not in wmf18. enwiki is being upgraded from wmf18 to wmf19 today,
+> hopefully that'll fix it.
+
+That's the patch that closed this bug (comment 3). But it appears there is indeed a new bug that causes the page settings dialog to be broken again due to an uncaught exception when the dialog is first created when clicking the page settings button.
+
+
+It fails in Chrome like this:
+
+Uncaught TypeError: Cannot use 'in' operator to search for 'scrollTop' in undefined load.php?…:102
+vendorPropName load.php?…:102
+jQuery.extend.css load.php?…:105
+Tween.propHooks._default.get load.php?…:136
+Tween.cur load.php?…:136
+Tween.init load.php?…:135
+Tween load.php?…:135
+Animation.deferred.promise.createTween load.php?…:131
+tweeners.* load.php?…:129
+(anonymous function) load.php?…:130
+jQuery.extend.each load.php?…:8
+createTweens load.php?…:130
+Animation load.php?…:132
+doAnimation load.php?…:137
+jQuery.extend.dequeue load.php?…:25
+(anonymous function) load.php?…:26
+jQuery.extend.each load.php?…:8
+jQuery.fn.jQuery.each load.php?…:4
+jQuery.fn.extend.queue load.php?…:26
+jQuery.fn.extend.animate load.php?…:138
+ve.Element.scrollIntoView load.php?ext.visualEditor…:11
+ve.Element.scrollElementIntoView load.php?ext.visualEditor…:12
+ve.ui.OptionWidget.setSelected load.php?ext.visualEditor…:404
+ve.ui.SelectWidget.selectItem load.php?ext.visualEditor…:400
+ve.ui.PagedDialog.addPage load.php?ext.visualEditor…:458
+ve.ui.MWMetaDialog.initialize load.php?ext.visualEditor…:461
+ve.ui.Window.onFrameInitialize load.php?ext.visualEditor…:353
+oo.EventEmitter.emit load.php?ext.visualEditor.bas…:133
+ve.ui.Frame.load load.php?ext.visualEditor…:351
+ve.ui.WindowSet.open load.php?ext.visualEditor…:356
+ve.init.mw.ViewPageTarget.onToolbarMwMetaButtonClick load.php?ext.visualEditor.bas…:87
+proxy load.php?…:10
+jQuery.event.dispatch load.php?…:45
+elemData.handle.eventHandle load.php?…:38",task_subcomment,"[""(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's the patch that closed this bug (comment 3)."", 'But it appears there is indeed a new bug that causes the page settings dialog to be broken again due to an uncaught exception when the dialog is first created when clicking the page settings button.', ""It fails in Chrome like this:\n\nUncaught TypeError: Cannot use 'in' operator to search for 'scrollTop' in undefined load.php?…:102\nvendorPropName load.php?…:102\njQuery.extend.css load.php?…:105\nTween.propHooks._default.get load.php?…:136\nTween.cur load.php?…:136\nTween.init load.php?…:135\nTween load.php?…:135\nAnimation.deferred.promise.createTween load.php?…:131\ntweeners."", '* load.php?…:129\n(anonymous function) load.php?…:130\njQuery.extend.each load.php?…:8\ncreateTweens load.php?…:130\nAnimation load.php?…:132\ndoAnimation load.php?…:137\njQuery.extend.dequeue load.php?…:25\n(anonymous function) load.php?…:26\njQuery.extend.each load.php?…:8\njQuery.fn.jQuery.each load.php?…:4\njQuery.fn.extend.queue load.php?…:26\njQuery.fn.extend.animate load.php?…:138\nve.Element.scrollIntoView load.php?ext.visualEditor…:11\nve.Element.scrollElementIntoView load.php?ext.visualEditor…:12\nve.ui.OptionWidget.setSelected load.php?ext.visualEditor…:404\nve.ui.SelectWidget.selectItem load.php?ext.visualEditor…:400\nve.ui.PagedDialog.addPage load.php?ext.visualEditor…:458\nve.ui.MWMetaDialog.initialize load.php?ext.visualEditor…:461\nve.ui.Window.onFrameInitialize load.php?ext.visualEditor…:353\noo.EventEmitter.emit load.php?ext.visualEditor.bas…:133\nve.ui.Frame.load load.php?ext.visualEditor…:351\nve.ui.WindowSet.open load.php?ext.visualEditor…:356\nve.init.mw.ViewPageTarget.onToolbarMwMetaButtonClick load.php?ext.visualEditor.bas…:87\nproxy load.php?…:10\njQuery.event.dispatch load.php?…:45\nelemData.handle.eventHandle load.php?…:38']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+247026,VisualEditor: [Regression] Page settings dialog broken in Firefox,"This should be fixed in https://gerrit.wikimedia.org/r/#/c/85692 , which is in wmf19 but not in wmf18. enwiki is being upgraded from wmf18 to wmf19 today, hopefully that'll fix it.",task_subcomment,"['This should be fixed in URL , which is in wmf19 but not in wmf18.', ""enwiki is being upgraded from wmf18 to wmf19 today, hopefully that'll fix it.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247020,VisualEditor: [Regression] Page settings dialog broken in Firefox,"Confirmed:
+
+* Working on latest master locally (Chrome).
+* Broken on mediawik.org (Chrome).",task_subcomment,"['Confirmed:\n\n* Working on latest master locally (Chrome).', '* Broken on mediawik.org (Chrome).']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+247014,VisualEditor: [Regression] Page settings dialog broken in Firefox,"It's still happening, unfortunately. Ed found out it works fine on local and mediawiki.org, though.
+
+TeamGale mentioned this today at en.wp:
+<>
+
+Fram tested as well:
+
+<>
+
+I can confirm that the second click just launches an empty window, with only the ""categories"" label text on the left column.
+
+<>",task_subcomment,"[""It's still happening, unfortunately."", 'Ed found out it works fine on local and mediawiki.org, though.', 'TeamGale mentioned this today at en.wp:\n<>\n\nFram tested as well:\n\n<>\n\nI can confirm that the second click just launches an empty window, with only the ""categories"" label text on the left column.', '<>']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247007,VisualEditor: [Regression] Page settings dialog broken in Firefox,"Problem solved. Tested with Firefox 24.0 on Windows 7 64BIT.
+>> Page-settings dialog is operational and working.",task_subcomment,"['Problem solved.', 'Tested with Firefox 24.0 on Windows 7 64BIT.', 'QUOTE']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+246999,VisualEditor: [Regression] Page settings dialog broken in Firefox,"Change 85692 merged by jenkins-bot:
+ve.Element: Account for getComputerStyle returning null
+
+https://gerrit.wikimedia.org/r/85692",task_subcomment,['Change 85692 merged by jenkins-bot:\nve.Element: Account for getComputerStyle returning null\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+246990,VisualEditor: [Regression] Page settings dialog broken in Firefox,"Change 85692 had a related patch set uploaded by Krinkle:
+ve.Element: Account for getComputerStyle returning null
+
+https://gerrit.wikimedia.org/r/85692",task_subcomment,['Change 85692 had a related patch set uploaded by Krinkle:\nve.Element: Account for getComputerStyle returning null\n\nGERRIT_URL'],['ACTION ON ISSUE']
+246981,VisualEditor: [Regression] Page settings dialog broken in Firefox,"I can confirm. When trying to open the Page settings dialog, an exception is thrown for ""style is null"":
+
+ve.Element.js, line:
+ 		top = parseFloat( loc ? style.borderTopWidth : $el.css( 'borderTopWidth' ) ) || 0,
+
+Context:
+ve.Element.getBorders = function ( el ) {
+	var doc = el.ownerDocument,
+		win = doc.parentWindow || doc.defaultView,
+		style = win && win.getComputedStyle ?
+			win.getComputedStyle( el, null ) : el.currentStyle,
+		loc = win && win.getComputedStyle ? true : false,
+		$el = $( el ),
+		top = parseFloat( loc ? style.borderTopWidth : $el.css( 'borderTopWidth' ) ) || 0,",task_subcomment,"['I can confirm.', 'When trying to open the Page settings dialog, an exception is thrown for ""style is null"":\n\nve.Element.js, line:\n \t\ttop = parseFloat( loc ?', ""style.borderTopWidth : $el.css( 'borderTopWidth' ) ) || 0,\n\nContext:\nve.Element.getBorders = function ( el ) {\n\tvar doc = el.ownerDocument,\n\t\twin = doc.parentWindow || doc.defaultView,\n\t\tstyle = win && win.getComputedStyle ?"", 'win.getComputedStyle( el, null ) : el.currentStyle,\n\t\tloc = win && win.getComputedStyle ?', 'true : false,\n\t\t$el = $( el ),\n\t\ttop = parseFloat( loc ?', ""style.borderTopWidth : $el.css( 'borderTopWidth' ) ) || 0,""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+56314,"VisualEditor: A pawn appears when undoing ""select transclusion and replace with text""","Steps to reproduce bug:
+1. Edit a page
+2. Insert a transclusion, apply changes
+# The transclusion is now selected (VE does this automatically for newly inserted nodes)
+3. Type a characters
+# Selected content is removed, text is inserted
+4. Undo
+
+The expected result is the text being replaced with the transclusion. Instead a pawn is inserted.
+
+Upon further inspection I noticed that the transclusion isn't lost, however. In fact it is right there when you Undo again (after getting the pawn).
+
+So it looks like the pawn was inserted as a transaction in the middle of removing the transclusion (its own transaction but not supposed to be?) and inserting the text.
+
+We auto-select the template after insertion and it is relatively easy to accidentally press a key afterwards. And Undo then shows the user something scary (their template appears lost). A fairly high priority bug regarding user experience.
+
+Not sure if this is a regression or not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: A pawn appears when undoing ""select transclusion and replace with text""\n\nSteps to reproduce bug:\n1.', 'Edit a page\n2.', 'Insert a transclusion, apply changes\n# The transclusion is now selected (VE does this automatically for newly inserted nodes)\n3.', 'Type a characters\n# Selected content is removed, text is inserted\n4.', 'Undo\n\nThe expected result is the text being replaced with the transclusion.', 'Instead a pawn is inserted.', ""Upon further inspection I noticed that the transclusion isn't lost, however."", 'In fact it is right there when you Undo again (after getting the pawn).', 'So it looks like the pawn was inserted as a transaction in the middle of removing the transclusion (its own transaction but not supposed to be?)', 'and inserting the text.', 'We auto-select the template after insertion and it is relatively easy to accidentally press a key afterwards.', 'And Undo then shows the user something scary (their template appears lost).', 'A fairly high priority bug regarding user experience.', 'Not sure if this is a regression or not.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPORT', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+246645,"VisualEditor: A pawn appears when undoing ""select transclusion and replace with text""","This is now fixed, AFAICS. Marking as such.",task_subcomment,"['This is now fixed, AFAICS.', 'Marking as such.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+56271,VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"From en.wp.
+
+John Broughton: <>
+
+Andrew Davidson: <>
+
+Salix alba: <>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Collapse all the text styling buttons (except link?)', 'into a single text-styling icon in the toolbar\n\nFrom en.wp.', ""John Broughton: <>\n\nAndrew Davidson: <>\n\nSalix alba: <>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243916,VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,I did this in wmf7.,task_subcomment,['I did this in wmf7.'],['OBSERVED BUG BEHAVIOR']
+243911,VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"FYI, he conversation is now happening at https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Toolbar .",task_subcomment,"['FYI, he conversation is now happening at URL .']",['POTENTIAL NEW ISSUES AND REQUESTS']
+243905,VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"Conversation on the best order of the toolbar is continuing and is pretty thoughtful and indepth at the English VE feedback page. :)
+
+Live link: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Toolbar_button_priority_proposal
+
+Permanent link to its current state:
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=573642781#Toolbar_button_priority_proposal",task_subcomment,"['Conversation on the best order of the toolbar is continuing and is pretty thoughtful and indepth at the English VE feedback page.', ':)\n\nLive link: URL\n\nPermanent link to its current state:\nURL']","['FUTURE PLAN', 'SOLUTION USAGE']"
+243901,VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"My feelings are similar to John's on this.  We can't bury important buttons like references in a dropdown menu.  And, as John points out, for the english user base anyway, the options of underline and strikethrough are very rarely used.  New users are going to experiment with the options most prominently placed, these should be the most useful tools that would lead to a constructive (i.e. not reverted) edit.",task_subcomment,"[""My feelings are similar to John's on this."", ""We can't bury important buttons like references in a dropdown menu."", 'And, as John points out, for the english user base anyway, the options of underline and strikethrough are very rarely used.', 'New users are going to experiment with the options most prominently placed, these should be the most useful tools that would lead to a constructive (i.e.', 'not reverted) edit.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+243897,VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"Grouping commands under a ""Text format"" drop-down menu is a natural (obvious, intuitive) way to collect commands that are rarely used. For example, bolding of text, in articles, is typically done ONCE (in the lead paragraph, by the author of the article), and then never again. 
+
+A ""Text format"" drop-down menu would take all of the following off of the main toolbar line, leaving space for (at the moment) everything else:
+
+* Bold
+* Italic
+* Superscript
+* Subscript
+* Programming language 
+* Underline
+* Strikethrough
+* Clear formatting
+
+Putting all these under a single menu has the advantage of - in the future - allowing projects to control which options are visible in which namespaces. For example, on the English Wikipedia, strikethrough almost certainly should not be a (visible) user choice in mainspace (articlespace), nor should underlining. 
+
+It's important, for SPEED, that frequently used functions are immediately accessible. Articles should have lots of footnotes, a fair number of templates (particularly for footnotes), and at least a couple of images. Putting the related commands into a drop-down menu, as opposed to having them directly on the toolbar, is undesirable: It makes VE less attractive to experienced editors (slower to use) and more difficult for new editors (because now they have to be instructed on, and remember, a TWO-step process (menu, select) rather than a one-step process (click), for important things like images and footnotes.",task_subcomment,"['Grouping commands under a ""Text format"" drop-down menu is a natural (obvious, intuitive) way to collect commands that are rarely used.', 'For example, bolding of text, in articles, is typically done ONCE (in the lead paragraph, by the author of the article), and then never again.', 'A ""Text format"" drop-down menu would take all of the following off of the main toolbar line, leaving space for (at the moment) everything else:\n\n* Bold\n* Italic\n* Superscript\n* Subscript\n* Programming language \n* Underline\n* Strikethrough\n* Clear formatting\n\nPutting all these under a single menu has the advantage of - in the future - allowing projects to control which options are visible in which namespaces.', 'For example, on the English Wikipedia, strikethrough almost certainly should not be a (visible) user choice in mainspace (articlespace), nor should underlining.', ""It's important, for SPEED, that frequently used functions are immediately accessible."", 'Articles should have lots of footnotes, a fair number of templates (particularly for footnotes), and at least a couple of images.', 'Putting the related commands into a drop-down menu, as opposed to having them directly on the toolbar, is undesirable: It makes VE less attractive to experienced editors (slower to use) and more difficult for new editors (because now they have to be instructed on, and remember, a TWO-step process (menu, select) rather than a one-step process (click), for important things like images and footnotes.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+243891,VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"User Pointillist on the English Wikipedia has some really interesting ideas on this subject, posted here: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=573508478#Toolbar_button_priority_proposal
+
+Without all the very useful images, he writes (please pardon my clumsy textual effort to reproduce his proposal and check out the link to see it the way it should look):
+
+Summary: as discussed above and in bug 54271, the sequence of buttons in the toolbar isn't appropriate for typical article editing activities.
+
+The current toolbar gives too much priority to hard-coded formatting such as Bold, Italic, Lists and Indents. As a result:
+* The most important buttons (e.g. for referencing) are pushed into a secondary position and may even be forced onto the ""More"" drop-down
+* Wikilinking is incorrectly associated with formatting
+* Formatting buttons are divided between the left-end of the toolbar and the ""More"" drop-down
+* It isn't immediately clear what ""More"" is offering
+
+
+I propose that article content buttons should be at the left end and formatting should be at the right end of the toolbar, so something like this:
+[Undo * Redo * Link * Media * Reference * References * Template * Equation * Paragraph * Clear formatting * Bold * Italic * Superscript * Subscript * Programming language * Unordered list * Ordered list * Reduce indent * Increase indent]
+
+If ""More"" is necessary, it would probably be inserted into the formatting buttons, and the users would expect to find more of them in the drop-down, like this:
+[Undo * Redo * Link * Media * Reference * References * Template * Equation * Paragraph * Clear formatting * Bold * Italic * Superscript * More]
+
+Of course, this is only a starting point. By the way: underscore and strikeout shouldn't be formatting options in the article space, ""Page title"" isn't necessary as a paragraph style. Thoughts?",task_subcomment,"[""User Pointillist on the English Wikipedia has some really interesting ideas on this subject, posted here: URL\n\nWithout all the very useful images, he writes (please pardon my clumsy textual effort to reproduce his proposal and check out the link to see it the way it should look):\n\nSummary: as discussed above and in bug 54271, the sequence of buttons in the toolbar isn't appropriate for typical article editing activities."", 'The current toolbar gives too much priority to hard-coded formatting such as Bold, Italic, Lists and Indents.', 'As a result:\n* The most important buttons (e.g.', 'for referencing) are pushed into a secondary position and may even be forced onto the ""More"" drop-down\n* Wikilinking is incorrectly associated with formatting\n* Formatting buttons are divided between the left-end of the toolbar and the ""More"" drop-down\n* It isn\'t immediately clear what ""More"" is offering\n\n\nI propose that article content buttons should be at the left end and formatting should be at the right end of the toolbar, so something like this:\n[Undo * Redo * Link * Media * Reference * References * Template * Equation * Paragraph * Clear formatting * Bold * Italic * Superscript * Subscript * Programming language * Unordered list * Ordered list * Reduce indent * Increase indent]\n\nIf ""More"" is necessary, it would probably be inserted into the formatting buttons, and the users would expect to find more of them in the drop-down, like this:\n[Undo * Redo * Link * Media * Reference * References * Template * Equation * Paragraph * Clear formatting * Bold * Italic * Superscript * More]\n\nOf course, this is only a starting point.', 'By the way: underscore and strikeout shouldn\'t be formatting options in the article space, ""Page title"" isn\'t necessary as a paragraph style.', 'Thoughts?']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+56193,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"I thought there was a bug for this, but I can't find it...
+
+Warning:  Recursion detected in RequestContext::getLanguage in /usr/local/apache/common-local/php-1.22wmf16/includes/context/RequestContext.php on line 281
+
+
+The amount of the warnings seems to have increased a lot more in wmf16/wmf17
+
+Such occurrences and stracktraces can be found in logstash with `_type: mediawiki` and `channel: recursion-guard`.
+",task_description,"[""Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284\n\nI thought there was a bug for this, but I can't find it..."", 'Warning:  Recursion detected in RequestContext::getLanguage in /usr/local/apache/common-local/php-1.22wmf16/includes/context/RequestContext.php on line 281\n\n\nThe amount of the warnings seems to have increased a lot more in wmf16/wmf17\n\nSuch occurrences and stracktraces can be found in logstash with CODE and CODE.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+812747,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,No events logged in the recursion-guard channel since December 2016.,task_subcomment,['No events logged in the recursion-guard channel since December 2016.'],['OBSERVED BUG BEHAVIOR']
+619113,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 273586 merged by jenkins-bot:
+Fix 'localpage' message handling
+
+[[https://gerrit.wikimedia.org/r/273586]]",task_subcomment,"[""Change 273586 merged by jenkins-bot:\nFix 'localpage' message handling\n\n[[GERRIT_URL]]""]",['GERRIT_URL']
+619105,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 273586 had a related patch set uploaded (by Anomie):
+Fix 'localpage' message handling
+
+[[https://gerrit.wikimedia.org/r/273586]]
+",task_subcomment,"[""Change 273586 had a related patch set uploaded (by Anomie):\nFix 'localpage' message handling\n\n[[GERRIT_URL]]""]",['GERRIT_URL']
+619104,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,">>! In T56193#2068539, @Mattflaschen wrote:
+> P2680
+
+> 16 0.8985 8361744 Message->isDisabled( ) ../TitleBlacklist.list.php:98
+
+WTF are you doing there, TitleBlacklist?",task_subcomment,"['QUOTE\nQUOTE\n\nQUOTE\n\nWTF are you doing there, TitleBlacklist?']",['OBSERVED BUG BEHAVIOR']
+618954,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,P2680,task_subcomment,['P2680'],['OBSERVED BUG BEHAVIOR']
+618953,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,Got this locally on MediaWiki-Vagrant.,task_subcomment,['Got this locally on MediaWiki-Vagrant.'],['OBSERVED BUG BEHAVIOR']
+588673,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,">>! In T56193#1926036, @mmodell wrote:
+> @bd808: do you think there is any value in keeping this error message?  It seems to me like it's expected behavior at this point and not really valuable.
+
+Disabling the log message has been proposed as a patch before () and @TStarling at that time wanted the message to stay until the underlying bug was fixed.",task_subcomment,['QUOTE\nQUOTE\n\nDisabling the log message has been proposed as a patch before (>! In T56193#1603723, @Southparkfan wrote:
+> Seems to not be Wikimedia-only, I experience this error too:
+
+This looks to be a variant on one of the patterns noted in T56193#554201:
+* getLanguage() → Log in from cookies → User::isUsableName() → Message → getLanguage()
+
+In this particular case, the `wfMessage()` call is going to be rendered using the `inContentLanguage()` method but before it can get that far the Parser wants to know the User's language.
+
+The statement of ""It should be a pretty simple change for Brad or Chris."" in T56193#554221 has thus far proved to be a variant on [[https://en.wikipedia.org/wiki/Fermat's_Last_Theorem|Fermat's Last Theorem]]. Many people have looked for the proof but none have yet been able to provide one.",task_subcomment,"[""QUOTE\nQUOTE\n\nThis looks to be a variant on one of the patterns noted in T56193#554201:\n* getLanguage() → Log in from cookies → User::isUsableName() → Message → getLanguage()\n\nIn this particular case, the CODE call is going to be rendered using the CODE method but before it can get that far the Parser wants to know the User's language."", 'The statement of ""It should be a pretty simple change for Brad or Chris.""', 'in T56193#554221 has thus far proved to be a variant on [[URL Last Theorem]].', 'Many people have looked for the proof but none have yet been able to provide one.']","['MOTIVATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+520523,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Seems to not be Wikimedia-only, I experience this error too:
+| Product | version
+| MediaWiki | 1.25.2 (9c89a16) 18:08, 3 September 2015
+| HHVM | 3.8.1 (srv)
+| MariaDB | 10.0.20-MariaDB-0+deb8u1-log
+Configuration: https://github.com/miraheze/mw-config/blob/master/LocalSettings.php
+```
+#0 /srv/mediawiki/w/includes/StubObject.php(204): RequestContext->getLanguage()
+#1 /srv/mediawiki/w/includes/StubObject.php(160): StubUserLang->_newObject()
+#2 /srv/mediawiki/w/includes/parser/ParserOptions.php(588): StubObject->_unstub()
+#3 /srv/mediawiki/w/includes/cache/MessageCache.php(148): ParserOptions->__construct()
+#4 /srv/mediawiki/w/includes/cache/MessageCache.php(988): MessageCache->getParserOptions()
+#5 /srv/mediawiki/w/includes/Message.php(1059): MessageCache->transform()
+#6 /srv/mediawiki/w/includes/Message.php(726): Message->transformText()
+#7 /srv/mediawiki/w/includes/Message.php(789): Message->toString()
+#8 /srv/mediawiki/w/includes/User.php(748): Message->text()
+#9 /srv/mediawiki/w/includes/User.php(790): User::isUsableName()
+#10 /srv/mediawiki/w/extensions/CentralAuth/includes/CentralAuthHooks.php(1082): User::isCreatableName()
+#11 /srv/mediawiki/w/extensions/CentralAuth/includes/CentralAuthHooks.php(835): CentralAuthHooks::attemptAddUser()
+#12 /srv/mediawiki/w/includes/Hooks.php(209): CentralAuthHooks::onUserLoadFromSession()
+#13 /srv/mediawiki/w/includes/User.php(1132): Hooks::run()
+#14 /srv/mediawiki/w/includes/User.php(361): User->loadFromSession()
+#15 /srv/mediawiki/w/includes/User.php(4942): User->load()
+#16 /srv/mediawiki/w/includes/User.php(2587): User->loadOptions()
+#17 /srv/mediawiki/w/includes/context/RequestContext.php(342): User->getOption()
+#18 /srv/mediawiki/w/includes/Message.php(577): RequestContext->getLanguage()
+#19 /srv/mediawiki/w/includes/context/RequestContext.php(436): Message->setContext()
+#20 /srv/mediawiki/w/includes/context/ContextSource.php(176): RequestContext->msg()
+#21 /srv/mediawiki/w/includes/OutputPage.php(974): ContextSource->msg()
+#22 /srv/mediawiki/w/includes/page/Article.php(512): OutputPage->setPageTitle()
+#23 /srv/mediawiki/w/includes/actions/ViewAction.php(44): Article->view()
+#24 /srv/mediawiki/w/includes/MediaWiki.php(395): ViewAction->show()
+#25 /srv/mediawiki/w/includes/MediaWiki.php(273): MediaWiki->performAction()
+#26 /srv/mediawiki/w/includes/MediaWiki.php(566): MediaWiki->performRequest()
+#27 /srv/mediawiki/w/includes/MediaWiki.php(414): MediaWiki->main()
+#28 /srv/mediawiki/w/index.php(41): MediaWiki->run()
+#29 {main}
+```",task_subcomment,"['Seems to not be Wikimedia-only, I experience this error too:\n| Product | version\n| MediaWiki | 1.25.2 (9c89a16) 18:08, 3 September 2015\n| HHVM | 3.8.1 (srv)\n| MariaDB | 10.0.20-MariaDB-0+deb8u1-log\nConfiguration: URL\n``CODE``']",['INVESTIGATION AND EXPLORATION']
+466726,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"That is still hitting us, stracktraces can be found in logstash with _type: mediawiki and channel: recursion-guard.
+
+Is anyone working on it?",task_subcomment,"['That is still hitting us, stracktraces can be found in logstash with _type: mediawiki and channel: recursion-guard.', 'Is anyone working on it?']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+400813,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 174057 abandoned by Umherirrender:
+Avoid calling Title::makeTitleSafe in User::idFromName
+
+Reason:
+Old branch, proper fix already in master (Ib902573996c69d1e77527cc7b2faf4e7fa5d3daf)
+
+[[https://gerrit.wikimedia.org/r/174057]]",task_subcomment,"['Change 174057 abandoned by Umherirrender:\nAvoid calling Title::makeTitleSafe in User::idFromName\n\nReason:\nOld branch, proper fix already in master (Ib902573996c69d1e77527cc7b2faf4e7fa5d3daf)\n\n[[GERRIT_URL]]']",['GERRIT_URL']
+239724,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 174057 had a related patch set uploaded by Ori.livneh:
+Avoid calling Title::makeTitleSafe in User::idFromName
+
+https://gerrit.wikimedia.org/r/174057",task_subcomment,['Change 174057 had a related patch set uploaded by Ori.livneh:\nAvoid calling Title::makeTitleSafe in User::idFromName\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239717,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 174051 merged by jenkins-bot:
+Avoid calling Title::makeTitleSafe in User::idFromName
+
+https://gerrit.wikimedia.org/r/174051",task_subcomment,['Change 174051 merged by jenkins-bot:\nAvoid calling Title::makeTitleSafe in User::idFromName\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+239711,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 174051 had a related patch set uploaded by Ori.livneh:
+Avoid calling Title::makeTitleSafe in User::idFromName
+
+https://gerrit.wikimedia.org/r/174051",task_subcomment,['Change 174051 had a related patch set uploaded by Ori.livneh:\nAvoid calling Title::makeTitleSafe in User::idFromName\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239703,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"(In reply to Tim Starling from comment #17)
+> Looks like bug 41201 again (""UserLoadFromSession considered evil""). I
+> probably should have pushed that one a bit harder during the CA2 sprint. It
+> should be a pretty simple change for Brad or Chris.
+
+Is it?",task_subcomment,['(In reply to Tim Starling from comment #17)\nQUOTE\nQUOTE\nQUOTE\n\nIs it?'],['ACTION ON ISSUE']
+239699,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Looks like bug 41201 again (""UserLoadFromSession considered evil""). I probably should have pushed that one a bit harder during the CA2 sprint. It should be a pretty simple change for Brad or Chris.",task_subcomment,"['Looks like bug 41201 again (""UserLoadFromSession considered evil"").', 'I probably should have pushed that one a bit harder during the CA2 sprint.', 'It should be a pretty simple change for Brad or Chris.']","['MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239696,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,Hiding the warning in fatal monitor with Gerrit change #102557 - the stacktrace logging is still on,task_subcomment,['Hiding the warning in fatal monitor with Gerrit change #102557 - the stacktrace logging is still on'],['OBSERVED BUG BEHAVIOR']
+239695,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"So the problem generally appears to be that Language::getLanguage() unstubs the User object by trying to fetch the 'language' pref, and the various hooks called during that process may themselves wind up doing something that tries to call Language::getLanguage(). There are also some instances where something hooking 'UserGetLanguageObject' tries to call getLanguage().
+
+Code paths I see in a quick look through the log include:
+* getLanguage() → Log in from cookies → Trying to get the localized alias for NS_USER on wikis with variants → getLanguage()
+** This seems to be a large number of the instances: srwiki, uzwiktionary, kuwiktionary, etc.
+* getLanguage() → Autocreate account → AbuseFilter's checkNewAccount hook → dividebyzero → Trying to get localized error message → getLanguage()
+** enwiki and eswiki have this
+* getLanguage() → ULS's getLanguage hook → User::saveOptions → BetaFeatures's hook on UserSaveOptions → VisualEditor's onGetBetaPreferences hook or VectorBeta's prefs hook → getLanguage()
+* getLanguage() → Autocreate account → User::saveOptions → BetaFeatures's hook on UserSaveOptions → VisualEditor's onGetBetaPreferences hook or VectorBeta's prefs hook → getLanguage()
+* getLanguage() → Autocreate account → TitleBlacklist hit → Trying to get localized error message → getLanguage()
+* getLanguage() → Autocreate account → NewUserMessage::createNewUserMessage → various different code paths involving the parser and/or MessageCache → getLanguage()
+
+I think that the fallback behavior added in Gerrit change 48080 is probably the best thing to do in general.
+
+BTW, the previous bug on this topic was probably bug 44754.",task_subcomment,"[""So the problem generally appears to be that Language::getLanguage() unstubs the User object by trying to fetch the 'language' pref, and the various hooks called during that process may themselves wind up doing something that tries to call Language::getLanguage()."", ""There are also some instances where something hooking 'UserGetLanguageObject' tries to call getLanguage()."", 'Code paths I see in a quick look through the log include:\n* getLanguage() → Log in from cookies → Trying to get the localized alias for NS_USER on wikis with variants → getLanguage()\n** This seems to be a large number of the instances: srwiki, uzwiktionary, kuwiktionary, etc.', ""* getLanguage() → Autocreate account → AbuseFilter's checkNewAccount hook → dividebyzero → Trying to get localized error message → getLanguage()\n** enwiki and eswiki have this\n* getLanguage() → ULS's getLanguage hook → User::saveOptions → BetaFeatures's hook on UserSaveOptions → VisualEditor's onGetBetaPreferences hook or VectorBeta's prefs hook → getLanguage()\n* getLanguage() → Autocreate account → User::saveOptions → BetaFeatures's hook on UserSaveOptions → VisualEditor's onGetBetaPreferences hook or VectorBeta's prefs hook → getLanguage()\n* getLanguage() → Autocreate account → TitleBlacklist hit → Trying to get localized error message → getLanguage()\n* getLanguage() → Autocreate account → NewUserMessage::createNewUserMessage → various different code paths involving the parser and/or MessageCache → getLanguage()\n\nI think that the fallback behavior added in Gerrit change 48080 is probably the best thing to do in general."", 'BTW, the previous bug on this topic was probably bug 44754.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION']"
+239693,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"(In reply to comment #12)
+> What a scary backtrace. It seems to relate on automatic creation of local
+> accounts interacting with abuse filter. No wonder it seems to only happen in
+> production.
+> 
+> I have no idea how to fix this. Perhaps automatic local account creation
+> should
+> happen somewhere else?
+
+cc Anomie",task_subcomment,['(In reply to comment #12)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\ncc Anomie'],['ACTION ON ISSUE']
+239692,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Given the backtrace, this does not seem to be an i18n issue, except for that the class (Stub)Language is involved at one level. Reclassifying and updating CCs accordingly. Niklas and I will stay on CC.",task_subcomment,"['Given the backtrace, this does not seem to be an i18n issue, except for that the class (Stub)Language is involved at one level.', 'Reclassifying and updating CCs accordingly.', 'Niklas and I will stay on CC.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239688,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"What a scary backtrace. It seems to relate on automatic creation of local accounts interacting with abuse filter. No wonder it seems to only happen in production.
+
+I have no idea how to fix this. Perhaps automatic local account creation should happen somewhere else?",task_subcomment,"['What a scary backtrace.', 'It seems to relate on automatic creation of local accounts interacting with abuse filter.', 'No wonder it seems to only happen in production.', 'I have no idea how to fix this.', 'Perhaps automatic local account creation should happen somewhere else?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+239686,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"(In reply to comment #6)
+> Would it be possible to provide more information about which wiki(s) display
+> this behavior, or possibly even page(s)? Being able t reproduce this would
+> probably go a long way towards resolving it.
+
+I added a trace; additional ones are available in fluorine:/a/mw-log/recursion-guard-stack-trace.log. If you want me to grab additional ones, let me know.
+
+(In reply to comment #7)
+> Side note: the logs this information is extracted from, could we make those
+> more widely available so they could get more eyeballs? From my experience
+> doing this at translatewiki.net it often helps in identifying issues a lot
+> earlier.
+
+Yeah, fair point. We (platform & ops) are working on setting up a better platform for log analysis, probably using logstash. The current situation sucks.",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nI added a trace; additional ones are available in fluorine:/a/mw-log/recursion-guard-stack-trace.log.', 'If you want me to grab additional ones, let me know.', '(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah, fair point.', 'We (platform & ops) are working on setting up a better platform for log analysis, probably using logstash.', 'The current situation sucks.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']"
+239684,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Created attachment 13858
+stack trace from fluorine:/a/mw-log/recursion-guard-stack-trace.log
+
+**Attached**: {F11344}",task_subcomment,['Created attachment 13858\nstack trace from fluorine:/a/mw-log/recursion-guard-stack-trace.log\n\n**Attached**: {F11344}'],['BUG REPRODUCTION']
+239681,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 96709 merged by Ori.livneh:
+Enable recursion-guard log bucket to investigate bug 54193
+
+https://gerrit.wikimedia.org/r/96709",task_subcomment,['Change 96709 merged by Ori.livneh:\nEnable recursion-guard log bucket to investigate bug 54193\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+239677,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Change 96709 had a related patch set uploaded by Ori.livneh:
+Enable recursion-guard log bucket to investigate bug 54193
+
+https://gerrit.wikimedia.org/r/96709",task_subcomment,['Change 96709 had a related patch set uploaded by Ori.livneh:\nEnable recursion-guard log bucket to investigate bug 54193\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239671,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Side note: the logs this information is extracted from, could we make those more widely available so they could get more eyeballs? From my experience doing this at translatewiki.net it often helps in identifying issues a lot earlier.",task_subcomment,"['Side note: the logs this information is extracted from, could we make those more widely available so they could get more eyeballs?', 'From my experience doing this at translatewiki.net it often helps in identifying issues a lot earlier.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239663,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Would it be possible to provide more information about which wiki(s) display this behavior, or possibly even page(s)?
+
+Being able t reproduce this would probably go a long way towards resolving it.",task_subcomment,"['Would it be possible to provide more information about which wiki(s) display this behavior, or possibly even page(s)?', 'Being able t reproduce this would probably go a long way towards resolving it.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+239655,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,>200 of these every hour in /a/mw-log/apache2.log,task_subcomment,['QUOTE'],['SOLUTION DISCUSSION']
+239649,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Every 2.0s: tail -n 1000 /home/wikipedia/syslog/apache.log | grep -v 'Search backend error' | grep -v -i 'swift' | grep 'PHP\|Segmentation ...  Tue Nov 12 22:33:46 2013
+
+    240 Warning:  Recursion detected in RequestContext::getLanguage in /usr/local/apache/common-local/php-1.23wmf3/includes/context/RequestContext.php on line 284
+     72 Warning:  Recursion detected in RequestContext::getLanguage in /usr/local/apache/common-local/php-1.23wmf2/includes/context/RequestContext.php on line 284",task_subcomment,"[""Every 2.0s: tail -n 1000 /home/wikipedia/syslog/apache.log | grep -v 'Search backend error' | grep -v -i 'swift' | grep 'PHP\\|Segmentation ...  Tue Nov 12 22:33:46 2013\n\n    240 Warning:  Recursion detected in RequestContext::getLanguage in /usr/local/apache/common-local/php-1.23wmf3/includes/context/RequestContext.php on line 284\n     72 Warning:  Recursion detected in RequestContext::getLanguage in /usr/local/apache/common-local/php-1.23wmf2/includes/context/RequestContext.php on line 284""]",['OBSERVED BUG BEHAVIOR']
+239645,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Yup, there are these warnings almost always shown in the last 1000 lines of the apache syslogs",task_subcomment,"['Yup, there are these warnings almost always shown in the last 1000 lines of the apache syslogs']",['OBSERVED BUG BEHAVIOR']
+239640,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,"Sam, are these still being observed, or have they gone away?",task_subcomment,"['Sam, are these still being observed, or have they gone away?']",['OBSERVED BUG BEHAVIOR']
+239635,Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,I can't do anything about this without a backtrace. Not sure how to mark that.,task_subcomment,"[""I can't do anything about this without a backtrace."", 'Not sure how to mark that.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+56140,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","e.g. Template:Information could be documented at TemplateData:Information instead of inside the source code of Template:Information.
+
+Pros:
+
+%%%1. More standard use of ContentHandler for JSON across projects
+2. Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages
+3. Easier to implement custom editors for ContentHandler pages than for portions of wikitext pages.%%%
+
+Cons:
+
+%%%1. Would need to have two separate systems - one for the JSON storage, then another to transclude the generated documentation onto template doc pages, e.g. with  or {{#templatedata}} or so (no params needed, because the TemplateData namespace page can be of the same name, like a talk page)
+2. Would need to rework the existing editor (sorry, mooeypoo) to work with the new system%%%
+
+--------------------------
+**See Also**: {T52512}",task_description,"['Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot\n\ne.g.', 'Template:Information could be documented at TemplateData:Information instead of inside the source code of Template:Information.', 'Pros:\n\n%%%1.', 'More standard use of ContentHandler for JSON across projects\n2.', 'Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages\n3.', 'Easier to implement custom editors for ContentHandler pages than for portions of wikitext pages.%%%\n\nCons:\n\n%%%1.', 'Would need to have two separate systems - one for the JSON storage, then another to transclude the generated documentation onto template doc pages, e.g.', 'with  or {{#templatedata}} or so (no params needed, because the TemplateData namespace page can be of the same name, like a talk page)\n2.', 'Would need to rework the existing editor (sorry, mooeypoo) to work with the new system%%%\n\n--------------------------\n**See Also**: {T52512}']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+2132794,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",">>! In T56140#8877796, @Jdforrester-WMF wrote:
+> For the transition, certainly. Long-term, probably not, and hacks to generate the transclusion data would have to make way for proper documentation.
+Having shared TemplateData between pages or generating TemplateData programmatically, which those cases cover, are legitimate uses of TemplateData and not hacks. If anything, more templates with the same parameter configurations (like, for example, navigation templates) would benefit from it if it was more widely adopted. Currently, TemplateData adoption is too low, and if anything, we should look for ways to encourage TemplateData adoption, not to discourage it.",task_subcomment,"['QUOTE\nQUOTE\nHaving shared TemplateData between pages or generating TemplateData programmatically, which those cases cover, are legitimate uses of TemplateData and not hacks.', 'If anything, more templates with the same parameter configurations (like, for example, navigation templates) would benefit from it if it was more widely adopted.', 'Currently, TemplateData adoption is too low, and if anything, we should look for ways to encourage TemplateData adoption, not to discourage it.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+2132790,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","For the record, TemplateData is also read to create automatic template examples, see https://ru.wikipedia.org/wiki/Module:TemplateDataDoc
+This is not a use case that will be supported by Lua if TemplateData data gets moved to another slot, without implementing {T107119}",task_subcomment,"['For the record, TemplateData is also read to create automatic template examples, see URL\nThis is not a use case that will be supported by Lua if TemplateData data gets moved to another slot, without implementing {T107119}']",['INVESTIGATION AND EXPLORATION']
+2131469,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",">>! In T56140#8877796, @Jdforrester-WMF wrote:
+> Long-term, probably not, and hacks to generate the transclusion data would have to make way for proper documentation.
+
+These are not hacks, these are proper solutions using the public API of TemplateData (a JSON blob), making template editors’ lives easier. How can this “proper documentation” be created without duplicating everything between the TemplateData-compatible documentation and the actually useful documentation (i.e. one that contains e.g. inline links)? Looking at the PoC patch, keeping support for JSON blobs in wikitext would probably need 5-10 lines of extra code, which doesn’t sound like a horrible tech debt even long-term.
+
+MediaWiki developers seem to sometimes forget how much the community relies on templates. Parsoid doesn’t support templates emitting unbalanced wikitext. The result? Large blocks of text, sometimes even whole pages, that have to be edited in wikitext in VisualEditor, or can’t be edited at all. Structured Data on Commons doesn’t support templates at all. The result? Instead of either using or replacing wikitext, all machine-readable metadata is still present in wikitext in one form, and bots duplicate it to another form, making actual edits to pages. Please don’t do the same mistake again and again.",task_subcomment,"['QUOTE\nQUOTE\n\nThese are not hacks, these are proper solutions using the public API of TemplateData (a JSON blob), making template editors’ lives easier.', 'How can this “proper documentation” be created without duplicating everything between the TemplateData-compatible documentation and the actually useful documentation (i.e.', 'one that contains e.g.', 'inline links)?', 'Looking at the PoC patch, keeping support for JSON blobs in wikitext would probably need 5-10 lines of extra code, which doesn’t sound like a horrible tech debt even long-term.', 'MediaWiki developers seem to sometimes forget how much the community relies on templates.', 'Parsoid doesn’t support templates emitting unbalanced wikitext.', 'The result?', 'Large blocks of text, sometimes even whole pages, that have to be edited in wikitext in VisualEditor, or can’t be edited at all.', 'Structured Data on Commons doesn’t support templates at all.', 'The result?', 'Instead of either using or replacing wikitext, all machine-readable metadata is still present in wikitext in one form, and bots duplicate it to another form, making actual edits to pages.', 'Please don’t do the same mistake again and again.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+2131467,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","Many many templates are not documented by an individual JSON for each single template, but derived from series of JSON data generated by documentation template or Lua module, creating TemplateData for many productive templates.
+
+German Wikipedia is documenting latin based language templates by [[ https://de.wikipedia.org/wiki/Template:lang/Latn/Doku | Template:lang/Latn/Doku ]] which provides one unique pattern for all of them ([[ https://de.wikipedia.org/w/index.php?search=hastemplate%3A%22Lang%2FLatn%2FDoku%22&title=Spezial%3ASuche&profile=advanced&fulltext=1&ns10=1 | 196 single templates ]]). The TemplateData and the entire documentation page is produced by very short transclusions like ##{{lang/Latn/Doku|CODE=lv|SPRACHE=lettischer Sprache|EXAMPLE=Rīga}}## in [[ https://de.wikipedia.org/w/index.php?title=Template:lvS&action=edit | Template:lvS ]].
+[[ https://de.wikipedia.org/wiki/Category:Vorlage:Metadokumentation | Category:Vorlage:Metadokumentation ]] lists a pile (53) of such meta documentation patterns. Currently we are planning schemes which are generating full documentation pages for several 10,000 single productive templates, with heading TemplateData of course.
+
+The concept of independent namespace for TemplateData is based on the assumption that every productive template has one static individual JSON code without any JSON code injection.",task_subcomment,"['Many many templates are not documented by an individual JSON for each single template, but derived from series of JSON data generated by documentation template or Lua module, creating TemplateData for many productive templates.', 'German Wikipedia is documenting latin based language templates by [[ URL | Template:lang/Latn/Doku ]] which provides one unique pattern for all of them ([[ URL | 196 single templates ]]).', 'The TemplateData and the entire documentation page is produced by very short transclusions like ##{{lang/Latn/Doku|CODE=lv|SPRACHE=lettischer Sprache|EXAMPLE=Rīga}}## in [[ URL | Template:lvS ]].', '[[ URL | Category:Vorlage:Metadokumentation ]] lists a pile (53) of such meta documentation patterns.', 'Currently we are planning schemes which are generating full documentation pages for several 10,000 single productive templates, with heading TemplateData of course.', 'The concept of independent namespace for TemplateData is based on the assumption that every productive template has one static individual JSON code without any JSON code injection.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+2129667,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",">>! In T56140#8869098, @Tacsipacsi wrote:
+> Would the current JSON structure continue to be supported?
+
+For the transition, certainly. Long-term, probably not, and hacks to generate the transclusion data would have to make way for proper documentation.
+
+> [[https://commons.wikimedia.org/wiki/Template:TemplateBox|c:Template:TemplateBox]] relies on being able to generate JSON to avoid unnecessarily duplicating content between the TemplateData and the wikitext description (the latter supports wiki markup, so TemplateData can’t entirely supersede it, unless TemplateData will also start to support wiki markup).
+
+Ack, the very-intentional lack of support for wikitext (and all the horrors that entails) means some forms of documentation are hard to do. We should probably add additional fields including link targets and good- and bad-example samples to augment the structured data so that it works better for secondary use cases. That's outside the scope of this task, however.",task_subcomment,"['QUOTE\nQUOTE\n\nFor the transition, certainly.', 'Long-term, probably not, and hacks to generate the transclusion data would have to make way for proper documentation.', 'QUOTE\n\nAck, the very-intentional lack of support for wikitext (and all the horrors that entails) means some forms of documentation are hard to do.', 'We should probably add additional fields including link targets and good- and bad-example samples to augment the structured data so that it works better for secondary use cases.', ""That's outside the scope of this task, however.""]","['SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+2127607,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","Change 921693 had a related patch set uploaded (by TK-999; author: TK-999):
+%%%[mediawiki/extensions/TemplateData@master] [PoC] MCR slot for TemplateData content%%%
+https://gerrit.wikimedia.org/r/921693",task_subcomment,['Change 921693 had a related patch set uploaded (by TK-999; author: TK-999):\n%%%[mediawiki/extensions/TemplateData@master] [PoC] MCR slot for TemplateData content%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+2127581,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","Would the current JSON structure continue to be supported? [[https://commons.wikimedia.org/wiki/Template:TemplateBox|c:Template:TemplateBox]] relies on being able to generate JSON to avoid unnecessarily duplicating content between the TemplateData and the wikitext description (the latter supports wiki markup, so TemplateData can’t entirely supersede it, unless TemplateData will also start to support wiki markup).",task_subcomment,"['Would the current JSON structure continue to be supported?', '[[URL relies on being able to generate JSON to avoid unnecessarily duplicating content between the TemplateData and the wikitext description (the latter supports wiki markup, so TemplateData can’t entirely supersede it, unless TemplateData will also start to support wiki markup).']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+2127544,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",Tagging #Wikimedia-Hackathon-2023 to showcase a basic PoC created during this event.,task_subcomment,['Tagging #Wikimedia-Hackathon-2023 to showcase a basic PoC created during this event.'],['INVESTIGATION AND EXPLORATION']
+1200143,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","See related approach by [[ https://www.mediawiki.org/wiki/Module:TNT | Module:TNT ]] -- it stores templatedata [[ https://commons.wikimedia.org/wiki/Data:Templatedata/Graph:Lines.tab | as a table (example) ]]. In this case  will be dynamically generated during the parse time, and is available to every language/every wiki.",task_subcomment,"['See related approach by [[ URL | Module:TNT ]] -- it stores templatedata [[ URL | as a table (example) ]].', 'In this case  will be dynamically generated during the parse time, and is available to every language/every wiki.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+1199675,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","Please note that these are not static pages.
+* The URI comment looks like assigning a static page which is simply transcluded.
+* Entire JSON TemplateData descriptions are generated individually by template or Lua programming; depending on parameters and existence of other pages.
+* You may have a look e.g. at [[ https://de.wikipedia.org/w/index.php?title=Vorlage:enS&action=edit | use of lang/Latn/Doku ]] and the derived page.",task_subcomment,"['Please note that these are not static pages.', '* The URI comment looks like assigning a static page which is simply transcluded.', '* Entire JSON TemplateData descriptions are generated individually by template or Lua programming; depending on parameters and existence of other pages.', '* You may have a look e.g.', 'at [[ URL | use of lang/Latn/Doku ]] and the derived page.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+1199609,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",">>! In T56140#3143510, @PerfektesChaos wrote:
+> * There are JSON objects built by template-like transclusion via ##{{#tag:}}## syntax.
+> ** See [[https://de.wikipedia.org/wiki/Kategorie:Vorlage:Metadokumentation | Kategorie:Vorlage:Metadokumentation]] on German Wikipedia – a dozen of so-called “meta documentation” pattern pages is generating nearly thousand TemplateData objects on particular template pages, controlled by template name and sometimes parameters.
+
+Interesting. json-schema allows referencing/embedding other schemas by using a special `""$ref"": ""[URI to another schema]""` key. Maybe something like that could be implemented in TemplateData instead of requiring the use of parser functions.
+
+",task_subcomment,"['QUOTE\nQUOTE\nQUOTE\n\nInteresting.', 'json-schema allows referencing/embedding other schemas by using a special CODE key.', 'Maybe something like that could be implemented in TemplateData instead of requiring the use of parser functions.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+911940,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",This could be held like doc subpages or currently deployed css subpages instead,task_subcomment,['This could be held like doc subpages or currently deployed css subpages instead'],['SOLUTION DISCUSSION']
+1068644,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","I do raise two issues against the proposal, at least for mandatory evaluation of JSON pages only.
+* Pro #2 reads as: “Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages”
+** This goes for any kind of lengthy documentation, and is usually solved by transclusion of a separated ##/doc## into main template page.
+** German Wikipedia is using that technique for any longer template documentation since 2008, and enforces TemplateData on separated docpage for all productive templates.
+* There are JSON objects built by template-like transclusion via ##{{#tag:}}## syntax.
+** See [[https://de.wikipedia.org/wiki/Kategorie:Vorlage:Metadokumentation | Kategorie:Vorlage:Metadokumentation]] on German Wikipedia – a dozen of so-called “meta documentation” pattern pages is generating nearly thousand TemplateData objects on particular template pages, controlled by template name and sometimes parameters.
+Optional separated ##.json## subpages may be introduced, but classic #### approach needs to be supported, too.
+",task_subcomment,"['I do raise two issues against the proposal, at least for mandatory evaluation of JSON pages only.', '* Pro #2 reads as: “Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages”\n** This goes for any kind of lengthy documentation, and is usually solved by transclusion of a separated ##/doc## into main template page.', '** German Wikipedia is using that technique for any longer template documentation since 2008, and enforces TemplateData on separated docpage for all productive templates.', '* There are JSON objects built by template-like transclusion via ##{{#tag:}}## syntax.', '** See [[URL | Kategorie:Vorlage:Metadokumentation]] on German Wikipedia – a dozen of so-called “meta documentation” pattern pages is generating nearly thousand TemplateData objects on particular template pages, controlled by template name and sometimes parameters.', 'Optional separated ##.json## subpages may be introduced, but classic #### approach needs to be supported, too.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+834499,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","I do raise two issues against the proposal, at least for mandatory evaluation of JSON pages only.
+* Pro #2 reads as: “Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages”
+** This goes for any kind of lengthy documentation, and is usually solved by transclusion of a separated ##/doc## into main template page.
+** German Wikipedia is using that technique for any longer template documentation since 2008, and enforces TemplateData on separated docpage for all productive templates.
+* There are JSON objects built by template-like transclusion via ##{{#tag:}}## syntax.
+** See [[https://de.wikipedia.org/wiki/Kategorie:Vorlage:Metadokumentation | Kategorie:Vorlage:Metadokumentation]] on German Wikipedia – a dozen of so-called “meta documentation” pattern pages is generating nearly thousand TemplateData objects on particular template pages, controlled by template name and sommetimes parameters.
+Optional separated ##.json## subpages may be introduced, but classic #### approach needs to be supported, too.
+",task_subcomment,"['I do raise two issues against the proposal, at least for mandatory evaluation of JSON pages only.', '* Pro #2 reads as: “Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages”\n** This goes for any kind of lengthy documentation, and is usually solved by transclusion of a separated ##/doc## into main template page.', '** German Wikipedia is using that technique for any longer template documentation since 2008, and enforces TemplateData on separated docpage for all productive templates.', '* There are JSON objects built by template-like transclusion via ##{{#tag:}}## syntax.', '** See [[URL | Kategorie:Vorlage:Metadokumentation]] on German Wikipedia – a dozen of so-called “meta documentation” pattern pages is generating nearly thousand TemplateData objects on particular template pages, controlled by template name and sommetimes parameters.', 'Optional separated ##.json## subpages may be introduced, but classic #### approach needs to be supported, too.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+590984,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","I've fiddled with this because either {T487} or {T107595} would both meet this need. I think the latter is both more likely to occur and a better outcome, but…",task_subcomment,"[""I've fiddled with this because either {T487} or {T107595} would both meet this need."", 'I think the latter is both more likely to occur and a better outcome, but…']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+236209,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",Re-wording; this is blocked by https://www.mediawiki.org/wiki/Requests_for_comment/Associated_namespaces being implemented.,task_subcomment,['Re-wording; this is blocked by URL being implemented.'],['OBSERVED BUG BEHAVIOR']
+236205,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","See also:
+https://www.mediawiki.org/wiki/Requests_for_comment/Associated_namespaces#Use_case_2b:_Structured_template_documentation",task_subcomment,['See also:\nURL'],['OBSERVED BUG BEHAVIOR']
+236200,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot","I talked about that briefly on IRC, we decided that since this is specifically about the namespace proposal, until we decided what to do about it, we'd leave both open. And closing that bug may not necessarily close this bug.",task_subcomment,"[""I talked about that briefly on IRC, we decided that since this is specifically about the namespace proposal, until we decided what to do about it, we'd leave both open."", 'And closing that bug may not necessarily close this bug.']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+236195,"Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot",Is this a dupe of https://bugzilla.wikimedia.org/show_bug.cgi?id=50512#c0 ?,task_subcomment,['Is this a dupe of URL ?'],['OBSERVED BUG BEHAVIOR']
+56045,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"When requesting random images from Commons' MediaWiki API and requesting a thumbnail for it, I often get a HTTP 500.
+
+For example:
+
+
+
+GET http://upload.wikimedia.org/wikipedia/commons/thumb/f/fb/USMC-05934.jpg/400px-USMC-05934.jpg
+HTTP 500
+Error generating thumbnail
+
+
    Error generating thumbnail
    
+
    
+Error creating thumbnail:
+
    
+
+
+
+
+
+Usually when trying again, it just works.
+
+I've been getting these errors in many different environments:
+* When reading articles and HiDPI plugin swaps the src attributes (the larger version would fail maybe)
+* When opening the VisualEditor (rendering the new DOM means we re-parse the tag and thus re-request it, thus making it more likely for the error to happen again)
+* When working with gadgets that render image galleries through requesting file category members and the thumbnail url.
+
+I don't think the scenario is relevant, there is either something wrong with the thumbnail generator script that is triggered by lots of images. Or there is a few faulty servers in the upload.wikimedia.org pool that cause the errors.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: critical",task_description,"[""Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error\n\nWhen requesting random images from Commons' MediaWiki API and requesting a thumbnail for it, I often get a HTTP 500."", 'For example:\n\n\n\nGET URL\nHTTP 500\nError generating thumbnail\n\n
    Error generating thumbnail
    \n
    \nError creating thumbnail:\n
    \n\n\n\n\n\nUsually when trying again, it just works.', ""I've been getting these errors in many different environments:\n* When reading articles and HiDPI plugin swaps the src attributes (the larger version would fail maybe)\n* When opening the VisualEditor (rendering the new DOM means we re-parse the tag and thus re-request it, thus making it more likely for the error to happen again)\n* When working with gadgets that render image galleries through requesting file category members and the thumbnail url."", ""I don't think the scenario is relevant, there is either something wrong with the thumbnail generator script that is triggered by lots of images."", 'Or there is a few faulty servers in the upload.wikimedia.org pool that cause the errors.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: critical']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254806,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"[02:06:08]  Can someone depool mw1154 from the image scaler cluster?
+[02:06:20]  what's wrong with it?
+[02:07:40]  It's seemingly generating a lot more errors (by a factor of 2 or so) than any of the other scalers
+[02:07:41]  https://bugzilla.wikimedia.org/show_bug.cgi?id=54045
+[02:08:32]  root@mw1154:~# ls /sys/fs/cgroup/memory/mediawiki/job
+[02:08:33]  ls: cannot access /sys/fs/cgroup/memory/mediawiki/job: No such file or directory
+[02:08:35]  blergh
+[02:09:01]  fixed
+[02:09:58]  is that's what's up with it?
+[02:10:05]  yes, fixed
+[02:10:09]  awesome
+[02:10:10]  thanks",task_subcomment,"['[02:06:08]  Can someone depool mw1154 from the image scaler cluster?', ""[02:06:20]  what's wrong with it?"", ""[02:07:40]  It's seemingly generating a lot more errors (by a factor of 2 or so) than any of the other scalers\n[02:07:41]  URL\n[02:08:32]  root@mw1154:~# ls /sys/fs/cgroup/memory/mediawiki/job\n[02:08:33]  ls: cannot access /sys/fs/cgroup/memory/mediawiki/job: No such file or directory\n[02:08:35]  blergh\n[02:09:01]  fixed\n[02:09:58]  is that's what's up with it?"", '[02:10:05]  yes, fixed\n[02:10:09]  awesome\n[02:10:10]  thanks']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'SOLUTION DISCUSSION']"
+254803,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"Yup, still mw1154
+
+
+reedy@fluorine:/a/mw-log$ grep -c mw1153 thumbnail.log
+50057
+reedy@fluorine:/a/mw-log$ grep -c mw1154 thumbnail.log
+125850
+reedy@fluorine:/a/mw-log$ grep -c mw1155 thumbnail.log
+50451
+reedy@fluorine:/a/mw-log$ grep -c mw1156 thumbnail.log
+50584
+reedy@fluorine:/a/mw-log$ grep -c mw1157 thumbnail.log
+51015
+reedy@fluorine:/a/mw-log$ grep -c mw1158 thumbnail.log
+50386
+reedy@fluorine:/a/mw-log$ grep -c mw1159 thumbnail.log
+50134
+reedy@fluorine:/a/mw-log$ grep -c mw1160 thumbnail.log
+51486",task_subcomment,"['Yup, still mw1154\n\n\nreedy@fluorine:/a/mw-log$ grep -c mw1153 thumbnail.log\n50057\nreedy@fluorine:/a/mw-log$ grep -c mw1154 thumbnail.log\n125850\nreedy@fluorine:/a/mw-log$ grep -c mw1155 thumbnail.log\n50451\nreedy@fluorine:/a/mw-log$ grep -c mw1156 thumbnail.log\n50584\nreedy@fluorine:/a/mw-log$ grep -c mw1157 thumbnail.log\n51015\nreedy@fluorine:/a/mw-log$ grep -c mw1158 thumbnail.log\n50386\nreedy@fluorine:/a/mw-log$ grep -c mw1159 thumbnail.log\n50134\nreedy@fluorine:/a/mw-log$ grep -c mw1160 thumbnail.log\n51486']",['OBSERVED BUG BEHAVIOR']
+254800,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,Ganglia graphs suggest so (mw1154 has less activity) but I haven't specificly tested.,task_subcomment,"[""Ganglia graphs suggest so (mw1154 has less activity) but I haven't specificly tested.""]",['OBSERVED BUG BEHAVIOR']
+254797,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,Part of the question would be is it still the same machine? (based on the fact it's already changed once),task_subcomment,"['Part of the question would be is it still the same machine?', ""(based on the fact it's already changed once)""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254793,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,Could this server be taken out of rotation until the issue is resolved?,task_subcomment,['Could this server be taken out of rotation until the issue is resolved?'],['CONTRIBUTION AND COMMITMENT']
+254787,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"The entries in /a/mw-log/thumbnail.log are often hard to correlate since they use temporary file names. However it appears some (or all?) contain a MediaWiki File-namespace url as well.
+
+I just got another HTTP 500 Internal Server Error and found the following entry:
+
+URL: https://upload.wikimedia.org/wikipedia/commons/thumb/e/e8/Trevor_Parscal_December_2008.jpg/660px-Trevor_Parscal_December_2008.jpg
+
+Triggered from an  tag on https://commons.wikimedia.org/w/index.php?title=File:Trevor_Parscal_December_2008.jpg&action=submit when previewing an edit.
+
+
+[04:11 UTC] krinkle at fluorine in /a/mw-log
+$ tail thumbnail.log  -n500 | ack-grep Trevor -C 10
+
+Bytes: 0xFF 0x27 0x20 0x69"" from ""'/usr/bin/'rsvg-convert --no-external-files -w 120 -h 61 -o '/tmp/transform_5a95aeb43c6b-1.png' '/tmp/localcopy_61a6c00091e1-1.svg' 2>&1""
+2013-09-17 04:10:06 mw1154 commonswiki: thumbnail failed on mw1154: error 1 """" from ""'/usr/bin/convert' -quality 80 -background white -define jpeg:size=660x440 '/tmp/localcopy_cb6372f89daf-1.jpg'  -thumbnail '660x440!' -set comment 'File source: http://commons.wikimedia.org/wiki/File:Trevor_Parscal_December_2008.jpg' -depth 8 -sharpen '0x0.8'  -rotate -0   '/tmp/transform_f22fd870a3fc-1.jpg' 2>&1""
+2013-09-17 04:10:06 mw1154 commonswiki: Removing bad 0-byte thumbnail ""/tmp/transform_f22fd870a3fc-1.jpg"". unlink() succeeded
+2013-09-17 04:10:06 mw1157 commonswiki: thumbnail failed on mw1157: error 1 ""convert: no decode delegate for this image format `/a/magick-tmp/magick-NyMRfqeG' @ error/constitute.c/ReadImage/532.
+convert: missing an image filename `/tmp/transform_6c0a3d0fd7c4-1.jpg' @ error/convert.c/ConvertImageCommand/3011."" from ""'/usr/bin/convert' -quality 80 -background white -define jpeg:size=120x53 ''  -thumbnail '120x53!' -set comment 'File source: http://commons.wikimedia.org/wiki/File:Banknote_5000_rubles_(1997)_front.jpg' -depth 8 -sharpen '0x0.8'  -rotate -0   '/tmp/transform_6c0a3d0fd7c4-1.jpg' 2>&1""
+..
+2013-09-17 04:13:59 mw1159 commonswiki: thumbnail failed on mw1159: error 1 ""Error reading SVG:Error domain 1 code 96 on line 1 column 17 of file:///tmp/localcopy_2362643f10ec-1.svg: Malformed declaration expecting version"" from ""'/usr/bin/'rsvg-convert --no-external-files -w 120 -h 96 -o '/tmp/transform_8ba6acf9d427-1.png' '/tmp/localcopy_2362643f10ec-1.svg' 2>&1""
+2013-09-17 04:13:59 mw1154 commonswiki: thumbnail failed on mw1154: error 1 """" from ""'/usr/bin/convert' -quality 80 -background white -define jpeg:size=660x440 '/tmp/localcopy_babba88e51a4-1.jpg'  -thumbnail '660x440!' -set comment 'File source: http://commons.wikimedia.org/wiki/File:Trevor_Parscal_December_2008.jpg' -depth 8 -sharpen '0x0.8'  -rotate -0   '/tmp/transform_de7473e35169-1.jpg' 2>&1""
+2013-09-17 04:13:59 mw1154 commonswiki: Removing bad 0-byte thumbnail ""/tmp/transform_de7473e35169-1.jpg"". unlink() succeeded
+2013-09-17 04:14:01 mw1154 commonswiki: Removing bad 0-byte thumbnail ""/tmp/transform_55d5b98e5f7b-1.png"". unlink() succeeded",task_subcomment,"['The entries in /a/mw-log/thumbnail.log are often hard to correlate since they use temporary file names.', 'However it appears some (or all?)', 'contain a MediaWiki File-namespace url as well.', 'I just got another HTTP 500 Internal Server Error and found the following entry:\n\nURL: URL\n\nTriggered from an  tag on URL when previewing an edit.', '[04:11 UTC] krinkle at fluorine in /a/mw-log\n$ tail thumbnail.log  -n500 | ack-grep Trevor -C 10\n\nBytes: 0xFF 0x27 0x20 0x69"" from ""\'/usr/bin/\'rsvg-convert --no-external-files -w 120 -h 61 -o \'/tmp/transform_5a95aeb43c6b-1.png\' \'/tmp/localcopy_61a6c00091e1-1.svg\' 2>&1""\n2013-09-17 04:10:06 mw1154 commonswiki: thumbnail failed on mw1154: error 1 """" from ""\'/usr/bin/convert\' -quality 80 -background white -define jpeg:size=660x440 \'/tmp/localcopy_cb6372f89daf-1.jpg\'  -thumbnail \'660x440!\'', '-set comment \'File source: URL -depth 8 -sharpen \'0x0.8\'  -rotate -0   \'/tmp/transform_f22fd870a3fc-1.jpg\' 2>&1""\n2013-09-17 04:10:06 mw1154 commonswiki: Removing bad 0-byte thumbnail ""/tmp/transform_f22fd870a3fc-1.jpg"".', 'unlink() succeeded\n2013-09-17 04:10:06 mw1157 commonswiki: thumbnail failed on mw1157: error 1 ""convert: no decode delegate for this image format CODE/tmp/transform_6c0a3d0fd7c4-1.jpg\' @ error/convert.c/ConvertImageCommand/3011.""', 'from ""\'/usr/bin/convert\' -quality 80 -background white -define jpeg:size=120x53 \'\'  -thumbnail \'120x53!\'', '-set comment \'File source: URL -depth 8 -sharpen \'0x0.8\'  -rotate -0   \'/tmp/transform_6c0a3d0fd7c4-1.jpg\' 2>&1""\n..\n2013-09-17 04:13:59 mw1159 commonswiki: thumbnail failed on mw1159: error 1 ""Error reading SVG:Error domain 1 code 96 on line 1 column 17 of file:///tmp/localcopy_2362643f10ec-1.svg: Malformed declaration expecting version"" from ""\'/usr/bin/\'rsvg-convert --no-external-files -w 120 -h 96 -o \'/tmp/transform_8ba6acf9d427-1.png\' \'/tmp/localcopy_2362643f10ec-1.svg\' 2>&1""\n2013-09-17 04:13:59 mw1154 commonswiki: thumbnail failed on mw1154: error 1 """" from ""\'/usr/bin/convert\' -quality 80 -background white -define jpeg:size=660x440 \'/tmp/localcopy_babba88e51a4-1.jpg\'  -thumbnail \'660x440!\'', '-set comment \'File source: URL -depth 8 -sharpen \'0x0.8\'  -rotate -0   \'/tmp/transform_de7473e35169-1.jpg\' 2>&1""\n2013-09-17 04:13:59 mw1154 commonswiki: Removing bad 0-byte thumbnail ""/tmp/transform_de7473e35169-1.jpg"".', 'unlink() succeeded\n2013-09-17 04:14:01 mw1154 commonswiki: Removing bad 0-byte thumbnail ""/tmp/transform_55d5b98e5f7b-1.png"".', 'unlink() succeeded']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254782,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"Btw, good debugging step would be for someone with shell to try running the convert command by hand (with limit.sh) to see what happens (e.g. if issue with cgroup config this would give an error that wouldn't be included in thumb log)
+
+See also gerrit change 83974 which would give more useful error messages in certain circumstances (which may or may not help for the current situation)",task_subcomment,"['Btw, good debugging step would be for someone with shell to try running the convert command by hand (with limit.sh) to see what happens (e.g.', ""if issue with cgroup config this would give an error that wouldn't be included in thumb log)\n\nSee also gerrit change 83974 which would give more useful error messages in certain circumstances (which may or may not help for the current situation)""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+254775,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,*** Bug 54188 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54188 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254767,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"(In reply to comment #5)
+> reedy@fluorine:/a/mw-log$ grep mw1154 thumbnail.log |grep -c error
+> 55424
+> reedy@fluorine:/a/mw-log$ grep -c mw1154 thumbnail.log
+> 111320
+
+We pass things with \n's in them to wfDebugLog for the thumbnail log. I don't think we log successful thumbnailing events at all. So I think all that means is many of the thumbnail error log messages span several lines.",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe pass things with \\n's in them to wfDebugLog for the thumbnail log."", ""I don't think we log successful thumbnailing events at all."", 'So I think all that means is many of the thumbnail error log messages span several lines.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254758,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"When you look at the 500 error message, its supposed to include all the stdout and stderr from convert. However these are empty. Perhaps https://gerrit.wikimedia.org/r/83974 would help debug the situation (including stderr from limit.sh in the 500 error message).",task_subcomment,"['When you look at the 500 error message, its supposed to include all the stdout and stderr from convert.', 'However these are empty.', 'Perhaps GERRIT_URL would help debug the situation (including stderr from limit.sh in the 500 error message).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254751,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"reedy@fluorine:/a/mw-log$ grep mw1154 thumbnail.log |grep -c error
+55424
+reedy@fluorine:/a/mw-log$ grep -c mw1154 thumbnail.log
+111320",task_subcomment,['reedy@fluorine:/a/mw-log$ grep mw1154 thumbnail.log |grep -c error\n55424\nreedy@fluorine:/a/mw-log$ grep -c mw1154 thumbnail.log\n111320'],['OBSERVED BUG BEHAVIOR']
+254744,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"I just did a test on commons - visited a page with 200 images which I suspect were not previously rendered before (note: all were tiff files). 28 of them failed, all from mw1154. There's only 8 image scalars. 200/8 = 25, so its not hard to imagine this means all requests to mw1154 are failing.
+
+Perhaps something is wrong with the cgroups config on that host (or something else that would prevent all shell commands from succeeding)
+
+The ganglia graph seems to indicate that the CPU usage on that host has dropped off since friday - http://ganglia.wikimedia.org/latest/graph.php?g=cpu_report&z=xlarge&c=Image%20scalers%20eqiad&h=mw1154.eqiad.wmnet&l=e2ecff&v=&r=week&su=1&st=1378942982&x=0&n=0",task_subcomment,"['I just did a test on commons - visited a page with 200 images which I suspect were not previously rendered before (note: all were tiff files).', '28 of them failed, all from mw1154.', ""There's only 8 image scalars."", '200/8 = 25, so its not hard to imagine this means all requests to mw1154 are failing.', 'Perhaps something is wrong with the cgroups config on that host (or something else that would prevent all shell commands from succeeding)\n\nThe ganglia graph seems to indicate that the CPU usage on that host has dropped off since friday - URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+254734,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"Looks like mw1153 has stopped being so noisy, and it's now mw1154. Which I guess makes this a dupe of 53753
+
+reedy@fluorine:/a/mw-log$ grep -c error thumbnail.log
+324850
+reedy@fluorine:/a/mw-log$ grep mw1153 thumbnail.log |grep -c error
+22013
+reedy@fluorine:/a/mw-log$ grep mw1154 thumbnail.log |grep -c error
+54280
+reedy@fluorine:/a/mw-log$ grep mw1155 thumbnail.log |grep -c error
+22011
+reedy@fluorine:/a/mw-log$ grep mw1156 thumbnail.log |grep -c error
+21980
+reedy@fluorine:/a/mw-log$ grep mw1157 thumbnail.log |grep -c error
+21847
+reedy@fluorine:/a/mw-log$ grep mw1158 thumbnail.log |grep -c error
+22146
+reedy@fluorine:/a/mw-log$ grep mw1159 thumbnail.log |grep -c error
+21905
+reedy@fluorine:/a/mw-log$ grep mw1160 thumbnail.log |grep -c error
+22107",task_subcomment,"[""Looks like mw1153 has stopped being so noisy, and it's now mw1154."", 'Which I guess makes this a dupe of 53753\n\nreedy@fluorine:/a/mw-log$ grep -c error thumbnail.log\n324850\nreedy@fluorine:/a/mw-log$ grep mw1153 thumbnail.log |grep -c error\n22013\nreedy@fluorine:/a/mw-log$ grep mw1154 thumbnail.log |grep -c error\n54280\nreedy@fluorine:/a/mw-log$ grep mw1155 thumbnail.log |grep -c error\n22011\nreedy@fluorine:/a/mw-log$ grep mw1156 thumbnail.log |grep -c error\n21980\nreedy@fluorine:/a/mw-log$ grep mw1157 thumbnail.log |grep -c error\n21847\nreedy@fluorine:/a/mw-log$ grep mw1158 thumbnail.log |grep -c error\n22146\nreedy@fluorine:/a/mw-log$ grep mw1159 thumbnail.log |grep -c error\n21905\nreedy@fluorine:/a/mw-log$ grep mw1160 thumbnail.log |grep -c error\n22107']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+254724,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"Always mw1154?
+
+See also bug 53573, mw1153 was (not sure if it's changed) seemingly causing a lot more errors than its counterparts",task_subcomment,"['Always mw1154?', ""See also bug 53573, mw1153 was (not sure if it's changed) seemingly causing a lot more errors than its counterparts""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254712,Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"See also bug 53573. (which was mostly mw1153)
+-----
+>I don't think the scenario is relevant, there is either something wrong with
+>the thumbnail generator script that is triggered by lots of images. Or there is
+>a few faulty servers in the upload.wikimedia.org pool that cause the errors.
+
+Thumbnail generation should be entirely independent of page view actions, so the scenario should definitely not matter",task_subcomment,"['See also bug 53573.', '(which was mostly mw1153)\n-----\nQUOTE\nQUOTE\nQUOTE\n\nThumbnail generation should be entirely independent of page view actions, so the scenario should definitely not matter']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+55972,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","The VisualEditor UI has an interface to check what version is currently deployed (similar to Special:Version), when asking around people seemed to assume that this has been disabled purposely on the cluster.
+
+However this does not seem to be true.
+
+For one, the configuration around is working perfectly fine.
+
+Though the HEAD commit is retreived by MediaWiki's GitInfo class without shell (it just reads from the .git/HEAD file directly), I additionally verified that $wgGitBin (used for calcuating the commit dates with `git show`) has also not been disabled in production and works fine (tested on tin.eqiad.wmnet).
+
+The .git directory itself is not excluded from our deployment scripts. Though partial syncs using sync-dir or sync-file will naturally not sync the .git directory, when using scap or sync-dir on an extension directory, it will be updated just fine.
+
+And, in fact, [[Special:Version]] does show a git hash (maybe not the best one, but it does show something).
+
+It doesn't work for extensions because the git data is stored in mediawiki-core (e.g. mediawiki-core/extensions/VisualEditor/.git is a placeholder file with a pointer to mediawiki-core/.git/modules/extensions/VisualEditor), and the pointer is hardcoded to the location of the working copy on tin, namely /a/common/php-1.22wmf16, which doesn't exist on apaches.
+
+For example:
+
+krinkle@mw1017:/apache/common/php-1.22wmf16/extensions/VisualEditor$ git show
+
+fatal: Not a git repository: /a/common/php-1.22wmf16/.git/modules/extensions/VisualEditor
+
+krinkle@mw1017:/apache/common/php-1.22wmf16/extensions/VisualEditor$ cat .git
+
+gitdir: /a/common/php-1.22wmf16/.git/modules/extensions/VisualEditor
+
+
+I'm not sure whether the resemblance of /a and /apache is a coincendence or whether one is intended to be a shortcut of the other. Either way, it seems fairly trivial to make this work.
+
+I'm not sure what the semantic meaning is of these directories (/a/ seems to be an existing but unused directory on all hosts other than tin).
+
+Depending on whether it is really empty we should probably just create a symlink from /a to /apache on all machines that have /apache (except for tin), or if /a is used for other stuff, put symlink inside and have one from /a/common to /apache/common (except for tin).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=36271",task_description,"['[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link\n\nThe VisualEditor UI has an interface to check what version is currently deployed (similar to Special:Version), when asking around people seemed to assume that this has been disabled purposely on the cluster.', 'However this does not seem to be true.', 'For one, the configuration around is working perfectly fine.', ""Though the HEAD commit is retreived by MediaWiki's GitInfo class without shell (it just reads from the .git/HEAD file directly), I additionally verified that $wgGitBin (used for calcuating the commit dates with CODE) has also not been disabled in production and works fine (tested on tin.eqiad.wmnet)."", 'The .git directory itself is not excluded from our deployment scripts.', 'Though partial syncs using sync-dir or sync-file will naturally not sync the .git directory, when using scap or sync-dir on an extension directory, it will be updated just fine.', 'And, in fact, [[Special:Version]] does show a git hash (maybe not the best one, but it does show something).', ""It doesn't work for extensions because the git data is stored in mediawiki-core (e.g."", ""mediawiki-core/extensions/VisualEditor/.git is a placeholder file with a pointer to mediawiki-core/.git/modules/extensions/VisualEditor), and the pointer is hardcoded to the location of the working copy on tin, namely /a/common/php-1.22wmf16, which doesn't exist on apaches."", ""For example:\n\nkrinkle@mw1017:/apache/common/php-1.22wmf16/extensions/VisualEditor$ git show\n\nfatal: Not a git repository: /a/common/php-1.22wmf16/.git/modules/extensions/VisualEditor\n\nkrinkle@mw1017:/apache/common/php-1.22wmf16/extensions/VisualEditor$ cat .git\n\ngitdir: /a/common/php-1.22wmf16/.git/modules/extensions/VisualEditor\n\n\nI'm not sure whether the resemblance of /a and /apache is a coincendence or whether one is intended to be a shortcut of the other."", 'Either way, it seems fairly trivial to make this work.', ""I'm not sure what the semantic meaning is of these directories (/a/ seems to be an existing but unused directory on all hosts other than tin)."", 'Depending on whether it is really empty we should probably just create a symlink from /a to /apache on all machines that have /apache (except for tin), or if /a is used for other stuff, put symlink inside and have one from /a/common to /apache/common (except for tin).', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250369,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 142320 merged by jenkins-bot:
+Set wgGitInfoCacheDirectory to point to scap managed location
+
+https://gerrit.wikimedia.org/r/142320",task_subcomment,['Change 142320 merged by jenkins-bot:\nSet wgGitInfoCacheDirectory to point to scap managed location\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250366,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Yay, thanks Bryan.",task_subcomment,"['Yay, thanks Bryan.']",['ACTION ON ISSUE']
+250361,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 142319 merged by jenkins-bot:
+Fix GitInfo cache file path computation and storage location
+
+https://gerrit.wikimedia.org/r/142319",task_subcomment,['Change 142319 merged by jenkins-bot:\nFix GitInfo cache file path computation and storage location\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+250355,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 142320 had a related patch set uploaded by Krinkle:
+Set wgGitInfoCacheDirectory to point to scap managed location
+
+https://gerrit.wikimedia.org/r/142320",task_subcomment,['Change 142320 had a related patch set uploaded by Krinkle:\nSet wgGitInfoCacheDirectory to point to scap managed location\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250350,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 142319 had a related patch set uploaded by BryanDavis:
+Fix GitInfo cache file path computation and storage location
+
+https://gerrit.wikimedia.org/r/142319",task_subcomment,['Change 142319 had a related patch set uploaded by BryanDavis:\nFix GitInfo cache file path computation and storage location\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250344,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","(In reply to Bryan Davis from comment #18)
+> I'll spend some more time looking into why $IP isn't what I
+> (and the paths inside $wgExtensionCredits) think it should be.
+
+Today I learned that WebStart.php clears $IP and then recreates it from the first of the MW_INSTALL_PATH environment variable, `realpath( '.' )` or `dirname( __DIR__ )`. In beta, the realpath branch wins and sets $IP to '/srv/common-local/php-master'.",task_subcomment,"['(In reply to Bryan Davis from comment #18)\nQUOTE\nQUOTE\n\nToday I learned that WebStart.php clears $IP and then recreates it from the first of the MW_INSTALL_PATH environment variable, CODE or CODE.', ""In beta, the realpath branch wins and sets $IP to '/srv/common-local/php-master'.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250338,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link",So when I echo $IP from `mweval` in beta I get /srv/common-local/php-master but apparently inside Apache $IP is /usr/local/apache/common-local/php-master. The latter is a symlink to former. This difference is causing GitInfo::getCacheFilePath() to compute the wrong path for the cache file. I'll spend some more time looking into why $IP isn't what I (and the paths inside $wgExtensionCredits) think it should be.,task_subcomment,"['So when I echo $IP from CODE in beta I get /srv/common-local/php-master but apparently inside Apache $IP is /usr/local/apache/common-local/php-master.', 'The latter is a symlink to former.', 'This difference is causing GitInfo::getCacheFilePath() to compute the wrong path for the cache file.', ""I'll spend some more time looking into why $IP isn't what I (and the paths inside $wgExtensionCredits) think it should be.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+250332,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","I'm looking into this again and still can't figure out why http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version isn't displaying the git SHA1 for extensions now.
+
+Debugging using `mwscript eval.php --wiki=enwiki` on deployment-apache01 and deployment-apache02 shows that GitInfo can read the precomputed git information there:
+
+    > $wgDebugLogGroups = array(); $wgDebugLogFile = 'php://stdout';
+    > $gitinfo = new GitInfo($IP); $coreId = $gitinfo->getHeadSHA1();
+    > $cache = wfGetCache( CACHE_ANYTHING );
+    > $path = ""$IP/extensions/VisualEditor/VisualEditor.php"";
+    > $memcKey = wfMemcKey( 'specialversion-ext-version-text', $path, $coreId );
+    > echo $memcKey;
+    enwiki:specialversion-ext-version-text:/srv/common-local/php-master/extensions/VisualEditor/VisualEditor.php:49952a405014c89b239da3bcaea158c47faf8251
+    > var_dump( $cache->get( $memcKey ) );
+    enwiki-bca38539: 649.4035  25.8M  [memcached] get(enwiki:specialversion-ext-version-text:/srv/common-local/php-master/extensions/VisualEditor/VisualEditor.php:49952a405014c89b239da3bcaea158c47faf8251)
+    enwiki-bca38539: 649.4047  25.8M  [memcached] result: NOT FOUND
+    bool(false)
+
+    > $gitinfo = new GitInfo( dirname( $path ) );
+    > echo $gitinfo->getHeadSHA1();
+    fefd3a5d72c118993cc555f0a53a561f58a5fd19
+    > echo $gitinfo->getHeadViewUrl();
+    https://git.wikimedia.org/commit/mediawiki%2Fextensions%2FVisualEditor.git/fefd3a5d72c118993cc555f0a53a561f58a5fd19
+    > echo $gitinfo->getHeadCommitDate();
+    1400528579
+
+I've verified that apache is running as the user ""apache"" on these nodes and that apache can read the *info.json files. The output of `eval.php` above shows that the php code is functional when executed from the cli. At this point I'm unable to understand why this output differs from SpecialVersion::getCreditsForExtension(). I'm sure I'm missing something in my analysis but I'm at a loss for what it is.",task_subcomment,"[""I'm looking into this again and still can't figure out why URL isn't displaying the git SHA1 for extensions now."", 'Debugging using CODE on deployment-apache01 and deployment-apache02 shows that GitInfo can read the precomputed git information there:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n    enwiki:specialversion-ext-version-text:/srv/common-local/php-master/extensions/VisualEditor/VisualEditor.php:49952a405014c89b239da3bcaea158c47faf8251\nQUOTE\n    enwiki-bca38539: 649.4035  25.8M  [memcached] get(enwiki:specialversion-ext-version-text:/srv/common-local/php-master/extensions/VisualEditor/VisualEditor.php:49952a405014c89b239da3bcaea158c47faf8251)\n    enwiki-bca38539: 649.4047  25.8M  [memcached] result: NOT FOUND\n    bool(false)\n\nQUOTE\nQUOTE\n    fefd3a5d72c118993cc555f0a53a561f58a5fd19\nQUOTE\n    URL\nQUOTE\n    1400528579\n\nI\'ve verified that apache is running as the user ""apache"" on these nodes and that apache can read the *info.json files.', 'The output of CODE above shows that the php code is functional when executed from the cli.', ""At this point I'm unable to understand why this output differs from SpecialVersion::getCreditsForExtension()."", ""I'm sure I'm missing something in my analysis but I'm at a loss for what it is.""]","['OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250326,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link",Still not seeing data in Special:Version. There must be something that I'm not understanding about the environment. I can get the info via eval.php as shown above.,task_subcomment,"['Still not seeing data in Special:Version.', ""There must be something that I'm not understanding about the environment."", 'I can get the info via eval.php as shown above.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250320,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","I put a temporary hack in place on the beta nodes that run MediaWiki (apache0[12], jobrunner01, and videoscaler01) by symlinking $wgCacheDirectory/gitinfo to $IP/cache/gitinfo. This should make the git version data visible on the Special:Version page the next time that the MW-Core hash changes (memcache cache buster).
+
+    deployment-apache01:~
+    bd808$ mwscript eval.php --wiki=enwiki
+    > var_dump( $gi = new GitInfo( ""$IP/extensions/VisualEditor"" ) );
+    object(GitInfo)#113 (3) {
+      [""basedir"":protected]=>
+      NULL
+      [""cacheFile"":protected]=>
+      string(62) ""/tmp/mw-cache-master/gitinfo/info-extensions-VisualEditor.json""
+      [""cache"":protected]=>
+      array(6) {
+        [""head""]=>
+        string(40) ""0496bd84506927039958cc683a35a5e3b5da2584""
+        [""remoteURL""]=>
+        string(70) ""https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git""
+        [""branch""]=>
+        string(40) ""0496bd84506927039958cc683a35a5e3b5da2584""
+        [""headCommitDate""]=>
+        string(10) ""1399417572""
+        [""headSHA1""]=>
+        string(40) ""0496bd84506927039958cc683a35a5e3b5da2584""
+        [""@directory""]=>
+        string(44) ""/a/common/php-master/extensions/VisualEditor""
+      }
+    }",task_subcomment,"['I put a temporary hack in place on the beta nodes that run MediaWiki (apache0[12], jobrunner01, and videoscaler01) by symlinking $wgCacheDirectory/gitinfo to $IP/cache/gitinfo.', 'This should make the git version data visible on the Special:Version page the next time that the MW-Core hash changes (memcache cache buster).', 'deployment-apache01:~\n    bd808$ mwscript eval.php --wiki=enwiki\nQUOTE\n    object(GitInfo)#113 (3) {\n      [""basedir"":protected]=>\n      NULL\n      [""cacheFile"":protected]=>\n      string(62) ""/tmp/mw-cache-master/gitinfo/info-extensions-VisualEditor.json""\n      [""cache"":protected]=>\n      array(6) {\n        [""head""]=>\n        string(40) ""0496bd84506927039958cc683a35a5e3b5da2584""\n        [""remoteURL""]=>\n        string(70) ""URL\n        [""branch""]=>\n        string(40) ""0496bd84506927039958cc683a35a5e3b5da2584""\n        [""headCommitDate""]=>\n        string(10) ""1399417572""\n        [""headSHA1""]=>\n        string(40) ""0496bd84506927039958cc683a35a5e3b5da2584""\n        [""@directory""]=>\n        string(44) ""/a/common/php-master/extensions/VisualEditor""\n      }\n    }']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+250315,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Patches are merged, but not sufficient. I didn't look into the value of $wgCacheDirectory in operations/mediawiki-config.git. In beta and the prod cluster we set the cache directory to a location outside of $IP rather than $IP/cache as I expected/coded the scap side to this change for.
+
+I'll either need to add a new global to set/change the location where GitInfo looks for the cache or add yet another scap step to copy the generated files around to adjust for this.",task_subcomment,"['Patches are merged, but not sufficient.', ""I didn't look into the value of $wgCacheDirectory in operations/mediawiki-config.git."", 'In beta and the prod cluster we set the cache directory to a location outside of $IP rather than $IP/cache as I expected/coded the scap side to this change for.', ""I'll either need to add a new global to set/change the location where GitInfo looks for the cache or add yet another scap step to copy the generated files around to adjust for this.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+250310,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 130560 merged by jenkins-bot:
+Precompute data for GitInfo
+
+https://gerrit.wikimedia.org/r/130560",task_subcomment,['Change 130560 merged by jenkins-bot:\nPrecompute data for GitInfo\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+250306,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 130498 merged by jenkins-bot:
+Support precomputed data in GitInfo
+
+https://gerrit.wikimedia.org/r/130498",task_subcomment,['Change 130498 merged by jenkins-bot:\nSupport precomputed data in GitInfo\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+250302,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 130560 had a related patch set uploaded by BryanDavis:
+Precompute data for GitInfo
+
+https://gerrit.wikimedia.org/r/130560",task_subcomment,['Change 130560 had a related patch set uploaded by BryanDavis:\nPrecompute data for GitInfo\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+250301,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Change 130498 had a related patch set uploaded by BryanDavis:
+Support precomputed data in GitInfo
+
+https://gerrit.wikimedia.org/r/130498",task_subcomment,['Change 130498 had a related patch set uploaded by BryanDavis:\nSupport precomputed data in GitInfo\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+250299,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link",I'm working on a fix for this problem by adding a step to scap that precomputes the information needed by GitInfo.php to json files that can be synced to the apaches. This would fix the path change issue and should slightly reduce runtime cost of Special:Version and other pages that use GitInfo. It would also allow us to drop syncing of the .git directories all together if we wanted.,task_subcomment,"[""I'm working on a fix for this problem by adding a step to scap that precomputes the information needed by GitInfo.php to json files that can be synced to the apaches."", 'This would fix the path change issue and should slightly reduce runtime cost of Special:Version and other pages that use GitInfo.', 'It would also allow us to drop syncing of the .git directories all together if we wanted.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250297,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","(In reply to Bryan Davis from comment #2)
+> I can't find any reason by grepping in operations/puppet that the general
+> mw* nodes would have /a and/or /a/common created but /a/common exists as an
+> empty directory on all of them that I randomly sampled.
+
+I eventually found the puppet code that creates /a/common as an empty directory on many hosts. The misc::deployment::vars class which in included from the misc::deployment::scap_scripts class creates the directory if it doesn't exist [0].
+
+[0]: https://github.com/wikimedia/operations-puppet/blob/c5b8fa0631d3b28b6ca062e313b98e80d7325d80/manifests/misc/deployment.pp#L368-L374",task_subcomment,"['(In reply to Bryan Davis from comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nI eventually found the puppet code that creates /a/common as an empty directory on many hosts.', ""The misc::deployment::vars class which in included from the misc::deployment::scap_scripts class creates the directory if it doesn't exist [0]."", '[0]: URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250291,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","(In reply to James Forrester from comment #6)
+> Could we just have scap re-write the .git files (or have them be relative
+> and not absolute in the first place)?
+
+Having them be relative in the first place would really be nicest. Do we have a git guru who could look into that?
+
+I had the same idea about rewriting the .git files as a scap step. It shouldn't be too hard to do. Because of the way that scap works right now we'd need to do this on each host as a post-update step similarly to the way that the l10n JSON intermediate files are recompiled into CDB files.",task_subcomment,"['(In reply to James Forrester from comment #6)\nQUOTE\nQUOTE\n\nHaving them be relative in the first place would really be nicest.', 'Do we have a git guru who could look into that?', 'I had the same idea about rewriting the .git files as a scap step.', ""It shouldn't be too hard to do."", ""Because of the way that scap works right now we'd need to do this on each host as a post-update step similarly to the way that the l10n JSON intermediate files are recompiled into CDB files.""]","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250285,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link",Could we just have scap re-write the .git files (or have them be relative and not absolute in the first place)?,task_subcomment,['Could we just have scap re-write the .git files (or have them be relative and not absolute in the first place)?'],['SOLUTION DISCUSSION']
+250278,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","This bug affects the beta environment now that scap is being used to deploy code there. The ideas for creating symlinks to restore the scame directory structure that is used on the deploy host (deployment-bastion.eqiad.wfmlabs) make even less sense in beta. Here's an example .git file from an extension there:
+
+    gitdir: /mnt/srv/scap-stage-dir/php-master/extensions/.git/modules/MultimediaViewer",task_subcomment,"['This bug affects the beta environment now that scap is being used to deploy code there.', 'The ideas for creating symlinks to restore the scame directory structure that is used on the deploy host (deployment-bastion.eqiad.wfmlabs) make even less sense in beta.', ""Here's an example .git file from an extension there:\n\n    gitdir: /mnt/srv/scap-stage-dir/php-master/extensions/.git/modules/MultimediaViewer""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+250273,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link",*** Bug 62760 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 62760 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250269,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link",*** Bug 53070 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53070 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250264,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","(In reply to Krinkle from comment #0)
+> I'm not sure what the semantic meaning is of these directories (/a/ seems to
+> be an existing but unused directory on all hosts other than tin).
+
+/a/common is the rsync server source directory on tin for scap. This directory is used to prepare the files that will be pushed out by scap to the members of the /etc/dsh/group/scap-proxies group and then subsequently to the rest of the cluster.
+
+The misc::deployment::vars puppet class ensures that this directory is created on all hosts where the misc::deployment::scap_scripts puppet class is applied. The misc::deployment::scap_scripts class is applied directly to arsenic, hume, terbium, and tin in site.pp. It's also applied indirectly on the snapshot* servers by the mediawiki::sync class.
+
+I can't find any reason by grepping in operations/puppet that the general mw* nodes would have /a and/or /a/common created but /a/common exists as an empty directory on all of them that I randomly sampled. It seems like it should be possible to add some puppet config (maybe in role::applicationserver::webserver?) to ensure that the /a directory is created and then symlink /a/common to /usr/local/apache/common.",task_subcomment,"['(In reply to Krinkle from comment #0)\nQUOTE\nQUOTE\n\n/a/common is the rsync server source directory on tin for scap.', 'This directory is used to prepare the files that will be pushed out by scap to the members of the /etc/dsh/group/scap-proxies group and then subsequently to the rest of the cluster.', 'The misc::deployment::vars puppet class ensures that this directory is created on all hosts where the misc::deployment::scap_scripts puppet class is applied.', 'The misc::deployment::scap_scripts class is applied directly to arsenic, hume, terbium, and tin in site.pp.', ""It's also applied indirectly on the snapshot* servers by the mediawiki::sync class."", ""I can't find any reason by grepping in operations/puppet that the general mw* nodes would have /a and/or /a/common created but /a/common exists as an empty directory on all of them that I randomly sampled."", 'It seems like it should be possible to add some puppet config (maybe in role::applicationserver::webserver?)', 'to ensure that the /a directory is created and then symlink /a/common to /usr/local/apache/common.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+250258,"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","(In reply to comment #0)
+> I'm not sure what the semantic meaning is of these directories (/a/ seems to
+> be
+> an existing but unused directory on all hosts other than tin).
+
+fluorine",task_subcomment,['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nfluorine'],['OBSERVED BUG BEHAVIOR']
+55895,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"On translatewiki.net during running repoupdate script: Randomly the script bails out with
+
+hash mismatch
+key_verify failed for server_host_key
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+
+This happens since migration of Gerrit to the new server two days ago.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",task_description,"[""Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch'\n\nOn translatewiki.net during running repoupdate script: Randomly the script bails out with\n\nhash mismatch\nkey_verify failed for server_host_key\nfatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n\nThis happens since migration of Gerrit to the new server two days ago."", '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246115,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"(In reply to christian from comment #28)
+> Since this bug has been around for a while and has affected quite some
+> people, I've been asked to give a short explanation of the root issue
+> and what SSHD-330 does.
+> 
+> Gerrit uses Apache Mina's SSHD [1] as ssh server. When connecting to
+> gerrit through ssh, this ssh server uses Java's own crypto/security
+> implementations to negotiate session keys (i.e.: different for each
+> connection attempt) with the client. Java's default provider yielded
+> those session keys without leading zero bytes, and Apache Mina's SSHD
+> relied on no leading zero bytes being present.
+> 
+> But at some point Java [2] changed behaviour and is no longer
+> stripping leading zero bytes, but Apache Mina SSHD still relied on no
+> leading zero bytes being present. Hence assumptions mismatched and
+> caused the issue.
+> 
+> The Java we use at gerrit.wikimedia.org is recent enough to no longer
+> strip leading zero bytes. So when connecting to our gerrit through
+> ssh, either
+> 
+> * the negotiated session key starts with a non-zero byte, and
+>   everything works nicely. This case happens most of the time.
+> 
+> * the negotiated session key starts with a zero byte. Then gerrit's
+>   built-in Apache Mina SSHD falsely treats the key as if there were no
+>   leading zero bytes and the connection setup with the client fails.
+> 
+> SSHD-330 adds stripping of leading zero bytes from the session key to
+> Apache Mina SSHD and thereby fixes the issue we are seeing.
+> 
+> ------
+> 
+> There was recently some FUD around OpenSSL generated keys not being
+> affected. That did not work for me, and I do not see in code how this
+> would make a difference.
+> 
+> Also, there was some recent discussion around extracting the keys from
+> the keystore to proper files. I did not get a chance to try that, but
+> that could do the trick too ... indirectly.
+> Because in order to get gerrit to use keys from separate files, one
+> needs to install BouncyCastle libraries to gerrit. BouncyCastle will
+> act as provider for the needed security/crypto functionality and
+> get used instead of Java's default providers. As the BouncyCastle
+> providers (for now) also strip the leading zero bytes, that could
+> work out.
+> 
+> Regardless, having Apache Mina SSHD to strip leading zero bytes seems
+> most reliable, so we backported the Apache Mina SSHD's upstream fix to
+> the version used in our gerrit, and rebuilt gerrit using that custom
+> built Apache Mina SSHD.
+> 
+> [1] https://mina.apache.org/sshd-project/
+> [2] I know that OpenJDK versions up to
+>   OpenJDK Runtime Environment (IcedTea7 2.2.1) (Gentoo build 1.7.0_05-b21)
+> work and the default providers strip the leading zeros, while the ones from
+>   OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1~0.12.04.2)
+> do not strip them.
+> 
+> 
+> Thanks Krinkle for the pointer to SSHD-330!
+
+And thank you for the analysis and the informative summary -- well done!",task_subcomment,['(In reply to christian from comment #28)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAnd thank you for the analysis and the informative summary -- well done!'],['ACTION ON ISSUE']
+246109,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',<3,task_subcomment,['<3'],['OBSERVED BUG BEHAVIOR']
+246101,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',The fix has been deployed at gerrit.wikimedia.org.,task_subcomment,['The fix has been deployed at gerrit.wikimedia.org.'],['ACTION ON ISSUE']
+246093,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Change 143388 merged by Chad:
+Upgrade sshd to include the fix for hash mismatch
+
+https://gerrit.wikimedia.org/r/143388",task_subcomment,['Change 143388 merged by Chad:\nUpgrade sshd to include the fix for hash mismatch\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+246086,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Since this bug has been around for a while and has affected quite some
+people, I've been asked to give a short explanation of the root issue
+and what SSHD-330 does.
+
+Gerrit uses Apache Mina's SSHD [1] as ssh server. When connecting to
+gerrit through ssh, this ssh server uses Java's own crypto/security
+implementations to negotiate session keys (i.e.: different for each
+connection attempt) with the client. Java's default provider yielded
+those session keys without leading zero bytes, and Apache Mina's SSHD
+relied on no leading zero bytes being present.
+
+But at some point Java [2] changed behaviour and is no longer
+stripping leading zero bytes, but Apache Mina SSHD still relied on no
+leading zero bytes being present. Hence assumptions mismatched and
+caused the issue.
+
+The Java we use at gerrit.wikimedia.org is recent enough to no longer
+strip leading zero bytes. So when connecting to our gerrit through
+ssh, either
+
+* the negotiated session key starts with a non-zero byte, and
+  everything works nicely. This case happens most of the time.
+
+* the negotiated session key starts with a zero byte. Then gerrit's
+  built-in Apache Mina SSHD falsely treats the key as if there were no
+  leading zero bytes and the connection setup with the client fails.
+
+SSHD-330 adds stripping of leading zero bytes from the session key to
+Apache Mina SSHD and thereby fixes the issue we are seeing.
+
+------
+
+There was recently some FUD around OpenSSL generated keys not being
+affected. That did not work for me, and I do not see in code how this
+would make a difference.
+
+Also, there was some recent discussion around extracting the keys from
+the keystore to proper files. I did not get a chance to try that, but
+that could do the trick too ... indirectly.
+Because in order to get gerrit to use keys from separate files, one
+needs to install BouncyCastle libraries to gerrit. BouncyCastle will
+act as provider for the needed security/crypto functionality and
+get used instead of Java's default providers. As the BouncyCastle
+providers (for now) also strip the leading zero bytes, that could
+work out.
+
+Regardless, having Apache Mina SSHD to strip leading zero bytes seems
+most reliable, so we backported the Apache Mina SSHD's upstream fix to
+the version used in our gerrit, and rebuilt gerrit using that custom
+built Apache Mina SSHD.
+
+[1] https://mina.apache.org/sshd-project/
+[2] I know that OpenJDK versions up to
+  OpenJDK Runtime Environment (IcedTea7 2.2.1) (Gentoo build 1.7.0_05-b21)
+work and the default providers strip the leading zeros, while the ones from
+  OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1~0.12.04.2)
+do not strip them.
+
+
+Thanks Krinkle for the pointer to SSHD-330!",task_subcomment,"[""Since this bug has been around for a while and has affected quite some\npeople, I've been asked to give a short explanation of the root issue\nand what SSHD-330 does."", ""Gerrit uses Apache Mina's SSHD [1] as ssh server."", ""When connecting to\ngerrit through ssh, this ssh server uses Java's own crypto/security\nimplementations to negotiate session keys (i.e."", ': different for each\nconnection attempt) with the client.', ""Java's default provider yielded\nthose session keys without leading zero bytes, and Apache Mina's SSHD\nrelied on no leading zero bytes being present."", 'But at some point Java [2] changed behaviour and is no longer\nstripping leading zero bytes, but Apache Mina SSHD still relied on no\nleading zero bytes being present.', 'Hence assumptions mismatched and\ncaused the issue.', 'The Java we use at gerrit.wikimedia.org is recent enough to no longer\nstrip leading zero bytes.', 'So when connecting to our gerrit through\nssh, either\n\n* the negotiated session key starts with a non-zero byte, and\n  everything works nicely.', 'This case happens most of the time.', '* the negotiated session key starts with a zero byte.', ""Then gerrit's\n  built-in Apache Mina SSHD falsely treats the key as if there were no\n  leading zero bytes and the connection setup with the client fails."", 'SSHD-330 adds stripping of leading zero bytes from the session key to\nApache Mina SSHD and thereby fixes the issue we are seeing.', '------\n\nThere was recently some FUD around OpenSSL generated keys not being\naffected.', 'That did not work for me, and I do not see in code how this\nwould make a difference.', 'Also, there was some recent discussion around extracting the keys from\nthe keystore to proper files.', 'I did not get a chance to try that, but\nthat could do the trick too ... indirectly.', 'Because in order to get gerrit to use keys from separate files, one\nneeds to install BouncyCastle libraries to gerrit.', ""BouncyCastle will\nact as provider for the needed security/crypto functionality and\nget used instead of Java's default providers."", 'As the BouncyCastle\nproviders (for now) also strip the leading zero bytes, that could\nwork out.', ""Regardless, having Apache Mina SSHD to strip leading zero bytes seems\nmost reliable, so we backported the Apache Mina SSHD's upstream fix to\nthe version used in our gerrit, and rebuilt gerrit using that custom\nbuilt Apache Mina SSHD."", '[1] URL\n[2] I know that OpenJDK versions up to\n  OpenJDK Runtime Environment (IcedTea7 2.2.1) (Gentoo build 1.7.0_05-b21)\nwork and the default providers strip the leading zeros, while the ones from\n  OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1~0.12.04.2)\ndo not strip them.', 'Thanks Krinkle for the pointer to SSHD-330!']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+246077,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"I have upgraded Gerrit on my test instance integration-dev.eqiad.wmflabs . There is no more any hash mismatch triggered when running for a while:
+
+while true; do ssh -p 29418 localhost; done;",task_subcomment,"['I have upgraded Gerrit on my test instance integration-dev.eqiad.wmflabs .', 'There is no more any hash mismatch triggered when running for a while:\n\nwhile true; do ssh -p 29418 localhost; done;']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246068,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"(In reply to Antoine ""hashar"" Musso from comment #25)
+> Christian could you possibly providee a gerrit.war  that has the patch ?
+
+Sure. For the next 2 weeks, you can fetch it from
+
+  http://quelltextlich.at/gerrit-2.8.1-4-ga1048ce.war
+
+> I
+> would like to test it out on the labs instance I am using for CI dev.
+
+Seeing the description of SSHD-330 allowed me to come up with an environment
+that allows to reproduce the bug. There, our deployed gerrit war failed for
+14 of 10000 connection attempts. The war I linked above showed 0 failures for
+10000 connection attempts.
+
+^d already said he'll discuss deploying the war with greg-g. So we'll
+hopefully see it live soon.",task_subcomment,"['(In reply to Antoine ""hashar"" Musso from comment #25)\nQUOTE\n\nSure.', 'For the next 2 weeks, you can fetch it from\n\n  URL\n\nQUOTE\nQUOTE\n\nSeeing the description of SSHD-330 allowed me to come up with an environment\nthat allows to reproduce the bug.', 'There, our deployed gerrit war failed for\n14 of 10000 connection attempts.', 'The war I linked above showed 0 failures for\n10000 connection attempts.', ""^d already said he'll discuss deploying the war with greg-g."", ""So we'll\nhopefully see it live soon.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+246058,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Christian could you possibly providee a gerrit.war  that has the patch ? I would like to test it out on the labs instance I am using for CI dev. Thanks!,task_subcomment,"['Christian could you possibly providee a gerrit.war  that has the patch ?', 'I would like to test it out on the labs instance I am using for CI dev.', 'Thanks!']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+246050,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Change 143388 had a related patch set uploaded by QChris:
+Upgrade sshd to include the fix for hash mismatch
+
+https://gerrit.wikimedia.org/r/143388",task_subcomment,['Change 143388 had a related patch set uploaded by QChris:\nUpgrade sshd to include the fix for hash mismatch\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+246041,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"The description of the SSHD-330 issue explains pretty much every aspect of
+the bug that we experienced.
+
+From it's sporadic nature to the ways some people could reproduce, but others
+couldn't.
+
+I'll see to preparing a new gerrit release ... hopefully we can get something
+deployed around that.",task_subcomment,"['The description of the SSHD-330 issue explains pretty much every aspect of\nthe bug that we experienced.', ""From it's sporadic nature to the ways some people could reproduce, but others\ncouldn't."", ""I'll see to preparing a new gerrit release ... hopefully we can get something\ndeployed around that.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+246035,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"The google group topic mentioned this issue in Apache mina-sshd (upstream from Gerrit):
+
+https://issues.apache.org/jira/browse/SSHD-330
+
+Which has been fixed in https://git-wip-us.apache.org/repos/asf?p=mina-sshd.git;a=commit;h=2aed686bdb21681a421033c6ee5997e5cd8a9a83
+
+If that is indeed the root issue, we them to make a minor release and Gerrit to upgrade to it.",task_subcomment,"['The google group topic mentioned this issue in Apache mina-sshd (upstream from Gerrit):\n\nURL\n\nWhich has been fixed in URL\n\nIf that is indeed the root issue, we them to make a minor release and Gerrit to upgrade to it.']",['INVESTIGATION AND EXPLORATION']
+246030,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"**paul.bourke** wrote:
+
+Hi, I've been able to reproduce this on a local Gerrit instance quite reliably by running the following:
+
+while true; do ssh  -p 29418; done
+
+A workaround that does work is to use the bouncy castle SSL library.  See the following thread for more info: https://groups.google.com/forum/#!topic/repo-discuss/JE7OM6o7DMs",task_subcomment,"[""**paul.bourke** wrote:\n\nHi, I've been able to reproduce this on a local Gerrit instance quite reliably by running the following:\n\nwhile true; do ssh  -p 29418; done\n\nA workaround that does work is to use the bouncy castle SSL library."", 'See the following thread for more info: URL']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+246027,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Bartosz: there is no need more for more examples.  We have traces of those errors in Zuul log and it happens a couple time per day.
+
+Marcin: we could tcpdump it if only we had a way to reliably reproduce the issue :-(",task_subcomment,"['Bartosz: there is no need more for more examples.', 'We have traces of those errors in Zuul log and it happens a couple time per day.', 'Marcin: we could tcpdump it if only we had a way to reliably reproduce the issue :-(']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246024,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Two examples from just today:
+* https://gerrit.wikimedia.org/r/#/c/139807/
+* https://gerrit.wikimedia.org/r/#/c/140046/",task_subcomment,['Two examples from just today:\n* URL\n* URL'],['OBSERVED BUG BEHAVIOR']
+246021,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Today again: https://gerrit.wikimedia.org/r/#/c/139047/,task_subcomment,['Today again: URL'],['OBSERVED BUG BEHAVIOR']
+246017,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Could somebody tcpdump it? It seems it me more like a broken (suddenly terminated) connection, probably occuring (mostly) early in the SSH negotiation phase.",task_subcomment,"['Could somebody tcpdump it?', 'It seems it me more like a broken (suddenly terminated) connection, probably occuring (mostly) early in the SSH negotiation phase.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246012,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Subsided for a while, then started happening a bit more often for me locally. Example in Gerrit from today: https://gerrit.wikimedia.org/r/#/c/138992/1",task_subcomment,"['Subsided for a while, then started happening a bit more often for me locally.', 'Example in Gerrit from today: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246006,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"This continues to happen, nearly daily.
+
+You could probably get a good list of affected changesets by grepping logs of #wikimedia-dev for my name and ""ignore jenkins"" :/",task_subcomment,"['This continues to happen, nearly daily.', 'You could probably get a good list of affected changesets by grepping logs of #wikimedia-dev for my name and ""ignore jenkins"" :/']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246002,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Another example, this time with the job that sync VisualEditor in mediawiki/extensions.git.  The merge of https://gerrit.wikimedia.org/r/#/c/111608/ triggered job http://integration.wikimedia.org/ci/job/mwext-VisualEditor-sync-gerrit/61/console which shows:
+
+  ssh -i /var/lib/jenkins/.ssh/jenkins-mwext-sync_id_rsa \
+    -p 29418 jenkins-mwext-sync@gerrit.wikimedia.org \
+    'gerrit review --code-review +2 --verified +2 --submit b519550809bba725b017281fe6c33c4c2fd123c1'
+  hash mismatch
+  key_verify failed for server_host_key",task_subcomment,"['Another example, this time with the job that sync VisualEditor in mediawiki/extensions.git.', ""The merge of URL triggered job URL which shows:\n\n  ssh -i /var/lib/jenkins/.ssh/jenkins-mwext-sync_id_rsa \\\n    -p 29418 jenkins-mwext-sync@gerrit.wikimedia.org \\\n    'gerrit review --code-review +2 --verified +2 --submit b519550809bba725b017281fe6c33c4c2fd123c1'\n  hash mismatch\n  key_verify failed for server_host_key""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245998,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"(In reply to comment #12)
+> Is this related: https://gerrit.wikimedia.org/r/#/c/107036/ ?
+
+Looking at Zuul debugging log on gallium.wikimedia.org it is a different issue. Filled another bug 59991 for it. Seems to be an issue in the python git module.",task_subcomment,"['(In reply to comment #12)\nQUOTE\n\nLooking at Zuul debugging log on gallium.wikimedia.org it is a different issue.', 'Filled another bug 59991 for it.', 'Seems to be an issue in the python git module.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+245994,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Is this related: https://gerrit.wikimedia.org/r/#/c/107036/ ?,task_subcomment,['Is this related: URL ?'],['OBSERVED BUG BEHAVIOR']
+245992,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Also got one today in command line.
+
+FYI: the -1s in Jenkins caused by this are very confusing.",task_subcomment,"['Also got one today in command line.', 'FYI: the -1s in Jenkins caused by this are very confusing.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245990,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"That does happen once or two per day on Zuul. Usually ""hash mismatch"" errors though we had some host key verification failed on Nov 20th.",task_subcomment,"['That does happen once or two per day on Zuul.', 'Usually ""hash mismatch"" errors though we had some host key verification failed on Nov 20th.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245988,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',*** Bug 57483 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 57483 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245985,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"(In reply to comment #7)
+> Just happened to me w/operations/puppet.
+> 
+> $ git pull
+> hash mismatch
+> key_verify failed for server_host_key
+> fatal: Could not read from remote repository.
+> 
+> Please make sure you have the correct access rights
+> and the repository exists.
+
+We see similar errors very regularly when updating 600 or so extension repos at translatewiki.net. I'm pretty certain that we have the correct access rights with L10n-bot, have the correct access rights at the local machine, and have consistent scripting up update the repos.
+
+A run I did just now resulted in the following errors:
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+/resources/siebrand/mediawiki-extensions/extensions/CategoryMagicWords failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+/resources/siebrand/mediawiki-extensions/extensions/ReplaceSet failed to update
+
+Just to make sure that it wasn't me configuring the two above repos incorrectly, I ran the updates again. This time with the following result:
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+/resources/siebrand/mediawiki-extensions/extensions/DidYouKnow failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch gerrit
+/resources/siebrand/mediawiki-extensions/extensions/FormatDates failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch gerrit
+/resources/siebrand/mediawiki-extensions/extensions/GoogleDocTag failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+/resources/siebrand/mediawiki-extensions/extensions/InviteSignup failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+/resources/siebrand/mediawiki-extensions/extensions/LightweightRDFa failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch gerrit
+/resources/siebrand/mediawiki-extensions/extensions/Numbertext failed to update
+
+/resources/siebrand/mediawiki-extensions/extensions/NumberOfWikis failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch gerrit
+/resources/siebrand/mediawiki-extensions/extensions/PageLanguage failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch origin
+/resources/siebrand/mediawiki-extensions/extensions/SidebarDonateBox failed to update
+
+hash mismatch
+key_verify failed for server_host_key
+fatal: The remote end hung up unexpectedly
+error: Could not fetch gerrit
+/resources/siebrand/mediawiki-extensions/extensions/UserStatus failed to update
+
+Permission denied (publickey).
+fatal: The remote end hung up unexpectedly
+error: Could not fetch gerrit
+/resources/siebrand/mediawiki-extensions/extensions/VersionView failed to update
+
+
+
+To compare, when updating repos on localhost form GitHub, I've not seen a similar error once.",task_subcomment,"['(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe see similar errors very regularly when updating 600 or so extension repos at translatewiki.net.', ""I'm pretty certain that we have the correct access rights with L10n-bot, have the correct access rights at the local machine, and have consistent scripting up update the repos."", 'A run I did just now resulted in the following errors:\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n/resources/siebrand/mediawiki-extensions/extensions/CategoryMagicWords failed to update\n\nPermission denied (publickey).', ""fatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n/resources/siebrand/mediawiki-extensions/extensions/ReplaceSet failed to update\n\nJust to make sure that it wasn't me configuring the two above repos incorrectly, I ran the updates again."", 'This time with the following result:\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n/resources/siebrand/mediawiki-extensions/extensions/DidYouKnow failed to update\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch gerrit\n/resources/siebrand/mediawiki-extensions/extensions/FormatDates failed to update\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch gerrit\n/resources/siebrand/mediawiki-extensions/extensions/GoogleDocTag failed to update\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n/resources/siebrand/mediawiki-extensions/extensions/InviteSignup failed to update\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n/resources/siebrand/mediawiki-extensions/extensions/LightweightRDFa failed to update\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch gerrit\n/resources/siebrand/mediawiki-extensions/extensions/Numbertext failed to update\n\n/resources/siebrand/mediawiki-extensions/extensions/NumberOfWikis failed to update\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch gerrit\n/resources/siebrand/mediawiki-extensions/extensions/PageLanguage failed to update\n\nPermission denied (publickey).', 'fatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n/resources/siebrand/mediawiki-extensions/extensions/SidebarDonateBox failed to update\n\nhash mismatch\nkey_verify failed for server_host_key\nfatal: The remote end hung up unexpectedly\nerror: Could not fetch gerrit\n/resources/siebrand/mediawiki-extensions/extensions/UserStatus failed to update\n\nPermission denied (publickey).', ""fatal: The remote end hung up unexpectedly\nerror: Could not fetch gerrit\n/resources/siebrand/mediawiki-extensions/extensions/VersionView failed to update\n\n\n\nTo compare, when updating repos on localhost form GitHub, I've not seen a similar error once.""]","['MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245981,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Just happened to me w/operations/puppet.
+
+$ git pull
+hash mismatch
+key_verify failed for server_host_key
+fatal: Could not read from remote repository.
+
+Please make sure you have the correct access rights
+and the repository exists.",task_subcomment,"['Just happened to me w/operations/puppet.', '$ git pull\nhash mismatch\nkey_verify failed for server_host_key\nfatal: Could not read from remote repository.', 'Please make sure you have the correct access rights\nand the repository exists.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245975,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',(Worked for me when I tried again),task_subcomment,['(Worked for me when I tried again)'],['BUG REPRODUCTION']
+245968,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"Several reports of this in the last few days. Reporters include Krenair, YuviPanda, and Krinkle.",task_subcomment,"['Several reports of this in the last few days.', 'Reporters include Krenair, YuviPanda, and Krinkle.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245960,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Still seeing this error randomly.,task_subcomment,['Still seeing this error randomly.'],['OBSERVED BUG BEHAVIOR']
+245951,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"(In reply to comment #2)
+> We changed IP addresses when moving servers (shouldn't have to ever happen
+> again), so please check your known_hosts for any outdated entries that you
+> can remove.
+
+How can I identify outdated entries? There are no IP addresses in known_hosts. Sample entry:
+
+ |1|umKi+qzw6pf8uXi/Z6/KtqlisCw=|YFoX/CdDjXhcVUVJ803EiP9nyro= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA2JmNg8ir9QvWwmS/C2k0PEqty1O26D0Nq24YGKC5jq1cr/0a92Pk7wa9FMMM/2O88bbe6rXZUPBKzDX1vVtYD+5vR4/c1XTnHWlNJ9sd6xSYjHhznqYs81VnjGMCLMPV1GhlIfUZsnQ+
+w1FaQUvJe39TEtwADA7ZOFAfT0M/Oqk=",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nHow can I identify outdated entries?', 'There are no IP addresses in known_hosts.', 'Sample entry:\n\n |1|umKi+qzw6pf8uXi/Z6/KtqlisCw=|YFoX/CdDjXhcVUVJ803EiP9nyro= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA2JmNg8ir9QvWwmS/C2k0PEqty1O26D0Nq24YGKC5jq1cr/0a92Pk7wa9FMMM/2O88bbe6rXZUPBKzDX1vVtYD+5vR4/c1XTnHWlNJ9sd6xSYjHhznqYs81VnjGMCLMPV1GhlIfUZsnQ+\nw1FaQUvJe39TEtwADA7ZOFAfT0M/Oqk=']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245945,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',"So, this sounds like you've got an old entry in your known_hosts files pointing to the old box.
+
+We changed IP addresses when moving servers (shouldn't have to ever happen again), so please check your known_hosts for any outdated entries that you can remove.",task_subcomment,"[""So, this sounds like you've got an old entry in your known_hosts files pointing to the old box."", ""We changed IP addresses when moving servers (shouldn't have to ever happen again), so please check your known_hosts for any outdated entries that you can remove.""]","['OBSERVED BUG BEHAVIOR', 'WORKAROUNDS']"
+245939,Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',We retained the same key for exactly this reason...,task_subcomment,['We retained the same key for exactly this reason...'],['SOLUTION DISCUSSION']
+55865,Review and deploy BetaFeatures extension,"The Multimedia team has come up with this framework, wrapped in an extension, for experimental features. It's part of our rollout plan to get it on test2 and mediawiki.org, so we can also start deploying extensions that use its framework.
+
+VisualEditor, Multimedia, Mobile, and E2 are all planning on using this framework in the coming quarter to gate features they aren't ready to release on an opt-out basis.
+
+Please review for security and performance (in particular the update jobs for user counts may be tricky for the latter) and add it to the extensions enabled on mediawiki.org and test2.
+
+Thanks!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Extension:BetaFeatures",task_description,"['Review and deploy BetaFeatures extension\n\nThe Multimedia team has come up with this framework, wrapped in an extension, for experimental features.', ""It's part of our rollout plan to get it on test2 and mediawiki.org, so we can also start deploying extensions that use its framework."", ""VisualEditor, Multimedia, Mobile, and E2 are all planning on using this framework in the coming quarter to gate features they aren't ready to release on an opt-out basis."", 'Please review for security and performance (in particular the update jobs for user counts may be tricky for the latter) and add it to the extensions enabled on mediawiki.org and test2.', 'Thanks!', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['FUTURE PLAN', 'FUTURE PLAN', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+244040,Review and deploy BetaFeatures extension,"We deployed to MediaWiki.org already. We were trying to deploy VectorBeta yesterday, but as you said, it crapped out - hence, bug 55749 stays open but this one got closed (and should have been closed much earlier)",task_subcomment,"['We deployed to MediaWiki.org already.', 'We were trying to deploy VectorBeta yesterday, but as you said, it crapped out - hence, bug 55749 stays open but this one got closed (and should have been closed much earlier)']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+244034,Review and deploy BetaFeatures extension,"Because this was supposed to happen yesterday, but the servers crapped themselves. I think the new deployment date is Monday.",task_subcomment,"['Because this was supposed to happen yesterday, but the servers crapped themselves.', 'I think the new deployment date is Monday.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+244029,Review and deploy BetaFeatures extension,Why is this bug marked fixed?,task_subcomment,['Why is this bug marked fixed?'],['OBSERVED BUG BEHAVIOR']
+244026,Review and deploy BetaFeatures extension,Ready to deploy.,task_subcomment,['Ready to deploy.'],['SOLUTION DISCUSSION']
+244019,Review and deploy BetaFeatures extension,"Adding dependencies - we're not deploying BF until the three listed extensions are also deployable. We're hoping that'll happen by Thursday morning.
+
+AWAY!!!!",task_subcomment,"[""Adding dependencies - we're not deploying BF until the three listed extensions are also deployable."", ""We're hoping that'll happen by Thursday morning."", 'AWAY!!!', '!']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244011,Review and deploy BetaFeatures extension,"Security fixes in https://gerrit.wikimedia.org/r/86023 should close the review portion of this bug - ready for deployment.
+
+We'll discuss deployment strategy after that patch is merged and we have a better idea of what we want out of it.",task_subcomment,"['Security fixes in GERRIT_URL should close the review portion of this bug - ready for deployment.', ""We'll discuss deployment strategy after that patch is merged and we have a better idea of what we want out of it.""]","['ACTION ON ISSUE', 'FUTURE PLAN']"
+244005,Review and deploy BetaFeatures extension,"Design review is done - security review only remaining review.
+
+== TODO/Check list ==
+Extension page on mediawiki.org: yes 
+Bugzilla component: yes
+Extension in Gerrit: yes
+Design Review: yes
+Archeticecture/Performance Review: yes
+Security Review: no
+Screencast (if applicable): N/A
+Community support: I believe so",task_subcomment,"['Design review is done - security review only remaining review.', '== TODO/Check list ==\nExtension page on mediawiki.org: yes \nBugzilla component: yes\nExtension in Gerrit: yes\nDesign Review: yes\nArcheticecture/Performance Review: yes\nSecurity Review: no\nScreencast (if applicable): N/A\nCommunity support: I believe so']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+243999,Review and deploy BetaFeatures extension,"Reedy did architecture/performance review. Chris will be doing security review sometime early next week. Design review is being finalized as we speak.
+
+We'll be rolling this out in tandem with a bunch of other changes, so the deployment won't happen right away, and it will happen in stages (like Notifications, basically).",task_subcomment,"['Reedy did architecture/performance review.', 'Chris will be doing security review sometime early next week.', 'Design review is being finalized as we speak.', ""We'll be rolling this out in tandem with a bunch of other changes, so the deployment won't happen right away, and it will happen in stages (like Notifications, basically).""]","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'FUTURE PLAN']"
+243993,Review and deploy BetaFeatures extension,"Hello, this is a quasi-automated-but-not-really message:
+
+I am reviewing all tracking bugs for extensions to review and deploy to WMF servers. See the list here:
+https://bugzilla.wikimedia.org/showdependencytree.cgi?id=31235&hide_resolved=1
+
+The [[mw:Review queue]] page lists the steps necessary to complete the review. I have copied them below and done some initial filling out based on what I can easily gleen from this bug and any linked to sources that are obvious. If I miss something/state something false, please do correct me.
+
+Also, if you haven't yet done so, please review the information on and linked to from:
+https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment
+
+
+== TODO/Check list ==
+Extension page on mediawiki.org: yes 
+Bugzilla component: yes
+Extension in Gerrit: yes
+Design Review: yes
+Archeticecture/Performance Review: no
+Security Review: no
+Screencast (if applicable): no
+Community support: I believe so",task_subcomment,"['Hello, this is a quasi-automated-but-not-really message:\n\nI am reviewing all tracking bugs for extensions to review and deploy to WMF servers.', 'See the list here:\nURL\n\nThe [[mw:Review queue]] page lists the steps necessary to complete the review.', 'I have copied them below and done some initial filling out based on what I can easily gleen from this bug and any linked to sources that are obvious.', 'If I miss something/state something false, please do correct me.', ""Also, if you haven't yet done so, please review the information on and linked to from:\nURL\n\n\n== TODO/Check list ==\nExtension page on mediawiki.org: yes \nBugzilla component: yes\nExtension in Gerrit: yes\nDesign Review: yes\nArcheticecture/Performance Review: no\nSecurity Review: no\nScreencast (if applicable): no\nCommunity support: I believe so""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE']"
+55836,Commit missing from mediawiki/exentions/MassMessage repo,"https://gerrit.wikimedia.org/r/#/c/82796/ - sha1: 8587e2e4b4f90ca9cdba0f39e647b235921a5ae8
+
+Missing on git.wm.o, gerrit, github:
+
+https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FMassMessage.git
+
+https://github.com/wikimedia/mediawiki-extensions-MassMessage/commits/master 
+
+km-mpb:~ km$ git clone ssh://legoktm@gerrit.wikimedia.org:29418/mediawiki/extensions/MassMessage.git
+Cloning into 'MassMessage'...
+[snipped]
+Checking connectivity... done
+km-mpb:~ km$ cd MassMessage/
+km-mpb:MassMessage km$ git log --oneline
+85283ca Localisation updates from http://translatewiki.net.
+b9ccd1c Autocomplete suggestions for spamlist input
+3027dc6 Localisation updates from http://translatewiki.net.
+8d106e1 Localisation updates from http://translatewiki.net.
+[snipped]
+
+Luckily this is a pretty minor change, so I can re-do it, but it really shouldn't have disappeared in the first place...
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major",task_description,"[""Commit missing from mediawiki/exentions/MassMessage repo\n\nURL - sha1: 8587e2e4b4f90ca9cdba0f39e647b235921a5ae8\n\nMissing on git.wm.o, gerrit, github:\n\nURL\n\nURL \n\nkm-mpb:~ km$ git clone ssh://legoktm@gerrit.wikimedia.org:29418/mediawiki/extensions/MassMessage.git\nCloning into 'MassMessage'...\n[snipped]\nChecking connectivity... done\nkm-mpb:~ km$ cd MassMessage/\nkm-mpb:MassMessage km$ git log --oneline\n85283ca Localisation updates from URL\nb9ccd1c Autocomplete suggestions for spamlist input\n3027dc6 Localisation updates from URL\n8d106e1 Localisation updates from URL\n[snipped]\n\nLuckily this is a pretty minor change, so I can re-do it, but it really shouldn't have disappeared in the first place...\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major""]",['INVESTIGATION AND EXPLORATION']
+242282,Commit missing from mediawiki/exentions/MassMessage repo,"
+
+*** This bug has been marked as a duplicate of bug 53841 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 53841 ***'],['ACTION ON ISSUE']
+242278,Commit missing from mediawiki/exentions/MassMessage repo,"(In reply to comment #7)
+> (In reply to comment #6)
+> > I don't think my issue is the same since the commit is missing from both the
+> > web viewers on git.wm.o and github.
+> > 
+> > I'm not sure I've hardcoded an IP anywhere, I just use gerrit.wikimedia.org
+> > when cloning.
+> 
+> So what happened here was the change was merged without a merge commit. Will
+> require some manual wrangling one way or the other to fix.
+
+Maybe I'm misunderstanding, but the commit was merged just fine. It didn't need a merge commit since at the time, it was directly on top of the current HEAD. It was replicated to github fine, and I pulled locally using my gerrit remote. When the upgrade happened it vanished. At that point, it was missing from gerrit.wm.o, but it was still visible on github, until the l10n-bot updated the translations, off of the HEAD on gerrit, which was (force?) pushed to github and overrode the ""fix typo"" commit.",task_subcomment,"[""(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nMaybe I'm misunderstanding, but the commit was merged just fine."", ""It didn't need a merge commit since at the time, it was directly on top of the current HEAD."", 'It was replicated to github fine, and I pulled locally using my gerrit remote.', 'When the upgrade happened it vanished.', 'At that point, it was missing from gerrit.wm.o, but it was still visible on github, until the l10n-bot updated the translations, off of the HEAD on gerrit, which was (force?)', 'pushed to github and overrode the ""fix typo"" commit.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+242275,Commit missing from mediawiki/exentions/MassMessage repo,"(In reply to comment #6)
+> I don't think my issue is the same since the commit is missing from both the
+> web viewers on git.wm.o and github.
+> 
+> I'm not sure I've hardcoded an IP anywhere, I just use gerrit.wikimedia.org
+> when cloning.
+
+So what happened here was the change was merged without a merge commit. Will require some manual wrangling one way or the other to fix.",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nSo what happened here was the change was merged without a merge commit.', 'Will require some manual wrangling one way or the other to fix.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+242272,Commit missing from mediawiki/exentions/MassMessage repo,"I don't think my issue is the same since the commit is missing from both the web viewers on git.wm.o and github.
+
+I'm not sure I've hardcoded an IP anywhere, I just use gerrit.wikimedia.org when cloning.",task_subcomment,"[""I don't think my issue is the same since the commit is missing from both the web viewers on git.wm.o and github."", ""I'm not sure I've hardcoded an IP anywhere, I just use gerrit.wikimedia.org when cloning.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242268,Commit missing from mediawiki/exentions/MassMessage repo,"To the original reporter: can you confirm the IP address you are using for gerrit.wikimedia.org?  That would let us figure out if you have the same issue I was having, or a different one.",task_subcomment,"['To the original reporter: can you confirm the IP address you are using for gerrit.wikimedia.org?', 'That would let us figure out if you have the same issue I was having, or a different one.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242263,Commit missing from mediawiki/exentions/MassMessage repo,Mea culpa -- my bug (in comment 2) was caused by an out-of-date entry for gerrit.wikimedia.org in my /etc/hosts file.  =(,task_subcomment,"['Mea culpa -- my bug (in comment 2) was caused by an out-of-date entry for gerrit.wikimedia.org in my /etc/hosts file.', '=(']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242258,Commit missing from mediawiki/exentions/MassMessage repo,"(In reply to comment #2)
+> This breakage seems to be a side-effect of the gerrit migration.  For me,
+> 
+> $ git clone
+> https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor
+> $ cd VisualEditor ; git log --oneline -1
+> feff1fb Merge ""Improve welcome dialog support for large fonts""
+> 
+I can't reproduce. I get
+47545a5 Remove no-insertion metadata corner case from `ve.dm.Transaction.pushReplace()`.
+
+as expected.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nI can't reproduce."", 'I get\n47545a5 Remove no-insertion metadata corner case from CODE.', 'as expected.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR']"
+242248,Commit missing from mediawiki/exentions/MassMessage repo,"This breakage seems to be a side-effect of the gerrit migration.  For me,
+
+$ git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor
+$ cd VisualEditor ; git log --oneline -1
+feff1fb Merge ""Improve welcome dialog support for large fonts""
+
+versus
+
+$ git clone https://git.wikimedia.org/git/mediawiki/extensions/VisualEditor.git
+$ cd VisualEditor ; git log --oneline -1
+47545a5 Remove no-insertion metadata corner case from `ve.dm.Transaction.pushReplace()`
+
+
+Note that https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FVisualEditor shows the latter commit, but 'git review -s ; git log gerrit/master' shows the former.",task_subcomment,"['This breakage seems to be a side-effect of the gerrit migration.', 'For me,\n\n$ git clone URL\n$ cd VisualEditor ; git log --oneline -1\nfeff1fb Merge ""Improve welcome dialog support for large fonts""\n\nversus\n\n$ git clone URL\n$ cd VisualEditor ; git log --oneline -1\n47545a5 Remove no-insertion metadata corner case from CODE\n\n\nNote that URL shows the latter commit, but \'git review -s ; git log gerrit/master\' shows the former.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+242238,Commit missing from mediawiki/exentions/MassMessage repo,"Eventhough the WebUI shows the change as having status 'Merged', the
+change cannot be fetched directly:
+
+  git fetch ssh://qchris@gerrit.wikimedia.org:29418/mediawiki/extensions/MassMessage refs/changes/96/82796/1
+  fatal: Couldn't find remote ref refs/changes/96/82796/1",task_subcomment,"[""Eventhough the WebUI shows the change as having status 'Merged', the\nchange cannot be fetched directly:\n\n  git fetch ssh://qchris@gerrit.wikimedia.org:29418/mediawiki/extensions/MassMessage refs/changes/96/82796/1\n  fatal: Couldn't find remote ref refs/changes/96/82796/1""]",['BUG REPRODUCTION']
+55788,VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"*Problem Description: If for spelling correction purposes only few charecters within any word are selected and replaced with other charecter of same or lesser length, without movement of arrow keys or spacebar, save button does not get enabled, so effectively we would not be able to save the change.
+
+**Additional details : Problem was identified when we were trying to reproduce bug 53758, intution is it may be some how indirectly related to bug 53758
+
+
+*Tested Browser and OS =Firefox+Win7
+
+**Were enabled: VisualEditor+ULS Method of input = अक्षरांतरण language=Marathi 
+Script=Devanagari  (Non-VE source edit environ,ULS Method of input = अक्षरांतरण
+works normal)     
+
+Steps to reproduce:
+* Steps to reproduce:
+1. Go to existing page with considerable Marathi Devnagari text may be like
+https://mr.wikipedia.org/wiki/अभिमन्यु
+
+2. Go to माझ्या पसंती (Preferences), संपादन and enable last option:
+यथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this
+enables VisualEditor
+3. Click cog next to इतर भाषांमध्ये
+4. Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण
+
+5. Select any random  marathi word from existing paragraph text 
+
+6.Make the changes in the word by changing alphabate but see that length of the word remains less after the change.
+**Please note do not move arrow keys or spacebar
+
+7 Save button does not apear
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change\n\n*Problem Description: If for spelling correction purposes only few charecters within any word are selected and replaced with other charecter of same or lesser length, without movement of arrow keys or spacebar, save button does not get enabled, so effectively we would not be able to save the change.', '**Additional details : Problem was identified when we were trying to reproduce bug 53758, intution is it may be some how indirectly related to bug 53758\n\n\n*Tested Browser and OS =Firefox+Win7\n\n**Were enabled: VisualEditor+ULS Method of input = अक्षरांतरण language=Marathi \nScript=Devanagari  (Non-VE source edit environ,ULS Method of input = अक्षरांतरण\nworks normal)     \n\nSteps to reproduce:\n* Steps to reproduce:\n1.', 'Go to existing page with considerable Marathi Devnagari text may be like\nURL\n\n2.', 'Go to माझ्या पसंती (Preferences), संपादन and enable last option:\nयथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this\nenables VisualEditor\n3.', 'Click cog next to इतर भाषांमध्ये\n4.', 'Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण\n\n5.', 'Select any random  marathi word from existing paragraph text \n\n6.Make the changes in the word by changing alphabate but see that length of the word remains less after the change.', '**Please note do not move arrow keys or spacebar\n\n7 Save button does not apear\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+239892,VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"Based on your comments, I'm marking this as FIXED - please check, and reopen if it's not!",task_subcomment,"[""Based on your comments, I'm marking this as FIXED - please check, and reopen if it's not!""]",['ACTION ON ISSUE']
+239884,VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"(In reply to comment #4)
+
+*This Test phase seems to have fixed problem on mediawiki.Tested at my user page on mediawiki at https://www.mediawiki.org/wiki/User:Mahitgar now works well
+
+
+*Still to be fixed on rest of the wikis including mr wikipedia   https://mr.wikipedia.org/wiki/अभिमन्यु
+
+Thanks and Regards
+
+-Mahitgar",task_subcomment,['(In reply to comment #4)\n\n*This Test phase seems to have fixed problem on mediawiki.Tested at my user page on mediawiki at URL now works well\n\n\n*Still to be fixed on rest of the wikis including mr wikipedia   URL\n\nThanks and Regards\n\n-Mahitgar'],['BUG REPRODUCTION']
+239880,VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:
+
+https://gerrit.wikimedia.org/r/#/c/82858/
+
+Please let us know whether it fixes the bug!",task_subcomment,"[""There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:\n\nURL\n\nPlease let us know whether it fixes the bug!""]",['BUG REPRODUCTION']
+239873,VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"(In reply to comment #2)
+
+Firefox version- 23.0.1 It gets automatically updated
+
+Rgds",task_subcomment,['(In reply to comment #2)\n\nFirefox version- 23.0.1 It gets automatically updated\n\nRgds'],['OBSERVED BUG BEHAVIOR']
+239865,VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"(In reply to comment #0)
+> *Tested Browser and OS =Firefox+Win7
+
+Please always provide exact version info (your Firefox version).",task_subcomment,['(In reply to comment #0)\nQUOTE\n\nPlease always provide exact version info (your Firefox version).'],['BUG REPRODUCTION']
+239859,VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"Sorry 
+*7 Save button does not get enabled",task_subcomment,['Sorry \n*7 Save button does not get enabled'],['BUG REPRODUCTION']
+55784,[EPIC] Use Parsoid HTML for all page views,"In the mid to end 2021 timeframe, the Parsing Team is aiming to start migrating read views for Wikimedia wikis from the core parser to Parsoid.
+
+https://www.mediawiki.org/wiki/Parsing/Parser_Unification is the wiki page for this project.
+
+This is a tracking task for getting this done. Subtasks track the specific work for getting this done.",task_description,"['[EPIC] Use Parsoid HTML for all page views\n\nIn the mid to end 2021 timeframe, the Parsing Team is aiming to start migrating read views for Wikimedia wikis from the core parser to Parsoid.', 'URL is the wiki page for this project.', 'This is a tracking task for getting this done.', 'Subtasks track the specific work for getting this done.']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+2143205,[EPIC] Use Parsoid HTML for all page views,"I'm removing #user-notice, as this task is too global. Specific tasks, with concrete actions, are more than welcome to be tagged for user announcements. ",task_subcomment,"[""I'm removing #user-notice, as this task is too global."", 'Specific tasks, with concrete actions, are more than welcome to be tagged for user announcements.']","['SOLUTION DISCUSSION', 'FUTURE PLAN']"
+2110328,[EPIC] Use Parsoid HTML for all page views,"Change 910556 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):
+%%%[operations/mediawiki-config@master] Turn on experimental Parsoid Read Views support, except on commons & wikidata%%%
+https://gerrit.wikimedia.org/r/910556",task_subcomment,"['Change 910556 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):\n%%%[operations/mediawiki-config@master] Turn on experimental Parsoid Read Views support, except on commons & wikidata%%%\nGERRIT_URL']",['ACTION ON ISSUE']
+2110327,[EPIC] Use Parsoid HTML for all page views,"Change 910044 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):
+%%%[mediawiki/services/parsoid@master] Experimenally enable Parsoid Read Views with ?useparsoid=1 query string%%%
+https://gerrit.wikimedia.org/r/910044",task_subcomment,['Change 910044 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):\n%%%[mediawiki/services/parsoid@master] Experimenally enable Parsoid Read Views with ?useparsoid=1 query string%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1137547,[EPIC] Use Parsoid HTML for all page views,"This ultra-epic is the perfect example of a task appropriately in the category of ""general MediaWiki tasks"".",task_subcomment,"['This ultra-epic is the perfect example of a task appropriately in the category of ""general MediaWiki tasks"".']",['INVESTIGATION AND EXPLORATION']
+1100468,[EPIC] Use Parsoid HTML for all page views,Tagging this for the Web and Infrastructure teams.,task_subcomment,['Tagging this for the Web and Infrastructure teams.'],['ACTION ON ISSUE']
+593537,[EPIC] Use Parsoid HTML for all page views,"Wikimedia Developer Summit 2016 ended two weeks ago. This task is still open. **If the session in this task took place**, please make sure 1) that the session Etherpad notes are linked from this task, 2) that followup tasks for any actions identified have been created and linked from this task, 3) to change the status of this task to ""resolved"". **If this session did not take place**, change the task status to ""declined"". **If this task** itself has become a well-defined action which **is not finished yet**, drag and drop this task into the ""Work continues after Summit"" column on the project workboard. Thank you for your help!",task_subcomment,"['Wikimedia Developer Summit 2016 ended two weeks ago.', 'This task is still open.', '**If the session in this task took place**, please make sure 1) that the session Etherpad notes are linked from this task, 2) that followup tasks for any actions identified have been created and linked from this task, 3) to change the status of this task to ""resolved"".', '**If this session did not take place**, change the task status to ""declined"".', '**If this task** itself has become a well-defined action which **is not finished yet**, drag and drop this task into the ""Work continues after Summit"" column on the project workboard.', 'Thank you for your help!']","['SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'ISSUE CONTENT MANAGEMENT', 'FUTURE PLAN', 'FUTURE PLAN', 'ACTION ON ISSUE']"
+559176,[EPIC] Use Parsoid HTML for all page views,"Today is November 6, and this proposal is basically not on track. Unless the situation suddenly changes and/or @robla-wmf and the Architecture Committee really want to schedule it, it will be removed as a #Wikimedia-Developer-Summit-2016 proposal.",task_subcomment,"['Today is November 6, and this proposal is basically not on track.', 'Unless the situation suddenly changes and/orSCREEN_NAME-wmf and the Architecture Committee really want to schedule it, it will be removed as a #Wikimedia-Developer-Summit-2016 proposal.']","['INVESTIGATION AND EXPLORATION', 'FUTURE PLAN']"
+554085,[EPIC] Use Parsoid HTML for all page views,"@mobrovac: if you really think this should happen, you should drive it rather than delegate it to #ArchCom.  @gwicke //might// volunteer to take this on, but I'm not going to speak for him.",task_subcomment,"['SCREEN_NAME: if you really think this should happen, you should drive it rather than delegate it to #ArchCom.', ""SCREEN_NAME //might// volunteer to take this on, but I'm not going to speak for him.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+553686,[EPIC] Use Parsoid HTML for all page views,"@Qgil, the reason is that this requires a wide cross-org consensus (and later work), so I'd say the ArchCom should drive this one.",task_subcomment,"[""SCREEN_NAME, the reason is that this requires a wide cross-org consensus (and later work), so I'd say the ArchCom should drive this one.""]",['SOLUTION DISCUSSION']
+553681,[EPIC] Use Parsoid HTML for all page views,"With so many blocking/blocked tasks, no specific Summit plans specified in the description, and no assignee, it is difficult to evaluate whether this Summit proposal is On Track with ongoing discussion. Can someone step in as driver of the discussion and confirm the interest in getting a slot in the Summit schedule, please?",task_subcomment,"['With so many blocking/blocked tasks, no specific Summit plans specified in the description, and no assignee, it is difficult to evaluate whether this Summit proposal is On Track with ongoing discussion.', 'Can someone step in as driver of the discussion and confirm the interest in getting a slot in the Summit schedule, please?']","['SOLUTION DISCUSSION', 'FUTURE PLAN']"
+540638,[EPIC] Use Parsoid HTML for all page views,"Congratulations! This is one of the 52 proposals that made it through the first deadline of the #Wikimedia-Developer-Summit-2016  [[ https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016#Submissions_and_selection_process | selection process ]]. Please pay attention to the next one:  > By **6 Nov 2015**, all Summit proposals must have active discussions and a Summit plan documented in the description. Proposals not reaching this critical mass can continue at their own path out of the Summit.",task_subcomment,"['Congratulations!', 'This is one of the 52 proposals that made it through the first deadline of the #Wikimedia-Developer-Summit-2016  [[ URL | selection process ]].', 'Please pay attention to the next one:  > By **6 Nov 2015**, all Summit proposals must have active discussions and a Summit plan documented in the description.', 'Proposals not reaching this critical mass can continue at their own path out of the Summit.']","['SOLUTION DISCUSSION', 'FUTURE PLAN', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+536650,[EPIC] Use Parsoid HTML for all page views,"FWIW, I did get some informal agreement that using Parsoid HTML for ""Printable page"" views was a reasonable thing to deploy on wikitech, as a first step.  I may try to write a standalone extension to do this.",task_subcomment,"['FWIW, I did get some informal agreement that using Parsoid HTML for ""Printable page"" views was a reasonable thing to deploy on wikitech, as a first step.', 'I may try to write a standalone extension to do this.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+418980,[EPIC] Use Parsoid HTML for all page views,">>! In T55784#1047315, @GWicke wrote:
+> @jdforrester-wmf, is this really high priority for you right now right now? Should we prioritize intermediate steps higher?
+
+It's not a Q3 urgency for VisualEditor, no.",task_subcomment,"[""QUOTE\nQUOTE\n\nIt's not a Q3 urgency for VisualEditor, no.""]",['FUTURE PLAN']
+413586,[EPIC] Use Parsoid HTML for all page views,"@jdforrester-wmf, is this really high priority for you right now right now? Should we prioritize intermediate steps higher?",task_subcomment,"['SCREEN_NAME-wmf, is this really high priority for you right now right now?', 'Should we prioritize intermediate steps higher?']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+239691,[EPIC] Use Parsoid HTML for all page views,*** Bug 53780 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53780 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+55758,Visualditor: Marathi/Devanagari: edit change not reflecting in edit preview,"*Problem Description:Where text is already present,Along with any of above problems, Some times edited aspect is shown in edit window but does not reflect in edit preview 
+
+**Additional Details : Probably problem arises when we insert any additional charecters or word between two existing words in a sentence.
+
+
+I suppose this would be easy to reproduce screen shot & will do it soon.
+
+
+* Steps to reproduce:
+1. Go to existing page with considerable Marathi Devnagari text may be like
+https://mr.wikipedia.org/wiki/अभिमन्यु
+
+2. Go to माझ्या पसंती (Preferences), संपादन and enable last option:
+यथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this
+enables VisualEditor
+3. Click cog next to इतर भाषांमध्ये
+4. Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण
+
+5. Select any random  two marathi word from existing paragraph text 
+
+6. insert any additional charecters or word between two existing words in a sentence.
+
+**Problem is not always but frequent .Tested on Win7 +Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['Visualditor: Marathi/Devanagari: edit change not reflecting in edit preview\n\n*Problem Description:Where text is already present,Along with any of above problems, Some times edited aspect is shown in edit window but does not reflect in edit preview \n\n**Additional Details : Probably problem arises when we insert any additional charecters or word between two existing words in a sentence.', 'I suppose this would be easy to reproduce screen shot & will do it soon.', '* Steps to reproduce:\n1.', 'Go to existing page with considerable Marathi Devnagari text may be like\nURL\n\n2.', 'Go to माझ्या पसंती (Preferences), संपादन and enable last option:\nयथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this\nenables VisualEditor\n3.', 'Click cog next to इतर भाषांमध्ये\n4.', 'Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण\n\n5.', 'Select any random  two marathi word from existing paragraph text \n\n6. insert any additional charecters or word between two existing words in a sentence.', '**Problem is not always but frequent .Tested on Win7 +Firefox\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237966,Visualditor: Marathi/Devanagari: edit change not reflecting in edit preview,"Based on your comments, I'm marking this as FIXED - please check, and reopen if it's not!",task_subcomment,"[""Based on your comments, I'm marking this as FIXED - please check, and reopen if it's not!""]",['ACTION ON ISSUE']
+237960,Visualditor: Marathi/Devanagari: edit change not reflecting in edit preview,"*Done first round of testing seems to have solved but since problem is not frequent one for final confirmation we will need to have more tests and time.
+
+Thanks and regards",task_subcomment,"['*Done first round of testing seems to have solved but since problem is not frequent one for final confirmation we will need to have more tests and time.', 'Thanks and regards']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+237952,Visualditor: Marathi/Devanagari: edit change not reflecting in edit preview,"There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:
+
+https://gerrit.wikimedia.org/r/#/c/82858/
+
+Please let us know whether it fixes the bug!",task_subcomment,"[""There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:\n\nURL\n\nPlease let us know whether it fixes the bug!""]",['BUG REPRODUCTION']
+237945,Visualditor: Marathi/Devanagari: edit change not reflecting in edit preview,Usually this problem does not come in isolation but comes when some other problems are happening reported in earlier bugs for Marathi/Devnagri but it is defficult to specify that the problem will come when exactly a specific other problem is existent.May need more observation to notify exact time of ocurrance.,task_subcomment,['Usually this problem does not come in isolation but comes when some other problems are happening reported in earlier bugs for Marathi/Devnagri but it is defficult to specify that the problem will come when exactly a specific other problem is existent.May need more observation to notify exact time of ocurrance.'],['OBSERVED BUG BEHAVIOR']
+55757,VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side,"*Problem description : spell correction of any word eats up text (with continuous motion) on right side until you press spacebar 
+
+**Additional Details: The problem is quite frequent but not always.Observed specially when we give backpace and add up more charecters to the word than earlier length of of the word  
+
+* Steps to reproduce:
+1. Go to existing page with considerable Marathi Devnagari text may be like https://mr.wikipedia.org/wiki/अभिमन्यु
+
+2. Go to माझ्या पसंती (Preferences), संपादन and enable last option:
+यथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this
+enables VisualEditor
+3. Click cog next to इतर भाषांमध्ये
+4. Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण
+
+5. Select any random  marathi word from text 
+
+6. delet few charecters with backspace
+
+7. Add few new marathi charectes to the word
+
+8. If the problem is not observed in single effort try spell corrections again in some other words 
+
+
+*VisualEditor+ULS Method of input = अक्षरांतरण language=Marathi 
+Script=Devanagari  (Non-VE source edit environ,ULS Method of input = अक्षरांतरण
+works normal   
+
+*Tested Browser and OS =Firefox+Win7
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51472",task_description,"['VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side\n\n*Problem description : spell correction of any word eats up text (with continuous motion) on right side until you press spacebar \n\n**Additional Details: The problem is quite frequent but not always.Observed specially when we give backpace and add up more charecters to the word than earlier length of of the word  \n\n* Steps to reproduce:\n1.', 'Go to existing page with considerable Marathi Devnagari text may be like URL\n\n2.', 'Go to माझ्या पसंती (Preferences), संपादन and enable last option:\nयथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this\nenables VisualEditor\n3.', 'Click cog next to इतर भाषांमध्ये\n4.', 'Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण\n\n5.', 'Select any random  marathi word from text \n\n6. delet few charecters with backspace\n\n7.', 'Add few new marathi charectes to the word\n\n8.', 'If the problem is not observed in single effort try spell corrections again in some other words \n\n\n*VisualEditor+ULS Method of input = अक्षरांतरण language=Marathi \nScript=Devanagari  (Non-VE source edit environ,ULS Method of input = अक्षरांतरण\nworks normal   \n\n*Tested Browser and OS =Firefox+Win7\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237895,VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side,"Change 80689 merged by jenkins-bot:
+Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",task_subcomment,['Change 80689 merged by jenkins-bot:\nRevert model to use simple UTF-16 code units\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237888,VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side,"Change 80689 had a related patch set uploaded by Divec:
+Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",task_subcomment,['Change 80689 had a related patch set uploaded by Divec:\nRevert model to use simple UTF-16 code units\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237881,VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side,"Hello,
+
+Would it be possible to test this against current master? You can use this at
+http://en.wikipedia.beta.wmflabs.org/ - we believe that we may have fixed the
+issues (or, at least, changed the behaviour) since you tested it.
+
+Thank you!",task_subcomment,"['Hello,\n\nWould it be possible to test this against current master?', 'You can use this at\nURL - we believe that we may have fixed the\nissues (or, at least, changed the behaviour) since you tested it.', 'Thank you!']","['TESTING', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237873,VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side,"(In reply to comment #1)
+
+*Did one round of test at my user page on media wiki https://www.mediawiki.org/wiki/User:Mahitgar 
+
+Seems to get partially fixed with some different wierdness in some other case so will need more tests and time to confirm
+
+
+Rgds",task_subcomment,['(In reply to comment #1)\n\n*Did one round of test at my user page on media wiki URL \n\nSeems to get partially fixed with some different wierdness in some other case so will need more tests and time to confirm\n\n\nRgds'],['OBSERVED BUG BEHAVIOR']
+237867,VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side,"There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:
+
+https://gerrit.wikimedia.org/r/#/c/82858/
+
+Please let us know whether it fixes the bug!",task_subcomment,"[""There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:\n\nURL\n\nPlease let us know whether it fixes the bug!""]",['BUG REPRODUCTION']
+55750,VisualEditor: Page down and page up not working as expected in Firefox,"an IP editor at en.wp reports:
+""At any given page, as long the edit box is selected (with the cursor blinking) pressing 'page down' or 'page up' takes you to the end of the page. Firefox 23.0, Linux Mint.""
+The example page they gave was [[Jet Lee]]
+
+Using Firefox 23 on Xubuntu linux with the monobook skin I am unable to duplicate that behaviour, but:
+At [[Jet Lee]] and [[User:Thryduulf/sandbox2]]: pressing page down or page up works as expected once but then does nothing. I then click anywhere in the body and again one of them works once, and then not until I click. However, once I've viewed the end of the page it expected. 
+
+At [[User:Thryduulf/sandbox]] and [[Timbuktu]] it works as expected from the start. 
+
+At [[Nigeria]] I saw the same behaviour as at [[Jet Lee]] but when I returned to the top of the page it went back to working only once.
+
+At [[Great Balls of Fire]] page down worked once, then didn't. I clicked and it worked as expected subsequently.
+
+At [[Malvern Link]] I saw the same as at [[Nigeria]], but after pressing page up both page up and page down then worked as expected.
+
+I'm struggling to see any pattern.
+
+Bug 33047 was suggested as having potential relevance, but that was fixed in October 2012 so my gut feeling is that its unlikely.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51957
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50726",task_description,"['VisualEditor: Page down and page up not working as expected in Firefox\n\nan IP editor at en.wp reports:\n""At any given page, as long the edit box is selected (with the cursor blinking) pressing \'page down\' or \'page up\' takes you to the end of the page.', 'Firefox 23.0, Linux Mint.""', 'The example page they gave was [[Jet Lee]]\n\nUsing Firefox 23 on Xubuntu linux with the monobook skin I am unable to duplicate that behaviour, but:\nAt [[Jet Lee]] and [[User:Thryduulf/sandbox2]]: pressing page down or page up works as expected once but then does nothing.', 'I then click anywhere in the body and again one of them works once, and then not until I click.', ""However, once I've viewed the end of the page it expected."", 'At [[User:Thryduulf/sandbox]] and [[Timbuktu]] it works as expected from the start.', 'At [[Nigeria]] I saw the same behaviour as at [[Jet Lee]] but when I returned to the top of the page it went back to working only once.', ""At [[Great Balls of Fire]] page down worked once, then didn't."", 'I clicked and it worked as expected subsequently.', 'At [[Malvern Link]] I saw the same as at [[Nigeria]], but after pressing page up both page up and page down then worked as expected.', ""I'm struggling to see any pattern."", 'Bug 33047 was suggested as having potential relevance, but that was fixed in October 2012 so my gut feeling is that its unlikely.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+237423,VisualEditor: Page down and page up not working as expected in Firefox,"AFAICT this is now works in Firefox since the Firefox-related CE fixes, though there are some oddities generally about Page Up / Page Down. Closing as such for now, but happy to re-open if I've missed something.",task_subcomment,"['AFAICT this is now works in Firefox since the Firefox-related CE fixes, though there are some oddities generally about Page Up / Page Down.', ""Closing as such for now, but happy to re-open if I've missed something.""]","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+237419,VisualEditor: Page down and page up not working as expected in Firefox,"I am able to reproduce this on Firefox 24/Linux.
+Page down on the following articles jumps to the bottom of the article, irrespective of where the cursor is placed.  Even stranger, page up also goes to the bottom of the article.
+https://en.wikipedia.org/wiki/Nigeria?veaction=edit
+https://en.wikipedia.org/wiki/Great_Balls_of_Fire?veaction=edit
+
+The problematic behaviour doesnt happen on simpler articles like
+https://en.wikipedia.org/w/index.php?title=Walter_T._Downing&veaction=edit
+https://en.wikipedia.org/w/index.php?title=Sienno,_W%C4%85growiec_County&veaction=edit
+
+Bug 51957 is another Firefox only keyboard navigation problem.",task_subcomment,"['I am able to reproduce this on Firefox 24/Linux.', 'Page down on the following articles jumps to the bottom of the article, irrespective of where the cursor is placed.', 'Even stranger, page up also goes to the bottom of the article.', 'URL\nURL\n\nThe problematic behaviour doesnt happen on simpler articles like\nURL\nURL\n\nBug 51957 is another Firefox only keyboard navigation problem.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237415,VisualEditor: Page down and page up not working as expected in Firefox,"Germanjoe comments suggests it may be related to problems establishing cursor position relative to templates:
+
+""Maybe a related error occured, while testing in [[Nigeria]], Firefox 23, mono. Enter VE-mode and click below one of the huge (really huge) navbox farms at the end of the article (in the blank line below them). Now i made two tests:
+
+Click ""Page up"" => OK, scrolls up as expected. 
+Now click ""Page up"" again => ERROR, jumps down to the initial position below the navbox.
+        
+another test from the same initial position below the huge navbox: 
+""Page up"", then ""Page down"", then ""Page up"" and a second ""Page up"" => works OK.
+
+If i had to guess (uneducated as always), it looks like VE has problems storing or establishing the cursor position while scrolling through some huge or complex templates. """,task_subcomment,"['Germanjoe comments suggests it may be related to problems establishing cursor position relative to templates:\n\n""Maybe a related error occured, while testing in [[Nigeria]], Firefox 23, mono.', 'Enter VE-mode and click below one of the huge (really huge) navbox farms at the end of the article (in the blank line below them).', 'Now i made two tests:\n\nClick ""Page up"" => OK, scrolls up as expected.', 'Now click ""Page up"" again => ERROR, jumps down to the initial position below the navbox.', 'another test from the same initial position below the huge navbox: \n""Page up"", then ""Page down"", then ""Page up"" and a second ""Page up"" => works OK.', 'If i had to guess (uneducated as always), it looks like VE has problems storing or establishing the cursor position while scrolling through some huge or complex templates. ""']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237409,VisualEditor: Page down and page up not working as expected in Firefox,"It's Windows 7, sorry. I am also the original reporter of the related bug 52445, whose effect is also being kicked to the end of the edit box and Firefox only.",task_subcomment,"[""It's Windows 7, sorry."", 'I am also the original reporter of the related bug 52445, whose effect is also being kicked to the end of the edit box and Firefox only.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237402,VisualEditor: Page down and page up not working as expected in Firefox,the same IP user has followed up saying (while I was reporting this) that they have been unable to reproduce their original report in Firefox 23.0.1 in Windows (they don't say which version),task_subcomment,"[""the same IP user has followed up saying (while I was reporting this) that they have been unable to reproduce their original report in Firefox 23.0.1 in Windows (they don't say which version)""]",['OBSERVED BUG BEHAVIOR']
+55712,run VE browser tests in vagrant,"My goal next week is to be able to run the VE tests in a mediawiki-vagrant instance. When I added the role, I get puppet errors. Just in case you ran into this, here's the error:
+
+notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: Installing ffi (1.9.0) with native extensions /usr/lib/ruby/1.9.1/rubygems/installer.rb:552:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)
+notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: 
+notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns:         /usr/bin/ruby1.9.1 extconf.rb 
+
+         notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: Results logged to /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0/ext/ffi_c/gem_make.out
+
+and all that contains is the line
+  /usr/bin/ruby1.9.1 extconf.rb 
+
+There's an extconf.rb in ~/.gem/ruby/1.9.1/gems/ffi-1.9.0/ext/ffi_c , so I ran that line, it created a Makefile, I ran make, and it built something.  But the next time I ran browsertests, it failed again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['run VE browser tests in vagrant\n\nMy goal next week is to be able to run the VE tests in a mediawiki-vagrant instance.', 'When I added the role, I get puppet errors.', ""Just in case you ran into this, here's the error:\n\nnotice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: Installing ffi (1.9.0) with native extensions /usr/lib/ruby/1.9.1/rubygems/installer.rb:552:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension."", ""(Gem::Installer::ExtensionBuildError)\nnotice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: \nnotice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns:         /usr/bin/ruby1.9.1 extconf.rb \n\n         notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: Results logged to /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0/ext/ffi_c/gem_make.out\n\nand all that contains is the line\n  /usr/bin/ruby1.9.1 extconf.rb \n\nThere's an extconf.rb in ~/.gem/ruby/1.9.1/gems/ffi-1.9.0/ext/ffi_c , so I ran that line, it created a Makefile, I ran make, and it built something."", 'But the next time I ran browsertests, it failed again.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+234968,run VE browser tests in vagrant,Closing since this looks like it has been fixed to me. Please reopen if needed.,task_subcomment,"['Closing since this looks like it has been fixed to me.', 'Please reopen if needed.']","['ISSUE CONTENT MANAGEMENT', 'ACTION ON ISSUE']"
+234963,run VE browser tests in vagrant,"**jhall** wrote:
+
+I was able to get this working on my MacBook Air with the following workflow (I have not been able to verify that this works on platforms other than Mac OS):
+
+1. vagrant enable-role visualeditor
+2. vagrant up
+3. vagrant provision
+4. vagrant ssh -- -X
+5. cd /srv/VisualEditor/VisualEditor/modules/ve-mw/test/browser
+6. export MEDIAWIKI_URL=
+7. export MEDIAWIKI_USER=
+8. export MEDIAWIKI_PASSWORD=
+9. export PATH=$PATH:/home/vagrant/.gem/ruby/1.9.1/gems/cucumber-1.3.8/bin 
+10. bundle exec cucumber ",task_subcomment,['**jhall** wrote:\n\nI was able to get this working on my MacBook Air with the following workflow (I have not been able to verify that this works on platforms other than Mac OS):\n\n1. vagrant enable-role visualeditor\n2. vagrant up\n3. vagrant provision\n4. vagrant ssh -- -X\n5. cd /srv/VisualEditor/VisualEditor/modules/ve-mw/test/browser\n6. export MEDIAWIKI_URL=\n7. export MEDIAWIKI_USER=\n8. export MEDIAWIKI_PASSWORD=\n9. export PATH=$PATH:/home/vagrant/.gem/ruby/1.9.1/gems/cucumber-1.3.8/bin \n10. bundle exec cucumber '],['INVESTIGATION AND EXPLORATION']
+55691,browsertests: triggers for VisualEditor,"Similar to bug 52120 for ULS. Once we've got this running on merge, we'll want to move to running on submit (V+2 submit?), but for now…
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52120
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57560",task_description,"['browsertests: triggers for VisualEditor\n\nSimilar to bug 52120 for ULS.', ""Once we've got this running on merge, we'll want to move to running on submit (V+2 submit?"", '), but for now…\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'INVESTIGATION AND EXPLORATION']"
+233751,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Basic test is merged and in place, so marking this bug resolved.",task_subcomment,"['**jhall** wrote:\n\nBasic test is merged and in place, so marking this bug resolved.']",['ACTION ON ISSUE']
+233747,browsertests: triggers for VisualEditor,"Change 111890 merged by jenkins-bot:
+[Browser test] Headless browser test(s)
+
+https://gerrit.wikimedia.org/r/111890",task_subcomment,['Change 111890 merged by jenkins-bot:\n[Browser test] Headless browser test(s)\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233741,browsertests: triggers for VisualEditor,"Change 100797 abandoned by Hashar:
+[browser test] Cucumber default profile for CI
+
+Reason:
+we are using something different than the ciwmf profile.
+
+https://gerrit.wikimedia.org/r/100797",task_subcomment,"['Change 100797 abandoned by Hashar:\n[browser test] Cucumber default profile for CI\n\nReason:\nwe are using something different than the ciwmf profile.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233734,browsertests: triggers for VisualEditor,"Change 111890 had a related patch set uploaded by Jhall:
+[Browser test] New test for headless browser testing on a fresh Mediawiki install with VisualEditor.
+
+https://gerrit.wikimedia.org/r/111890",task_subcomment,"['Change 111890 had a related patch set uploaded by Jhall:\n[Browser test] New test for headless browser testing on a fresh Mediawiki install with VisualEditor.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233729,browsertests: triggers for VisualEditor,"Change 110468 abandoned by Jhall:
+[Browser test] WIP Headless test for VE verification on a fresh Mediawiki install (as on Integration server).
+
+Reason:
+Abandoning this change since I'm going to start fresh with a slightly different approach.
+
+https://gerrit.wikimedia.org/r/110468",task_subcomment,"['Change 110468 abandoned by Jhall:\n[Browser test] WIP Headless test for VE verification on a fresh Mediawiki install (as on Integration server).', ""Reason:\nAbandoning this change since I'm going to start fresh with a slightly different approach."", 'GERRIT_URL']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233725,browsertests: triggers for VisualEditor,"Change 110468 had a related patch set uploaded by Jhall:
+[Browser test] WIP Headless test for VE verification on a fresh Mediawiki install (as on Integration server).
+
+https://gerrit.wikimedia.org/r/110468",task_subcomment,"['Change 110468 had a related patch set uploaded by Jhall:\n[Browser test] WIP Headless test for VE verification on a fresh Mediawiki install (as on Integration server).', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233718,browsertests: triggers for VisualEditor,"Change 102960 abandoned by Jhall:
+[Browser test] WIP Modifications for PhantomJS compatibility
+
+Reason:
+Abandoning this patch since we have implemented support for headless browser testing in the mediawiki-selenium Rubygem (rather than implementing it in each individual repo).
+
+https://gerrit.wikimedia.org/r/102960",task_subcomment,"['Change 102960 abandoned by Jhall:\n[Browser test] WIP Modifications for PhantomJS compatibility\n\nReason:\nAbandoning this patch since we have implemented support for headless browser testing in the mediawiki-selenium Rubygem (rather than implementing it in each individual repo).', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233714,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+After some further investigation, we've decided to use the ""headless"" Rubygem for headless browser testing, and we've decided to incorporate that support into the mediawiki-selenium Rubygem so that it will be available to all WMF repositories that have browser tests.  The task for updating the mediawiki-selenium is captured in Bugzilla 60584.",task_subcomment,"['**jhall** wrote:\n\nAfter some further investigation, we\'ve decided to use the ""headless"" Rubygem for headless browser testing, and we\'ve decided to incorporate that support into the mediawiki-selenium Rubygem so that it will be available to all WMF repositories that have browser tests.', 'The task for updating the mediawiki-selenium is captured in Bugzilla 60584.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+233709,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Scripts used to evaluate PhantomJS ""bind"" injection
+
+After a pairing session with Željko, I went back to basics and tried to get Function.prototype.bind injection working directly with PhantomJS (ignoring the rest of our test infrastructure for the time being).  
+
+Per the attached scripts, I tried all of the relevant methods noted in the PhantomJS API documentation:
+
+http://phantomjs.org/api/webpage/
+
+...and still no luck.  The Main_Page loads fine, with the exception of the VE editing link/tab, which is available to other browsers (Chrome, Firefox, etc) at the same URL.
+
+Per a suggestion from Antoine, it might be time to investigate using Firefox in a headless mode as a potential substitute for PhantomJS.
+
+**Attached**: {F11112}",task_subcomment,"['**jhall** wrote:\n\nScripts used to evaluate PhantomJS ""bind"" injection\n\nAfter a pairing session with Željko, I went back to basics and tried to get Function.prototype.bind injection working directly with PhantomJS (ignoring the rest of our test infrastructure for the time being).', 'Per the attached scripts, I tried all of the relevant methods noted in the PhantomJS API documentation:\n\nURL\n\n...and still no luck.', 'The Main_Page loads fine, with the exception of the VE editing link/tab, which is available to other browsers (Chrome, Firefox, etc) at the same URL.', 'Per a suggestion from Antoine, it might be time to investigate using Firefox in a headless mode as a potential substitute for PhantomJS.', '**Attached**: {F11112}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233703,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Changing bug status since task in still WIP.",task_subcomment,['**jhall** wrote:\n\nChanging bug status since task in still WIP.'],['ACTION ON ISSUE']
+233697,browsertests: triggers for VisualEditor,"Change 102960 had a related patch set uploaded by Jhall:
+[Browser test] WIP Modifications for PhantomJS compatibility
+
+https://gerrit.wikimedia.org/r/102960",task_subcomment,['Change 102960 had a related patch set uploaded by Jhall:\n[Browser test] WIP Modifications for PhantomJS compatibility\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233690,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Timo pointed me in the right direction:
+
+
+jeffrey-hall:browser jeffreyhall$ phantomjs
+phantomjs> Function.prototype.bind
+undefined
+
+
+Turns out PhantomJS is built with an old version of JavaScriptCore that is missing the ""bind"" implementation, which is needed to satisfy Visual Editor's es5 features check: 
+
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/cf7f2b141d/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js#L72-L84
+
+…but a workaround is available:
+
+https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/bind?redirectlocale=en-US&redirectslug=JavaScript%2FReference%2FGlobal_Objects%2FFunction%2Fbind#Compatibility
+
+…so I'll investigate the workaround next.",task_subcomment,"['**jhall** wrote:\n\nTimo pointed me in the right direction:\n\n\njeffrey-hall:browser jeffreyhall$ phantomjs\nphantomjs> Function.prototype.bind\nundefined\n\n\nTurns out PhantomJS is built with an old version of JavaScriptCore that is missing the ""bind"" implementation, which is needed to satisfy Visual Editor\'s es5 features check: \n\nURL\n\n…but a workaround is available:\n\nURL\n\n…so I\'ll investigate the workaround next.']",['INVESTIGATION AND EXPLORATION']
+233682,browsertests: triggers for VisualEditor,"Created attachment 14138
+ve phantomjs
+
+**Attached**: {F11111}",task_subcomment,['Created attachment 14138\nve phantomjs\n\n**Attached**: {F11111}'],['INVESTIGATION AND EXPLORATION']
+233676,browsertests: triggers for VisualEditor,"Created attachment 14137
+ve ff
+
+**Attached**: {F11109}",task_subcomment,['Created attachment 14137\nve ff\n\n**Attached**: {F11109}'],['ATTACHMENT']
+233668,browsertests: triggers for VisualEditor,"Strange. I am pretty sure PhantomJS has JS. :)
+
+But, this simple script takes screen shot that shows it can not load visual editor.
+
+require ""watir-webdriver""
+browser = Watir::Browser.new :phantomjs
+browser.goto ""https://test2.wikipedia.org/wiki/User:Zeljko.filipin%28WMF%29?veaction=edit&vewhitelist=1""
+browser.window.resize_to 1280, 1024
+browser.screenshot.save ""ve.png""
+
+If :phantomjs is replaced with :firefox, then visual editor opens just fine (see screen shots).",task_subcomment,"['Strange.', 'I am pretty sure PhantomJS has JS.', ':)\n\nBut, this simple script takes screen shot that shows it can not load visual editor.', 'require ""watir-webdriver""\nbrowser = Watir::Browser.new :phantomjs\nbrowser.goto ""URL\nbrowser.window.resize_to 1280, 1024\nbrowser.screenshot.save ""ve.png""\n\nIf :phantomjs is replaced with :firefox, then visual editor opens just fine (see screen shots).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+233661,browsertests: triggers for VisualEditor,"If a browser is not on the blacklist, and meets the functionality criteria, then the edit tabs for VisualEditor should show up. A browser not being on the whitelist just means the user gets a warning when they edit. Adding PhantomJS to the whitelist will not make VisualEditor appear if it doesn't already.
+
+(Also, you can bypass the blacklist with ?veaction=edit&vewhitelist=1 which should trigger VE even if you don't have a functional browser, as long as it has JS.)",task_subcomment,"['If a browser is not on the blacklist, and meets the functionality criteria, then the edit tabs for VisualEditor should show up.', 'A browser not being on the whitelist just means the user gets a warning when they edit.', ""Adding PhantomJS to the whitelist will not make VisualEditor appear if it doesn't already."", ""(Also, you can bypass the blacklist with ?veaction=edit&vewhitelist=1 which should trigger VE even if you don't have a functional browser, as long as it has JS.)""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+233656,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Ah, I believe Željko is correct - looks like VE has a whitelist in addition to a blacklist.  See section beginning on line 169 in this file:
+
+https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/1cd761dad8aed132619c2897abe367404ca8f3ca/modules%2Fve-mw%2Finit%2Ftargets%2Fve.init.mw.ViewPageTarget.js
+
+Will talk to the VE dev team and see if we can get PhantomJS whitelisted.",task_subcomment,"['**jhall** wrote:\n\nAh, I believe Željko is correct - looks like VE has a whitelist in addition to a blacklist.', 'See section beginning on line 169 in this file:\n\nURL\n\nWill talk to the VE dev team and see if we can get PhantomJS whitelisted.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+233653,browsertests: triggers for VisualEditor,"Created attachment 14130
+phantomjs screen shot
+
+**Attached**: {F11108}",task_subcomment,['Created attachment 14130\nphantomjs screen shot\n\n**Attached**: {F11108}'],['ATTACHMENT']
+233651,browsertests: triggers for VisualEditor,Looks like phantomjs is blacklisted (or not whitelisted). There is no visual editor edit option (see screen shot).,task_subcomment,"['Looks like phantomjs is blacklisted (or not whitelisted).', 'There is no visual editor edit option (see screen shot).']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+233649,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Looks like it's not a problem with PhantomJS being blacklisted, per the VisualEditor browser blacklist which begins at line 890 of this file:
+
+https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/b922592902ad57f770b6810566b820aada74aa47/VisualEditor.php
+
+…so I'll spend some more time tomorrow to see if I can figure out why PhantomJS doesn't seem to work as intended even when navigating directly to an ""editing mode"" URL.",task_subcomment,"['**jhall** wrote:\n\nLooks like it\'s not a problem with PhantomJS being blacklisted, per the VisualEditor browser blacklist which begins at line 890 of this file:\n\nURL\n\n…so I\'ll spend some more time tomorrow to see if I can figure out why PhantomJS doesn\'t seem to work as intended even when navigating directly to an ""editing mode"" URL.']",['INVESTIGATION AND EXPLORATION']
+233646,browsertests: triggers for VisualEditor,"Could it be that phantomjs lack some javascript functionality that would cause VisualEditor to disable itself ?  Might be a browser whitelist as well.  Honestly, I have no clue how it is handled in VisualEditor.",task_subcomment,"['Could it be that phantomjs lack some javascript functionality that would cause VisualEditor to disable itself ?', 'Might be a browser whitelist as well.', 'Honestly, I have no clue how it is handled in VisualEditor.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233642,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+PhantomJS screenshot from VE editing mode URL
+
+Thanks Željko.  I tried modifying the ""anon.feature"" test to navigate directly to the Visual Editor editing URL (?veaction=edit), but from capturing both a screenshot (attached) and the raw HTML that PhantomJS lands on, it does not appear that PhantomJS is successfully entering into Visual Editor editing mode.
+
+In any case, we're getting closer step-by-step, so I'll continue to work on this.
+
+**Attached**: {F11106}",task_subcomment,"['**jhall** wrote:\n\nPhantomJS screenshot from VE editing mode URL\n\nThanks Željko.', 'I tried modifying the ""anon.feature"" test to navigate directly to the Visual Editor editing URL (?veaction=edit), but from capturing both a screenshot (attached) and the raw HTML that PhantomJS lands on, it does not appear that PhantomJS is successfully entering into Visual Editor editing mode.', ""In any case, we're getting closer step-by-step, so I'll continue to work on this."", '**Attached**: {F11106}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233638,browsertests: triggers for VisualEditor,"Created attachment 14080
+phantomjs screen shot
+
+**Attached**: {F11105}",task_subcomment,['Created attachment 14080\nphantomjs screen shot\n\n**Attached**: {F11105}'],['ATTACHMENT']
+233633,browsertests: triggers for VisualEditor,"(In reply to comment #6)
+> The test case currently does not work with PhantomJS, so I'll spend more time
+> tomorrow trying to figure out why PhantomJS can't click into Visual Editor
+> editing mode.
+
+In phantomjs, ""edit"" link is not visible by default, see attached screen shot.",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nIn phantomjs, ""edit"" link is not visible by default, see attached screen shot.']",['OBSERVED BUG BEHAVIOR']
+233628,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+I went ahead and amended the existing Gerrit ID:
+
+https://gerrit.wikimedia.org/r/#/c/100797/
+
+…with an additional anon test case that edits a random page (which will likely always be the ""Main Page"" for a fresh wiki install).  
+
+The test case currently does not work with PhantomJS, so I'll spend more time tomorrow trying to figure out why PhantomJS can't click into Visual Editor editing mode.",task_subcomment,"['**jhall** wrote:\n\nI went ahead and amended the existing Gerrit ID:\n\nURL\n\n…with an additional anon test case that edits a random page (which will likely always be the ""Main Page"" for a fresh wiki install).', ""The test case currently does not work with PhantomJS, so I'll spend more time tomorrow trying to figure out why PhantomJS can't click into Visual Editor editing mode.""]","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+233622,browsertests: triggers for VisualEditor,"Jeff : sure, if you can get a test that roughly does:
+
+ - anonymous user
+ - go to main page
+ - press Edit (visual editor version)
+ - ensure visual editor is loaded
+
+That would be a nice first step that would validate the Jenkins job and VE/Parsoid is properly setup :-)",task_subcomment,"['Jeff : sure, if you can get a test that roughly does:\n\n - anonymous user\n - go to main page\n - press Edit (visual editor version)\n - ensure visual editor is loaded\n\nThat would be a nice first step that would validate the Jenkins job and VE/Parsoid is properly setup :-)']",['BUG REPRODUCTION']
+233614,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Sorry I wasn't able to get to work on this bug quickly Antoine - let me know if you want me to work on creating a new browser test that will succeed in this scenario (the existing anon test will fail since it presumes the existence of a User page in the target wiki).",task_subcomment,"[""**jhall** wrote:\n\nSorry I wasn't able to get to work on this bug quickly Antoine - let me know if you want me to work on creating a new browser test that will succeed in this scenario (the existing anon test will fail since it presumes the existence of a User page in the target wiki).""]",['INVESTIGATION AND EXPLORATION']
+233607,browsertests: triggers for VisualEditor,"And I manage to get VisualEditor + Parsoid to be setup automatically using Jenkins. The related job configuration is pending in https://gerrit.wikimedia.org/r/#/c/100800/ (need to be polished).
+
+I confirmed the wiki is functional and managed to edit a page using VE \O/
+
+Next steps:
+* cleanup the job configuration
+* make the wiki faster (sqlite is not on tmpfs as an example)
+* try to get at least ONE browser test scenario to pass (anon ones are good candidates apparently)",task_subcomment,"['And I manage to get VisualEditor + Parsoid to be setup automatically using Jenkins.', 'The related job configuration is pending in URL (need to be polished).', 'I confirmed the wiki is functional and managed to edit a page using VE \\O/\n\nNext steps:\n* cleanup the job configuration\n* make the wiki faster (sqlite is not on tmpfs as an example)\n* try to get at least ONE browser test scenario to pass (anon ones are good candidates apparently)']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+233601,browsertests: triggers for VisualEditor,"Change 100797 had a related patch set uploaded by Hashar:
+[browser test] cucumber default profile for CI
+
+https://gerrit.wikimedia.org/r/100797",task_subcomment,['Change 100797 had a related patch set uploaded by Hashar:\n[browser test] cucumber default profile for CI\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233597,browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Assigning to myself per an e-mail thread with Antoine, Chris, and Željko.",task_subcomment,"['**jhall** wrote:\n\nAssigning to myself per an e-mail thread with Antoine, Chris, and Željko.']",['INVESTIGATION AND EXPLORATION']
+55679,VisualEditor: Selection-expansion doesn't trigger for Thai script text,"When editing, clicking in the middle of or adjacent to an existing word in Latin, Hebrew, Arabic or Cyrillic scripts (others not tested) and pressing ctrl+k or clicking the link icon selects that word as the suggested sequence that is desired to be linked. When doing the same in Thai text nothing is selected by default.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"[""VisualEditor: Selection-expansion doesn't trigger for Thai script text\n\nWhen editing, clicking in the middle of or adjacent to an existing word in Latin, Hebrew, Arabic or Cyrillic scripts (others not tested) and pressing ctrl+k or clicking the link icon selects that word as the suggested sequence that is desired to be linked."", 'When doing the same in Thai text nothing is selected by default.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+257335,VisualEditor: Selection-expansion doesn't trigger for Thai script text,"This is not a ""bug"" per se - VisualEditor's word boundary detection only works for scripts that use word boundaries. Consequently it doesn't operate on Chinese or Thai (which don't use word boundaries), but does for Korean, Latin and Cyrillic languages, and others (which do).
+
+Theoretically it would be possible to build some code for applying algorithmic word boundary rules for Thai, but that's both complex and slow, so if that is desired it should be opened as an enhancement (and we'd need to see how we can make it only slow down users who are editing in Thai).
+
+Marking as INVALID.",task_subcomment,"['This is not a ""bug"" per se - VisualEditor\'s word boundary detection only works for scripts that use word boundaries.', ""Consequently it doesn't operate on Chinese or Thai (which don't use word boundaries), but does for Korean, Latin and Cyrillic languages, and others (which do)."", ""Theoretically it would be possible to build some code for applying algorithmic word boundary rules for Thai, but that's both complex and slow, so if that is desired it should be opened as an enhancement (and we'd need to see how we can make it only slow down users who are editing in Thai)."", 'Marking as INVALID.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+257331,VisualEditor: Selection-expansion doesn't trigger for Thai script text,"I tested with Telugu and Malayalam, and this doesn't happen there. Must be something special with Thai.",task_subcomment,"[""I tested with Telugu and Malayalam, and this doesn't happen there."", 'Must be something special with Thai.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+257325,VisualEditor: Selection-expansion doesn't trigger for Thai script text,"Confirmed in Thai Wikipedia and in the English Wikipedia with Thai words.
+
+Furthermore, if you Ctrl-K on a Latin word and then Ctrl-K on a Thai word, the Latin word appears in the input box. See this test case:
+https://en.wikipedia.org/wiki/User:Amire80/VE-Thai",task_subcomment,"['Confirmed in Thai Wikipedia and in the English Wikipedia with Thai words.', 'Furthermore, if you Ctrl-K on a Latin word and then Ctrl-K on a Thai word, the Latin word appears in the input box.', 'See this test case:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+55642,VisualEditor: Removing formatting from part of a link causes a snowman,"I tried editing [[Fred Pittman]], including adding a comma after a link. The editor auto-added it to the link text, which wasn't what I wanted, so I selected the comma and clicked the remove-formatting button. This replaced the comma with a snowman. Woo!
+
+I'd also say that the auto-link-addition heuristic is a little buggy if it includes commas, but that's maybe just me. :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Removing formatting from part of a link causes a snowman\n\nI tried editing [[Fred Pittman]], including adding a comma after a link.', ""The editor auto-added it to the link text, which wasn't what I wanted, so I selected the comma and clicked the remove-formatting button."", 'This replaced the comma with a snowman.', 'Woo!', ""I'd also say that the auto-link-addition heuristic is a little buggy if it includes commas, but that's maybe just me."", ':)\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+255039,VisualEditor: Removing formatting from part of a link causes a snowman,This was fixed two weeks ago; sorry for the slowness in replying.,task_subcomment,['This was fixed two weeks ago; sorry for the slowness in replying.'],['ACTION ON ISSUE']
+55560,"VisualEditor: After adding a link, cursor appears before rather than after the new insertion","When adding a link from scratch (without marking an existing word first)  the cursor ends up being at the beginning of the new link rather than at its end -- which stops fluent typing.
+
+Reproduce:
+1. Go to an RTL wiki.
+2. Go to a new sentence or new paragraph (cursor should be in an empty space)
+3. Create link, followed by enter/enter to close the inspector
+4. The cursor appears at the left of the word (which is the beginning in RTL) rather than the right of the word.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: After adding a link, cursor appears before rather than after the new insertion\n\nWhen adding a link from scratch (without marking an existing word first)  the cursor ends up being at the beginning of the new link rather than at its end -- which stops fluent typing.', 'Reproduce:\n1.', 'Go to an RTL wiki.', '2.', 'Go to a new sentence or new paragraph (cursor should be in an empty space)\n3.', 'Create link, followed by enter/enter to close the inspector\n4.', 'The cursor appears at the left of the word (which is the beginning in RTL) rather than the right of the word.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249995,"VisualEditor: After adding a link, cursor appears before rather than after the new insertion","Change 81872 merged by jenkins-bot:
+Cursor fix after link insertion
+
+https://gerrit.wikimedia.org/r/81872",task_subcomment,['Change 81872 merged by jenkins-bot:\nCursor fix after link insertion\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249994,"VisualEditor: After adding a link, cursor appears before rather than after the new insertion","Change 81872 had a related patch set uploaded by Jforrester:
+Cursor fix after link insertion
+
+https://gerrit.wikimedia.org/r/81872",task_subcomment,['Change 81872 had a related patch set uploaded by Jforrester:\nCursor fix after link insertion\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+249991,"VisualEditor: After adding a link, cursor appears before rather than after the new insertion","This was actually not just for RTL wikis, and the submitted patch fixes the problem for both directions in Annotation Inspector (for both links and languages)",task_subcomment,"['This was actually not just for RTL wikis, and the submitted patch fixes the problem for both directions in Annotation Inspector (for both links and languages)']",['BUG REPRODUCTION']
+55543,VisualEditor: Editing a  block with the experimental generic editor leads to brokenness because the attributes get blanked,"**Author:** `wojciech.r`
+
+**Description:**
+When I edit existing content in  tags, while editing it, error is shown about invalid language specified (lang=) and after saving it puts fragment of HTML code of this tag divs and entities into source of page and my code is broken.
+
+https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&oldid=773552
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Editing a  block with the experimental generic editor leads to brokenness because the attributes get blanked\n\n**Author:** CODE\n\n**Description:**\nWhen I edit existing content in  tags, while editing it, error is shown about invalid language specified (lang=) and after saving it puts fragment of HTML code of this tag divs and entities into source of page and my code is broken.', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+249251,VisualEditor: Editing a  block with the experimental generic editor leads to brokenness because the attributes get blanked,"This is now fixed in master, and will be released to MediaWiki.org on Thursday 5 September. Sorry for the disruption.",task_subcomment,"['This is now fixed in master, and will be released to MediaWiki.org on Thursday 5 September.', 'Sorry for the disruption.']","['SOLUTION USAGE', 'ACTION ON ISSUE']"
+249244,VisualEditor: Editing a  block with the experimental generic editor leads to brokenness because the attributes get blanked,"Change 82063 merged by jenkins-bot:
+Round trip alien extensions correctly when edited
+
+https://gerrit.wikimedia.org/r/82063",task_subcomment,['Change 82063 merged by jenkins-bot:\nRound trip alien extensions correctly when edited\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249239,VisualEditor: Editing a  block with the experimental generic editor leads to brokenness because the attributes get blanked,This fix preserves attributes correctly. The above bug would allow you to edit them.,task_subcomment,"['This fix preserves attributes correctly.', 'The above bug would allow you to edit them.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+249235,VisualEditor: Editing a  block with the experimental generic editor leads to brokenness because the attributes get blanked,Related bug 53614,task_subcomment,['Related bug 53614'],['OBSERVED BUG BEHAVIOR']
+249231,VisualEditor: Editing a  block with the experimental generic editor leads to brokenness because the attributes get blanked,"Change 82063 had a related patch set uploaded by Esanders:
+Round trip alien extensions correctly when edited
+
+https://gerrit.wikimedia.org/r/82063",task_subcomment,['Change 82063 had a related patch set uploaded by Esanders:\nRound trip alien extensions correctly when edited\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+55507,VisualEditor: Pressing up while next to an inline image throws an exception,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor: Pressing up while next to an inline image throws an exception\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+246922,VisualEditor: Pressing up while next to an inline image throws an exception,"Change 81596 merged by jenkins-bot:
+Move contentEditable=false to protected node
+
+https://gerrit.wikimedia.org/r/81596",task_subcomment,['Change 81596 merged by jenkins-bot:\nMove contentEditable=false to protected node\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+246919,VisualEditor: Pressing up while next to an inline image throws an exception,"Change 81596 had a related patch set uploaded by Esanders:
+Move contentEditable=false to protected node
+
+https://gerrit.wikimedia.org/r/81596",task_subcomment,['Change 81596 had a related patch set uploaded by Esanders:\nMove contentEditable=false to protected node\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+55477,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".)
+
+Example institution page:
+http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma
+
+Example course page:
+http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages\n\nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"".', '(VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".)', 'Example institution page:\nURL\n\nExample course page:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+244684,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote:
+
+P.S. Go to a production wiki and try this in a js console:
+
+mw.config.get('wgContentNamespaces')
+
+The results coincide:
+
+https://github.com/wikimedia/operations-mediawiki-config/blob/master/wmf-config/InitialiseSettings.php#L9292-9349
+
+I lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...",task_subcomment,"['**andrew.green.df** wrote:\n\nP.S.', ""Go to a production wiki and try this in a js console:\n\nmw.config.get('wgContentNamespaces')\n\nThe results coincide:\n\nURL\n\nI lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...""]","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION']"
+244678,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote:
+
+Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",task_subcomment,"['**andrew.green.df** wrote:\n\nAdded a comment on the Gerrit change.', 'tl;dr: Is $wgContentNamespaces getting checked?', ""I don't see how EP_NS could be there, and checking it in js seems to fix the issue."", 'Thanks!']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+244674,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Change 125233 merged by jenkins-bot:
+Don't change tabs on Education Program pages
+
+https://gerrit.wikimedia.org/r/125233",task_subcomment,"[""Change 125233 merged by jenkins-bot:\nDon't change tabs on Education Program pages\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+244670,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","(In reply to Andrew Green from comment #9)
+> I can look into making the EP extension warn VE through some generic
+> mechanism.
+
+Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-)
+
+
+> BTW, I wouldn't recommend that anyone try to make major changes to the EP
+> extension, as the plan is just to rewrite it.
+
+Understood. 
+
+
+> Alex's patch also looks like a fine temporary solution. :)
+
+Alex's patch is necessarily a horrible hack, but yeah…",task_subcomment,"['(In reply to Andrew Green from comment #9)\nQUOTE\nQUOTE\n\nIdeally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely.', ':-)\n\n\nQUOTE\nQUOTE\n\nUnderstood.', ""QUOTE\n\nAlex's patch is necessarily a horrible hack, but yeah…""]","['MOTIVATION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+244666,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote:
+
+I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes.
+
+BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it.
+
+The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",task_subcomment,"['**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism.', ""The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes."", ""BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it."", 'The issues Krinkle mentions are certainly valid.', ""Alex's patch also looks like a fine temporary solution."", ':)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244665,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","(In reply to Krinkle from comment #7)
+> I'd say EP should either let us know how to generically detect it without
+> being EP specific, or it should implement support to at least do one thing
+> right. Possibly we could do the latter ourselves (maybe Alex is interested
+> in patching EP).
+
+I don't really think this bug is important enough to VE to justify making big changes to how another extension works...",task_subcomment,"[""(In reply to Krinkle from comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't really think this bug is important enough to VE to justify making big changes to how another extension works...""]",['SOLUTION DISCUSSION']
+244661,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.
+
+Not one of them is being used by EP right now.
+
+* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page).
+
+* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id.
+
+* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because:
+  1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=).
+  2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected.
+  3) Existence check impossible.  Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.
+
+There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them.
+
+I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",task_subcomment,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n  1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244658,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Change 125233 had a related patch set uploaded by Alex Monk:
+Only make tab changes on articles
+
+https://gerrit.wikimedia.org/r/125233",task_subcomment,['Change 125233 had a related patch set uploaded by Alex Monk:\nOnly make tab changes on articles\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244655,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages",I think VE shouldn't be modifying tabs on pages which aren't articles (check wgIsArticle is true before doing anything).,task_subcomment,"[""I think VE shouldn't be modifying tabs on pages which aren't articles (check wgIsArticle is true before doing anything).""]",['OBSERVED BUG BEHAVIOR']
+244651,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Slinging to Alex – not sure what the fix here would be (it feels like overriding the semantics of a tab is something that should involve a class change, really) – thoughts?",task_subcomment,"['Slinging to Alex – not sure what the fix here would be (it feels like overriding the semantics of a tab is something that should involve a class change, really) – thoughts?']",['SOLUTION DISCUSSION']
+244643,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it. :)",task_subcomment,"['Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it.', ':)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244637,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages",*** Bug 56844 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 56844 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244633,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","@James: Any chance of getting this fixed soon? Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.",task_subcomment,"['SCREEN_NAME: Any chance of getting this fixed soon?', 'Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+55445,VisualEditor: Metadata information missing from transaction when content is inserted,"The final case in ve.dm.Document.getMetadataReplace() applies if insert.length > remove.length.  But in this case only the 'retain' and 'insert' fields are set on the returned object.  In ve.dm.Transaction.pushReplace() we only add the {retain,remove,insert}Metadata fields to the operation if the 'remove' field on the object returned from getMetadataReplace() is not undefined.  So these fields won't be set correctly if insert.length > remove.length.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Metadata information missing from transaction when content is inserted\n\nThe final case in ve.dm.Document.getMetadataReplace() applies if insert.length > remove.length.', ""But in this case only the 'retain' and 'insert' fields are set on the returned object."", ""In ve.dm.Transaction.pushReplace() we only add the {retain,remove,insert}Metadata fields to the operation if the 'remove' field on the object returned from getMetadataReplace() is not undefined."", ""So these fields won't be set correctly if insert.length > remove.length."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242791,VisualEditor: Metadata information missing from transaction when content is inserted,"Change 81928 merged by jenkins-bot:
+Collapse metadata on any removal.
+
+https://gerrit.wikimedia.org/r/81928",task_subcomment,"['Change 81928 merged by jenkins-bot:\nCollapse metadata on any removal.', 'GERRIT_URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+242785,VisualEditor: Metadata information missing from transaction when content is inserted,"Change 81928 had a related patch set uploaded by Cscott:
+Collapse metadata on any removal.
+
+https://gerrit.wikimedia.org/r/81928",task_subcomment,"['Change 81928 had a related patch set uploaded by Cscott:\nCollapse metadata on any removal.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+55444,VisualEditor: Metadata should always be collapsed on replace,"In ve.dm.Document.getMetadataReplace(), we only merge metadata if the amount removed is larger than the amount inserted.  But this could end up putting metadata in odd positions, for example if you have Foo[[Category:Bar]]BazQuux and you delete 'ooBa' and replace it with {image}xxx{/image}, then the category ends up inside the image.
+
+We should always merge metadata when a segment is deleted, so that it appears outside any new structure added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Metadata should always be collapsed on replace\n\nIn ve.dm.Document.getMetadataReplace(), we only merge metadata if the amount removed is larger than the amount inserted.', ""But this could end up putting metadata in odd positions, for example if you have Foo[[Category:Bar]]BazQuux and you delete 'ooBa' and replace it with {image}xxx{/image}, then the category ends up inside the image."", 'We should always merge metadata when a segment is deleted, so that it appears outside any new structure added.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+242747,VisualEditor: Metadata should always be collapsed on replace,"Change 81928 merged by jenkins-bot:
+Collapse metadata on any removal.
+
+https://gerrit.wikimedia.org/r/81928",task_subcomment,"['Change 81928 merged by jenkins-bot:\nCollapse metadata on any removal.', 'GERRIT_URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+242738,VisualEditor: Metadata should always be collapsed on replace,"Change 81928 had a related patch set uploaded by Cscott:
+Collapse metadata on any removal.
+
+https://gerrit.wikimedia.org/r/81928",task_subcomment,"['Change 81928 had a related patch set uploaded by Cscott:\nCollapse metadata on any removal.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+55436,"VisualEditor: Style Parsoid's 
    s to look like MediaWiki's 
    s rather than replacing them","Right now VisualEditor transforms the HTML Parsoid gives us (which is nicely-structured 
    s) into the mess of 
    s that MediaWiki's PHP parser throws out (up?). This is so that VE's rendered HTML magically inherits the styling that the images get on the read page, which includes
+
+Instead, we should just style these using CSS. However, this is difficult because the styles are specific to 
    s with known classes (and Parsoid's HTML has no 
    s), and is often over-ridden in wiki- or user-specific CSS (e.g. Wikia's sites' skins, or that on Cherokee Wikipedia).
+
+From quickly playing around, a basic CSS style that implements core-MW would be something like:
+
+figure
+	float: right;
+	border: 1px solid #CCC;
+	padding: 3px;
+	width: 172px;
+	background: #FAFAFA;
+	font-size: 13px;
+	margin-right: 1.2em;
+
+img
+	border: 1px solid #CCC;
+
+figcaption
+	padding: 3px;
+	font-size: smaller;
+	line-height: 1.4em;
+	width: 15em;
+	margin: 2px 0px;
+	padding-top: 0px;
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Style Parsoid\'s 
    s to look like MediaWiki\'s 
    s rather than replacing them\n\nRight now VisualEditor transforms the HTML Parsoid gives us (which is nicely-structured 
    s) into the mess of 
    s that MediaWiki\'s PHP parser throws out (up?).', ""This is so that VE's rendered HTML magically inherits the styling that the images get on the read page, which includes\n\nInstead, we should just style these using CSS."", ""However, this is difficult because the styles are specific to 
    s with known classes (and Parsoid's HTML has no 
    s), and is often over-ridden in wiki- or user-specific CSS (e.g."", ""Wikia's sites' skins, or that on Cherokee Wikipedia)."", 'From quickly playing around, a basic CSS style that implements core-MW would be something like:\n\nfigure\n\tfloat: right;\n\tborder: 1px solid #CCC;\n\tpadding: 3px;\n\twidth: 172px;\n\tbackground: #FAFAFA;\n\tfont-size: 13px;\n\tmargin-right: 1.2em;\n\nimg\n\tborder: 1px solid #CCC;\n\nfigcaption\n\tpadding: 3px;\n\tfont-size: smaller;\n\tline-height: 1.4em;\n\twidth: 15em;\n\tmargin: 2px 0px;\n\tpadding-top: 0px;\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+242319,"VisualEditor: Style Parsoid's 
    s to look like MediaWiki's 
    s rather than replacing them","Change 93417 merged by jenkins-bot:
+Render CE MWBlockImageNodes as styled 
    s
+
+https://gerrit.wikimedia.org/r/93417",task_subcomment,['Change 93417 merged by jenkins-bot:\nRender CE MWBlockImageNodes as styled 
    s\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+242317,"VisualEditor: Style Parsoid's 
    s to look like MediaWiki's 
    s rather than replacing them","Change 93417 had a related patch set uploaded by Jforrester:
+Render CE MWBlockImageNodes as styled 
    s
+
+https://gerrit.wikimedia.org/r/93417",task_subcomment,['Change 93417 had a related patch set uploaded by Jforrester:\nRender CE MWBlockImageNodes as styled 
    s\n\nGERRIT_URL'],['ACTION ON ISSUE']
+55413,"TemplateData: Consider support for non-template transclusions (magic words, parser functions)","Right now it is only intended for data about custom wiki-made templates.
+
+To support magic words and parser functions, we'll need to make a few changes to make sure there are no conflicts or wrong assumptions.
+
+A few random points:
+* 'titles' parameter in the API module
+* The PHP parser prefers native magic word over templates (creating Template:PAGENAME and using {{PAGENAME}}, will not use that template).
+* Should there be an implied property 'type':
+  - type:template -> {{Foo}}, {{:Foo}}, {{Template:Foo}}, {{Project:Foo}}
+  - type:parserfunction -> {{PAGENAME}}, {{urlencode:123}}, {{#special:Watchlist}}
+
+* parser functions don't have numerical parameters, and the first parameter is separated by colon, not by pipe. So we need a way (both in TemplateData and VisualEditor) to insert unnamed parameters without using numbers.
+
+ e.g. {{urlencode:Foo|WIKI}} is correct, but {{urlencode:Foo|1=WIKI}} or {{urlencode:1=Foo|2=WIKI}} or {{urlencode|1=Foo|2=WIKI}} is wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['TemplateData: Consider support for non-template transclusions (magic words, parser functions)\n\nRight now it is only intended for data about custom wiki-made templates.', ""To support magic words and parser functions, we'll need to make a few changes to make sure there are no conflicts or wrong assumptions."", ""A few random points:\n* 'titles' parameter in the API module\n* The PHP parser prefers native magic word over templates (creating Template:PAGENAME and using {{PAGENAME}}, will not use that template)."", ""* Should there be an implied property 'type':\n  - type:template -> {{Foo}}, {{:Foo}}, {{Template:Foo}}, {{Project:Foo}}\n  - type:parserfunction -> {{PAGENAME}}, {{urlencode:123}}, {{#special:Watchlist}}\n\n* parser functions don't have numerical parameters, and the first parameter is separated by colon, not by pipe."", 'So we need a way (both in TemplateData and VisualEditor) to insert unnamed parameters without using numbers.', 'e.g.', '{{urlencode:Foo|WIKI}} is correct, but {{urlencode:Foo|1=WIKI}} or {{urlencode:1=Foo|2=WIKI}} or {{urlencode|1=Foo|2=WIKI}} is wrong.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+1960990,"TemplateData: Consider support for non-template transclusions (magic words, parser functions)","Change 819740 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):
+%%%[mediawiki/extensions/TemplateData@master] Specification.md: Update to add parser functions and extension tags%%%
+https://gerrit.wikimedia.org/r/819740",task_subcomment,['Change 819740 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):\n%%%[mediawiki/extensions/TemplateData@master] Specification.md: Update to add parser functions and extension tags%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1959573,"TemplateData: Consider support for non-template transclusions (magic words, parser functions)","Briefly: {T204371} proposing allowing a vertical pipe to separate the first argument of a parser function, so that's not necessarily an issue.  {T204307} proposes allowing parser functions to opt-in to the ""standard"" named-argument processing such as used in templates, which I think is a better way of solving that particular problem in the long term than teaching VE/Parsoid a whole new set of serialization options.
+
+In general I'd like to have a ""parser function syntax"" alternative for every extension and magic word, so that we wouldn't ""need"" the `type` parameter, we'd just always look up the various constructs in their ""parser function form"".  The one tricky case is extensions, which do already have a parser function form in `{{#tag}}` but then would need an additional extension hook because `{{#tag}}` is used for *every* extension.  It's a little awkward, because I don't ""really"" want to have to do dynamic dispatch on both the first argument *and* the parser function name, but I guess doing so would help with {{#invoke}} as well, so maybe I just need to support delegation.",task_subcomment,"[""Briefly: {T204371} proposing allowing a vertical pipe to separate the first argument of a parser function, so that's not necessarily an issue."", '{T204307} proposes allowing parser functions to opt-in to the ""standard"" named-argument processing such as used in templates, which I think is a better way of solving that particular problem in the long term than teaching VE/Parsoid a whole new set of serialization options.', 'In general I\'d like to have a ""parser function syntax"" alternative for every extension and magic word, so that we wouldn\'t ""need"" the CODE parameter, we\'d just always look up the various constructs in their ""parser function form"".', 'The one tricky case is extensions, which do already have a parser function form in CODE but then would need an additional extension hook because CODE is used for *every* extension.', 'It\'s a little awkward, because I don\'t ""really"" want to have to do dynamic dispatch on both the first argument *and* the parser function name, but I guess doing so would help with {{#invoke}} as well, so maybe I just need to support delegation.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+55385,VisualEditor: Cursor movement stalls after cut-pasting text containing ref tags,"Steps to produce the error
+
+1. Edit a page with VE
+2. Cut a block of text containing a reference tag
+3. Paste it somewhere else
+
+Now try to move the cursor by arrow keys
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",task_description,"['VisualEditor: Cursor movement stalls after cut-pasting text containing ref tags\n\nSteps to produce the error\n\n1.', 'Edit a page with VE\n2.', 'Cut a block of text containing a reference tag\n3.', 'Paste it somewhere else\n\nNow try to move the cursor by arrow keys\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+401464,VisualEditor: Cursor movement stalls after cut-pasting text containing ref tags," Firefox and Chrome on Mac - a cursor, when moved with arrow keys,  successfully skips the ref section.  Checked in test2/production. 
+
+",task_subcomment,"[' Firefox and Chrome on Mac - a cursor, when moved with arrow keys,  successfully skips the ref section.', 'Checked in test2/production.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+400967,VisualEditor: Cursor movement stalls after cut-pasting text containing ref tags," Firefox and Chrome on Mac - a cursor, when moved with arrow keys,  successfully skips the ref section.  Checked in test2. 
+
+Since it's an old bug - marking it's an invalid for now. ",task_subcomment,"[' Firefox and Chrome on Mac - a cursor, when moved with arrow keys,  successfully skips the ref section.', 'Checked in test2.', ""Since it's an old bug - marking it's an invalid for now.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+55375,VisualEditor: Firefox doesn't fire a copy event when only a FocusableNode is selected,"Only workaround I can think of is to create a fake hidden selection whenever a FocusableNode(s) is selected on it's own.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Firefox doesn't fire a copy event when only a FocusableNode is selected\n\nOnly workaround I can think of is to create a fake hidden selection whenever a FocusableNode(s) is selected on it's own."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+239233,VisualEditor: Firefox doesn't fire a copy event when only a FocusableNode is selected,"Change 83222 merged by jenkins-bot:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",task_subcomment,['Change 83222 merged by jenkins-bot:\nThe Great [...] Rewrite of 2013: Clipboard edition\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239227,VisualEditor: Firefox doesn't fire a copy event when only a FocusableNode is selected,"Change 83222 had a related patch set uploaded by Esanders:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",task_subcomment,['Change 83222 had a related patch set uploaded by Esanders:\nThe Great [...] Rewrite of 2013: Clipboard edition\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+55366,VisualEditor: getNearestCorrectOffset doesn't ignore internal lists,"This causes an exception to be thrown if you try to delete a content node at the end of the visible document (e.g. a reference list)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: getNearestCorrectOffset doesn't ignore internal lists\n\nThis causes an exception to be thrown if you try to delete a content node at the end of the visible document (e.g."", 'a reference list)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238731,VisualEditor: getNearestCorrectOffset doesn't ignore internal lists,"ElementLinearData#getRelativeOffset now checks for handlesOwnChildren, which prevents this from being an issue.",task_subcomment,"['ElementLinearData#getRelativeOffset now checks for handlesOwnChildren, which prevents this from being an issue.']",['BUG REPRODUCTION']
+238723,VisualEditor: getNearestCorrectOffset doesn't ignore internal lists,May have been ameliorated by https://gerrit.wikimedia.org/r/98515,task_subcomment,['May have been ameliorated by GERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+55365,VisualEditor: Unnamed references don't register when cloned,"1. Copy and paste an unnamed reference
+2. It doesn't appear as a subitem in the ref list
+3. Undo. The reference is now index 0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Unnamed references don't register when cloned\n\n1."", 'Copy and paste an unnamed reference\n2.', ""It doesn't appear as a subitem in the ref list\n3."", 'Undo.', 'The reference is now index 0.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238675,VisualEditor: Unnamed references don't register when cloned,"Change 81417 merged by jenkins-bot:
+Always give references names. Ignore if used once.
+
+https://gerrit.wikimedia.org/r/81417",task_subcomment,"['Change 81417 merged by jenkins-bot:\nAlways give references names.', 'Ignore if used once.', 'GERRIT_URL']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238672,VisualEditor: Unnamed references don't register when cloned,"Change 81417 had a related patch set uploaded by Esanders:
+Always give references names. Ignore if used once.
+
+https://gerrit.wikimedia.org/r/81417",task_subcomment,"['Change 81417 had a related patch set uploaded by Esanders:\nAlways give references names.', 'Ignore if used once.', 'GERRIT_URL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+55364,VisualEditor: [Regression] Copying over nodes results in paste adding newlines,"Select text around a content node (e.g. a reference: ""foo [1] bar"" ) and then copy paste it. Note you now have extra newlines.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: [Regression] Copying over nodes results in paste adding newlines\n\nSelect text around a content node (e.g.', 'a reference: ""foo [1] bar"" ) and then copy paste it.', 'Note you now have extra newlines.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238631,VisualEditor: [Regression] Copying over nodes results in paste adding newlines,"Change 81028 merged by jenkins-bot:
+When pasting, try to use original range
+
+https://gerrit.wikimedia.org/r/81028",task_subcomment,"['Change 81028 merged by jenkins-bot:\nWhen pasting, try to use original range\n\nGERRIT_URL']",['ACTION ON ISSUE']
+238622,VisualEditor: [Regression] Copying over nodes results in paste adding newlines,"Change 81028 had a related patch set uploaded by Esanders:
+When pasting, try to use original range
+
+https://gerrit.wikimedia.org/r/81028",task_subcomment,"['Change 81028 had a related patch set uploaded by Esanders:\nWhen pasting, try to use original range\n\nGERRIT_URL']",['OBSERVED BUG BEHAVIOR']
+55362,VisualEditor: Document loses focus after cutting a FocusableNode,"1. select a focusable node only (e.g. a reference)
+2. Cut it (ctrl+x)
+3. Note you now have no cursor/selection
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Document loses focus after cutting a FocusableNode\n\n1. select a focusable node only (e.g.', 'a reference)\n2.', 'Cut it (ctrl+x)\n3.', 'Note you now have no cursor/selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['1.', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238550,VisualEditor: Document loses focus after cutting a FocusableNode,Fixed in master; will be deployed on Thursday as part of the regular push.,task_subcomment,['Fixed in master; will be deployed on Thursday as part of the regular push.'],['ACTION ON ISSUE']
+238545,VisualEditor: Document loses focus after cutting a FocusableNode,"Change 81027 merged by jenkins-bot:
+Give document real focus after cut
+
+https://gerrit.wikimedia.org/r/81027",task_subcomment,['Change 81027 merged by jenkins-bot:\nGive document real focus after cut\n\nGERRIT_URL'],['ACTION ON ISSUE']
+238535,VisualEditor: Document loses focus after cutting a FocusableNode,"Change 81027 had a related patch set uploaded by Jforrester:
+Give document real focus after cut
+
+https://gerrit.wikimedia.org/r/81027",task_subcomment,['Change 81027 had a related patch set uploaded by Jforrester:\nGive document real focus after cut\n\nGERRIT_URL'],['BUG REPRODUCTION']
+238529,VisualEditor: Document loses focus after cutting a FocusableNode,https://gerrit.wikimedia.org/r/#/c/81027/ fixes,task_subcomment,['URL fixes'],['SOLUTION DISCUSSION']
+55360,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"example 1
+
+new issue as of Aug 26, seen on test2wiki
+
+this is easily triggered by an automated browser test but can also be triggered manually: 
+
+while typing edits, click the Save page button.  
+click Review 
+
+Edited page and diff view contents are not the same. See screen shot examples 1 and 2. 
+
+ex 1: ""asfdaEdit"" in edited page vs ""asEdadit"" in diff view where original page has ""Edit""
+
+ex 2: ""aaqaaaStarting"" in edited page vs ""aSqaaatarting"" in diff view where original page has ""Starting""
+
+in at least one case, the actual saved contents of the page differs from the buffer that appears upon clicking Edit to invoke VE, see example 3
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F11309}",task_description,"['VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?)', 'example 1\n\nnew issue as of Aug 26, seen on test2wiki\n\nthis is easily triggered by an automated browser test but can also be triggered manually: \n\nwhile typing edits, click the Save page button.', 'click Review \n\nEdited page and diff view contents are not the same.', 'See screen shot examples 1 and 2. \n\nex 1: ""asfdaEdit"" in edited page vs ""asEdadit"" in diff view where original page has ""Edit""\n\nex 2: ""aaqaaaStarting"" in edited page vs ""aSqaaatarting"" in diff view where original page has ""Starting""\n\nin at least one case, the actual saved contents of the page differs from the buffer that appears upon clicking Edit to invoke VE, see example 3\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11309}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238443,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"This has been fixed in VisualEditor master as part of gerrit 81213, and we will do an emergency push of this to wmf14 tomorrow to fix it in product; sorry for the disruption.",task_subcomment,"['This has been fixed in VisualEditor master as part of gerrit 81213, and we will do an emergency push of this to wmf14 tomorrow to fix it in product; sorry for the disruption.']",['ACTION ON ISSUE']
+238435,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),I should mention that the (corrupted) diff view contents is what is actually saved when finally saving the page in VE,task_subcomment,['I should mention that the (corrupted) diff view contents is what is actually saved when finally saving the page in VE'],['OBSERVED BUG BEHAVIOR']
+238429,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"I can reproduce this consistently on test2wiki most of the time manually and automatedly all of the time as of the last VE deploy.  To repro manually (I use Chrome): 
+
+* Pick a random page on test2wiki that has existing text
+* click Edit for VE. click no other thing.
+* Poise your right hand so that you are prepared to click 'Save page'
+* With your left hand type randomly very very quickly. While typing with your left hand, click 'Save page' with your right hand
+
+* take a look at the VE page contents (CE I assume).  It will appear to be accurate.  It will be different than what is in the diff view (DM I assume). 
+
+Note: the automated test moves quickly enough that *nothing* typed into the VE edit interface is reflected in the diff view.  I can demo this if you'd like.
+
+Again, this is new behavior as of Aug 26.",task_subcomment,"['I can reproduce this consistently on test2wiki most of the time manually and automatedly all of the time as of the last VE deploy.', 'To repro manually (I use Chrome): \n\n* Pick a random page on test2wiki that has existing text\n* click Edit for VE.', 'click no other thing.', ""* Poise your right hand so that you are prepared to click 'Save page'\n* With your left hand type randomly very very quickly."", ""While typing with your left hand, click 'Save page' with your right hand\n\n* take a look at the VE page contents (CE I assume)."", 'It will appear to be accurate.', 'It will be different than what is in the diff view (DM I assume).', 'Note: the automated test moves quickly enough that *nothing* typed into the VE edit interface is reflected in the diff view.', ""I can demo this if you'd like."", 'Again, this is new behavior as of Aug 26.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238423,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"I still can't reproduce these in Chrome/Firefox/Safari/Opera testing on local master, on production test2, or production enwiki/mediawikiwiki.
+
+What does ""can also be triggered manually"" mean - how? Or is this an unreliable/occasional thing? Possibly a system-load issue?
+
+Is this specific to test2?
+
+From the screenshots, the displayed content (from CE) and the data model (in DM) appear to have gotten out of sync, which Shouldn't Ever Happen(tm).",task_subcomment,"[""I still can't reproduce these in Chrome/Firefox/Safari/Opera testing on local master, on production test2, or production enwiki/mediawikiwiki."", 'What does ""can also be triggered manually"" mean - how?', 'Or is this an unreliable/occasional thing?', 'Possibly a system-load issue?', 'Is this specific to test2?', ""From the screenshots, the displayed content (from CE) and the data model (in DM) appear to have gotten out of sync, which Shouldn't Ever Happen(tm).""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238418,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13176
+example 3
+
+**Attached**: {F11316}",task_subcomment,['Created attachment 13176\nexample 3\n\n**Attached**: {F11316}'],['ATTACHMENT']
+238413,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13175
+example 3
+
+**Attached**: {F11315}",task_subcomment,['Created attachment 13175\nexample 3\n\n**Attached**: {F11315}'],['ATTACHMENT']
+238407,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13174
+example 2
+
+**Attached**: {F11312}",task_subcomment,['Created attachment 13174\nexample 2\n\n**Attached**: {F11312}'],['ATTACHMENT']
+238401,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13173
+example 2
+
+**Attached**: {F11311}",task_subcomment,['Created attachment 13173\nexample 2\n\n**Attached**: {F11311}'],['ATTACHMENT']
+238395,VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13172
+example 1
+
+**Attached**: {F11310}",task_subcomment,['Created attachment 13172\nexample 1\n\n**Attached**: {F11310}'],['ATTACHMENT']
+55345,VisualEditor: Creating a new reference with blank content leads to insertion of a  tag in the wikitext,"See https://pl.wikipedia.org/w/index.php?title=Wojnicz&diff=37347163&oldid=37312891 for an example - I'm not sure what the problem is, here, since that's a meaningless tag :/.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Creating a new reference with blank content leads to insertion of a  tag in the wikitext\n\nSee URL for an example - I'm not sure what the problem is, here, since that's a meaningless tag :/."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237658,VisualEditor: Creating a new reference with blank content leads to insertion of a  tag in the wikitext,Fixed in master; will be deployed on Thursday as part of the regular push.,task_subcomment,['Fixed in master; will be deployed on Thursday as part of the regular push.'],['ACTION ON ISSUE']
+237652,VisualEditor: Creating a new reference with blank content leads to insertion of a  tag in the wikitext,"Change 81438 merged by jenkins-bot:
+Disable inserting/changing references when surface widget is empty
+
+https://gerrit.wikimedia.org/r/81438",task_subcomment,['Change 81438 merged by jenkins-bot:\nDisable inserting/changing references when surface widget is empty\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237647,VisualEditor: Creating a new reference with blank content leads to insertion of a  tag in the wikitext,"Change 81438 had a related patch set uploaded by Esanders:
+Disable inserting/changing references when surface widget is empty
+
+https://gerrit.wikimedia.org/r/81438",task_subcomment,['Change 81438 had a related patch set uploaded by Esanders:\nDisable inserting/changing references when surface widget is empty\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237642,VisualEditor: Creating a new reference with blank content leads to insertion of a  tag in the wikitext,"Looks like it's what happens when you insert a reference without typing anything into the box. Hit ""insert reference"", leave the main field blank, go immediately to the insert button, and... https://pl.wikipedia.org/w/index.php?title=Wikipedysta%3AOkeyes_%28WMF%29&diff=37370424&oldid=37257359",task_subcomment,"[""Looks like it's what happens when you insert a reference without typing anything into the box."", 'Hit ""insert reference"", leave the main field blank, go immediately to the insert button, and... URL']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+55303,"Don't allow nested s, because Cite.php doesn't","From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE.2C_Sfn_template_within_reference.2C_Vcite_error
+
+Adding a  tag (e.g., a bibliographic citation) inside another  tag with a different group (e.g., an explanatory footnote), displays as desired in VisualEditor, but when you save the page, it isn't visible because of T22707 in Cite.php
+
+This is most likely to happen with a ref-creating template like {{sfn}}, since VisualEditor doesn't have the buttons to created nested ref tags directly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=570036528&oldid=570035364",task_description,"[""Don't allow nested s, because Cite.php doesn't\n\nFrom URL\n\nAdding a  tag (e.g., a bibliographic citation) inside another  tag with a different group (e.g., an explanatory footnote), displays as desired in VisualEditor, but when you save the page, it isn't visible because of T22707 in Cite.php\n\nThis is most likely to happen with a ref-creating template like {{sfn}}, since VisualEditor doesn't have the buttons to created nested ref tags directly."", '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**URL**: URL']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+235284,"Don't allow nested s, because Cite.php doesn't","We have mismatched behavior.  Either *both* systems should display nested refs, or VisualEditor should stop displaying nested refs to match the limited features available to readers.
+
+Whether this mismatch should be solved by reducing VisualEditor's ability to process nested refs or by increasing the other system's ability to process nested refs is beyond my paygrade.",task_subcomment,"['We have mismatched behavior.', 'Either *both* systems should display nested refs, or VisualEditor should stop displaying nested refs to match the limited features available to readers.', ""Whether this mismatch should be solved by reducing VisualEditor's ability to process nested refs or by increasing the other system's ability to process nested refs is beyond my paygrade.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235274,"Don't allow nested s, because Cite.php doesn't","(In reply to comment #0)
+> Adding a  tag (e.g., a bibliographic citation) inside another  tag
+> with a different group (e.g., an explanatory footnote), displays as desired
+> in
+> VisualEditor, but when you save the page, it isn't visible because of Bug
+> 20707
+> in Cite.php
+
+If this problem is covered in bug 20707 already I'm not sure what your intention was to file another bug report. Could you clarify please?",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIf this problem is covered in bug 20707 already I'm not sure what your intention was to file another bug report."", 'Could you clarify please?']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+55251,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing","The editor has the title and tooltip ""LaTeX"". This is not entirely correct. It's just the math environment subset for LaTeX that we can handle and support.
+
+The label also conflicts with the visual symbol, which clearly communicates the Math function using the sum symbol. Remember that many people might not even know what LaTeX even is, causing further confusion.
+
+The problem here is that we want to explain to the user that we want him to enter the math using LaTeX, because otherwise he might not understand how to enter his formula. Perhaps that is why the LaTeX label was chosen.
+
+We should find a better way. Perhaps using a label or placeholder. ""Enter formula using AMS-LaTeX""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43058",task_description,"['VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing\n\nThe editor has the title and tooltip ""LaTeX"".', 'This is not entirely correct.', ""It's just the math environment subset for LaTeX that we can handle and support."", 'The label also conflicts with the visual symbol, which clearly communicates the Math function using the sum symbol.', 'Remember that many people might not even know what LaTeX even is, causing further confusion.', 'The problem here is that we want to explain to the user that we want him to enter the math using LaTeX, because otherwise he might not understand how to enter his formula.', 'Perhaps that is why the LaTeX label was chosen.', 'We should find a better way.', 'Perhaps using a label or placeholder.', '""Enter formula using AMS-LaTeX""\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+257059,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",verified in test2:https://test2.wikipedia.org/w/index.php?title=13th_december&veaction=edit,task_subcomment,['verified in test2:URL'],['OBSERVED BUG BEHAVIOR']
+257052,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",Verified in Betalabs,task_subcomment,['Verified in Betalabs'],['OBSERVED BUG BEHAVIOR']
+257045,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",This is now fixed in betalabs after we caused the English messages to get re-synched.,task_subcomment,['This is now fixed in betalabs after we caused the English messages to get re-synched.'],['SOLUTION USAGE']
+257040,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",okay but I checked it on Betalabs.,task_subcomment,['okay but I checked it on Betalabs.'],['OBSERVED BUG BEHAVIOR']
+257034,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing","@ryasmeen Fixed != deployed to production. That happens at a later time, usually somewhere within 2 weeks after getting fixed.",task_subcomment,"['SCREEN_NAME Fixed != deployed to production.', 'That happens at a later time, usually somewhere within 2 weeks after getting fixed.']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+257028,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",I am still seeing label Latex instead of Formula,task_subcomment,['I am still seeing label Latex instead of Formula'],['OBSERVED BUG BEHAVIOR']
+257021,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing","Change 100112 merged by jenkins-bot:
+Re-label the formula inspector to not be LaTeX
+
+https://gerrit.wikimedia.org/r/100112",task_subcomment,['Change 100112 merged by jenkins-bot:\nRe-label the formula inspector to not be LaTeX\n\nGERRIT_URL'],['ACTION ON ISSUE']
+257015,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing","Change 100112 had a related patch set uploaded by Jforrester:
+Re-label the formula inspector to not be LaTeX
+
+https://gerrit.wikimedia.org/r/100112",task_subcomment,['Change 100112 had a related patch set uploaded by Jforrester:\nRe-label the formula inspector to not be LaTeX\n\nGERRIT_URL'],['ACTION ON ISSUE']
+257009,"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing","I'm minded to just call it ""Formula"". Thoughts?",task_subcomment,"['I\'m minded to just call it ""Formula"".', 'Thoughts?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+55228,Nowiki tag not properly escaped when combined with other wiki markup,"From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Bold_and_nowiki.2C_other_markup
+
+If you add a nowiki tag by itself, the angle brackets get escaped out (&lt;nowiki&gt;, or does just plain </nowiki> work here at Bugzilla?).  If you add a nowiki tag plus some wikimarkup, like an asterisk at the start of a line or bold text, it doesn't.  This results in unpaired tags, sometimes functional wikimarkup, and always unexpected results.
+
+Try this:
+
+* You need a  tag '''here'''.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Nowiki tag not properly escaped when combined with other wiki markup\n\nFrom URL\n\nIf you add a nowiki tag by itself, the angle brackets get escaped out (&lt;nowiki&gt;, or does just plain </nowiki> work here at Bugzilla?).', ""If you add a nowiki tag plus some wikimarkup, like an asterisk at the start of a line or bold text, it doesn't."", 'This results in unpaired tags, sometimes functional wikimarkup, and always unexpected results.', ""Try this:\n\n* You need a  tag '''here'''."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+255560,Nowiki tag not properly escaped when combined with other wiki markup,"Change 137525 merged by jenkins-bot:
+Escape nowiki when combined with other wiki markup
+
+https://gerrit.wikimedia.org/r/137525",task_subcomment,['Change 137525 merged by jenkins-bot:\nEscape nowiki when combined with other wiki markup\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+255553,Nowiki tag not properly escaped when combined with other wiki markup,"Change 137525 had a related patch set uploaded by Arlolra:
+Escape nowiki when combined with other wiki markup
+
+https://gerrit.wikimedia.org/r/137525",task_subcomment,['Change 137525 had a related patch set uploaded by Arlolra:\nEscape nowiki when combined with other wiki markup\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+255546,Nowiki tag not properly escaped when combined with other wiki markup,"This is a Parsoid serializer bug:
+
+[subbu@earth tests] echo '* </nowiki> tag' | node parse --html2wt
+*  tag",task_subcomment,"[""This is a Parsoid serializer bug:\n\n[subbu@earth tests] echo '* </nowiki> tag' | node parse --html2wt\n*  tag""]",['OBSERVED BUG BEHAVIOR']
+55214,"Slugs are created inside empty table rows, creating pawns if used","At https://en.wikipedia.org/w/index.php?title=Churnet_Valley_Railway&diff=prev&oldid=569277862 it seems that a table ending with trailing new line syntax
+
+|-
+|}
+
+caused pawns to be added to the article. As discussed at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569732999#Chess_pieces_still_happening this syntax, although technically wrong, will continue to be added to articles. VE and Parsoid should therefore deal with this cleanly without the addition of any pawns to the article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Slugs are created inside empty table rows, creating pawns if used\n\nAt URL it seems that a table ending with trailing new line syntax\n\n|-\n|}\n\ncaused pawns to be added to the article.', 'As discussed at URL this syntax, although technically wrong, will continue to be added to articles.', 'VE and Parsoid should therefore deal with this cleanly without the addition of any pawns to the article.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+254487,"Slugs are created inside empty table rows, creating pawns if used","Change 119067 merged by jenkins-bot:
+Only insert slugs where paragraphs are allowed
+
+https://gerrit.wikimedia.org/r/119067",task_subcomment,['Change 119067 merged by jenkins-bot:\nOnly insert slugs where paragraphs are allowed\n\nGERRIT_URL'],['ACTION ON ISSUE']
+254479,"Slugs are created inside empty table rows, creating pawns if used","Change 119067 had a related patch set uploaded by Esanders:
+Only insert slugs where paragraphs are allowed
+
+https://gerrit.wikimedia.org/r/119067",task_subcomment,['Change 119067 had a related patch set uploaded by Esanders:\nOnly insert slugs where paragraphs are allowed\n\nGERRIT_URL'],['ACTION ON ISSUE']
+254471,"Slugs are created inside empty table rows, creating pawns if used",I think this edit https://fr.wikipedia.org/w/index.php?title=Cash_investigation&diff=96500094&oldid=95914321 is related.,task_subcomment,['I think this edit URL is related.'],['OBSERVED BUG BEHAVIOR']
+254465,"Slugs are created inside empty table rows, creating pawns if used","(In reply to comment #2)
+> To perhaps clarify, VE and parsoid should accept both
+> 
+> |content
+> |-
+> |}
+> 
+> and
+> 
+> |content
+> |}
+> 
+> as validly closed templates that should be displayed and rendered
+> identically.
+
+We currently don't strip empty table rows, which seems to be done in some conditions in the PHP parser + tidy combo. We could emulate this behavior in templated content and maybe also outside of templated content, but will need to avoid dirty diffs and preserve WYSIWYG behavior even when another row is added in VE.
+
+> Both syntaxes should be retained as is when roundtripping.
+
+This should already be the case in Parsoid. I just verified this at http://parsoid.wmflabs.org/_rtform/. Pawn insertion would a DOM modification in VE.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe currently don't strip empty table rows, which seems to be done in some conditions in the PHP parser + tidy combo."", 'We could emulate this behavior in templated content and maybe also outside of templated content, but will need to avoid dirty diffs and preserve WYSIWYG behavior even when another row is added in VE.', 'QUOTE\n\nThis should already be the case in Parsoid.', 'I just verified this at URL Pawn insertion would a DOM modification in VE.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+254461,"Slugs are created inside empty table rows, creating pawns if used","To perhaps clarify, VE and parsoid should accept both
+
+|content
+|-
+|}
+
+and
+
+|content
+|}
+
+as validly closed templates that should be displayed and rendered identically. Both syntaxes should be retained as is when roundtripping.",task_subcomment,"['To perhaps clarify, VE and parsoid should accept both\n\n|content\n|-\n|}\n\nand\n\n|content\n|}\n\nas validly closed templates that should be displayed and rendered identically.', 'Both syntaxes should be retained as is when roundtripping.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254459,"Slugs are created inside empty table rows, creating pawns if used",Pawns are firmly VE territory. Moving to the VisualEditor product.,task_subcomment,"['Pawns are firmly VE territory.', 'Moving to the VisualEditor product.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+55206,"VisualEditor: Blank page, list, [enter] lose cursor","<>
+
+Same for me, on Chrome the cursor does not disappear and you can press icons more than once, but if you type a word it will be split on more lines and you won't be able to wikilink it.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Blank page, list, [enter] lose cursor\n\n<>\n\nSame for me, on Chrome the cursor does not disappear and you can press icons more than once, but if you type a word it will be split on more lines and you won't be able to wikilink it."", 'Thanks.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+254051,"VisualEditor: Blank page, list, [enter] lose cursor",This was fixed a long while ago.,task_subcomment,['This was fixed a long while ago.'],['BUG REPRODUCTION']
+55151,VisualEditor: MW images shouldn't be able to take a link annotation,"There is no way to convert an image wrapped in a link to wikitext, so we shouldn't let a user do it. A plain image, on the other hand, can be link wrapped and we already handle this correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: MW images shouldn't be able to take a link annotation\n\nThere is no way to convert an image wrapped in a link to wikitext, so we shouldn't let a user do it."", 'A plain image, on the other hand, can be link wrapped and we already handle this correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+251316,VisualEditor: MW images shouldn't be able to take a link annotation,"Change 85010 merged by jenkins-bot:
+Node annotation blacklists
+
+https://gerrit.wikimedia.org/r/85010",task_subcomment,['Change 85010 merged by jenkins-bot:\nNode annotation blacklists\n\nGERRIT_URL'],['ACTION ON ISSUE']
+251310,VisualEditor: MW images shouldn't be able to take a link annotation,"Change 85011 merged by jenkins-bot:
+MW*ImageNode's can't take link annotations
+
+https://gerrit.wikimedia.org/r/85011",task_subcomment,"[""Change 85011 merged by jenkins-bot:\nMW*ImageNode's can't take link annotations\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+251302,VisualEditor: MW images shouldn't be able to take a link annotation,"Change 85011 had a related patch set uploaded by Esanders:
+MW*ImageNode's can't take link annotations
+
+https://gerrit.wikimedia.org/r/85011",task_subcomment,"[""Change 85011 had a related patch set uploaded by Esanders:\nMW*ImageNode's can't take link annotations\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+251293,VisualEditor: MW images shouldn't be able to take a link annotation,"Change 85010 had a related patch set uploaded by Esanders:
+Node annotation blacklists
+
+https://gerrit.wikimedia.org/r/85010",task_subcomment,['Change 85010 had a related patch set uploaded by Esanders:\nNode annotation blacklists\n\nGERRIT_URL'],['ACTION ON ISSUE']
+55143,Implement non-linear transitions,"Implement non-linear transitions between steps.  This is one of the key goals of the planned update to the API.  
+
+The idea is that each step has a callback function which decides which step to proceed to.  This callback is called when an event occurs, such certain mw.hook, a user-provided event (there will be a way to tell the tour to check at a particular time), or a page change.
+
+There can also be global transitions, which apply throughout the whole tour (for example, clicking ""edit source"" at any time may transition to the first step of the wikitext editing flow).
+
+Simple use case:
+
+Have a single tour with the basics of both wikitext and VisualEditor editing.  When you click ""edit source"" or ""edit beta"" at any time (unlike today, you don't have to be at the beginning), it transitions to the appropriate step.  You can then walk through the basic flows of the editors (as today)
+
+More elaborate:
+
+Your are in a detailed tour for VisualEditor.  You are in the step for the references dialog.  You click the template button, and it transitions to the step for adding a template.  When you walk through and save that, it transitions to a step for saving the reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['Implement non-linear transitions\n\nImplement non-linear transitions between steps.', 'This is one of the key goals of the planned update to the API.', 'The idea is that each step has a callback function which decides which step to proceed to.', 'This callback is called when an event occurs, such certain mw.hook, a user-provided event (there will be a way to tell the tour to check at a particular time), or a page change.', 'There can also be global transitions, which apply throughout the whole tour (for example, clicking ""edit source"" at any time may transition to the first step of the wikitext editing flow).', 'Simple use case:\n\nHave a single tour with the basics of both wikitext and VisualEditor editing.', 'When you click ""edit source"" or ""edit beta"" at any time (unlike today, you don\'t have to be at the beginning), it transitions to the appropriate step.', 'You can then walk through the basic flows of the editors (as today)\n\nMore elaborate:\n\nYour are in a detailed tour for VisualEditor.', 'You are in the step for the references dialog.', 'You click the template button, and it transitions to the step for adding a template.', 'When you walk through and save that, it transitions to a step for saving the reference.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250806,Implement non-linear transitions,"Change 116228 merged by jenkins-bot:
+Refactor and add non-linear tours, with tests
+
+https://gerrit.wikimedia.org/r/116228",task_subcomment,"['Change 116228 merged by jenkins-bot:\nRefactor and add non-linear tours, with tests\n\nGERRIT_URL']",['INVESTIGATION AND EXPLORATION']
+250796,Implement non-linear transitions,"Change 116228 had a related patch set uploaded by Mattflaschen:
+WIP: Refactor and add non-linear tours
+
+https://gerrit.wikimedia.org/r/116228",task_subcomment,['Change 116228 had a related patch set uploaded by Mattflaschen:\nWIP: Refactor and add non-linear tours\n\nGERRIT_URL'],['ACTION ON ISSUE']
+55079,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"This seems sporadic, and while it doesn't happen all the time, it does happen a lot, so I hope I am giving enough details to repeat this:
+
+1. Put the cursor on an empty line without text.
+2. Click the ""Bold"" button.
+3. Type gibberish fast (ldkjlskdfjlkdjs lskdjf lsdkjflsdkjljsf....)
+4. Witness weirdness: new characters pop up in the line underneath or in between the bits of gibberish, and if I try ""backspace"" to erase the lines even weirder stuff happen (like characters popup instead of being deleted, etc.
+
+This doesn't happen when I typed regular language, I suspect, then, that it has to do with the speed of the insertion?
+
+But after a single occurrence of this bug, the behavior of delete/backspace creates further bugs even if I stop typing quickly, or start new lines, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?)', ""This seems sporadic, and while it doesn't happen all the time, it does happen a lot, so I hope I am giving enough details to repeat this:\n\n1."", 'Put the cursor on an empty line without text.', '2.', 'Click the ""Bold"" button.', '3.', 'Type gibberish fast (ldkjlskdfjlkdjs lskdjf lsdkjflsdkjljsf....)\n4.', 'Witness weirdness: new characters pop up in the line underneath or in between the bits of gibberish, and if I try ""backspace"" to erase the lines even weirder stuff happen (like characters popup instead of being deleted, etc.', ""This doesn't happen when I typed regular language, I suspect, then, that it has to do with the speed of the insertion?"", 'But after a single occurrence of this bug, the behavior of delete/backspace creates further bugs even if I stop typing quickly, or start new lines, etc.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+247320,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),*** Bug 53317 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53317 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247314,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"Change 81213 merged by jenkins-bot:
+Detect outdated pending post KeyPress handler
+
+https://gerrit.wikimedia.org/r/81213",task_subcomment,['Change 81213 merged by jenkins-bot:\nDetect outdated pending post KeyPress handler\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247308,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),Further to my previous comment: it seems that it's actually onDocumentKeyPress which is doing the setTimeout which gets outdated; and that we can code our way around it because it's just there to do a surface-to-model poll.,task_subcomment,"[""Further to my previous comment: it seems that it's actually onDocumentKeyPress which is doing the setTimeout which gets outdated; and that we can code our way around it because it's just there to do a surface-to-model poll.""]",['SOLUTION DISCUSSION']
+247301,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"Change 81213 had a related patch set uploaded by Divec:
+Detect outdated pending post KeyPress handler
+
+https://gerrit.wikimedia.org/r/81213",task_subcomment,['Change 81213 had a related patch set uploaded by Divec:\nDetect outdated pending post KeyPress handler\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+247293,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"I can reproduce this just by holding a key down for a few seconds. It seems to be because of setTimeout( f(), 0 ) causing event handling to overlap. This could be challenging to resolve because of the way browser event handling works. Gory details below :-)
+
+On my slow Ubuntu laptop, I can reliably reproduce the bug. It happens if I just hold the 'x' key down inside a 
     for a couple of seconds.
+
+I'm pretty sure it's happening because we use setTimeout to process events. This can get complex up when two events are emitted by the browser at virtually the same time. In this case, ve.ce.SurfaceObserver.onDocumentKeyDown receives event 1, does some processing, then effectively does a setTimeout( f(), 0 ) to finish the processing. But by that time, the browser has already queued the handlers for event 2, so the processing for event 2 will start before the processing for event 1 has finished.
+
+I tested this by putting two lines at the top of onDocumentKeydown: a ve.log(""main..."") and a setTimeout( ve.log(""post...""), 0) . The corruption happens exactly when we get ""main..."" twice in a row followed by ""post..."" twice in a row. See http://pastebin.com/dzGYbpDq for full output.
+
+This may be challenging to resolve, because we probably need to do stuff both before and after the browser's native keydown handler. We can't manage all the handling in our own queue, because (afaik) the browser's native handling can't be postponed. So it seems the only obvious option would be to detect when there are overlapping events, and try and do act delicately enough that things don't break.
+
+Timo, any thoughts?",task_subcomment,"['I can reproduce this just by holding a key down for a few seconds.', 'It seems to be because of setTimeout( f(), 0 ) causing event handling to overlap.', 'This could be challenging to resolve because of the way browser event handling works.', 'Gory details below :-)\n\nOn my slow Ubuntu laptop, I can reliably reproduce the bug.', ""It happens if I just hold the 'x' key down inside a 
     for a couple of seconds."", ""I'm pretty sure it's happening because we use setTimeout to process events."", 'This can get complex up when two events are emitted by the browser at virtually the same time.', 'In this case, ve.ce.SurfaceObserver.onDocumentKeyDown receives event 1, does some processing, then effectively does a setTimeout( f(), 0 ) to finish the processing.', 'But by that time, the browser has already queued the handlers for event 2, so the processing for event 2 will start before the processing for event 1 has finished.', 'I tested this by putting two lines at the top of onDocumentKeydown: a ve.log(""main..."") and a setTimeout( ve.log(""post...""), 0) .', 'The corruption happens exactly when we get ""main..."" twice in a row followed by ""post..."" twice in a row.', 'See URL for full output.', ""This may be challenging to resolve, because we probably need to do stuff both before and after the browser's native keydown handler."", ""We can't manage all the handling in our own queue, because (afaik) the browser's native handling can't be postponed."", ""So it seems the only obvious option would be to detect when there are overlapping events, and try and do act delicately enough that things don't break."", 'Timo, any thoughts?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247287,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"This is problematic, since I couldn't properly and reliably replicate the bug since then, it only happens occasionally, I'm not sure if it's because of the speed or some other aspect. 
+
+But I did find that it happens not only with the Bold button - it happens either with ""just"" rapid text (no annotation) and with strikethrough and italics as well. I think it's probably safe to say that this isn't a specific annotation bug.
+
+Another small detail about that bug was that once it *does* happen, the rest of the editing is a mess -- that is, once it happens, even if I stop rapid typing, and then start editing normally, I still get random letters and gibberish added, and the 'delete' functionality goes wonky. To get rid of it I need to refresh the page and start over. 
+
+Also, This happened on my local wiki (using current VisualEditor master), installed on Ubuntu 13.04, and used through Firefox, and I just replicated it in MediaWiki.org",task_subcomment,"[""This is problematic, since I couldn't properly and reliably replicate the bug since then, it only happens occasionally, I'm not sure if it's because of the speed or some other aspect."", 'But I did find that it happens not only with the Bold button - it happens either with ""just"" rapid text (no annotation) and with strikethrough and italics as well.', ""I think it's probably safe to say that this isn't a specific annotation bug."", ""Another small detail about that bug was that once it *does* happen, the rest of the editing is a mess -- that is, once it happens, even if I stop rapid typing, and then start editing normally, I still get random letters and gibberish added, and the 'delete' functionality goes wonky."", 'To get rid of it I need to refresh the page and start over.', 'Also, This happened on my local wiki (using current VisualEditor master), installed on Ubuntu 13.04, and used through Firefox, and I just replicated it in MediaWiki.org']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247281,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"<>
+
+http://www.mediawiki.org/w/index.php?title=User:Chris857&oldid=770602
+http://en.wikipedia.org/wiki/File:Visual_Editor_-_subscript_and_superscript.PNG
+http://en.wikipedia.org/wiki/File:Wikitext_editor_-_subscript_and_superscript.PNG
+
+The user think this is related to the new super/sub script features.
+
+
+I don't think it has to do with them. Proof is, I can reproduce (on Mediawiki) the same bug without using them. You just need to add quickly casual sequences of words, as if you were vandalizing the page. In this diff http://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/SandboxVE&diff=prev&oldid=771184 I kept writing on the third line, it was VE which splitted what I wrote on more lines. I was also able to reproduce the difference among the content you ""write"" and the one which is saved. I can recall a vaguely similar behavior (not with casual letters though) when starting a list, but I can't say which bug that would be. I am also not sure whether this is a real bug or some counter-vandalism filter in action :)
+Thanks.",task_subcomment,"['<>\n\nURL\nURL\nURL\n\nThe user think this is related to the new super/sub script features.', ""I don't think it has to do with them."", 'Proof is, I can reproduce (on Mediawiki) the same bug without using them.', 'You just need to add quickly casual sequences of words, as if you were vandalizing the page.', 'In this diff URL I kept writing on the third line, it was VE which splitted what I wrote on more lines.', 'I was also able to reproduce the difference among the content you ""write"" and the one which is saved.', ""I can recall a vaguely similar behavior (not with casual letters though) when starting a list, but I can't say which bug that would be."", 'I am also not sure whether this is a real bug or some counter-vandalism filter in action :)\nThanks.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247274,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"Hi Moriel, David, can you please specify on which wiki this happens?
+I am not able to reproduce it on en.wp or it.wp, 
+but it does happen on mw.org - even if you do not use the Bold button or the new features, like another user suggested. 
+I'd say this bug probably needs to be renamed.",task_subcomment,"['Hi Moriel, David, can you please specify on which wiki this happens?', 'I am not able to reproduce it on en.wp or it.wp, \nbut it does happen on mw.org - even if you do not use the Bold button or the new features, like another user suggested.', ""I'd say this bug probably needs to be renamed.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247268,VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"I can reproduce this in Firefox but not in Chromium, on a slowish Ubuntu machine.",task_subcomment,"['I can reproduce this in Firefox but not in Chromium, on a slowish Ubuntu machine.']",['OBSERVED BUG BEHAVIOR']
+55071,about=null entries on 
     elements (because of dom-fragment reuse),"From WP:VE/F page (http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=567413854)
+
+------------------------------
+Following a report on frwiki, I tried a simple modification by changing a text into a wikilink. VE messed up the article by duplicating parts (not even complete parts), see [http://fr.wikipedia.org/w/index.php?title=Gen%C3%A8ve&diff=95604102&oldid=95601955 diff]. It seems to be reproducible on this article. --[[User:NicoV|NicoV]] ([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]]) 15:51, 6 August 2013 (UTC)
+------------------------------
+
+A cursory investigation back then revealed that this could be because of incorrect DOM fragment reuse for figures which all had about=null.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47326",task_description,"['about=null entries on 
     elements (because of dom-fragment reuse)\n\nFrom WP:VE/F page (URL\n\n------------------------------\nFollowing a report on frwiki, I tried a simple modification by changing a text into a wikilink.', 'VE messed up the article by duplicating parts (not even complete parts), see [URL diff].', 'It seems to be reproducible on this article.', '--[[User:NicoV|NicoV]] ([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]]) 15:51, 6 August 2013 (UTC)\n------------------------------\n\nA cursory investigation back then revealed that this could be because of incorrect DOM fragment reuse for figures which all had about=null.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+246783,about=null entries on 
     elements (because of dom-fragment reuse),I am marking this resolved. Haven't seen any reports about this in a while.,task_subcomment,"['I am marking this resolved.', ""Haven't seen any reports about this in a while.""]","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+246780,about=null entries on 
     elements (because of dom-fragment reuse),Is this still happening in production?,task_subcomment,['Is this still happening in production?'],['OBSERVED BUG BEHAVIOR']
+246778,about=null entries on 
     elements (because of dom-fragment reuse),https://gerrit.wikimedia.org/r/#/c/83216/ fixes the dsr inconsistency warnings  reported in this bug.,task_subcomment,['URL fixes the dsr inconsistency warnings  reported in this bug.'],['BUG REPRODUCTION']
+246775,about=null entries on 
     elements (because of dom-fragment reuse),"Sorry, I linked the wrong bug which is how you got the email ;-) .. fixing it.",task_subcomment,"['Sorry, I linked the wrong bug which is how you got the email ;-) .. fixing it.']",['ACTION ON ISSUE']
+246772,about=null entries on 
     elements (because of dom-fragment reuse),"You guys sure you wanted me on the CC for this bug?  I'm just making sure it wasn't another ""Dan"" :)",task_subcomment,"['You guys sure you wanted me on the CC for this bug?', 'I\'m just making sure it wasn\'t another ""Dan"" :)']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+246769,about=null entries on 
     elements (because of dom-fragment reuse),"Based on IRC discussions, we figured that there are different bugs that are interaction and producing the same end result -- duplication in some cases.  The Trieste bug could be a result of a bad parse of ''[[Foo|''bar'']]'' and interaction of the about=null issue.  Dalmine seems to be something else.",task_subcomment,"['Based on IRC discussions, we figured that there are different bugs that are interaction and producing the same end result -- duplication in some cases.', ""The Trieste bug could be a result of a bad parse of ''[[Foo|''bar'']]'' and interaction of the about=null issue."", 'Dalmine seems to be something else.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246765,about=null entries on 
     elements (because of dom-fragment reuse),"This patch addresses the about=""null"" issue.
+
+I am however not 100% sure that this is indeed the root cause for bug 53071. A
+scenario I can think of is this:
+
+1) getAboutSiblings returned sibling nodes without about attributes
+2) for some reason that is unclear to me those were *not* assigned
+   about=""null"" attributes in unpackDOMFragments on reuse
+3) the serializer faithfully serialized out the new content
+
+
+The diffs in
+https://it.wikipedia.org/w/index.php?title=Trieste&diff=prev&oldid=61046913
+would support this, as the entire image link is duplicated.
+
+The diff in https://it.wikipedia.org/w/index.php?title=Dalmine&oldid=61238456
+however looks like an incomplete image duplication. 
+
+There are several figure-related DSR errors when parsing that page of this pattern:
+
+WARNING: DSR inconsistency: cs/s mismatch for node: FIGURE s: 22704; cs: 22817
+WARNING: DSR inconsistency: cs/s mismatch for node: FIGURE s: 18478; cs: 18586
+
+Those warnings are still there when parsing the page with fragment reuse
+enabled, so this might be a different issue.",task_subcomment,"['This patch addresses the about=""null"" issue.', 'I am however not 100% sure that this is indeed the root cause for bug 53071.', 'A\nscenario I can think of is this:\n\n1) getAboutSiblings returned sibling nodes without about attributes\n2) for some reason that is unclear to me those were *not* assigned\n   about=""null"" attributes in unpackDOMFragments on reuse\n3) the serializer faithfully serialized out the new content\n\n\nThe diffs in\nURL\nwould support this, as the entire image link is duplicated.', 'The diff in URL\nhowever looks like an incomplete image duplication.', 'There are several figure-related DSR errors when parsing that page of this pattern:\n\nWARNING: DSR inconsistency: cs/s mismatch for node: FIGURE s: 22704; cs: 22817\nWARNING: DSR inconsistency: cs/s mismatch for node: FIGURE s: 18478; cs: 18586\n\nThose warnings are still there when parsing the page with fragment reuse\nenabled, so this might be a different issue.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+246761,about=null entries on 
     elements (because of dom-fragment reuse),"Change 82676 merged by jenkins-bot:
+Bug 53071: Handle about-less images better
+
+https://gerrit.wikimedia.org/r/82676",task_subcomment,['Change 82676 merged by jenkins-bot:\nBug 53071: Handle about-less images better\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+246757,about=null entries on 
     elements (because of dom-fragment reuse),"Change 82676 had a related patch set uploaded by GWicke:
+Bug 53071: Handle about-less images better
+
+https://gerrit.wikimedia.org/r/82676",task_subcomment,['Change 82676 had a related patch set uploaded by GWicke:\nBug 53071: Handle about-less images better\n\nGERRIT_URL'],['BUG REPRODUCTION']
+246750,about=null entries on 
     elements (because of dom-fragment reuse),"One more example:
+
+https://it.wikipedia.org/w/index.php?title=Dalmine&diff=61238476&oldid=61238456",task_subcomment,['One more example:\n\nURL'],['OBSERVED BUG BEHAVIOR']
+246741,about=null entries on 
     elements (because of dom-fragment reuse),"One more instance now reported on itwiki:
+
+1. Diff: https://it.wikipedia.org/w/index.php?title=Trieste&diff=prev&oldid=61046913 (see 2 images duplicated further down)
+
+2. Open https://it.wikipedia.org/w/index.php?title=Trieste&oldid=61038476&veaction=edit in Chrome and dump Parsoid HTML in the console ""copy(ve.init.mw.targets[0].originalHtml)"" You will see a lot of 
     tags with about=null",task_subcomment,"['One more instance now reported on itwiki:\n\n1.', 'Diff: URL (see 2 images duplicated further down)\n\n2.', 'Open URL in Chrome and dump Parsoid HTML in the console ""copy(ve.init.mw.targets[0].originalHtml)"" You will see a lot of 
     tags with about=null']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+55064,VisualEditor: IME input into an empty slug causes characters to overwrite one another,"Create an empty document by deleting everything. Enable Input method (e.g. Ibus Chinese Cantonese). Start typing, e.g. ""jung"" (select ""中"") then ""gwok"" (select ""國""). The second character will overwrite the first, leaving just ""國"" instead of ""中國"".
+
+Observed using chromium and firefox on Ubuntu. Happens with the following ibus input methods: Chinese cantonese, Chinese Pinyin, Korean, Malayalam swanalekha, Hindi inscript. Does not seem to happen with Kannada inscript.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: IME input into an empty slug causes characters to overwrite one another\n\nCreate an empty document by deleting everything.', 'Enable Input method (e.g.', 'Ibus Chinese Cantonese).', 'Start typing, e.g.', '""jung"" (select ""中"") then ""gwok"" (select ""國"").', 'The second character will overwrite the first, leaving just ""國"" instead of ""中國"".', 'Observed using chromium and firefox on Ubuntu.', 'Happens with the following ibus input methods: Chinese cantonese, Chinese Pinyin, Korean, Malayalam swanalekha, Hindi inscript.', 'Does not seem to happen with Kannada inscript.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246279,VisualEditor: IME input into an empty slug causes characters to overwrite one another,"
+
+*** This bug has been marked as a duplicate of bug 45240 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 45240 ***'],['ACTION ON ISSUE']
+55050,VisualEditor: Expose build number,"Quite often we get bug reports for issues that have been recently fixed but not deployed to the smaller wikis.
+
+It would be very useful if we had build numbers that we could access (e.g. ve.version) in the client so we could tell quickly how out of date the deployed code is before we waste time debugging an issue someone else has already fixed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Expose build number\n\nQuite often we get bug reports for issues that have been recently fixed but not deployed to the smaller wikis.', 'It would be very useful if we had build numbers that we could access (e.g.', 've.version) in the client so we could tell quickly how out of date the deployed code is before we waste time debugging an issue someone else has already fixed.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+569455,VisualEditor: Expose build number,FYI - This might be removed in {T119750},task_subcomment,['FYI - This might be removed in {T119750}'],['POTENTIAL NEW ISSUES AND REQUESTS']
+245454,VisualEditor: Expose build number,"Change 84334 merged by jenkins-bot:
+Hide version info if not available
+
+https://gerrit.wikimedia.org/r/84334",task_subcomment,['Change 84334 merged by jenkins-bot:\nHide version info if not available\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245447,VisualEditor: Expose build number,"Change 84334 had a related patch set uploaded by Esanders:
+Hide version info if not available
+
+https://gerrit.wikimedia.org/r/84334",task_subcomment,['Change 84334 had a related patch set uploaded by Esanders:\nHide version info if not available\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+245440,VisualEditor: Expose build number,"Yes, there's an issue with our deployment process which prevents it from working ATM. We're working on a fix.",task_subcomment,"[""Yes, there's an issue with our deployment process which prevents it from working ATM."", ""We're working on a fix.""]","['OBSERVED BUG BEHAVIOR', 'WORKAROUNDS']"
+245433,VisualEditor: Expose build number,"This isn't working.  When I click on ""Beta"" to see this, it says ""Version false"", with a link to https://en.wikipedia.org/w/false (from userspace) or https://en.wikipedia.org/wiki/false (from article space).",task_subcomment,"[""This isn't working."", 'When I click on ""Beta"" to see this, it says ""Version false"", with a link to URL (from userspace) or URL (from article space).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245427,VisualEditor: Expose build number,"Change 81877 merged by jenkins-bot:
+Expose version information in the client
+
+https://gerrit.wikimedia.org/r/81877",task_subcomment,['Change 81877 merged by jenkins-bot:\nExpose version information in the client\n\nGERRIT_URL'],['SOLUTION DISCUSSION']
+245419,VisualEditor: Expose build number,"Change 81877 had a related patch set uploaded by Esanders:
+Expose version information in the client
+
+https://gerrit.wikimedia.org/r/81877",task_subcomment,['Change 81877 had a related patch set uploaded by Esanders:\nExpose version information in the client\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+55045,VisualEditor: Line height on beta warning message is too narrow,"Line height example
+
+See screenshot for 1.25em vs 1.5em.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F11545}",task_description,"['VisualEditor: Line height on beta warning message is too narrow\n\nLine height example\n\nSee screenshot for 1.25em vs 1.5em.', '--------------------------\n**Version**: unspecified\n**Severity**: trivial\n\n**Attached**: {F11545}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+245137,VisualEditor: Line height on beta warning message is too narrow,"Change 79804 merged by jenkins-bot:
+Increase line height in beta warning
+
+https://gerrit.wikimedia.org/r/79804",task_subcomment,['Change 79804 merged by jenkins-bot:\nIncrease line height in beta warning\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245132,VisualEditor: Line height on beta warning message is too narrow,"Change 79804 had a related patch set uploaded by Esanders:
+Increase line height in beta warning
+
+https://gerrit.wikimedia.org/r/79804",task_subcomment,['Change 79804 had a related patch set uploaded by Esanders:\nIncrease line height in beta warning\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+55012,VisualEditor: Repeated insertion of multi-byte characters,"See the third example at https://www.mediawiki.org/w/index.php?title=User:Miya/VE4&oldid=762831.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor: Repeated insertion of multi-byte characters\n\nSee the third example at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+243323,VisualEditor: Repeated insertion of multi-byte characters,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",task_subcomment,"['Marking this as ""FIXED"" on the expectation that it\'s fixed - please re-open if you find that it is still occurring.']",['ACTION ON ISSUE']
+243319,VisualEditor: Repeated insertion of multi-byte characters,"There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:
+
+https://gerrit.wikimedia.org/r/#/c/82858/
+
+Please let us know whether it fixes the bug!",task_subcomment,"[""There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:\n\nURL\n\nPlease let us know whether it fixes the bug!""]",['BUG REPRODUCTION']
+243316,VisualEditor: Repeated insertion of multi-byte characters,"This might have been fixed with the changes in gerrit 79451 - David, does this fit the same pattern?",task_subcomment,"['This might have been fixed with the changes in gerrit 79451 - David, does this fit the same pattern?']",['OBSERVED BUG BEHAVIOR']
+54987,"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","I cannot take a screenshot ;)
+
+* Scroll over a the toolbar
+The button group outline, focused button box, and finger pointer flicker for a frame, then disappear.  Now the buttons to not go , and I have the arrow pointer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing\n\nI cannot take a screenshot ;)\n\n* Scroll over a the toolbar\nThe button group outline, focused button box, and finger pointer flicker for a frame, then disappear.', 'Now the buttons to not go , and I have the arrow pointer.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241653,"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","Still can't reproduce, unfortunately. :-(",task_subcomment,"[""Still can't reproduce, unfortunately."", ':-(']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+241648,"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","My VE just died with a slightly different behavior.  Now, the highlighting and outlining is drawn correctly, and persists, also the pointer is the index finger, indicating elements are click-enabled.  However, clicking Nothing Happens.
+
+FF 23.0.1",task_subcomment,"['My VE just died with a slightly different behavior.', 'Now, the highlighting and outlining is drawn correctly, and persists, also the pointer is the index finger, indicating elements are click-enabled.', 'However, clicking Nothing Happens.', 'FF 23.0.1']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+241644,"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","Created attachment 13119
+screenshot, I lied
+
+**Attached**: {F11406}",task_subcomment,"['Created attachment 13119\nscreenshot, I lied\n\n**Attached**: {F11406}']",['ATTACHMENT']
+54981,"VisualEditor: ""Some magic combination of arrow keys and actions involving the heading level toolbar"" scrambles document","screenshot
+
+I opened a wiki page, clicked ""Edit"", modified some stuff in the first paragraph involving links and a footnote reference.  Next, I demoted my outline from Page title to Heading, lowering all subheadings as well.  Said action was performed by triple-clicking each heading like, then mousing to the heading toolbar and clicking on the next level down.
+
+I believe I was on the last heading, when some magic combination of arrow keys and actions involving the heading level toolbar (I may have cursored down and hit  this time) caused a total HsiT scramble.  A sequence of characters of roughly equivalent length replaced the heading line I had been editing.
+
+The damage seems to have spread elsewhere in the document.  See attached screenshot.
+
+Separate but related bugs from the same editing session have been filed, jfyi to flesh out this story ;)
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F11397}",task_description,"['VisualEditor: ""Some magic combination of arrow keys and actions involving the heading level toolbar"" scrambles document\n\nscreenshot\n\nI opened a wiki page, clicked ""Edit"", modified some stuff in the first paragraph involving links and a footnote reference.', 'Next, I demoted my outline from Page title to Heading, lowering all subheadings as well.', 'Said action was performed by triple-clicking each heading like, then mousing to the heading toolbar and clicking on the next level down.', 'I believe I was on the last heading, when some magic combination of arrow keys and actions involving the heading level toolbar (I may have cursored down and hit  this time) caused a total HsiT scramble.', 'A sequence of characters of roughly equivalent length replaced the heading line I had been editing.', 'The damage seems to have spread elsewhere in the document.', 'See attached screenshot.', 'Separate but related bugs from the same editing session have been filed, jfyi to flesh out this story ;)\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical\n\n**Attached**: {F11397}']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+241332,"VisualEditor: ""Some magic combination of arrow keys and actions involving the heading level toolbar"" scrambles document","I *believe* that this may be related to bug 53360, which is now fixed, and so will mark as ""WORKSFORME"" (I can't make ""FIXED"" stand up given the lack of reproducible steps from these kinds of issues).
+
+Sorry for the disruption. :-(",task_subcomment,"['I *believe* that this may be related to bug 53360, which is now fixed, and so will mark as ""WORKSFORME"" (I can\'t make ""FIXED"" stand up given the lack of reproducible steps from these kinds of issues).', 'Sorry for the disruption.', ':-(']","['WORKAROUNDS', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+54913,Move info about template-affected attributes from meta tags into data-mw,"We currently use meta tags to mark up template-affected attributes:
+http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Templates_in_attributes
+
+This turned out to be problematic for several reasons:
+
+These meta tags can end up in foster-parentable positions for inputs like this:
+
+
    
+
+They can end up outside of an extension fragment, which makes it hard to reuse fragments. This currently blocks https://gerrit.wikimedia.org/r/#/c/65575/
+
+We have been discussing moving this information to data-mw ever since we added that as a public interface. Subbu has sketched a possible encoding in https://gist.github.com/subbuss/6092148/raw/e153a444b6e252d9eebd690e996e28cdbb859df7/gistfile1.txt
+
+We should work this out further in http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Templates_in_attributes
+and implement the resulting spec. 
+
+An issue to consider is the interaction between template content editing (http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Template_content) and templated attributes. For simple cases like echo '[[{{echo|foo}}]]' | node parse, we currently only add mw:ExpandedAttrs/Transclusion info. For echo '
    {{echo|
    }}' | node parse however we add both mw:Transclusion and mw:ExpandedAttrs/Transclusion. The templated attribute can already be edited as wikitext in the mw:Transclusion interface (data-mw.parts). We might want to omit the attribute interface here in favor of the general template-affected content interface.
+
+Fragment reuse is another issue to consider. We currently don't reuse attribute expansions. These are relatively rare and cheap, so this might be ok for now. We should however choose a representation that makes it easy to add caching for these later.
+
+Currently the VisualEditor completely ignores information about template-affected attributes, so no deployment coordination will be required as long as the mw:Transclusion interface does not change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Move info about template-affected attributes from meta tags into data-mw\n\nWe currently use meta tags to mark up template-affected attributes:\nURL\n\nThis turned out to be problematic for several reasons:\n\nThese meta tags can end up in foster-parentable positions for inputs like this:\n\n
    \n\nThey can end up outside of an extension fragment, which makes it hard to reuse fragments.', 'This currently blocks URL\n\nWe have been discussing moving this information to data-mw ever since we added that as a public interface.', 'Subbu has sketched a possible encoding in URL\n\nWe should work this out further in URL\nand implement the resulting spec.', 'An issue to consider is the interaction between template content editing (URL and templated attributes.', ""For simple cases like echo '[[{{echo|foo}}]]' | node parse, we currently only add mw:ExpandedAttrs/Transclusion info."", 'For echo \'
    {{echo|
    }}\' | node parse however we add both mw:Transclusion and mw:ExpandedAttrs/Transclusion.', 'The templated attribute can already be edited as wikitext in the mw:Transclusion interface (data-mw.parts).', 'We might want to omit the attribute interface here in favor of the general template-affected content interface.', 'Fragment reuse is another issue to consider.', ""We currently don't reuse attribute expansions."", 'These are relatively rare and cheap, so this might be ok for now.', 'We should however choose a representation that makes it easy to add caching for these later.', 'Currently the VisualEditor completely ignores information about template-affected attributes, so no deployment coordination will be required as long as the mw:Transclusion interface does not change.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237667,Move info about template-affected attributes from meta tags into data-mw,"This was fixed by 283bfd554bf1, so closing this bug. Please reopen if there is something we overlooked.",task_subcomment,"['This was fixed by 283bfd554bf1, so closing this bug.', 'Please reopen if there is something we overlooked.']","['SOLUTION USAGE', 'ACTION ON ISSUE']"
+237662,Move info about template-affected attributes from meta tags into data-mw,Meta tags in foster-parentable positions aren't really an issue anymore.,task_subcomment,"[""Meta tags in foster-parentable positions aren't really an issue anymore.""]",['OBSERVED BUG BEHAVIOR']
+54848,VisualEditor: FlaggedRevs inserts its tabs in the midst of the edit and edit source tabs,"Screenshot
+
+On wikis with FlaggedRevs, the interface historically displays buttons in the order [edit][pending changes]. This seems logical.
+
+Under the VE (screenshot attached) it goes [edit][pending changes][edit source]. This doesn't ;p. Restoring the previous setup (so that it would show as [edit][edit source][pending changes]) would be good.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11122}",task_description,"['VisualEditor: FlaggedRevs inserts its tabs in the midst of the edit and edit source tabs\n\nScreenshot\n\nOn wikis with FlaggedRevs, the interface historically displays buttons in the order [edit][pending changes].', 'This seems logical.', 'Under the VE (screenshot attached) it goes [edit][pending changes][edit source].', ""This doesn't ;p. Restoring the previous setup (so that it would show as [edit][edit source][pending changes]) would be good."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11122}']","['INVESTIGATION AND EXPLORATION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233854,VisualEditor: FlaggedRevs inserts its tabs in the midst of the edit and edit source tabs,"Change 110862 merged by Catrope:
+Don't try to insert the pending changes in the middle of VE's 'Edit' and 'Edit source'
+
+https://gerrit.wikimedia.org/r/110862",task_subcomment,"[""Change 110862 merged by Catrope:\nDon't try to insert the pending changes in the middle of VE's 'Edit' and 'Edit source'\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+233846,VisualEditor: FlaggedRevs inserts its tabs in the midst of the edit and edit source tabs,"Change 110862 had a related patch set uploaded by Alex Monk:
+Don't try to insert the pending changes in the middle of VE's 'Edit' and 'Edit source'
+
+https://gerrit.wikimedia.org/r/110862",task_subcomment,"[""Change 110862 had a related patch set uploaded by Alex Monk:\nDon't try to insert the pending changes in the middle of VE's 'Edit' and 'Edit source'\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+233839,VisualEditor: FlaggedRevs inserts its tabs in the midst of the edit and edit source tabs,"For me it shows [pending changes][edit] without VE (and the comments indicate this is the intended behaviur), so I think with VE should be [pending changes][edit][edit source].",task_subcomment,"['For me it shows [pending changes][edit] without VE (and the comments indicate this is the intended behaviur), so I think with VE should be [pending changes][edit][edit source].']",['INVESTIGATION AND EXPLORATION']
+54845,VisualEditor: Inspector fails to render correctly for embedded buttons,"Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Inspector fails to render correctly for embedded buttons\n\nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g."", 'Math) we need it to work in block mode as well.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233583,VisualEditor: Inspector fails to render correctly for embedded buttons,"Change 79055 merged by jenkins-bot:
+Fix rendering of inspector for embedded buttons
+
+https://gerrit.wikimedia.org/r/79055",task_subcomment,['Change 79055 merged by jenkins-bot:\nFix rendering of inspector for embedded buttons\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233581,VisualEditor: Inspector fails to render correctly for embedded buttons,"Change 79055 had a related patch set uploaded by Esanders:
+Fix rendering of inspector for embedded buttons
+
+https://gerrit.wikimedia.org/r/79055",task_subcomment,['Change 79055 had a related patch set uploaded by Esanders:\nFix rendering of inspector for embedded buttons\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+54771,VisualEditor: Pasting block level elements can lose annotations,"If you copy a block level element and try to paste it all the annotations (links, bold, italic etc.) are removed and it is just pasted as plain text. You need to select the whole line with the selection region going all the way to the right of the screen. 
+
+For example in 
+http://en.wikipedia.org/wiki/User:Salix_alba/VE_test 
+selecting the whole of the final paragraph and coping and pasting loses anotation.
+
+Examining the clipboard in this case its something like
+

    
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52770",task_description,"['VisualEditor: Pasting block level elements can lose annotations\n\nIf you copy a block level element and try to paste it all the annotations (links, bold, italic etc.)', 'are removed and it is just pasted as plain text.', 'You need to select the whole line with the selection region going all the way to the right of the screen.', 'For example in \nURL \nselecting the whole of the final paragraph and coping and pasting loses anotation.', 'Examining the clipboard in this case its something like\n

    \n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254115,VisualEditor: Pasting block level elements can lose annotations,Can confirm that this has been incidentally fixed as part of Ed's work on copy-and-paste - tested in Chrome/Firefox/Safari/Opera. (Yay.),task_subcomment,"[""Can confirm that this has been incidentally fixed as part of Ed's work on copy-and-paste - tested in Chrome/Firefox/Safari/Opera."", '(Yay.)']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+254110,VisualEditor: Pasting block level elements can lose annotations,Can't reproduce.,task_subcomment,"[""Can't reproduce.""]",['OBSERVED BUG BEHAVIOR']
+54752,VisualEditor: Edit to a template somehow removing equals signs in markup?,"See https://ja.wikipedia.org/w/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Frozen-mikan/sandbox&diff=48779068&oldid=48778951 which used https://ja.wikipedia.org/wiki/Template:%E3%83%AA%E3%83%B3%E3%82%AF%E4%BF%AE%E6%AD%A3%E4%BE%9D%E9%A0%BC/%E6%94%B9%E5%90%8D
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Edit to a template somehow removing equals signs in markup?', 'See URL which used URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+399856,VisualEditor: Edit to a template somehow removing equals signs in markup?,AFAICT this is fixed; no recurrences in months have been reported.,task_subcomment,['AFAICT this is fixed; no recurrences in months have been reported.'],['BUG REPRODUCTION']
+253210,VisualEditor: Edit to a template somehow removing equals signs in markup?,Aha; sorry :).,task_subcomment,['Aha; sorry :).'],['SOLUTION DISCUSSION']
+253205,VisualEditor: Edit to a template somehow removing equals signs in markup?,"Thank you.
+
+(In reply to comment #0)
+> which used
+> https://ja.wikipedia.org/wiki/Template:
+> %E3%83%AA%E3%83%B3%E3%82%AF%E4%BF%AE%E6%AD%A3%E4%BE%9D%E9%A0%BC/
+> %E6%94%B9%E5%90%8D
+
+I do not use this template. I used a dummy template. This is not created.
+https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Frozen-mikan/Template:%E7%A9%BA%E3%81%AE%E5%BC%95%E6%95%B0",task_subcomment,"['Thank you.', '(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI do not use this template.', 'I used a dummy template.', 'This is not created.', 'URL']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+54751,Regression: Wikitext for new lists has unnecessary newlines after bullets,"Output after saving
+
+My setup:
+
+MediaWiki:
+1.22alpha (ffa9b0a) 19:02, 11. Aug. 2013
+
+VisualEditor (Version 0.1.0)(0e76b1b)20:01, 11. Aug. 2013
+
+ParsoidServer:
+commit a4fec47e5201c329925967376f4106abd11178e3
+Merge: fdb6e06 30315ed Author: jenkins-bot 
+Date:   Fri Aug 9 02:43:12 2013 +0000
+
+
+When I put in a simple Unsorted list the Parsoid Server throws an error message:
+Incompatible constraints 1: LI P {a:{min: 0, max: 0}, b:{min: 1, max: 2}, min:0, max 0}
+
+
+Attached you find the resulting output after I saved the page. Notice the extra Line that got added by Parsoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11826}",task_description,"['Regression: Wikitext for new lists has unnecessary newlines after bullets\n\nOutput after saving\n\nMy setup:\n\nMediaWiki:\n1.22alpha (ffa9b0a) 19:02, 11.', 'Aug. 2013\n\nVisualEditor (Version 0.1.0)(0e76b1b)20:01, 11.', 'Aug. 2013\n\nParsoidServer:\ncommit a4fec47e5201c329925967376f4106abd11178e3\nMerge: fdb6e06 30315ed Author: jenkins-bot \nDate:   Fri Aug 9 02:43:12 2013 +0000\n\n\nWhen I put in a simple Unsorted list the Parsoid Server throws an error message:\nIncompatible constraints 1: LI P {a:{min: 0, max: 0}, b:{min: 1, max: 2}, min:0, max 0}\n\n\nAttached you find the resulting output after I saved the page.', 'Notice the extra Line that got added by Parsoid.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11826}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253169,Regression: Wikitext for new lists has unnecessary newlines after bullets,"Change 78913 merged by jenkins-bot:
+(Bug 52751): Serialize p-wrapped list items correctly
+
+https://gerrit.wikimedia.org/r/78913",task_subcomment,['Change 78913 merged by jenkins-bot:\n(Bug 52751): Serialize p-wrapped list items correctly\n\nGERRIT_URL'],['BUG REPRODUCTION']
+253165,Regression: Wikitext for new lists has unnecessary newlines after bullets,"Change 78913 had a related patch set uploaded by Subramanya Sastry:
+(Bug 52751): Serialize p-wrapped list items correctly
+
+https://gerrit.wikimedia.org/r/78913",task_subcomment,['Change 78913 had a related patch set uploaded by Subramanya Sastry:\n(Bug 52751): Serialize p-wrapped list items correctly\n\nGERRIT_URL'],['BUG REPRODUCTION']
+253161,Regression: Wikitext for new lists has unnecessary newlines after bullets,git bisect shows that c0de1d5839430e9fde79ff4195caf6841baab0d3 is the culprit.  Will investigate and fix.,task_subcomment,"['git bisect shows that c0de1d5839430e9fde79ff4195caf6841baab0d3 is the culprit.', 'Will investigate and fix.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+253155,Regression: Wikitext for new lists has unnecessary newlines after bullets,"I suspect this is a regression of some sort.  Can be duplicated with this HTML below (VE wraps li-content in p-tags).
+
+[subbu@earth tests] echo ""
    • a
    "" | node parse --html2wt
+Incompatible constraints 1: LI P { a: { min: 0, max: 0 }, b: { min: 1, max: 2 }, min: 0, max: 0 }
+* 
+a",task_subcomment,"['I suspect this is a regression of some sort.', 'Can be duplicated with this HTML below (VE wraps li-content in p-tags).', '[subbu@earth tests] echo ""
    • a
    "" | node parse --html2wt\nIncompatible constraints 1: LI P { a: { min: 0, max: 0 }, b: { min: 1, max: 2 }, min: 0, max: 0 }\n* \na']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+54745,VisualEditor: Add a keyboard shortcut to trigger Save dialog,"It is requested to implement a keyboard shortcut for Save the edits. Ctrl+Shift+S combination will be the most suitable for this, as it is being used by the conventional editor right now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Add a keyboard shortcut to trigger Save dialog\n\nIt is requested to implement a keyboard shortcut for Save the edits.', 'Ctrl+Shift+S combination will be the most suitable for this, as it is being used by the conventional editor right now.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+252803,VisualEditor: Add a keyboard shortcut to trigger Save dialog,"Merging with another suggestion for the same.
+
+*** This bug has been marked as a duplicate of bug 50897 ***",task_subcomment,"['Merging with another suggestion for the same.', '*** This bug has been marked as a duplicate of bug 50897 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252797,VisualEditor: Add a keyboard shortcut to trigger Save dialog,"> Ctrl+Shift+S
+
+Sorry, I meant Alt+Shift+S",task_subcomment,"['QUOTE\n\nSorry, I meant Alt+Shift+S']",['ACTION ON ISSUE']
+54716,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"When you edit captions and input Japanese text with Japanese input method (of ことえり, the default Japanese method of Mac OS X), for example 生醤油 (kijouyu), the cursor will place itself after the first character, but it should place itself after the last (3rd) character. Tested on Firefox and OSX, but may happen in other browsers and operating systems. Thanks to Takashi Ota and Josh Lim for testing and reporting.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters\n\nWhen you edit captions and input Japanese text with Japanese input method (of ことえり, the default Japanese method of Mac OS X), for example 生醤油 (kijouyu), the cursor will place itself after the first character, but it should place itself after the last (3rd) character.', 'Tested on Firefox and OSX, but may happen in other browsers and operating systems.', 'Thanks to Takashi Ota and Josh Lim for testing and reporting.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+250463,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"Given that this is now merged, I'm going to mark this as fixed. However, this is provisional - please re-open if you think that this has not worked!",task_subcomment,"[""Given that this is now merged, I'm going to mark this as fixed."", 'However, this is provisional - please re-open if you think that this has not worked!']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+250461,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"Change 80080 merged by jenkins-bot:
+Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",task_subcomment,"[""Change 80080 merged by jenkins-bot:\nDon't emit Surface changes back to the Surface\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+250459,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"Change 80080 had a related patch set uploaded by Jforrester:
+WIP:Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",task_subcomment,"[""Change 80080 had a related patch set uploaded by Jforrester:\nWIP:Don't emit Surface changes back to the Surface\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+250457,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"Patch has been reverted due to other issues, sadly.",task_subcomment,"['Patch has been reverted due to other issues, sadly.']",['ACTION ON ISSUE']
+250455,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,Doesn't seem to be happening any more.,task_subcomment,"[""Doesn't seem to be happening any more.""]",['OBSERVED BUG BEHAVIOR']
+250454,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"This seems to be caused by a call to surfaceObserver.stop() in Surface's onDocumentKeyDown method, which is wrongly asynchronous. The same problem was affecting Malayalam and probably other scripts/IMEs too.
+
+I *think* it should be fixed by https://gerrit.wikimedia.org/r/#/c/79451 (just merged).",task_subcomment,"[""This seems to be caused by a call to surfaceObserver.stop() in Surface's onDocumentKeyDown method, which is wrongly asynchronous."", 'The same problem was affecting Malayalam and probably other scripts/IMEs too.', 'I *think* it should be fixed by URL (just merged).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250450,VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"Now I tested it myself on Fedora 18 with Firefox. It happens there too. To reproduce:
+
+1. Enabled the ""Japanese (Anthy)"" keyboard in GNOME input sources.
+2. In a VisualEditor window type ""mitsubishi"". It appears as four Kana characters: ""みつびし"".
+3. Press the space bar. The four characters change to two Kanji characters: ""三菱"".
+4. Press Enter. This accepts the Kanji representation.
+
+Observed: The cursor is placed between 三 and 菱.
+Expected: The cursor should be placed after 三菱. That is what happens in other text editors on my system.",task_subcomment,"['Now I tested it myself on Fedora 18 with Firefox.', 'It happens there too.', 'To reproduce:\n\n1.', 'Enabled the ""Japanese (Anthy)"" keyboard in GNOME input sources.', '2.', 'In a VisualEditor window type ""mitsubishi"".', 'It appears as four Kana characters: ""みつびし"".', '3.', 'Press the space bar.', 'The four characters change to two Kanji characters: ""三菱"".', '4.', 'Press Enter.', 'This accepts the Kanji representation.', 'Observed: The cursor is placed between 三 and 菱.', 'Expected: The cursor should be placed after 三菱.', 'That is what happens in other text editors on my system.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54714,Enable Echo / Notifications on se.wikimedia.org,"The Swedish chapter would like to get Notifications enabled on their wiki at se.wikimedia.org. Please use the default settings.
+
+Poll here: http://se.wikimedia.org/wiki/Tråd:Wikimedia:Bybrunnen/VisualEditor_och_Notifications
+
+/Jan
+CEO
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",task_description,"['Enable Echo / Notifications on se.wikimedia.org\n\nThe Swedish chapter would like to get Notifications enabled on their wiki at se.wikimedia.org.', 'Please use the default settings.', 'Poll here: URL\n\n/Jan\nCEO\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+250378,Enable Echo / Notifications on se.wikimedia.org,Seems like this wiki was included in the last roll-out.,task_subcomment,['Seems like this wiki was included in the last roll-out.'],['OBSERVED BUG BEHAVIOR']
+250373,Enable Echo / Notifications on se.wikimedia.org,"Thank you, it was my pleasure! Bear in mind that this is an additional request to enable it on the chapter wiki, and we do not need to wait for a specific date there, just turn it on at your will.",task_subcomment,"['Thank you, it was my pleasure!', 'Bear in mind that this is an additional request to enable it on the chapter wiki, and we do not need to wait for a specific date there, just turn it on at your will.']","['SOLUTION DISCUSSION', 'FUTURE PLAN']"
+250368,Enable Echo / Notifications on se.wikimedia.org,"Thanks, Jan!
+
+It was a pleasure to meet you at Wikimania last week.
+
+I am so glad that the Swedish Wikipedia will be one of the first non-English Wikipedia to deploy Echo next week, as outlined in this release plan:
+
+http://www.mediawiki.org/wiki/Echo/Release_Plan_2013
+
+We're now scheduled to deploy on Tuesday August 20 at 12pm PT - on the French, Polish, Portuguese and Swedish Wikipedias, if all goes well. 
+
+Please let us know if you have any final questions.
+
+Cheers ...",task_subcomment,"['Thanks, Jan!', 'It was a pleasure to meet you at Wikimania last week.', ""I am so glad that the Swedish Wikipedia will be one of the first non-English Wikipedia to deploy Echo next week, as outlined in this release plan:\n\nURL\n\nWe're now scheduled to deploy on Tuesday August 20 at 12pm PT - on the French, Polish, Portuguese and Swedish Wikipedias, if all goes well."", 'Please let us know if you have any final questions.', 'Cheers ...']","['ACTION ON ISSUE', 'SOCIAL CONVERSATION', 'FUTURE PLAN', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+250364,Enable Echo / Notifications on se.wikimedia.org,"I don't think Echo is under general deployment yet.
+
+CC'ing Fabrice",task_subcomment,"[""I don't think Echo is under general deployment yet."", ""CC'ing Fabrice""]","['INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE']"
+54686,VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension,"Because we love Mark:
+
+http://m.mediawiki.org/wiki/Extension:BetaFeatures
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,['VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension\n\nBecause we love Mark:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'],['INVESTIGATION AND EXPLORATION']
+248561,VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension,Done in gerrit 91108.,task_subcomment,['Done in gerrit 91108.'],['SOLUTION DISCUSSION']
+248554,VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension,"Change 78795 merged by jenkins-bot:
+Integrate with BetaPreferences
+
+https://gerrit.wikimedia.org/r/78795",task_subcomment,['Change 78795 merged by jenkins-bot:\nIntegrate with BetaPreferences\n\nGERRIT_URL'],['ACTION ON ISSUE']
+248548,VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension,"Change 78795 had a related patch set uploaded by Esanders:
+[WIP] Integrate with BetaPreferences
+
+https://gerrit.wikimedia.org/r/78795",task_subcomment,['Change 78795 had a related patch set uploaded by Esanders:\n[WIP] Integrate with BetaPreferences\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+54670,VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen,"When the list of potential articles is longer than the displayed list there is no way to see other articles without continuing to type part of the name. In some cases this isn't going to be much of a problem, but when there are lots of items that could have the same title (e.g. [[Nexus]]) it essentially requires you to know which disambiguator is used, defeating the point of the suggestions list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen\n\nWhen the list of potential articles is longer than the displayed list there is no way to see other articles without continuing to type part of the name."", ""In some cases this isn't going to be much of a problem, but when there are lots of items that could have the same title (e.g."", '[[Nexus]]) it essentially requires you to know which disambiguator is used, defeating the point of the suggestions list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+247683,VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen,"No, it was in error. Sorry!",task_subcomment,"['No, it was in error.', 'Sorry!']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247681,VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen,"James, did you mean to reopen this four seconds after closing it?",task_subcomment,"['James, did you mean to reopen this four seconds after closing it?']",['ACTION ON ISSUE']
+247679,VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen,I believe that this was fixed in the scrollable-update in October. Sorry for the slow triage.,task_subcomment,"['I believe that this was fixed in the scrollable-update in October.', 'Sorry for the slow triage.']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+54659,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Screenshot FF, vector skin, mediawiki,ca-action
+
+[Regression]: mw-notification-area makes vector-hover-dropdown closing
+----
+How to reproduce:
+* Be an admin at Commons or have otherwise at least 3 entries in your ca-action dropdown.
+* Fire mw.notify('foo') in your js-console
+* Scroll to top
+* Click the message ('foo') to ""hide"" it
+* Hover the ca-action arrow.
+* Try to click ""protect"" (see screenshot)
+
+As soon as your cursor is over the mw-notification-area (made visible in other screenshot), the dropdown closes.
+
+----
+Expected behaviour: Can move/protect page. Dropdown does not close out of the blue.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal
+
+**Attached**: {F11622}",task_description,"['[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events\n\nScreenshot FF, vector skin, mediawiki,ca-action\n\n[Regression]: mw-notification-area makes vector-hover-dropdown closing\n----\nHow to reproduce:\n* Be an admin at Commons or have otherwise at least 3 entries in your ca-action dropdown.', '* Fire mw.notify(\'foo\') in your js-console\n* Scroll to top\n* Click the message (\'foo\') to ""hide"" it\n* Hover the ca-action arrow.', '* Try to click ""protect"" (see screenshot)\n\nAs soon as your cursor is over the mw-notification-area (made visible in other screenshot), the dropdown closes.', '----\nExpected behaviour: Can move/protect page.', 'Dropdown does not close out of the blue.', '--------------------------\n**Version**: 1.22.0\n**Severity**: normal\n\n**Attached**: {F11622}']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+247166,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Change 158659 merged by jenkins-bot:
+mediawiki.notification: Also hide #mw-notification-area upon creation
+
+https://gerrit.wikimedia.org/r/158659",task_subcomment,['Change 158659 merged by jenkins-bot:\nmediawiki.notification: Also hide #mw-notification-area upon creation\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247161,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,*** Bug 55457 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 55457 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247156,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Change 158659 had a related patch set uploaded by Catrope:
+Followup 6c5b246: also hide #mw-notification-area upon creation
+
+https://gerrit.wikimedia.org/r/158659",task_subcomment,['Change 158659 had a related patch set uploaded by Catrope:\nFollowup 6c5b246: also hide #mw-notification-area upon creation\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247150,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Change 109124 merged by jenkins-bot:
+mediawiki.notification: Hide #mw-notification-area when it's empty
+
+https://gerrit.wikimedia.org/r/109124",task_subcomment,"[""Change 109124 merged by jenkins-bot:\nmediawiki.notification: Hide #mw-notification-area when it's empty\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+247142,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,Rephrasing bug title as it was cut-off.,task_subcomment,['Rephrasing bug title as it was cut-off.'],['OBSERVED BUG BEHAVIOR']
+247133,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Thanks, Bartosz.",task_subcomment,"['Thanks, Bartosz.']",['SOLUTION DISCUSSION']
+247127,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Change 109124 had a related patch set uploaded by Bartosz Dziewoński:
+mediawiki.notification: Hide #mw-notification-area when it's empty
+
+https://gerrit.wikimedia.org/r/109124",task_subcomment,"[""Change 109124 had a related patch set uploaded by Bartosz Dziewoński:\nmediawiki.notification: Hide #mw-notification-area when it's empty\n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+247118,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Ugh, I guess no one will do this if I don't.",task_subcomment,"[""Ugh, I guess no one will do this if I don't.""]",['SOLUTION DISCUSSION']
+247113,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,I am resetting this to high priority only as per the maintainer judgement in comment 4.,task_subcomment,['I am resetting this to high priority only as per the maintainer judgement in comment 4.'],['ACTION ON ISSUE']
+247107,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"jforrester: Should this really be highest priority (set in comment 7), or be
+kept as high (as you did in comment 4)?",task_subcomment,"['jforrester: Should this really be highest priority (set in comment 7), or be\nkept as high (as you did in comment 4)?']",['SOLUTION DISCUSSION']
+247101,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"jforrester: Should this really be highest priority (set in comment 7), or be kept as high (as you did in comment 4)?",task_subcomment,"['jforrester: Should this really be highest priority (set in comment 7), or be kept as high (as you did in comment 4)?']",['ACTION ON ISSUE']
+247094,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"(In reply to comment #2)
+> Unless somebody has a better idea, we should probably implement toggling
+> 'display' in JavaScript.
+
+If the ca-action dropdown is the only exposed UI problem, perhaps the ca-action dropdown buttons could have a higher z-index, as a temporary fix at least?
+
+(In reply to comment #5)
+> So I was right that VE is *pushed* by the Wikimedia Foundation:
+> https://bugzilla.wikimedia.org/show_activity.cgi?id=52659
+
+It certainly is. While this regression outside of VisualEditor codebase is regrettable, and hopefully will be fixed soon, the VE team have pushed lots of great JS into core, and fixed bugs like bug 38081 which will benefit Wikimedia Commons.
+
+I have bumped the importance up (but not wedded to it) as it is a regression caused by VE and affecting non-VE environments, and was reported two months ago, and the code change causing it was deployed in July.
+
+In addition to impacting sysops with three ca-actions, it also affects non-sysops on every wiki, although not as pronounced.  Non sysops only have the the 'Move' button in the ca-action dropdown of Vector, and it is partially inaccessible.  If the user slowly moves their mouse cursor down into the dropdown, they can click the move icon if the click on the first few pixels above the word 'Move' - if they continue going down so that their mouse cursor hovers over the word 'Move', the drop down disappears.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\n\nIf the ca-action dropdown is the only exposed UI problem, perhaps the ca-action dropdown buttons could have a higher z-index, as a temporary fix at least?', '(In reply to comment #5)\nQUOTE\nQUOTE\n\nIt certainly is.', 'While this regression outside of VisualEditor codebase is regrettable, and hopefully will be fixed soon, the VE team have pushed lots of great JS into core, and fixed bugs like bug 38081 which will benefit Wikimedia Commons.', 'I have bumped the importance up (but not wedded to it) as it is a regression caused by VE and affecting non-VE environments, and was reported two months ago, and the code change causing it was deployed in July.', 'In addition to impacting sysops with three ca-actions, it also affects non-sysops on every wiki, although not as pronounced.', ""Non sysops only have the the 'Move' button in the ca-action dropdown of Vector, and it is partially inaccessible."", ""If the user slowly moves their mouse cursor down into the dropdown, they can click the move icon if the click on the first few pixels above the word 'Move' - if they continue going down so that their mouse cursor hovers over the word 'Move', the drop down disappears.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247087,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"(In reply to comment #5)
+> So I was right that VE is *pushed* by the Wikimedia Foundation:
+> https://bugzilla.wikimedia.org/show_activity.cgi?id=52659
+
+I'm confused. What are you saying?",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\n\nI'm confused."", 'What are you saying?']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+247081,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,So I was right that VE is *pushed* by the Wikimedia Foundation: https://bugzilla.wikimedia.org/show_activity.cgi?id=52659,task_subcomment,['So I was right that VE is *pushed* by the Wikimedia Foundation: URL'],['OBSERVED BUG BEHAVIOR']
+247076,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"From bug 55457 comment 0:
+
+| 1. Trigger a notification
+| 2. Click on the notification to dismiss it
+| 3. The notification area (
    ) is now empty, but
+| still obscures a narrow strip in the top right corner:
+| 
+| > $('#mw-notification-area').outerHeight()
+| 12
+| > $('#mw-notification-area').outerWidth()
+| 269
+| > $('#mw-notification-area').position()
+| Object {top: 89.59375, left: 1251.203125}
+| > $('#mw-notification-area').css('z-index')
+| ""10000""
+| 
+| This is a problem because the div steals events and mouse interaction from the
+| UI elements below it. For instance, in VisualEditor:
+| 1. Open a page in VE
+| 2. Type '[['. The wikitext warning appears
+| 3. Click the warning to dismiss it
+| 4. Reveal #mw-notification-area in the inspector and observe how it's on top
+|    of part of the save button
+| 5. Very carefully move the mouse over the save button, and you'll notice a
+|    small (12px tall) area where mouse pointer is a normal pointer instead of a
+|    hand. Clicking in this area does not press the save button.",task_subcomment,"['From bug 55457 comment 0:\n\n| 1.', 'Trigger a notification\n| 2.', 'Click on the notification to dismiss it\n| 3.', 'The notification area (
    ) is now empty, but\n| still obscures a narrow strip in the top right corner:\n| \n| > $(\'#mw-notification-area\').outerHeight()\n| 12\n| > $(\'#mw-notification-area\').outerWidth()\n| 269\n| > $(\'#mw-notification-area\').position()\n| Object {top: 89.59375, left: 1251.203125}\n| > $(\'#mw-notification-area\').css(\'z-index\')\n| ""10000""\n| \n| This is a problem because the div steals events and mouse interaction from the\n| UI elements below it.', 'For instance, in VisualEditor:\n| 1.', 'Open a page in VE\n| 2.', ""Type '[['."", 'The wikitext warning appears\n| 3.', 'Click the warning to dismiss it\n| 4.', ""Reveal #mw-notification-area in the inspector and observe how it's on top\n|    of part of the save button\n| 5."", ""Very carefully move the mouse over the save button, and you'll notice a\n|    small (12px tall) area where mouse pointer is a normal pointer instead of a\n|    hand."", 'Clicking in this area does not press the save button.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+247068,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,*** Bug 55457 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 55457 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247060,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"The culprit is this line:
+	padding: 1em 1em 0 0;
+in mediawiki.notification.css. It causes .mw-notification-area to have a non-zero height and thus cover other elements, like the dropdown.
+
+There are two obvious ways to fix it which don't work:
+
+* Change the padding to margin. This causes the notifications to ""jump"" slightly when scrolling, as detailed in commit message of https://gerrit.wikimedia.org/r/#/c/75614/
+
+* Add .mw-notification-area:empty { display: none; }. This doesn't work on IE<9 and other old browsers. [http://caniuse.com/#feat=css-sel3]
+
+Unless somebody has a better idea, we should probably implement toggling 'display' in JavaScript.",task_subcomment,"['The culprit is this line:\n\tpadding: 1em 1em 0 0;\nin mediawiki.notification.css.', 'It causes .mw-notification-area to have a non-zero height and thus cover other elements, like the dropdown.', ""There are two obvious ways to fix it which don't work:\n\n* Change the padding to margin."", 'This causes the notifications to ""jump"" slightly when scrolling, as detailed in commit message of URL\n\n* Add .mw-notification-area:empty { display: none; }.', ""This doesn't work on IE<9 and other old browsers."", ""[URL\n\nUnless somebody has a better idea, we should probably implement toggling 'display' in JavaScript.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247052,[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Created attachment 13078
+Screenshot FF, vector skin, mediawiki, mw-notify
+
+I suppose this regression was introduced by fixing https://bugzilla.wikimedia.org/show_bug.cgi?id=50870
+- When I test locally (codebase about 4 weeks old), the menu/dropdown does not close unexpectedly.
+
+**Attached**: {F11623}",task_subcomment,"['Created attachment 13078\nScreenshot FF, vector skin, mediawiki, mw-notify\n\nI suppose this regression was introduced by fixing URL\n- When I test locally (codebase about 4 weeks old), the menu/dropdown does not close unexpectedly.', '**Attached**: {F11623}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54638,Selser regression: pages with templates that generate tables and foster content out of the table are broken,"At http://en.wikipedia.org/wiki/Raven-Symon%C3%A9?oldid=566906720 , if you edit anything in the document, the infobox is deleted, but if you make a null edit, the infobox is retained.
+
+This appears to be a bug in selser: if the HTML doesn't change, the wikitext doesn't change, but any small change in the HTML results in the infobox being deleted. I verified that VisualEditor isn't dirtying anything, but just to be sure I also reproduced this on the command line by just making a 1-character change to the HTML as shown below.
+
+I think this may have something to do with the double }} closing in the infobox.
+
+$ mkdir tmp
+$ cd tmp
+$ wget 'http://parsoid.wmflabs.org/en/Raven-Symon%C3%A9?oldid=566906720' -O originalHTML
+$ wget 'http://en.wikipedia.org/wiki/Raven-Symon%C3%A9?oldid=566906720&action=raw' -O originalWikitext
+$ cp originalHTML editedHTML
+$ vi editedHTML   # Change '
    Life and career
    ' to '
    Life and careeer
    '
+$ node parse.js --html2wt --selser --oldtextfile originalWikitext --oldhtmlfile originalHTML --inputfile editedHTML > newWikitext
+$ diff -u originalWikitext newWikitext
+
+--- /home/catrope/tmp/originalWikitext	2013-08-08 14:34:46.463998552 +0800
++++ /home/catrope/tmp/newWikitext	2013-08-08 17:04:41.596239434 +0800
+@@ -1,29 +1,7 @@
+ {{Use mdy dates|date=June 2013}}
+ {{pp-move-indef}}
+-{{Infobox person
+-| image           = Raven-Symoné 2011.jpg
+-| caption         = Raven-Symoné in 2011 
+-| birth_name      = Raven-Symoné Christina Pearman 
+-| alias           = Raven
    Raven-Symone
+-| background      = solo_singer
+-| instrument      = [[Singing|Vocals]], [[piano]]
+-| birth_date      = {{birth date and age|mf=yes|1985|12|10}}
+-| birth_place     = [[Atlanta]], [[Georgia (U.S. state)|Georgia]], U.S.{{cite web |url=http://movies.msn.com/celebrities/celebrity-biography/raven-symone/|title=Raven Symone:Biography on MSN |accessdate=2008-07-15 |year=2008 |publisher=[[MSN]]}} 
+-| genre           = 
+-| occupation      = Actress, singer, [[comedienne]], dancer, television producer, [[fashion model]]
+-| years_active    = 1989–present
+-| label           = [[MCA Records|MCA]], Crash, RayBlaze, [[Hollywood Records|Hollywood]]
+-| associated_acts = [[The Cheetah Girls (band)|The Cheetah Girls]]
+-| website         = [http://www.myspace.com/ravensymone Raven-Symoné Myspace page]
+-| module         = {{Infobox musical artist|embed=yes
+-| background          = solo_singer
+-| genre               = [[Contemporary R&B|R&B]], [[pop music|pop]], [[Hip hop music|hip hop]], [[Soul music|soul]], [[dance music|dance]]
+-| instrument          = Vocals, [[piano]]
+-| years_active        = 1993–present
+-}}
+ 
+-}}
+ '''Raven-Symoné Christina Pearman'''[http://www.mlive.com/entertainment/saginaw/index.ssf/2008/08/ravensymone_steps_out_of_chara.html], (born December 10, 1985), known professionally as '''Raven-Symoné''' (pronounced {{IPA|/ˈreɪ.vən sɪˈmoʊn/}}, as though unaccented), or simply '''Raven''', is an American actress and singer. Raven-Symoné launched her career in 1989 after appearing in ''[[The Cosby Show]]'' as Olivia. She released her debut album, ''[[Here's to New Dreams]]'' in 1993; the single, ""[[That's What Little Girls Are Made Of]]"" charted number 68 on the US ''Billboard'' [[Hot 100]].[http://www.billboard.com/song/raven-symone/that-s-what-little-girls-are-made-of/450772#/song/raven-symone/that-s-what-little-girls-are-made-of/450772 That's What Little Girls Are Made Of – Raven-Symoné]. Billboard.com. Retrieved 2012-05-19. The next album, ''[[Undeniable (Raven-Symoné album)|Undeniable]]'', was released on May 4, 1999.
+ 
+ Raven-Symoné appeared in several successful television series, such as ''[[The Cosby Show]]'' and ''[[Hangin' with Mr. Cooper]]'', in the late 1980s and early 1990s. From 2003 to 2007, she starred in the [[Disney Channel]] series, ''[[That's So Raven]]'' in which she played Raven Baxter, a psychic teenager who tried her best to keep her psychic powers a secret. During her time on ''That's So Raven'', Raven-Symoné released her third studio album, ''[[This Is My Time (Raven-Symoné album)|This is My Time]]'' (2004) which was her best selling solo album to date, charting at number 51 on the ''Billboard'' 200.[{{BillboardURLbyName|artist=raven-symoné|chart=Billboard 200}} Raven-Symoné]. Billboard.com. Retrieved 2012-05-19. After a year of the end of ''That's So Raven'', she released her fourth studio album, ''[[Raven-Symoné (album)|Raven-Symoné]]'' (2008). The album peaked at number 159 on the ''Billboard'' 200. During 2003 to 2006, she participated in four soundtracks from Disney, [[RIAA certification|RIAA-certified]] double-platinum album, ''[[The Cheetah Girls (soundtrack)|The Cheetah Girls]]'' (2003), RIAA-certified gold album, ''[[That's So Raven (soundtrack)|That's So Raven]]'' (2004), ''[[That's So Raven Too!]]'' (2006) and RIAA-certified platinum album, ''[[The Cheetah Girls 2 (soundtrack)|The Cheetah Girls 2]]'' (2006). The soundtracks sold a combined 4.1 million copies in the U.S. alone. As of April 2008, Raven-Symoné has sold 314,000 albums in the United States.
+@@ -32,7 +10,7 @@
+ 
+ In 2012, Raven-Symoné ranked number eight on ''[[VH1]]''{{'s}} ""100 Greatest Kid Stars Of All Time"" list,[http://blog.vh1.com/2012-12-02/and-the-1-greatest-kid-star-of-all-time-is/ Greatest Kid Star Of All Time] and ranked number one on ''Loop21''{{'s}} ""10 Richest Black Actresses Under 40"" list.[http://www.loop21.com/entertainment/10-richest-black-actresses-under-40 10 Richest Black Actresses Under 40]
+ 
+-==Life and career==
++==Life and careeer==
+ 
+ ===1985–99: Early life and career beginnings with ''The Cosby Show''===
+ Raven-Symoné was born in Atlanta, Georgia to Lydia (née Gaulden) and Christopher B. Pearman. Raven-Symoné is of [[African-American]] http://www.tv.com/people/raven-symone/http://xfinity.comcast.net/slideshow/entertainment-aachildactors/3/http://ethnicelebs.com/raven-symonehttp://www.imdb.com/name/nm0712368/biohttp://www.nndb.com/people/017/000103705/ and [[Native Americans in the United States|Native American]] ancestry. At age three, her family moved to [[Ossining (village), New York|Ossining, New York]] where she attended Park School.Charlotte Moore (January 25, 2004). [http://www.pe.com/lifestyles/teen/stories/PE_Fea_Teen_raven0125.a11bc.html Raven takes flight]{{dead link|date=September 2011}} PE.com.[http://ftp.rootsweb.com/pub/usgenweb/la/winn/bios/sym1569.txt Rootsweb.com]{{Dead link|date=May 2010}} As an infant, she worked for Atlanta's Young Faces Inc. Modeling Agency and was featured in local print advertisements. At age two, she worked with Ford Models in New York City and appeared in ads for [[Ritz cracker]]s, [[gelatin dessert|Jell-O]], [[Fisher-Price]], and [[Cool Whip]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Selser regression: pages with templates that generate tables and foster content out of the table are broken\n\nAt URL , if you edit anything in the document, the infobox is deleted, but if you make a null edit, the infobox is retained.', ""This appears to be a bug in selser: if the HTML doesn't change, the wikitext doesn't change, but any small change in the HTML results in the infobox being deleted."", ""I verified that VisualEditor isn't dirtying anything, but just to be sure I also reproduced this on the command line by just making a 1-character change to the HTML as shown below."", 'I think this may have something to do with the double }} closing in the infobox.', ""$ mkdir tmp\n$ cd tmp\n$ wget 'URL -O originalHTML\n$ wget 'URL -O originalWikitext\n$ cp originalHTML editedHTML\n$ vi editedHTML   # Change '
    Life and career
    ' to '
    Life and careeer
    '\n$ node parse.js --html2wt --selser --oldtextfile originalWikitext --oldhtmlfile originalHTML --inputfile editedHTML > newWikitext\n$ diff -u originalWikitext newWikitext\n\n--- /home/catrope/tmp/originalWikitext\t2013-08-08 14:34:46.463998552 +0800\n+++ /home/catrope/tmp/newWikitext\t2013-08-08 17:04:41.596239434 +0800\n@@ -1,29 +1,7 @@\n {{Use mdy dates|date=June 2013}}\n {{pp-move-indef}}\n-{{Infobox person\n-| image           = Raven-Symoné 2011.jpg\n-| caption         = Raven-Symoné in 2011 \n-| birth_name      = Raven-Symoné Christina Pearman \n-| alias           = Raven
    Raven-Symone\n-| background      = solo_singer\n-| instrument      = [[Singing|Vocals]], [[piano]]\n-| birth_date      = {{birth date and age|mf=yes|1985|12|10}}\n-| birth_place     = [[Atlanta]], [[Georgia (U.S. state)|Georgia]], U.S.{{cite web |url=URL Symone:Biography on MSN |accessdate=2008-07-15 |year=2008 |publisher=[[MSN]]}} \n-| genre           = \n-| occupation      = Actress, singer, [[comedienne]], dancer, television producer, [[fashion model]]\n-| years_active    = 1989–present\n-| label           = [[MCA Records|MCA]], Crash, RayBlaze, [[Hollywood Records|Hollywood]]\n-| associated_acts = [[The Cheetah Girls (band)|The Cheetah Girls]]\n-| website         = [URL Raven-Symoné Myspace page]\n-| module         = {{Infobox musical artist|embed=yes\n-| background          = solo_singer\n-| genre               = [[Contemporary R&B|R&B]], [[pop music|pop]], [[Hip hop music|hip hop]], [[Soul music|soul]], [[dance music|dance]]\n-| instrument          = Vocals, [[piano]]\n-| years_active        = 1993–present\n-}}\n \n-}}\n '''Raven-Symoné Christina Pearman'''[URL (born December 10, 1985), known professionally as '''Raven-Symoné''' (pronounced {{IPA|/ˈreɪ.vən sɪˈmoʊn/}}, as though unaccented), or simply '''Raven''', is an American actress and singer."", 'Raven-Symoné launched her career in 1989 after appearing in \'\'[[The Cosby Show]]\'\' as Olivia.', 'She released her debut album, \'\'[[Here\'s to New Dreams]]\'\' in 1993; the single, ""[[That\'s What Little Girls Are Made Of]]"" charted number 68 on the US \'\'Billboard\'\' [[Hot 100]].[URL That\'s What Little Girls Are Made Of – Raven-Symoné].', 'Billboard.com.', ""Retrieved 2012-05-19. The next album, ''[[Undeniable (Raven-Symoné album)|Undeniable]]'', was released on May 4, 1999."", ""Raven-Symoné appeared in several successful television series, such as ''[[The Cosby Show]]'' and ''[[Hangin' with Mr. Cooper]]'', in the late 1980s and early 1990s."", ""From 2003 to 2007, she starred in the [[Disney Channel]] series, ''[[That's So Raven]]'' in which she played Raven Baxter, a psychic teenager who tried her best to keep her psychic powers a secret."", 'During her time on \'\'That\'s So Raven\'\', Raven-Symoné released her third studio album, \'\'[[This Is My Time (Raven-Symoné album)|This is My Time]]\'\' (2004) which was her best selling solo album to date, charting at number 51 on the \'\'Billboard\'\' 200.[{{BillboardURLbyName|artist=raven-symoné|chart=Billboard 200}} Raven-Symoné].', 'Billboard.com.', ""Retrieved 2012-05-19. After a year of the end of ''That's So Raven'', she released her fourth studio album, ''[[Raven-Symoné (album)|Raven-Symoné]]'' (2008)."", ""The album peaked at number 159 on the ''Billboard'' 200."", ""During 2003 to 2006, she participated in four soundtracks from Disney, [[RIAA certification|RIAA-certified]] double-platinum album, ''[[The Cheetah Girls (soundtrack)|The Cheetah Girls]]'' (2003), RIAA-certified gold album, ''[[That's So Raven (soundtrack)|That's So Raven]]'' (2004), ''[[That's So Raven Too!]]''"", ""(2006) and RIAA-certified platinum album, ''[[The Cheetah Girls 2 (soundtrack)|The Cheetah Girls 2]]'' (2006)."", 'The soundtracks sold a combined 4.1 million copies in the U.S. alone.', 'As of April 2008, Raven-Symoné has sold 314,000 albums in the United States.', '@@ -32,7 +10,7 @@\n \n In 2012, Raven-Symoné ranked number eight on \'\'[[VH1]]\'\'{{\'s}} ""100 Greatest Kid Stars Of All Time"" list,[URL Greatest Kid Star Of All Time] and ranked number one on \'\'Loop21\'\'{{\'s}} ""10 Richest Black Actresses Under 40"" list.[URL 10 Richest Black Actresses Under 40]\n \n-==Life and career==\n+==Life and careeer==\n \n ===1985–99: Early life and career beginnings with \'\'The Cosby Show\'\'===\n Raven-Symoné was born in Atlanta, Georgia to Lydia (née Gaulden) and Christopher B. Pearman.', 'Raven-Symoné is of [[African-American]] URL name=""imdb"">URL and [[Native Americans in the United States|Native American]] ancestry. At age three, her family moved to [[Ossining (village), New York|Ossining, New York]] where she attended Park School.Charlotte Moore (January 25, 2004).', ""[URL Raven takes flight]{{dead link|date=September 2011}} PE.com.[URL Rootsweb.com]{{Dead link|date=May 2010}} As an infant, she worked for Atlanta's Young Faces Inc."", 'Modeling Agency and was featured in local print advertisements.', 'At age two, she worked with Ford Models in New York City and appeared in ads for [[Ritz cracker]]s, [[gelatin dessert|Jell-O]], [[Fisher-Price]], and [[Cool Whip]].', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'MOTIVATION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+245979,Selser regression: pages with templates that generate tables and foster content out of the table are broken,Cache is now purged.  I tested on http://en.wikipedia.org/wiki/Crayon_Shin-chan (another page that had been reported with the bug) and verified fixed.,task_subcomment,"['Cache is now purged.', 'I tested on URL (another page that had been reported with the bug) and verified fixed.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+245973,Selser regression: pages with templates that generate tables and foster content out of the table are broken,"Fix deployed -- cache is not yet purged, but on purge tomorrow, this will be fixed.",task_subcomment,"['Fix deployed -- cache is not yet purged, but on purge tomorrow, this will be fixed.']",['WORKAROUNDS']
+245966,Selser regression: pages with templates that generate tables and foster content out of the table are broken,"Change 78242 merged by jenkins-bot:
+(Bug 52638) Fix selser regression introduced by fix for bug 51217
+
+https://gerrit.wikimedia.org/r/78242",task_subcomment,['Change 78242 merged by jenkins-bot:\n(Bug 52638) Fix selser regression introduced by fix for bug 51217\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245956,Selser regression: pages with templates that generate tables and foster content out of the table are broken,"Change 78242 had a related patch set uploaded by Subramanya Sastry:
+(Bug 52638) Fix selser regression introduced by fix for bug 51217
+
+https://gerrit.wikimedia.org/r/78242",task_subcomment,['Change 78242 had a related patch set uploaded by Subramanya Sastry:\n(Bug 52638) Fix selser regression introduced by fix for bug 51217\n\nGERRIT_URL'],['BUG REPRODUCTION']
+245949,Selser regression: pages with templates that generate tables and foster content out of the table are broken,"Reduced test case on which the problem can be reproduced:
+
+{|
+{{echo|a}}
+|-
+|x
+}}
+
+This is a selser regression introduced by a fix for bug 51217.
+
+A fix will be in shortly.",task_subcomment,"['Reduced test case on which the problem can be reproduced:\n\n{|\n{{echo|a}}\n|-\n|x\n}}\n\nThis is a selser regression introduced by a fix for bug 51217.', 'A fix will be in shortly.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+245942,Selser regression: pages with templates that generate tables and foster content out of the table are broken,"Confirmed. 
+
+It is not a double-closed infobox.  It is an infobox within an infobox.  Although, I have gone through a number of these scenarios of infoboxes within infoboxes earlier and handled them in our regular serializer ... and confirmed that normal WTS (wt serializer) can handle it.  Now examining what gives selser the fits.
+
+Thanks for the thorough testing and a way to reproduce it.  Will find a reduced test case and proceed.",task_subcomment,"['Confirmed.', 'It is not a double-closed infobox.', 'It is an infobox within an infobox.', 'Although, I have gone through a number of these scenarios of infoboxes within infoboxes earlier and handled them in our regular serializer ... and confirmed that normal WTS (wt serializer) can handle it.', 'Now examining what gives selser the fits.', 'Thanks for the thorough testing and a way to reproduce it.', 'Will find a reduced test case and proceed.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+54596,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"**Author:** `sandrobt.wiki`
+
+**Description:**
+When trying to link a page with less than or equal to 3 characters, the page is often indicated as New Page in the link box. For example, try to link ""A"", ""AB"" or ""ABB"" on en.wiki (both with capital letters and in lower case, the latter being redirects). 
+
+Notice that this problem doesn't happen with CD and NBA, but it does with Cd and Nba (all these pages are redirects on en.wiki).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50898",task_description,"['VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box\n\n**Author:** CODE\n\n**Description:**\nWhen trying to link a page with less than or equal to 3 characters, the page is often indicated as New Page in the link box.', 'For example, try to link ""A"", ""AB"" or ""ABB"" on en.wiki (both with capital letters and in lower case, the latter being redirects).', ""Notice that this problem doesn't happen with CD and NBA, but it does with Cd and Nba (all these pages are redirects on en.wiki)."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243461,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"
+
+*** This bug has been marked as a duplicate of bug 51013 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51013 ***'],['ISSUE CONTENT MANAGEMENT']
+243457,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"This is because VisualEditor relies on MediaWiki's search system to work out what pages exist, and the search engine ignores short strings as not worth bothering with.
+
+We could theoretically fix this in VisualEditor with a hack, but fixing search would be a better solution.",task_subcomment,"[""This is because VisualEditor relies on MediaWiki's search system to work out what pages exist, and the search engine ignores short strings as not worth bothering with."", 'We could theoretically fix this in VisualEditor with a hack, but fixing search would be a better solution.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+243453,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,*** Bug 53547 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53547 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243450,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"Indeed very, very odd. I've adjusted the bug summary to reflect the discovered behaviour. It is almost certainly unrelated to redirects though.",task_subcomment,"['Indeed very, very odd.', ""I've adjusted the bug summary to reflect the discovered behaviour."", 'It is almost certainly unrelated to redirects though.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+243446,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"**sandrobt.wiki** wrote:
+
+Another surprising case is ""Cara"" on it.wiki. It exists and it is not a redirect but is not recognized as existent (neither writing ""Cara"" nor ""cara""), and ""CARA"" doesn't exist at all. 
+So I guess this is not (only) related with redirects and it definitely appears also with pages with more than one character.",task_subcomment,"['**sandrobt.wiki** wrote:\n\nAnother surprising case is ""Cara"" on it.wiki.', 'It exists and it is not a redirect but is not recognized as existent (neither writing ""Cara"" nor ""cara""), and ""CARA"" doesn\'t exist at all.', 'So I guess this is not (only) related with redirects and it definitely appears also with pages with more than one character.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+243441,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"Hmm, not necessarily as simple as that as it recognises [[User:ABC]] and [[user:APL]]. It recognises both [[User:BBX]] and [[User:Bbx]] which are different pages and different users (the former Irish the latter a Finland-Swede).
+
+It doesn't recognise [[User:Jim]] but that is a redirect to [[User:Jim (usurped)]].
+
+It does recognise [[User:RVJ]], [[User:ZzZ]] and [[User:PQ3]]. 
+
+I'm stumped!",task_subcomment,"['Hmm, not necessarily as simple as that as it recognises [[User:ABC]] and [[user:APL]].', 'It recognises both [[User:BBX]] and [[User:Bbx]] which are different pages and different users (the former Irish the latter a Finland-Swede).', ""It doesn't recognise [[User:Jim]] but that is a redirect to [[User:Jim (usurped)]]."", 'It does recognise [[User:RVJ]], [[User:ZzZ]] and [[User:PQ3]].', ""I'm stumped!""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243436,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"(edit conflict)
+Actually assuming that what happens in the user: namespace matches what happens in the article namespace then it is to do with the presence of a redirect. [[User:Rob]] exists but no pages (redirects or otherwise) exist for other capitalisations of those three letters. [[User:Rob]] does appear in the list of suggestions. Now whether that is this bug or bug 50898 I haven't got a clue, so I'll comment there as well.
+
+(new text)
+So it appears that it might be capitalisation related rather than redirect related - it works with sentence case Rob but not allcaps AB and FRA.",task_subcomment,"['(edit conflict)\nActually assuming that what happens in the user: namespace matches what happens in the article namespace then it is to do with the presence of a redirect.', '[[User:Rob]] exists but no pages (redirects or otherwise) exist for other capitalisations of those three letters.', '[[User:Rob]] does appear in the list of suggestions.', ""Now whether that is this bug or bug 50898 I haven't got a clue, so I'll comment there as well."", '(new text)\nSo it appears that it might be capitalisation related rather than redirect related - it works with sentence case Rob but not allcaps AB and FRA.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243429,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"**sandrobt.wiki** wrote:
+
+> Hmm, although redirects do exist at Ab and Fra which is probably confusing
+> the
+> issue. I think all TLAs exist as redirects or articles in uppercase and
+> titlecase form so I don't know how to test this.
+
+Also User:AB and User:FRA erroneously appear as non-existing (and user:Ab and User:Fra don't exist).",task_subcomment,"[""**sandrobt.wiki** wrote:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAlso User:AB and User:FRA erroneously appear as non-existing (and user:Ab and User:Fra don't exist).""]",['OBSERVED BUG BEHAVIOR']
+243424,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"
+
+(In reply to comment #3)
+> What about ""AB"" or ""FRA""? Those are not redirects. Maybe ""single character
+> titles"" is not accurate enough.
+
+Hmm, although redirects do exist at Ab and Fra which is probably confusing the issue. I think all TLAs exist as redirects or articles in uppercase and titlecase form so I don't know how to test this.
+
+(In reply to comment #4)
+> Created attachment 13081 [details]
+> Link dialog doesn't recognise that existence of single-character page names
+
+This shows that it is the page name (excluding namespace) not the full page name (including namespace) that matters as [[User:A]] (which exists) is not recognised.
+
+**Attached**: {F11470}",task_subcomment,"['\n\n(In reply to comment #3)\nQUOTE\nQUOTE\n\nHmm, although redirects do exist at Ab and Fra which is probably confusing the issue.', ""I think all TLAs exist as redirects or articles in uppercase and titlecase form so I don't know how to test this."", '(In reply to comment #4)\nQUOTE\nQUOTE\n\nThis shows that it is the page name (excluding namespace) not the full page name (including namespace) that matters as [[User:A]] (which exists) is not recognised.', '**Attached**: {F11470}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243420,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"Created attachment 13081
+Link dialog doesn't recognise that existence of single-character page names
+
+**Attached**: {F11470}",task_subcomment,"[""Created attachment 13081\nLink dialog doesn't recognise that existence of single-character page names\n\n**Attached**: {F11470}""]",['BUG REPRODUCTION']
+243417,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"**sandrobt.wiki** wrote:
+
+What about ""AB"" or ""FRA""? Those are not redirects. Maybe ""single character titles"" is not accurate enough.",task_subcomment,"['**sandrobt.wiki** wrote:\n\nWhat about ""AB"" or ""FRA""?', 'Those are not redirects.', 'Maybe ""single character titles"" is not accurate enough.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243414,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"Redirects not showing in the list are due to case sensitivity issues, see bug 50898 
+
+Single character titles are never recognised, whether they are articles (e.g [[A]], [[Ä]]) or redirects, so I'm boldly refocusing this bug solely on this issue.",task_subcomment,"[""Redirects not showing in the list are due to case sensitivity issues, see bug 50898 \n\nSingle character titles are never recognised, whether they are articles (e.g [[A]], [[Ä]]) or redirects, so I'm boldly refocusing this bug solely on this issue.""]",['OBSERVED BUG BEHAVIOR']
+243410,VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box,"**sandrobt.wiki** wrote:
+
+Maybe writing ""short"" in the title was a mistake (but anyway this bug appears more often with short titles): SEGA, FIDO and GOOGLE also are not recognized as existing pages. However these are all redirects, so perhaps this is another known independent issue?",task_subcomment,"['**sandrobt.wiki** wrote:\n\nMaybe writing ""short"" in the title was a mistake (but anyway this bug appears more often with short titles): SEGA, FIDO and GOOGLE also are not recognized as existing pages.', 'However these are all redirects, so perhaps this is another known independent issue?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54561,VisualEditor: Dragging mouse clicks VE buttons upon release,"From Cryptic C62:
+
+Load VE on any page. Click and hold the left mouse button anywhere inside the browser window. Move the mouse on top of any button in the VE toolbar. Release the left mouse button. This activates the button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Dragging mouse clicks VE buttons upon release\n\nFrom Cryptic C62:\n\nLoad VE on any page.', 'Click and hold the left mouse button anywhere inside the browser window.', 'Move the mouse on top of any button in the VE toolbar.', 'Release the left mouse button.', 'This activates the button.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+241301,VisualEditor: Dragging mouse clicks VE buttons upon release,"I cant reproduce any combination supported on Linux, or Firefox/Windows/monobook.",task_subcomment,"['I cant reproduce any combination supported on Linux, or Firefox/Windows/monobook.']",['OBSERVED BUG BEHAVIOR']
+241295,VisualEditor: Dragging mouse clicks VE buttons upon release,"Does this still occur for anyone?
+Using the version of VE currently live on en.wp in Firefox 24/monobook/Linux I can't reproduce this at all, not even the way I could in comment 2",task_subcomment,"['Does this still occur for anyone?', ""Using the version of VE currently live on en.wp in Firefox 24/monobook/Linux I can't reproduce this at all, not even the way I could in comment 2""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241290,VisualEditor: Dragging mouse clicks VE buttons upon release,"After clarification I have done more testing and found that I can't reproduce this when any text is selected (including text in a table), but I can if the selection is exclusively an image or template (including an image in table).
+
+Further Cryptic C62 uses Windows Vista not Windows 7.",task_subcomment,"[""After clarification I have done more testing and found that I can't reproduce this when any text is selected (including text in a table), but I can if the selection is exclusively an image or template (including an image in table)."", 'Further Cryptic C62 uses Windows Vista not Windows 7.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241286,VisualEditor: Dragging mouse clicks VE buttons upon release,"Cryptic stated in the original bug report ""Some testing shows that this is universal (Firefox/Vector, Opera/Vector, Safari/Monobook)"". From other bug reports of theirs I believe that they run Windows 7.
+
+I have not been able to reproduce this in Firefox 22 on Xubuntu linux using Monobook. The toolbar button depresses as if it were going to apply its function, but nothing actually happens.",task_subcomment,"['Cryptic stated in the original bug report ""Some testing shows that this is universal (Firefox/Vector, Opera/Vector, Safari/Monobook)"".', 'From other bug reports of theirs I believe that they run Windows 7.', 'I have not been able to reproduce this in Firefox 22 on Xubuntu linux using Monobook.', 'The toolbar button depresses as if it were going to apply its function, but nothing actually happens.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54526,VisualEditor: Inspectors should not display below visible page area,"As an editor has pointed out on Mediawiki, the link dialog appears below the selected link.  If an editor has selected text at the bottom of the visible page area, the dialog appears ""below the fold"" and the editor must scroll down to access it.  Dialog should be forced to appear in the area currently visible when it is activated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Inspectors should not display below visible page area\n\nAs an editor has pointed out on Mediawiki, the link dialog appears below the selected link.', 'If an editor has selected text at the bottom of the visible page area, the dialog appears ""below the fold"" and the editor must scroll down to access it.', 'Dialog should be forced to appear in the area currently visible when it is activated.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239212,VisualEditor: Inspectors should not display below visible page area,"Change 163228 merged by jenkins-bot:
+DesktopContext: Ensure that inspectors/menus are fully visible when created
+
+https://gerrit.wikimedia.org/r/163228",task_subcomment,['Change 163228 merged by jenkins-bot:\nDesktopContext: Ensure that inspectors/menus are fully visible when created\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239205,VisualEditor: Inspectors should not display below visible page area,"(This only affects inspectors, and they're a VE feature; moving.)",task_subcomment,"[""(This only affects inspectors, and they're a VE feature; moving.)""]",['SOLUTION DISCUSSION']
+239198,VisualEditor: Inspectors should not display below visible page area,"Change 163280 merged by jenkins-bot:
+PopupWidget: Make $element not be a 0x0 box
+
+https://gerrit.wikimedia.org/r/163280",task_subcomment,['Change 163280 merged by jenkins-bot:\nPopupWidget: Make $element not be a 0x0 box\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+239192,VisualEditor: Inspectors should not display below visible page area,"Change 163280 had a related patch set uploaded by Bartosz Dziewoński:
+PopupWidget: Make $element not be a 0x0 box
+
+https://gerrit.wikimedia.org/r/163280",task_subcomment,['Change 163280 had a related patch set uploaded by Bartosz Dziewoński:\nPopupWidget: Make $element not be a 0x0 box\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239187,VisualEditor: Inspectors should not display below visible page area,"Change 163228 had a related patch set uploaded by Bartosz Dziewoński:
+[WIP] DesktopContext: Ensure that inspectors/menus are fully visible when created
+
+https://gerrit.wikimedia.org/r/163228",task_subcomment,['Change 163228 had a related patch set uploaded by Bartosz Dziewoński:\n[WIP] DesktopContext: Ensure that inspectors/menus are fully visible when created\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239182,VisualEditor: Inspectors should not display below visible page area,This is fixed for dialogs in gerrit 139550. It's not yet fixed for inspectors (which I suppose should scroll-into-view?).,task_subcomment,"['This is fixed for dialogs in gerrit 139550.', ""It's not yet fixed for inspectors (which I suppose should scroll-into-view?"", ').']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+54517,VisualEditor: Cannot apply annotations to link in specific case in Firefox,"At https://en.wikipedia.org/w/index.php?title=Indian_massacre_of_1622&oldid=564508110&veaction=edit, I can not unitalicize 'Nemattanew' (""In the spring of 1622, after a settler murdered his adviser ''[[Nemattanew]]'',"") in Firefox/Iceweasel 21.  It marks it as unitalicized in the toolbar, but if you click away and click back it shows italics again.
+
+I confirmed it wasn't related to my preferences by testing logged out (still in Firefox).  However, it does work fine logged out in Chromium.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Indian_massacre_of_1622&oldid=564508110&veaction=edit",task_description,"['VisualEditor: Cannot apply annotations to link in specific case in Firefox\n\nAt URL I can not unitalicize \'Nemattanew\' (""In the spring of 1622, after a settler murdered his adviser \'\'[[Nemattanew]]\'\',"") in Firefox/Iceweasel 21.', 'It marks it as unitalicized in the toolbar, but if you click away and click back it shows italics again.', ""I confirmed it wasn't related to my preferences by testing logged out (still in Firefox)."", 'However, it does work fine logged out in Chromium.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238713,VisualEditor: Cannot apply annotations to link in specific case in Firefox,"Change 114000 merged by jenkins-bot:
+Fix ce#getOffset when cursor is to the left of an annotation.
+
+https://gerrit.wikimedia.org/r/114000",task_subcomment,"['Change 114000 merged by jenkins-bot:\nFix ce#getOffset when cursor is to the left of an annotation.', 'GERRIT_URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238705,VisualEditor: Cannot apply annotations to link in specific case in Firefox,"Change 114000 had a related patch set uploaded by Esanders:
+Fix ce#getOffset when cursor is to the left of an annotation.
+
+https://gerrit.wikimedia.org/r/114000",task_subcomment,"['Change 114000 had a related patch set uploaded by Esanders:\nFix ce#getOffset when cursor is to the left of an annotation.', 'GERRIT_URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+238698,VisualEditor: Cannot apply annotations to link in specific case in Firefox,"(In reply to Ed Sanders from comment #3)
+> Can't reproduce in FF 27. Can someone else?
+
+Yes.",task_subcomment,['(In reply to Ed Sanders from comment #3)\nQUOTE\n\nYes.'],['SOLUTION DISCUSSION']
+238692,VisualEditor: Cannot apply annotations to link in specific case in Firefox,Can't reproduce in FF 27. Can someone else?,task_subcomment,"[""Can't reproduce in FF 27."", 'Can someone else?']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+238686,VisualEditor: Cannot apply annotations to link in specific case in Firefox,"Confirmed. Very odd. Note that making the selection broader (e.g. a character either side of the link) lets you make it bold/remove italics/etc.
+
+Sorry for very slow triage.",task_subcomment,"['Confirmed.', 'Very odd.', 'Note that making the selection broader (e.g.', 'a character either side of the link) lets you make it bold/remove italics/etc.', 'Sorry for very slow triage.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+238681,VisualEditor: Cannot apply annotations to link in specific case in Firefox,"Note, the way I tried to unitalicize was by double-clicking the name (so it's all highlighted), then clicking the toolbar italics icon (which showed as enabled before I clicked).",task_subcomment,"[""Note, the way I tried to unitalicize was by double-clicking the name (so it's all highlighted), then clicking the toolbar italics icon (which showed as enabled before I clicked).""]",['OBSERVED BUG BEHAVIOR']
+54504,VisualEditor: Top bar not staying at top,"It should go without saying, but you can't see it anymore when you scroll down, on occasion :D
+A few unrelated ways to reproduce this:
+
+1) http://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=567022295 here, the removed lines triggered this bug (original reporter experienced this while creating a page with that text). Also, when VEditing the version on the left, an ""up arrow"" before the very first word.
+
+2) http://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=567025383&oldid=567025004 that is, throw some text on an existing link, you'll lose the toolbar as well.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52433
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52441",task_description,"[""VisualEditor: Top bar not staying at top\n\nIt should go without saying, but you can't see it anymore when you scroll down, on occasion :D\nA few unrelated ways to reproduce this:\n\n1) URL here, the removed lines triggered this bug (original reporter experienced this while creating a page with that text)."", 'Also, when VEditing the version on the left, an ""up arrow"" before the very first word.', ""2) URL that is, throw some text on an existing link, you'll lose the toolbar as well."", 'Thanks.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237954,VisualEditor: Top bar not staying at top,"(In reply to comment #4)
+> I can't reproduce this now, is anyone else still seeing it or can we presume
+> that bug 52441 did fix the issue?
+
+My test file doesn't show the problem any more, certainly: seems to be fixed, thanks.",task_subcomment,"[""(In reply to comment #4)\nQUOTE\nQUOTE\n\nMy test file doesn't show the problem any more, certainly: seems to be fixed, thanks.""]",['SOLUTION USAGE']
+237946,VisualEditor: Top bar not staying at top,"I can't reproduce this now, is anyone else still seeing it or can we presume that bug 52441 did fix the issue?",task_subcomment,"[""I can't reproduce this now, is anyone else still seeing it or can we presume that bug 52441 did fix the issue?""]",['BUG REPRODUCTION']
+237938,VisualEditor: Top bar not staying at top,Will the fix of Bug 52441 (awaiting deployment) also solve this?,task_subcomment,['Will the fix of Bug 52441 (awaiting deployment) also solve this?'],['BUG REPRODUCTION']
+237934,VisualEditor: Top bar not staying at top,"Compare http://en.wikipedia.org/wiki/User:PamD/sandbox_for_VE/test2 (top bar disappears) http://en.wikipedia.org/wiki/User:PamD/sandbox_for_VE/test3 (no problem): only difference is addition of ""a "" before the linked text on first line. No other links, templates, complexities, in the files.",task_subcomment,"['Compare URL (top bar disappears) URL (no problem): only difference is addition of ""a "" before the linked text on first line.', 'No other links, templates, complexities, in the files.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237926,VisualEditor: Top bar not staying at top,"http://en.wikipedia.org/w/index.php?title=User%3APamD%2Fsandbox_for_VE%2Ftest1&diff=567087060&oldid=567086998  Unlinking the first word seems to have solved the problem. Given that most dab pages with titles in ""Foo (disambiguation)"" start off with a bolded link to Foo, this is a problem.",task_subcomment,"['URL  Unlinking the first word seems to have solved the problem.', 'Given that most dab pages with titles in ""Foo (disambiguation)"" start off with a bolded link to Foo, this is a problem.']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+54499,VisualEditor: Protected node css with * selector breaks some template layouts,"Specifically [[Template:Football kit]] which was created in 2004 by some young genius.
+
+The rules which cause problems are:
+
+.ve-ce-protectedNode * {
+	position: relative !important;
+	top: 0 !important;
+	left: 0 !important;
+	bottom: 0 !important;
+	right: 0 !important;
+...
+}
+
+in ve.ce.Node.css
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61497",task_description,"['VisualEditor: Protected node css with * selector breaks some template layouts\n\nSpecifically [[Template:Football kit]] which was created in 2004 by some young genius.', 'The rules which cause problems are:\n\n.ve-ce-protectedNode * {\n\tposition: relative !important;\n\ttop: 0 !important;\n\tleft: 0 !important;\n\tbottom: 0 !important;\n\tright: 0 !important;\n...\n}\n\nin ve.ce.Node.css\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+237587,VisualEditor: Protected node css with * selector breaks some template layouts,"Change 130823 merged by jenkins-bot:
+Remove '*' selector for protected nodes
+
+https://gerrit.wikimedia.org/r/130823",task_subcomment,"[""Change 130823 merged by jenkins-bot:\nRemove '*' selector for protected nodes\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+237577,VisualEditor: Protected node css with * selector breaks some template layouts,"Created attachment 15263
+Screenshot of problem and patched version
+
+**Attached**: {F11282}",task_subcomment,['Created attachment 15263\nScreenshot of problem and patched version\n\n**Attached**: {F11282}'],['ATTACHMENT']
+237569,VisualEditor: Protected node css with * selector breaks some template layouts,"Change 130823 had a related patch set uploaded by Esanders:
+Remove '*' selector for protected nodes
+
+https://gerrit.wikimedia.org/r/130823",task_subcomment,"[""Change 130823 had a related patch set uploaded by Esanders:\nRemove '*' selector for protected nodes\n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+54490,VisualEditor: Reference fails to display in reference list on init or change (but appears if you add a new use of it),"In the VE editing Window, VE does now not show references or only some of them on De.WP; both in editing the entire article and only the respective section:
+
+http://de.wikipedia.org/wiki/Google#Einzelnachweise 1 out of 55
+
+http://de.wikipedia.org/wiki/Chaim_Perelman#Einzelnachweise 0 out of 1
+
+http://de.wikipedia.org/wiki/Seilkorb#Einzelnachweise 5 out of 15
+
+http://de.wikipedia.org/wiki/Joan_Coromines#Fu.C3.9Fnoten 0 out of 3
+
+Three people looked at it but it is hard to track down a pattern. Perhabs (wild ceteris paribus-guess) related to 51741?
+
+Report:
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121153367#Einzelnachweise_am_Artikelende_werden_im_VE_nicht_angezeigt
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Reference fails to display in reference list on init or change (but appears if you add a new use of it)\n\nIn the VE editing Window, VE does now not show references or only some of them on De.WP; both in editing the entire article and only the respective section:\n\nURL 1 out of 55\n\nURL 0 out of 1\n\nURL 5 out of 15\n\nURL 0 out of 3\n\nThree people looked at it but it is hard to track down a pattern.', 'Perhabs (wild ceteris paribus-guess) related to 51741?', 'Report:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+236998,VisualEditor: Reference fails to display in reference list on init or change (but appears if you add a new use of it),This was fixed by https://gerrit.wikimedia.org/r/#/c/77346/1 . Apparently yet to deploy on de.wiki.,task_subcomment,"['This was fixed by URL .', 'Apparently yet to deploy on de.wiki.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+236988,VisualEditor: Reference fails to display in reference list on init or change (but appears if you add a new use of it),This looks like a bug we fixed recently with unnamed references. What version is deployed to de.wiki?,task_subcomment,"['This looks like a bug we fixed recently with unnamed references.', 'What version is deployed to de.wiki?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236980,VisualEditor: Reference fails to display in reference list on init or change (but appears if you add a new use of it),Does de.wp have more than one method of displaying references (equivalent to en's {{reflist}} and )? If so then this could be related to bug 52371,task_subcomment,"[""Does de.wp have more than one method of displaying references (equivalent to en's {{reflist}} and )?"", 'If so then this could be related to bug 52371']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+54483,"TemplateData: Fix ""TypeError: Cannot read property 'content' of undefined"" (when applying template changes)","Looks like we don't account for the API returning an error in ve.ce.MWTransclusionNode.prototype.generateContents. Unconditionally response.visualeditor.content is accessed.
+
+API has a clear path both for dieUsage() and result === success.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['TemplateData: Fix ""TypeError: Cannot read property \'content\' of undefined"" (when applying template changes)\n\nLooks like we don\'t account for the API returning an error in ve.ce.MWTransclusionNode.prototype.generateContents.', 'Unconditionally response.visualeditor.content is accessed.', 'API has a clear path both for dieUsage() and result === success.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+236608,"TemplateData: Fix ""TypeError: Cannot read property 'content' of undefined"" (when applying template changes)","Change 77460 merged by jenkins-bot:
+ve.ce.MWTransclusionNode: Check for API errors
+
+https://gerrit.wikimedia.org/r/77460",task_subcomment,['Change 77460 merged by jenkins-bot:\nve.ce.MWTransclusionNode: Check for API errors\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+236600,"TemplateData: Fix ""TypeError: Cannot read property 'content' of undefined"" (when applying template changes)","Change 77460 had a related patch set uploaded by Krinkle:
+ve.ce.MWTransclusionNode: Check for API errors
+
+https://gerrit.wikimedia.org/r/77460",task_subcomment,['Change 77460 had a related patch set uploaded by Krinkle:\nve.ce.MWTransclusionNode: Check for API errors\n\nGERRIT_URL'],['ACTION ON ISSUE']
+54477,VisualEditor: Data model should be able to default between equivalent annotations,"We want to be able to treat some pairs (more than pairs?) of annotations as the same, edited in the same way:
+
+* code / tt
+* b / strong
+* i / em
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Data model should be able to default between equivalent annotations\n\nWe want to be able to treat some pairs (more than pairs?)', 'of annotations as the same, edited in the same way:\n\n* code / tt\n* b / strong\n* i / em\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+236355,VisualEditor: Data model should be able to default between equivalent annotations,"Change 78204 merged by jenkins-bot:
+Generic support for multiple tags in TextStyleAnnotation
+
+https://gerrit.wikimedia.org/r/78204",task_subcomment,['Change 78204 merged by jenkins-bot:\nGeneric support for multiple tags in TextStyleAnnotation\n\nGERRIT_URL'],['ACTION ON ISSUE']
+236349,VisualEditor: Data model should be able to default between equivalent annotations,"Change 78204 had a related patch set uploaded by Catrope:
+Generic support for multiple tags in TextStyleAnnotation
+
+https://gerrit.wikimedia.org/r/78204",task_subcomment,['Change 78204 had a related patch set uploaded by Catrope:\nGeneric support for multiple tags in TextStyleAnnotation\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+236343,VisualEditor: Data model should be able to default between equivalent annotations,code/tt duplicate of bug 52352,task_subcomment,['code/tt duplicate of bug 52352'],['OBSERVED BUG BEHAVIOR']
+54476,Update tours for new edit tab selectors,"VE changed the edit tab selectors as part of their UI update to show it's in Beta.
+
+Now, on English Wikipedia, with VE enabled:
+
+* ca-edit is source editing
+* ca-ve-edit is VE editing
+
+In a blacklisted browser:
+
+* ca-edit is source editing
+* ca-ve-edit is hidden
+
+The tours need to be adjusted accordingly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"[""Update tours for new edit tab selectors\n\nVE changed the edit tab selectors as part of their UI update to show it's in Beta."", 'Now, on English Wikipedia, with VE enabled:\n\n* ca-edit is source editing\n* ca-ve-edit is VE editing\n\nIn a blacklisted browser:\n\n* ca-edit is source editing\n* ca-ve-edit is hidden\n\nThe tours need to be adjusted accordingly.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+236298,Update tours for new edit tab selectors,"Change 78026 merged by jenkins-bot:
+Update VE section edit selector
+
+https://gerrit.wikimedia.org/r/78026",task_subcomment,['Change 78026 merged by jenkins-bot:\nUpdate VE section edit selector\n\nGERRIT_URL'],['ACTION ON ISSUE']
+236295,Update tours for new edit tab selectors,"Change 78026 had a related patch set uploaded by Mattflaschen:
+Update VE section edit selector
+
+https://gerrit.wikimedia.org/r/78026",task_subcomment,['Change 78026 had a related patch set uploaded by Mattflaschen:\nUpdate VE section edit selector\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+236290,Update tours for new edit tab selectors,"Change 77387 merged by jenkins-bot:
+Update to match new VisualEditor edit tab selector
+
+https://gerrit.wikimedia.org/r/77387",task_subcomment,['Change 77387 merged by jenkins-bot:\nUpdate to match new VisualEditor edit tab selector\n\nGERRIT_URL'],['ACTION ON ISSUE']
+236285,Update tours for new edit tab selectors,"Change 77387 had a related patch set uploaded by Mattflaschen:
+Update to match new VisualEditor edit tab selector
+
+https://gerrit.wikimedia.org/r/77387",task_subcomment,['Change 77387 had a related patch set uploaded by Mattflaschen:\nUpdate to match new VisualEditor edit tab selector\n\nGERRIT_URL'],['ACTION ON ISSUE']
+236279,Update tours for new edit tab selectors,"**swalling** wrote:
+
+Yes, without this fixed I get the gettinstartedtasktoolbarve tour (meant for VE) pointing to edit source, not the new beta tab. 
+
+Thankfully it's just missing some steps, not causing any visibly broken or confusing behavior.",task_subcomment,"['**swalling** wrote:\n\nYes, without this fixed I get the gettinstartedtasktoolbarve tour (meant for VE) pointing to edit source, not the new beta tab.', ""Thankfully it's just missing some steps, not causing any visibly broken or confusing behavior.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54475,VisualEditor:  User guide should open in a new tab/window,"From user:PamD at en.wp:
+
+Clicking on the ""Read the User Guide"" link (within the Beta/questionmark popup) has the effect of losing all current editing, because it opens the User Guide in the current window, without warning that it's going to do so. Imagine: half an hour's editing, find a problem, remember seeing that link and think it might offer advice, click for the popup, click to open the User Guide, and ... one very unhappy editor. I suggest that either the User Guide should open in a new tab or window, or, if this is impossible, there should be a warning ""Read the User Guide (and lose any current edits)"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor:  User guide should open in a new tab/window\n\nFrom user:PamD at en.wp:\n\nClicking on the ""Read the User Guide"" link (within the Beta/questionmark popup) has the effect of losing all current editing, because it opens the User Guide in the current window, without warning that it\'s going to do so.', ""Imagine: half an hour's editing, find a problem, remember seeing that link and think it might offer advice, click for the popup, click to open the User Guide, and ... one very unhappy editor."", 'I suggest that either the User Guide should open in a new tab or window, or, if this is impossible, there should be a warning ""Read the User Guide (and lose any current edits)"".', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+236240,VisualEditor:  User guide should open in a new tab/window,"Thanks for the reply, that is very useful to know.
+
+Brevity is not my strong suit so I've refrained from making a change to it myself. I've asked for suggestions at [[WP:VE/F#User Manual should open in new tab/window]], feel free to opine.",task_subcomment,"['Thanks for the reply, that is very useful to know.', ""Brevity is not my strong suit so I've refrained from making a change to it myself."", ""I've asked for suggestions at [[WP:VE/F#User Manual should open in new tab/window]], feel free to opine.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+236236,VisualEditor:  User guide should open in a new tab/window,"The text is controlled by https://en.wikipedia.org/wiki/MediaWiki:Visualeditor-help-label - but I'd counsel against putting a lot of text into it, as it may not look very good.",task_subcomment,"[""The text is controlled by URL - but I'd counsel against putting a lot of text into it, as it may not look very good.""]",['SOLUTION DISCUSSION']
+236233,VisualEditor:  User guide should open in a new tab/window,"Thanks for the super-quick fix.
+
+As for the wait until deployment, would it be possible to add something like ""(hold CTRL while clicking this link to open it in a new window)"" before this goes live?
+If not it's not worth doing anything, but if we can as an interim measure help some people that's better than nothing.",task_subcomment,"['Thanks for the super-quick fix.', 'As for the wait until deployment, would it be possible to add something like ""(hold CTRL while clicking this link to open it in a new window)"" before this goes live?', ""If not it's not worth doing anything, but if we can as an interim measure help some people that's better than nothing.""]","['SOLUTION USAGE', 'SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+236231,VisualEditor:  User guide should open in a new tab/window,"Now fixed in the code; next scheduled deployment is not until 15 August, however. :-(",task_subcomment,"['Now fixed in the code; next scheduled deployment is not until 15 August, however.', ':-(']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+236229,VisualEditor:  User guide should open in a new tab/window,"Change 77374 merged by jenkins-bot:
+Make the link to the user guide open in a new window
+
+https://gerrit.wikimedia.org/r/77374",task_subcomment,['Change 77374 merged by jenkins-bot:\nMake the link to the user guide open in a new window\n\nGERRIT_URL'],['ACTION ON ISSUE']
+236225,VisualEditor:  User guide should open in a new tab/window,"Change 77374 had a related patch set uploaded by Jforrester:
+Make the link to the user guide open in a new window
+
+https://gerrit.wikimedia.org/r/77374",task_subcomment,['Change 77374 had a related patch set uploaded by Jforrester:\nMake the link to the user guide open in a new window\n\nGERRIT_URL'],['ACTION ON ISSUE']
+236219,VisualEditor:  User guide should open in a new tab/window,Marking as high priority like similar bug 52093,task_subcomment,['Marking as high priority like similar bug 52093'],['BUG REPRODUCTION']
+54463,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"en.wp user:Wouterstomp asks.
+""When no image is found, please display a message saying so, now it looks like nothing is happening (especially [if you] missed the short busy animation of the search bar)""
+The context is the image insertion dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",task_description,"['VisualEditor: Media insertion dialog should display a message if no media is found for the given search\n\nen.wp user:Wouterstomp asks.', '""When no image is found, please display a message saying so, now it looks like nothing is happening (especially [if you] missed the short busy animation of the search bar)""\nThe context is the image insertion dialog.', '--------------------------\n**Version**: unspecified\n**Severity**: trivial']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+235622,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,Verified in production,task_subcomment,['Verified in production'],['OBSERVED BUG BEHAVIOR']
+235618,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,Verified the fix in Betalabs,task_subcomment,['Verified the fix in Betalabs'],['BUG REPRODUCTION']
+235614,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Change 133864 merged by jenkins-bot:
+Hide 'no results found' once there's at least one result
+
+https://gerrit.wikimedia.org/r/133864",task_subcomment,"[""Change 133864 merged by jenkins-bot:\nHide 'no results found' once there's at least one result\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+235610,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Change 133864 had a related patch set uploaded by Jforrester:
+Hide 'no results found' once there's at least one result
+
+https://gerrit.wikimedia.org/r/133864",task_subcomment,"[""Change 133864 had a related patch set uploaded by Jforrester:\nHide 'no results found' once there's at least one result\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+235606,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Change 133858 merged by jenkins-bot:
+Hide 'no results found' once there's at least one result
+
+https://gerrit.wikimedia.org/r/133858",task_subcomment,"[""Change 133858 merged by jenkins-bot:\nHide 'no results found' once there's at least one result\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+235601,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Change 133858 had a related patch set uploaded by Mooeypoo:
+Hide 'no results found' once there's at least one result
+
+https://gerrit.wikimedia.org/r/133858",task_subcomment,"[""Change 133858 had a related patch set uploaded by Mooeypoo:\nHide 'no results found' once there's at least one result\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+235598,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Created attachment 15419
+Screenshot
+
+**Attached**: {F11195}",task_subcomment,['Created attachment 15419\nScreenshot\n\n**Attached**: {F11195}'],['ATTACHMENT']
+235592,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"The message ""No results found"" stays in the dialog even if user changed the search string and the matched images appear inside the dialog.See the screenshot attached",task_subcomment,"['The message ""No results found"" stays in the dialog even if user changed the search string and the matched images appear inside the dialog.See the screenshot attached']",['OBSERVED BUG BEHAVIOR']
+235585,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Change 133050 merged by jenkins-bot:
+If no media is found display a message in media insert dialog
+
+https://gerrit.wikimedia.org/r/133050",task_subcomment,['Change 133050 merged by jenkins-bot:\nIf no media is found display a message in media insert dialog\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+235579,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Change 133050 had a related patch set uploaded by Mooeypoo:
+If no media is found display a message in media insert dialog
+
+https://gerrit.wikimedia.org/r/133050",task_subcomment,['Change 133050 had a related patch set uploaded by Mooeypoo:\nIf no media is found display a message in media insert dialog\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+235572,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"WhatamIdoing, there is a design that has not been implemented yet for the image dialog that allow quick access to users uploads, perhaps in the case of zero search results, we can automatically show that mode.",task_subcomment,"['WhatamIdoing, there is a design that has not been implemented yet for the image dialog that allow quick access to users uploads, perhaps in the case of zero search results, we can automatically show that mode.']",['SOLUTION DISCUSSION']
+235565,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,*** Bug 60932 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 60932 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235561,VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Given the fact that users often want to add the image that they just uploaded, and that Commons's search is fairly often taking a couple of days to ""notice"" that these images exist, the default message on wikis that use Commons should say something like ""No image was found.  If you just uploaded an image with this name, this may be due to the image not being indexed in Commons's search database yet.  Please try again in a couple of days.""
+
+It might also be worth linking to a help page that describes limitations in the search protocol.  For example, it will find images if I give it the whole name (""2013AliceAndBob"") but not if I give it just the start of the name (""2013Alice"").",task_subcomment,"['Given the fact that\xa0users often want to add the image that they just uploaded, and that Commons\'s search is fairly often taking a couple of days to ""notice"" that these images exist, the default message on wikis that use Commons should say something like ""No image was found.', ""If you just uploaded an image with this name, this may be due to the image not being indexed in Commons's search database yet."", 'Please try again in a couple of days.""', 'It might also be worth linking to a help page that describes limitations in the search protocol.', 'For example, it will find images if I give it the whole name (""2013AliceAndBob"") but not if I give it just the start of the name (""2013Alice"").']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+54460,VisualEditor:  Inserting media when text is selected should not overwrite text,"When a user tries to inset an image or other media while they have text selected, the text is replaced by the media. This probably is not what they want and is contrary to how the transclusion editor works (inserts the template after the selected text).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor:  Inserting media when text is selected should not overwrite text\n\nWhen a user tries to inset an image or other media while they have text selected, the text is replaced by the media.', 'This probably is not what they want and is contrary to how the transclusion editor works (inserts the template after the selected text).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+235386,VisualEditor:  Inserting media when text is selected should not overwrite text,"Change 82463 merged by jenkins-bot:
+Insert images after selection, not in place of it
+
+https://gerrit.wikimedia.org/r/82463",task_subcomment,"['Change 82463 merged by jenkins-bot:\nInsert images after selection, not in place of it\n\nGERRIT_URL']",['ACTION ON ISSUE']
+235380,VisualEditor:  Inserting media when text is selected should not overwrite text,"Change 82463 had a related patch set uploaded by Trevor Parscal:
+Insert images after selection, not in place of it
+
+https://gerrit.wikimedia.org/r/82463",task_subcomment,"['Change 82463 had a related patch set uploaded by Trevor Parscal:\nInsert images after selection, not in place of it\n\nGERRIT_URL']",['ACTION ON ISSUE']
+54441,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,"As of recently the toolbar no longer goes in/out of floating mode after opening an inspector. It will stay in whatever position it was (fixed/absolute, top/left/right/height)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52504",task_description,"['VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector\n\nAs of recently the toolbar no longer goes in/out of floating mode after opening an inspector.', 'It will stay in whatever position it was (fixed/absolute, top/left/right/height)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+234329,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52739 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52739 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234323,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52789 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52789 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234316,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52433 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52433 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234310,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52326 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52326 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234304,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,"Now fixed in the code; next scheduled deployment is not until 15 August,
+however. :-(",task_subcomment,"['Now fixed in the code; next scheduled deployment is not until 15 August,\nhowever.', ':-(']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+234297,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,"Change 77274 merged by jenkins-bot:
+ve.ui.Toolbar: Use closure instead of ve.bind for event handlers
+
+https://gerrit.wikimedia.org/r/77274",task_subcomment,['Change 77274 merged by jenkins-bot:\nve.ui.Toolbar: Use closure instead of ve.bind for event handlers\n\nGERRIT_URL'],['ACTION ON ISSUE']
+234287,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,"Change 77274 had a related patch set uploaded by Krinkle:
+ve.ui.Toolbar: Use closure instead of ve.bind for event handlers
+
+https://gerrit.wikimedia.org/r/77274",task_subcomment,['Change 77274 had a related patch set uploaded by Krinkle:\nve.ui.Toolbar: Use closure instead of ve.bind for event handlers\n\nGERRIT_URL'],['ACTION ON ISSUE']
+234279,VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,"After much debugging (filed the bug only now), I figured out what caused it:
+
+The target toolbar continues to have toolbar.floatable === true. That never gets disabled by anything, so that's good.
+
+What happens is that the toolbar inside the context menu, twice, gets called disableFloatable on. Though that is a separate instance, independent, there is 1 place where it effects global state unfortunately: the $window handlers.
+
+The prototype is inherited by each instance, naturally, which means toolbarA.onWindowScroll === toolbarB.onWindowScroll. So when we pass them to $window.off to unbind by reference, it does exactly what you (now) expect, thus also breaking it for other toolbars.
+
+However that's not what's happening, actually, because we (of course) want each toolbar to have the event bound to the exact instance of ve.ui.Toolbar, and we do so by using ve.bind.
+
+Which means toolbarA.windowEvents.scroll is a unique closure, separate from toolbarB.windowEvents.scroll. That is what makes it work. So why does it fail?
+
+Well, jQuery.proxy (=== ve.bind) is so nice for us that it tacks a guid property on the function reference to make sure that when binding a function to a scope, we can still identify it. This e.g. makes the following possible:
+
+ 1: $foo.on( 'scroll', $.proxy( myHandler ) );
+ 2: $foo.off( 'scroll', myHandler );
+ 3: // or alternatively, though useless:
+ 4: $foo.off( 'scroll', $.proxy( myHandler ) );
+
+jQuery's event system uses this same guid (when present) to unbind a method.
+
+So the first time we call ve.bind in a ve.ui.Toolbar construction, a guid is added to #onWindowScroll.. And the second time it just uses the same guid again (which makes line 4 above work). It does still make a new closure, so there's no problem with the second one being given a cached closure or something that refers to the first instance, nothing like that.
+
+However we very much don't want this. We need each one to be unique not just by reference and context bound, but no shared guids.
+
+Finally, why did this break only recently? Well, before 14343c7bf7 toolbar.$window was null by default and stayed that way until enableFloating was called. So the call to disableFloating for the context menu toolbar did nothing.
+
+14343c7bf7 refactored the code to always need a toolbar.$window during initialisation, and for efficiency kept the instance around as to not create/destroy it each time.
+
+So though 14343c7bf7 introduced the bug being more visible, the problem was already in the code. Both then and now, when enableFloating is called and then disableFloating, the disableFloating unbinds all window events for effectively all toolbars.
+
+
+Also:
+- During debugging I found that we're calling disableFloatable *twice* on the context menu toolbar (once when the inspector is opened and again when we close it). That should be optimised to one. Or better, don't call it at all since it is disabled by default.",task_subcomment,"['After much debugging (filed the bug only now), I figured out what caused it:\n\nThe target toolbar continues to have toolbar.floatable === true.', ""That never gets disabled by anything, so that's good."", 'What happens is that the toolbar inside the context menu, twice, gets called disableFloatable on.', 'Though that is a separate instance, independent, there is 1 place where it effects global state unfortunately: the $window handlers.', 'The prototype is inherited by each instance, naturally, which means toolbarA.onWindowScroll === toolbarB.onWindowScroll.', 'So when we pass them to $window.off to unbind by reference, it does exactly what you (now) expect, thus also breaking it for other toolbars.', ""However that's not what's happening, actually, because we (of course) want each toolbar to have the event bound to the exact instance of ve.ui.Toolbar, and we do so by using ve.bind."", 'Which means toolbarA.windowEvents.scroll is a unique closure, separate from toolbarB.windowEvents.scroll.', 'That is what makes it work.', 'So why does it fail?', 'Well, jQuery.proxy (=== ve.bind) is so nice for us that it tacks a guid property on the function reference to make sure that when binding a function to a scope, we can still identify it.', 'This e.g.', ""makes the following possible:\n\n 1: $foo.on( 'scroll', $.proxy( myHandler ) );\n 2: $foo.off( 'scroll', myHandler );\n 3: // or alternatively, though useless:\n 4: $foo.off( 'scroll', $.proxy( myHandler ) );\n\njQuery's event system uses this same guid (when present) to unbind a method."", 'So the first time we call ve.bind in a ve.ui.Toolbar construction, a guid is added to #onWindowScroll.. And the second time it just uses the same guid again (which makes line 4 above work).', ""It does still make a new closure, so there's no problem with the second one being given a cached closure or something that refers to the first instance, nothing like that."", ""However we very much don't want this."", 'We need each one to be unique not just by reference and context bound, but no shared guids.', 'Finally, why did this break only recently?', 'Well, before 14343c7bf7 toolbar.$window was null by default and stayed that way until enableFloating was called.', 'So the call to disableFloating for the context menu toolbar did nothing.', '14343c7bf7 refactored the code to always need a toolbar.$window during initialisation, and for efficiency kept the instance around as to not create/destroy it each time.', 'So though 14343c7bf7 introduced the bug being more visible, the problem was already in the code.', 'Both then and now, when enableFloating is called and then disableFloating, the disableFloating unbinds all window events for effectively all toolbars.', ""Also:\n- During debugging I found that we're calling disableFloatable *twice* on the context menu toolbar (once when the inspector is opened and again when we close it)."", 'That should be optimised to one.', ""Or better, don't call it at all since it is disabled by default.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+54427,VisualEditor: references in image captions are not included in reflists,"Similar to bug 51289 and bug 52398 references that are defined in image captions do not appear in reflists. Example at [[Radiocarbon dating]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51289
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52398
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50459",task_description,"['VisualEditor: references in image captions are not included in reflists\n\nSimilar to bug 51289 and bug 52398 references that are defined in image captions do not appear in reflists.', 'Example at [[Radiocarbon dating]].', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233531,VisualEditor: references in image captions are not included in reflists,"Re-setting as FIXED, and have raised the regression as bug 57228.",task_subcomment,"['Re-setting as FIXED, and have raised the regression as bug 57228.']",['SOLUTION USAGE']
+233527,VisualEditor: references in image captions are not included in reflists,"<<[...] the references 20 and 21 in https://en.wikipedia.org/wiki/Baruch_Spinoza?veaction=edit which are in image captions disappear from the references list in VE and the numbering becomes discombobulated. Win7 FF 24.0 Monobook. --Atethnekos (Discussion, Contributions) 05:42, 12 November 2013 (UTC)>>.",task_subcomment,"['<<[...] the references 20 and 21 in URL which are in image captions disappear from the references list in VE and the numbering becomes discombobulated.', 'Win7 FF 24.0 Monobook.', '--Atethnekos (Discussion, Contributions) 05:42, 12 November 2013 (UTC)>>.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'CONTRIBUTION AND COMMITMENT']"
+233523,VisualEditor: references in image captions are not included in reflists,"Change 77346 merged by jenkins-bot:
+Only skip past empty keyedNodes sets if key exists
+
+https://gerrit.wikimedia.org/r/77346",task_subcomment,['Change 77346 merged by jenkins-bot:\nOnly skip past empty keyedNodes sets if key exists\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233519,VisualEditor: references in image captions are not included in reflists,"Change 77346 had a related patch set uploaded by Esanders:
+Only skip past empty keyedNodes sets if key exists
+
+https://gerrit.wikimedia.org/r/77346",task_subcomment,['Change 77346 had a related patch set uploaded by Esanders:\nOnly skip past empty keyedNodes sets if key exists\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233516,VisualEditor: references in image captions are not included in reflists,"**kwwilliams** wrote:
+
+52300 may also be related.",task_subcomment,['**kwwilliams** wrote:\n\n52300 may also be related.'],['OBSERVED BUG BEHAVIOR']
+54372,VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"At https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=566679647#Spellchecking_wikilinks_causes_odd_behavior en.wp editor Cryptic C62 has identified that spellchecking links causes inconsistent and apparently unpredictable behaviour. Undoing that change sometimes introduces another layer of inconsistent behaviour.
+
+On some occasions both correcting the spelling and undoing it works as it should, but there are at least six types of undesired behaviour where some or all of the link is unlinked. 
+
+Detailed examples are at the above link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Using browser native interactive spell-check tool breaks in Firefox\n\nAt URL en.wp editor Cryptic C62 has identified that spellchecking links causes inconsistent and apparently unpredictable behaviour.', 'Undoing that change sometimes introduces another layer of inconsistent behaviour.', 'On some occasions both correcting the spelling and undoing it works as it should, but there are at least six types of undesired behaviour where some or all of the link is unlinked.', 'Detailed examples are at the above link.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+255215,VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 50822 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50822 ***'],['ISSUE CONTENT MANAGEMENT']
+255205,VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"**crypticc62** wrote:
+
+I've found that a similar problem occurs with Chrome on an iPad 3, though with very different results. In this environment, the spellcheck seems to work fine, but undo causes the original string to be appended to the new string, rather than replacing it.",task_subcomment,"[""**crypticc62** wrote:\n\nI've found that a similar problem occurs with Chrome on an iPad 3, though with very different results."", 'In this environment, the spellcheck seems to work fine, but undo causes the original string to be appended to the new string, rather than replacing it.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54366,VisualEditor: Make beta notice more prominent,"The current beta notice for VisualEditor is currently easy to miss. While it uses a circled ""?"" and the text ""BETA"", it can blend in with the rest of the VisualEditor editing interface pretty easily (I only really noticed that there was any kind of warning today).
+
+The notice that VisualEditor is beta software should be made more prominent.
+
+James has suggested showing a more prominent notice for first-time VisualEditor users (presumably based on a cookie).
+
+My preference is to make the notice dismissable (using a hidden user preference).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Make beta notice more prominent\n\nThe current beta notice for VisualEditor is currently easy to miss.', 'While it uses a circled ""?""', 'and the text ""BETA"", it can blend in with the rest of the VisualEditor editing interface pretty easily (I only really noticed that there was any kind of warning today).', 'The notice that VisualEditor is beta software should be made more prominent.', 'James has suggested showing a more prominent notice for first-time VisualEditor users (presumably based on a cookie).', 'My preference is to make the notice dismissable (using a hidden user preference).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+254893,VisualEditor: Make beta notice more prominent,"We've now made a modal dialog pop up warning the user about the beta status of VisualEditor, and labelled VisualEditor as ""beta"" on its edit tab (and the edit section links that launch it).
+
+I'm going to presumptively (;-)) mark this as ""fixed"", but please re-open if you think we should do more.",task_subcomment,"['We\'ve now made a modal dialog pop up warning the user about the beta status of VisualEditor, and labelled VisualEditor as ""beta"" on its edit tab (and the edit section links that launch it).', 'I\'m going to presumptively (;-)) mark this as ""fixed"", but please re-open if you think we should do more.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+54355,"VisualEditor (and possibly other beta tools) need an exposed, easy-to-use on/off switch","One of the pain points we're seeing is that disabling VisualEditor is cumbersome. Even though there's now a user preference to disable the software, going to [[Special:Preferences]] is disruptive to user workflow.
+
+James and I discussed the possibility of adding a switch to the user interface to enable or disable VisualEditor.
+
+This switch might be located in the personal tools section, it might be a sidebar section, or it might be elsewhere. It should be viewable from ?action=view, ?action=edit, and ?veaction=edit.
+
+This switch might affect only VisualEditor or it might affect all ""beta"" features deployed to Wikimedia wikis.
+
+This switch will be available to both logged-in users and anonymous users.
+
+I believe this is a high priority bug to address.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54862",task_description,"[""VisualEditor (and possibly other beta tools) need an exposed, easy-to-use on/off switch\n\nOne of the pain points we're seeing is that disabling VisualEditor is cumbersome."", ""Even though there's now a user preference to disable the software, going to [[Special:Preferences]] is disruptive to user workflow."", 'James and I discussed the possibility of adding a switch to the user interface to enable or disable VisualEditor.', 'This switch might be located in the personal tools section, it might be a sidebar section, or it might be elsewhere.', 'It should be viewable from ?action=view, ?action=edit, and ?veaction=edit.', 'This switch might affect only VisualEditor or it might affect all ""beta"" features deployed to Wikimedia wikis.', 'This switch will be available to both logged-in users and anonymous users.', 'I believe this is a high priority bug to address.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+254366,"VisualEditor (and possibly other beta tools) need an exposed, easy-to-use on/off switch",BetaFeatures is in place for this now.,task_subcomment,['BetaFeatures is in place for this now.'],['SOLUTION DISCUSSION']
+254364,"VisualEditor (and possibly other beta tools) need an exposed, easy-to-use on/off switch","Hi MZMcBride, a desktop framework for beta testing features is already underway[1}, although it was originally envisioned for smaller experiments we can certainly think about the idea of leveraging it for larger pieces of functionality as well. 
+
+
+[1] http://www.mediawiki.org/wiki/Beta_Experiments",task_subcomment,"['Hi MZMcBride, a desktop framework for beta testing features is already underway[1}, although it was originally envisioned for smaller experiments we can certainly think about the idea of leveraging it for larger pieces of functionality as well.', '[1] URL']","['FUTURE PLAN', 'SOLUTION DISCUSSION']"
+54339,VisualEditor: Selection highlighting breaks if an inline alien wraps,"wrapped inline alien: incorrect highlighting in chromium
+
+If an inline alien gets word wrapped, then selecting it leads to incorrect highlighting.
+
+Reproducing: make a  ...  with enough content to word wrap. Select with the mouse (or use CTRL+A).
+
+In chromium, the highlighter erroneously draws a box enclosing the first character and the last (see first attachment).
+
+In firefox, the highlighter erroneously highlights to the end of the first line only (see second attachment).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11839}",task_description,"['VisualEditor: Selection highlighting breaks if an inline alien wraps\n\nwrapped inline alien: incorrect highlighting in chromium\n\nIf an inline alien gets word wrapped, then selecting it leads to incorrect highlighting.', 'Reproducing: make a  ...  with enough content to word wrap.', 'Select with the mouse (or use CTRL+A).', 'In chromium, the highlighter erroneously draws a box enclosing the first character and the last (see first attachment).', 'In firefox, the highlighter erroneously highlights to the end of the first line only (see second attachment).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11839}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253519,VisualEditor: Selection highlighting breaks if an inline alien wraps,*** Bug 67062 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 67062 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253516,VisualEditor: Selection highlighting breaks if an inline alien wraps,"Change 139805 merged by jenkins-bot:
+Shields are dead, long live getClientRects
+
+https://gerrit.wikimedia.org/r/139805",task_subcomment,"['Change 139805 merged by jenkins-bot:\nShields are dead, long live getClientRects\n\nGERRIT_URL']",['ACTION ON ISSUE']
+253513,VisualEditor: Selection highlighting breaks if an inline alien wraps,"Change 139805 had a related patch set uploaded by Esanders:
+Shields are dead, long live getClientRects
+
+https://gerrit.wikimedia.org/r/139805",task_subcomment,"['Change 139805 had a related patch set uploaded by Esanders:\nShields are dead, long live getClientRects\n\nGERRIT_URL']",['ACTION ON ISSUE']
+253509,VisualEditor: Selection highlighting breaks if an inline alien wraps,"Created attachment 13036
+wrapped inline alien: incorrect highlighting in firefox
+
+**Attached**: {F11840}",task_subcomment,['Created attachment 13036\nwrapped inline alien: incorrect highlighting in firefox\n\n**Attached**: {F11840}'],['INVESTIGATION AND EXPLORATION']
+253505,VisualEditor: Selection highlighting breaks if an inline alien wraps,"Created attachment 13035
+wrapped inline alien: incorrect highlighting in firefox
+
+//attachment wrapped-inline-alien-firefox.png ignored as obsolete//",task_subcomment,['Created attachment 13035\nwrapped inline alien: incorrect highlighting in firefox\n\n//attachment wrapped-inline-alien-firefox.png ignored as obsolete//'],['OBSERVED BUG BEHAVIOR']
+54326,VisualEditor: Toolbar overlaps top of page links,"Toolbar overlapping page head links Firefox 22/Linux/Monobook
+
+In Firefox 22 on Linux with Monobook skin (not tested in other combinations) sometimes the VE toolbar overlaps the page head links and tabs (userpage etc). See the screenshot.
+
+I haven't figured out how to reliably reproduce this but the following sequence /usually/ seems to work.
+1. Make one or more changes to a page in VE
+2. click on an element near the left or bottom of the window (to trigger bug 52317)
+3. open the save page dialog
+4. with the dialog still open, scroll to the very top and very bottom of the page
+5. close the save dialog without saving
+6. click a different element and repeat steps 3 to 5.
+7. scroll to the top of the screen and observe the position of the toolbar.
+
+If it doesn't work, try again from step 2.
+It doesn't always work, but actions like this do seem to trigger it more often than not. I don't know whether this is dependent on bug 52317 but it was in testing that bug that I found this one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52317
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52433
+
+**Attached**: {F11800}",task_description,"['VisualEditor: Toolbar overlaps top of page links\n\nToolbar overlapping page head links Firefox 22/Linux/Monobook\n\nIn Firefox 22 on Linux with Monobook skin (not tested in other combinations) sometimes the VE toolbar overlaps the page head links and tabs (userpage etc).', 'See the screenshot.', ""I haven't figured out how to reliably reproduce this but the following sequence /usually/ seems to work."", '1.', 'Make one or more changes to a page in VE\n2. click on an element near the left or bottom of the window (to trigger bug 52317)\n3. open the save page dialog\n4. with the dialog still open, scroll to the very top and very bottom of the page\n5. close the save dialog without saving\n6. click a different element and repeat steps 3 to 5.', '7. scroll to the top of the screen and observe the position of the toolbar.', ""If it doesn't work, try again from step 2."", ""It doesn't always work, but actions like this do seem to trigger it more often than not."", ""I don't know whether this is dependent on bug 52317 but it was in testing that bug that I found this one."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\n\n**Attached**: {F11800}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+252828,VisualEditor: Toolbar overlaps top of page links,"I guess https://bugzilla.wikimedia.org/show_bug.cgi?id=52433 is a duplicate then?
+Thanks.",task_subcomment,"['I guess URL is a duplicate then?', 'Thanks.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+252824,VisualEditor: Toolbar overlaps top of page links,"This was fixed last week (but not deployed yet, sorry) - merging with the other report.
+
+*** This bug has been marked as a duplicate of bug 52441 ***",task_subcomment,"['This was fixed last week (but not deployed yet, sorry) - merging with the other report.', '*** This bug has been marked as a duplicate of bug 52441 ***']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+252819,VisualEditor: Toolbar overlaps top of page links,"users Jay8g and Wouterstomp at en.wp have confirmed this happening in ""Monobook, FF 22, Windows 7"" and in Chrome (presumably on Windows) respectively.
+
+Jay8g provided a screenshot at https://en.wikipedia.org/wiki/File:VE_error-top_bar_over_toolbar.jpg",task_subcomment,"['users Jay8g and Wouterstomp at en.wp have confirmed this happening in ""Monobook, FF 22, Windows 7"" and in Chrome (presumably on Windows) respectively.', 'Jay8g provided a screenshot at URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252812,VisualEditor: Toolbar overlaps top of page links,"**sandrobt.wiki** wrote:
+
+It happen to me several tipe with MacOS 10.6 and Firexfox 22.0. 
+
+I didn't need to do all those step to get this bug, it was enough to scroll down, modify something and then go back up. It doens't always happen, but when it doesn't, it is usually enough to repeati the above operation to get the overlapping.",task_subcomment,"['**sandrobt.wiki** wrote:\n\nIt happen to me several tipe with MacOS 10.6 and Firexfox 22.0.', ""I didn't need to do all those step to get this bug, it was enough to scroll down, modify something and then go back up."", ""It doens't always happen, but when it doesn't, it is usually enough to repeati the above operation to get the overlapping.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252806,VisualEditor: Toolbar overlaps top of page links,"User CrypticC62 at en.wp has reproduced this in the following environments:
+
+
+    Firefox 22 / Monobook / Windows Vista: Reproduced (followed steps, occurred in one attempt)
+    Chrome 28 / Vector / Windows Vista: Found similar effect after step 3. See screenshot.
+
+
+The screenshot referred to is [[File:VE Chrome Toolbar Overlap.png]]",task_subcomment,"['User CrypticC62 at en.wp has reproduced this in the following environments:\n\n\n    Firefox 22 / Monobook / Windows Vista: Reproduced (followed steps, occurred in one attempt)\n    Chrome 28 / Vector / Windows Vista: Found similar effect after step 3.', 'See screenshot.', 'The screenshot referred to is [[File:VE Chrome Toolbar Overlap.png]]']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54276,VisualEditor: Localised tag description should link to content language documentation page,"When working with tags in edits, the tag can be localised in the page history (and recent changes, etc.). For example the history of [[mw:Localisation]][1] shows ""(Tag: VisualEditor)"" where ""tag"" links to [[mw:Special:Tags]] and ""VisualEditor"" links to [[mw:VisualEditor]].
+
+When viewing the same history in Dutch[2], this log line part displays as ""Label: Visuele tekstverwerker"", which in itself is a correct localisation for Dutch. When inspecting the links, the following observations are made:
+
+Observed:
+I. ""Label"" links to Special:Tags (expected)
+II. ""Visuele tekstverwerker"" links to ""Visuele tekstverwerker""
+
+Expected:
+III. ""Visuele tekstverwerker"" links to the documentation page in the content language (in this example ""VisualEditor""). Otherwise each wiki would be expected to have documentation in all usable user interface languages (or at least redirects) to avoid red links.
+
+[1] https://www.mediawiki.org/w/index.php?title=Localisation&action=history&uselang=en
+[2] https://www.mediawiki.org/w/index.php?title=Localisation&action=history&uselang=nl
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Localised tag description should link to content language documentation page\n\nWhen working with tags in edits, the tag can be localised in the page history (and recent changes, etc.).', 'For example the history of [[mw:Localisation]][1] shows ""(Tag: VisualEditor)"" where ""tag"" links to [[mw:Special:Tags]] and ""VisualEditor"" links to [[mw:VisualEditor]].', 'When viewing the same history in Dutch[2], this log line part displays as ""Label: Visuele tekstverwerker"", which in itself is a correct localisation for Dutch.', 'When inspecting the links, the following observations are made:\n\nObserved:\nI.', '""Label"" links to Special:Tags (expected)\nII.', '""Visuele tekstverwerker"" links to ""Visuele tekstverwerker""\n\nExpected:\nIII.', '""Visuele tekstverwerker"" links to the documentation page in the content language (in this example ""VisualEditor"").', 'Otherwise each wiki would be expected to have documentation in all usable user interface languages (or at least redirects) to avoid red links.', '[1] URL\n[2] URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'III.', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+249706,VisualEditor: Localised tag description should link to content language documentation page,Fixed; we'll deploy this later today.,task_subcomment,"[""Fixed; we'll deploy this later today.""]",['SOLUTION USAGE']
+249702,VisualEditor: Localised tag description should link to content language documentation page,"Change 76763 merged by jenkins-bot:
+Partial revert of gerrit 8ed6dfa5423 to avoid i18n mis-links
+
+https://gerrit.wikimedia.org/r/76763",task_subcomment,['Change 76763 merged by jenkins-bot:\nPartial revert of gerrit 8ed6dfa5423 to avoid i18n mis-links\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249699,VisualEditor: Localised tag description should link to content language documentation page,"Change 76763 had a related patch set uploaded by Jforrester:
+Partial revert of gerrit 8ed6dfa5423 to avoid i18n mis-links
+
+https://gerrit.wikimedia.org/r/76763",task_subcomment,['Change 76763 had a related patch set uploaded by Jforrester:\nPartial revert of gerrit 8ed6dfa5423 to avoid i18n mis-links\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+249694,VisualEditor: Localised tag description should link to content language documentation page,This was caused by gerrit 75559 - will partially-revert.,task_subcomment,['This was caused by gerrit 75559 - will partially-revert.'],['OBSERVED BUG BEHAVIOR']
+249689,VisualEditor: Localised tag description should link to content language documentation page,Right. It should probably be [[{{MediaWiki:visualeditor-descriptionpagelink}}|VisualEditor]].,task_subcomment,"['Right.', 'It should probably be [[{{MediaWiki:visualeditor-descriptionpagelink}}|VisualEditor]].']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+249683,VisualEditor: Localised tag description should link to content language documentation page,"[[mw:MediaWiki:Tag-visualeditor]] is using int: to fetch the visualeditor-descriptionpagelink, that should be done only for the content language. The link should be changed to {{MediaWiki:visualeditor-descriptionpagelink}}.
+
+That is a problem in VisualEditor, moving component",task_subcomment,"['[[mw:MediaWiki:Tag-visualeditor]] is using int: to fetch the visualeditor-descriptionpagelink, that should be done only for the content language.', 'The link should be changed to {{MediaWiki:visualeditor-descriptionpagelink}}.', 'That is a problem in VisualEditor, moving component']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+54271,VisualEditor: Editing a pasted template alters copy buffer. Displayed result differs from saved result.,"Mike Christie at en.wp reports that when performing the sequence: 
+1. copy template, 
+2. paste template, 
+3. edit parameter of pasted template, 
+4. paste template
+Step 4 pastes the template with the parameter values added in step 3 not the original ones.
+
+""To reproduce:
+
+1   Edit [[User:Mike Christie/Sandbox3]] in VE.
+2   Select the 13 C (produced with {{chem|13|C}} ) in the middle using the mouse; make sure to select some text on either side, since pasting a template doesn't work unless it's embedded in a string. The colons are there to make it easy to be sure you've got some text in addition to the template.
+3    Copy the selected text and then paste it at the end of the sentence.
+4    Click on the pasted template, click on the jigsaw piece, and change the 13 in parameter 1 to a 15. Apply changes.
+5    Now paste again at the end of the sentence. You'll see that the pasted template contains a 15, not a 13; so the copy/paste buffer was modified by the edit to the pasted template.""
+
+Another test case using a different template:
+1. Edit https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=566402676#Section_3:_tl.2C_etc_templates_added_in_VE in VE
+2. select ""tlp: {{tlp|as of|1999}} :"" and copy it to the clipboard
+3. paste the template elsewhere.
+4. edit the template you have just pasted (change parameter 2 to 2013) and apply the changes.
+5. paste the template again.
+Expected result: tlp: {{tlp|as of|1999}} :
+Actual result: tlp: {{tlp|as of|2013}} :
+
+Interestingly, pasting into a text editor gives the 1999 value as originally copied, not the 2013 value you get pasting into VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49396",task_description,"['VisualEditor: Editing a pasted template alters copy buffer.', 'Displayed result differs from saved result.', 'Mike Christie at en.wp reports that when performing the sequence: \n1. copy template, \n2. paste template, \n3. edit parameter of pasted template, \n4. paste template\nStep 4 pastes the template with the parameter values added in step 3 not the original ones.', '""To reproduce:\n\n1   Edit [[User:Mike Christie/Sandbox3]] in VE.', ""2   Select the 13 C (produced with {{chem|13|C}} ) in the middle using the mouse; make sure to select some text on either side, since pasting a template doesn't work unless it's embedded in a string."", ""The colons are there to make it easy to be sure you've got some text in addition to the template."", '3    Copy the selected text and then paste it at the end of the sentence.', '4    Click on the pasted template, click on the jigsaw piece, and change the 13 in parameter 1 to a 15.', 'Apply changes.', '5    Now paste again at the end of the sentence.', 'You\'ll see that the pasted template contains a 15, not a 13; so the copy/paste buffer was modified by the edit to the pasted template.""', 'Another test case using a different template:\n1.', 'Edit URL in VE\n2. select ""tlp: {{tlp|as of|1999}} :"" and copy it to the clipboard\n3. paste the template elsewhere.', '4. edit the template you have just pasted (change parameter 2 to 2013) and apply the changes.', '5. paste the template again.', 'Expected result: tlp: {{tlp|as of|1999}} :\nActual result: tlp: {{tlp|as of|2013}} :\n\nInterestingly, pasting into a text editor gives the 1999 value as originally copied, not the 2013 value you get pasting into VE.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+249423,VisualEditor: Editing a pasted template alters copy buffer. Displayed result differs from saved result.,"(In reply to comment #2)
+> This appears to be fixed in master.
+
+Confirmed - fixed in master, broken in wmf15. Marking as such.",task_subcomment,"['(In reply to comment #2)\nQUOTE\n\nConfirmed - fixed in master, broken in wmf15.', 'Marking as such.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249416,VisualEditor: Editing a pasted template alters copy buffer. Displayed result differs from saved result.,This appears to be fixed in master.,task_subcomment,['This appears to be fixed in master.'],['BUG REPRODUCTION']
+249410,VisualEditor: Editing a pasted template alters copy buffer. Displayed result differs from saved result.,"Mike Christie comments further:
+What is saved is not always what you see on screen.
+
+To reproduce in a sandbox:
+
+Add a template such as {{chem}}; I used 14C, created by {{chem|14|C}}. Put some text on either side of it so you can copy/paste it with text, since templates won't copy/paste successfully by themselves.
+
+Save that page, and edit again.
+
+
+Now copy the template and paste it twice, so you have something like this:
+-- 14C -- -- 14C -- -- 14C --
+
+Now edit the first pasted one -- the middle one in the example above -- so that it changes a parameter:
+
+-- 14C -- -- 12C -- -- 14C --
+
+Paste again; the pasted version will be 12C, which is bug 52271.
+
+a) I've seen two different behaviours for the next step. One is that you'll now see this:
+
+-- 14C -- -- 12C -- -- 14C -- -- 12C --
+
+but when you save the third one will be a 12 -- that is, it will have changed what you see on screen to be different in the saved file.
+
+b) The other behaviour I've seen is that after the final paste, all four of the templates show ""12"", not ""14"".",task_subcomment,"['Mike Christie comments further:\nWhat is saved is not always what you see on screen.', 'To reproduce in a sandbox:\n\nAdd a template such as {{chem}}; I used 14C, created by {{chem|14|C}}.', ""Put some text on either side of it so you can copy/paste it with text, since templates won't copy/paste successfully by themselves."", 'Save that page, and edit again.', ""Now copy the template and paste it twice, so you have something like this:\n-- 14C -- -- 14C -- -- 14C --\n\nNow edit the first pasted one -- the middle one in the example above -- so that it changes a parameter:\n\n-- 14C -- -- 12C -- -- 14C --\n\nPaste again; the pasted version will be 12C, which is bug 52271.\n\na) I've seen two different behaviours for the next step."", ""One is that you'll now see this:\n\n-- 14C -- -- 12C -- -- 14C -- -- 12C --\n\nbut when you save the third one will be a 12 -- that is, it will have changed what you see on screen to be different in the saved file."", 'b) The other behaviour I\'ve seen is that after the final paste, all four of the templates show ""12"", not ""14"".']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+54256,"VisualEditor: Link widget in a slug fails with ""No class registered by that name: undefined""","ve.Factory.prototype.create throws an Error, ""No class registered by that name: undefined"" when using the link widget.  It can be reproduced with:
+
+1. Start with blank document
+2. Hit Ctrl-K
+3. Type some page name that doesn't exist
+4. Hit escape twice.
+
+This leaves a broken widget that takes several clicks (not sure the exact pattern here) to clear.
+
+5. Try to open the link widget again.  It won't be possible, either with Ctrl+K or the button.
+
+This is live on English Wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50446",task_description,"['VisualEditor: Link widget in a slug fails with ""No class registered by that name: undefined""\n\nve.Factory.prototype.create throws an Error, ""No class registered by that name: undefined"" when using the link widget.', 'It can be reproduced with:\n\n1.', 'Start with blank document\n2.', 'Hit Ctrl-K\n3.', ""Type some page name that doesn't exist\n4."", 'Hit escape twice.', 'This leaves a broken widget that takes several clicks (not sure the exact pattern here) to clear.', '5.', 'Try to open the link widget again.', ""It won't be possible, either with Ctrl+K or the button."", 'This is live on English Wikipedia.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248587,"VisualEditor: Link widget in a slug fails with ""No class registered by that name: undefined""",This seems to be fixed by https://gerrit.wikimedia.org/r/#/c/81437/,task_subcomment,['This seems to be fixed by URL'],['BUG REPRODUCTION']
+248582,"VisualEditor: Link widget in a slug fails with ""No class registered by that name: undefined""","It also copies the page name from the link widget to the document as apparent plain text, even though you exit out with double-ESC.",task_subcomment,"['It also copies the page name from the link widget to the document as apparent plain text, even though you exit out with double-ESC.']",['OBSERVED BUG BEHAVIOR']
+248577,"VisualEditor: Link widget in a slug fails with ""No class registered by that name: undefined""","Created attachment 13014
+Broken link widget after pressing Ctrl-K on empty page, then exiting
+
+**Attached**: {F11679}",task_subcomment,"['Created attachment 13014\nBroken link widget after pressing Ctrl-K on empty page, then exiting\n\n**Attached**: {F11679}']",['BUG REPRODUCTION']
+54238,VisualEditor: categories being duplicated,"See https://sv.wikipedia.org/w/index.php?title=Tjeckiens_president&diff=22846804&oldid=21540497 and https://pl.wikipedia.org/w/index.php?title=Mi%C4%99dzynarodowa_Federacja_Tenisa_Sto%C5%82owego&curid=407381&diff=37148333&oldid=37118048 - no duplication (ahahaha) steps of which I'm aware, I'm afraid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54169",task_description,"[""VisualEditor: categories being duplicated\n\nSee URL and URL - no duplication (ahahaha) steps of which I'm aware, I'm afraid."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247579,VisualEditor: categories being duplicated,Going out in a little while.,task_subcomment,['Going out in a little while.'],['INVESTIGATION AND EXPLORATION']
+247574,VisualEditor: categories being duplicated,"Change 76665 merged by jenkins-bot:
+Don't duplicate categories when unlisting
+
+https://gerrit.wikimedia.org/r/76665",task_subcomment,"[""Change 76665 merged by jenkins-bot:\nDon't duplicate categories when unlisting\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+247569,VisualEditor: categories being duplicated,"Change 76665 had a related patch set uploaded by Catrope:
+Don't duplicate categories when unlisting
+
+https://gerrit.wikimedia.org/r/76665",task_subcomment,"[""Change 76665 had a related patch set uploaded by Catrope:\nDon't duplicate categories when unlisting\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+247565,VisualEditor: categories being duplicated,"Isolated test case:
+
+1. Create a page with ""*Foo\n[[Category:Bar]]\n[[Category:Baz]]""
+2. Edit the page in VE
+3. Move the cursor to the end of the list item and press enter. This creates a new list item and puts the cursor in it
+4. Click the list button (the one that's depressed) in the toolbar. This causes the list item to go away and makes the cursor jump out of the list.
+5. Review changes. The diff will duplicate both of the categories at the beginning of the page, preceded by a newline.",task_subcomment,"['Isolated test case:\n\n1.', 'Create a page with ""*Foo\\n[[Category:Bar]]\\n[[Category:Baz]]""\n2.', 'Edit the page in VE\n3.', 'Move the cursor to the end of the list item and press enter.', 'This creates a new list item and puts the cursor in it\n4.', ""Click the list button (the one that's depressed) in the toolbar."", 'This causes the list item to go away and makes the cursor jump out of the list.', '5. Review changes.', 'The diff will duplicate both of the categories at the beginning of the page, preceded by a newline.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+247561,VisualEditor: categories being duplicated,http://youtu.be/1rmp5rTDPOM,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+54228,VisualEditor: VE will not save multiple consecutive references,"Following a report of the issue by a user, I attempted to add multiple consecutive references. I began with bare URLs and started with 6. You can see that VE thinks it is going okay (http://en.wikipedia.org/wiki/File:VEmultiref.png), but when you save it only saves one (http://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=566304458&oldid=566304152)
+
+I tested it all the way down to two.
+
+In case it was an issue with bare refs, I tried it using citation templates, and it would also not save two in a row. It still only saved one:
+http://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=566306613&oldid=566306049
+
+I'm using Chrome, Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: VE will not save multiple consecutive references\n\nFollowing a report of the issue by a user, I attempted to add multiple consecutive references.', 'I began with bare URLs and started with 6.', 'You can see that VE thinks it is going okay (URL but when you save it only saves one (URL\n\nI tested it all the way down to two.', 'In case it was an issue with bare refs, I tried it using citation templates, and it would also not save two in a row.', ""It still only saved one:\nURL\n\nI'm using Chrome, Windows 7."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247096,VisualEditor: VE will not save multiple consecutive references,"(In reply to comment #6)
+> Users are reporting that VE is still not saving multiple references:
+
+Unfortunately, this is ""again"", not ""still"", and is caused by bug 53434 in Parsoid, I think. :-( Marking this as ""fixed"" but highlighting on that one how urgent this is. Sorry for the disruption.",task_subcomment,"['(In reply to comment #6)\nQUOTE\n\nUnfortunately, this is ""again"", not ""still"", and is caused by bug 53434 in Parsoid, I think.', ':-( Marking this as ""fixed"" but highlighting on that one how urgent this is.', 'Sorry for the disruption.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+247090,VisualEditor: VE will not save multiple consecutive references,"Users are reporting that VE is still not saving multiple references:
+
+Reported today by The Devil's Advocate
+if I add multiple citations to back a statement, the Visual Editor only saves the first citation I added. This happened once when I added three citations to back a claim and had to add each one individually over the course of three edits and again just now when I had to add a second citation after it didn't get saved. Multiple citations can be added if they are separate as I had added a citation for another statement in the same edit and it was saved.
+
+Reported on the 22nd by Sue Gardner
+Last night I created a new article with multiple references, and when I saved the page many of the references disappeared and some I think had jumped around. (I didn't save-as-I-went -- I wrote the whole thing and saved once, at the end.) I can't describe exactly what happened, but here's a diff: [1] the latest revision [2] is roughly what I was aiming to do, and the earlier revision [3] is what I actually achieved. (Ignore the missing reflist: I just hadn't gotten around to figuring out how to add it in VE yet, so I did it afterwards in wiki syntax.)
+
+So, in my initial VE save, it looks like references #5, 6 & 7 disappeared as did #14 and 15. (Numbers taken from the latest revision.) This suggests to me there's a problem with VE saving multiple adjacent references -- when there are multiples adjacent, it seems to save only the first. I think also some references jumped around, but I'm not 100% sure about that.
+
+[1] https://en.wikipedia.org/w/index.php?title=Mansplaining&diff=569638597&oldid=569526861
+[2] https://en.wikipedia.org/w/index.php?title=Mansplaining&oldid=569638597
+[3] https://en.wikipedia.org/w/index.php?title=Mansplaining&oldid=569526861",task_subcomment,"[""Users are reporting that VE is still not saving multiple references:\n\nReported today by The Devil's Advocate\nif I add multiple citations to back a statement, the Visual Editor only saves the first citation I added."", ""This happened once when I added three citations to back a claim and had to add each one individually over the course of three edits and again just now when I had to add a second citation after it didn't get saved."", 'Multiple citations can be added if they are separate as I had added a citation for another statement in the same edit and it was saved.', 'Reported on the 22nd by Sue Gardner\nLast night I created a new article with multiple references, and when I saved the page many of the references disappeared and some I think had jumped around.', ""(I didn't save-as-I-went -- I wrote the whole thing and saved once, at the end.)"", ""I can't describe exactly what happened, but here's a diff: [1] the latest revision [2] is roughly what I was aiming to do, and the earlier revision [3] is what I actually achieved."", ""(Ignore the missing reflist: I just hadn't gotten around to figuring out how to add it in VE yet, so I did it afterwards in wiki syntax.)"", 'So, in my initial VE save, it looks like references #5, 6 & 7 disappeared as did #14 and 15.', '(Numbers taken from the latest revision.)', ""This suggests to me there's a problem with VE saving multiple adjacent references -- when there are multiples adjacent, it seems to save only the first."", ""I think also some references jumped around, but I'm not 100% sure about that."", '[1] URL\n[2] URL\n[3] URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+247083,VisualEditor: VE will not save multiple consecutive references,*** Bug 52269 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52269 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247078,VisualEditor: VE will not save multiple consecutive references,Fixed and will get deployed in a little while.,task_subcomment,['Fixed and will get deployed in a little while.'],['SOLUTION USAGE']
+247072,VisualEditor: VE will not save multiple consecutive references,"Change 76836 merged by jenkins-bot:
+Remove the DM 'about' attribute from references and reference lists
+
+https://gerrit.wikimedia.org/r/76836",task_subcomment,"[""Change 76836 merged by jenkins-bot:\nRemove the DM 'about' attribute from references and reference lists\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+247064,VisualEditor: VE will not save multiple consecutive references,"Change 76836 had a related patch set uploaded by Catrope:
+Remove the DM 'about' attribute from references and reference lists
+
+https://gerrit.wikimedia.org/r/76836",task_subcomment,"[""Change 76836 had a related patch set uploaded by Catrope:\nRemove the DM 'about' attribute from references and reference lists\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+247055,VisualEditor: VE will not save multiple consecutive references,"This happens because we send Parsoid something like
+
+
+
+which then gets about-grouped. We need to just drop the about attribute if we don't have it.
+
+Ironically we've had breakage in the other direction before, where Parsoid output multiple adjacent images with about=""null"". Karma's a bitch :)",task_subcomment,"['This happens because we send Parsoid something like\n\n\n\nwhich then gets about-grouped.', ""We need to just drop the about attribute if we don't have it."", 'Ironically we\'ve had breakage in the other direction before, where Parsoid output multiple adjacent images with about=""null"".', ""Karma's a bitch :)""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+54189,VisualEditor: Using bold button on partially bolded selection causes double-bolding,"+++ This bug was initially created as a clone of Bug #50170 +++
+
+1. Edit [[mw:VisualEditor:Sfioj]] in VE
+2. Make a selection such as
+
+     These wor[ds are ve]ry bold
+
+3. Click the ""Bold"" button on the toolbar
+
+The selected text goes extra-bold, in Firefox 22. 
+
+I should mention that in my case, the font is Arial, which has an extra bold ""Arial-Black"" variant.
+
+Basically the same as 50170 except that this is narrower.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Using bold button on partially bolded selection causes double-bolding\n\n+++ This bug was initially created as a clone of Bug #50170 +++\n\n1.', 'Edit [[mw:VisualEditor:Sfioj]] in VE\n2.', 'Make a selection such as\n\n     These wor[ds are ve]ry bold\n\n3.', 'Click the ""Bold"" button on the toolbar\n\nThe selected text goes extra-bold, in Firefox 22.', 'I should mention that in my case, the font is Arial, which has an extra bold ""Arial-Black"" variant.', 'Basically the same as 50170 except that this is narrower.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244588,VisualEditor: Using bold button on partially bolded selection causes double-bolding,"Change 119282 merged by jenkins-bot:
+Prevent comparable annotations from being applied twice
+
+https://gerrit.wikimedia.org/r/119282",task_subcomment,['Change 119282 merged by jenkins-bot:\nPrevent comparable annotations from being applied twice\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244581,VisualEditor: Using bold button on partially bolded selection causes double-bolding,"Change 119282 had a related patch set uploaded by Esanders:
+Prevent comparable annotations from being applied twice
+
+https://gerrit.wikimedia.org/r/119282",task_subcomment,['Change 119282 had a related patch set uploaded by Esanders:\nPrevent comparable annotations from being applied twice\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244574,VisualEditor: Using bold button on partially bolded selection causes double-bolding,"No it isn't: if you follow the STR, you will still see this bug on Firefox 25.",task_subcomment,"[""No it isn't: if you follow the STR, you will still see this bug on Firefox 25.""]",['OBSERVED BUG BEHAVIOR']
+244567,VisualEditor: Using bold button on partially bolded selection causes double-bolding,"This was the same bug as bug 50170, however; merging.
+
+*** This bug has been marked as a duplicate of bug 50170 ***",task_subcomment,"['This was the same bug as bug 50170, however; merging.', '*** This bug has been marked as a duplicate of bug 50170 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+244557,VisualEditor: Using bold button on partially bolded selection causes double-bolding,"(In reply to comment #0)
+> this is narrower.
+
+A narrower set of circumstances, not a narrower font!",task_subcomment,"['(In reply to comment #0)\nQUOTE\n\nA narrower set of circumstances, not a narrower font!']",['SOLUTION DISCUSSION']
+54185,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"**Author:** `jonathan_haas`
+
+**Description:**
+To reproduce:
+
+Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit
+
+1. Click on infobox
+2. Hit the ""a"" key
+3. Hit ctrl+z
+
+Repeat steps 1-3 as long as necessary (about 1-6 times)
+
+Current result:
+
+Instead of being restored on ctrl+z, sometimes the infobox is replaced by a pawn.
+The article begins with ""♙The Binding of Isaac"" then.
+
+Also, ctrl+z should probably also restore the selection, so I think it's another bugh that you have to repeat step 1 every time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52113",task_description,"['VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙)\n\n**Author:** CODE\n\n**Description:**\nTo reproduce:\n\nGoto URL\n\n1.', 'Click on infobox\n2.', 'Hit the ""a"" key\n3.', 'Hit ctrl+z\n\nRepeat steps 1-3 as long as necessary (about 1-6 times)\n\nCurrent result:\n\nInstead of being restored on ctrl+z, sometimes the infobox is replaced by a pawn.', 'The article begins with ""♙The Binding of Isaac"" then.', ""Also, ctrl+z should probably also restore the selection, so I think it's another bugh that you have to repeat step 1 every time."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'MOTIVATION', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+244354,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"Pressing anything other than delete no longer does anything for me, which seems sensible.",task_subcomment,"['Pressing anything other than delete no longer does anything for me, which seems sensible.']",['OBSERVED BUG BEHAVIOR']
+244347,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),Bumping; this is happening 100% of the time now.,task_subcomment,['Bumping; this is happening 100% of the time now.'],['OBSERVED BUG BEHAVIOR']
+244340,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"**jonathan.haas** wrote:
+
+Using the current Firefox 27 alpha (Aurora build), the problem seems to be much worse, as the pawn appears reliably in step 2 just after pressing ""a"". Maybe it's a different issue, but maybe it helps debugging this one.
+
+TBH, this pawn stuff seems to be very weird and unstable to me. Why can they appear in the first place?",task_subcomment,"['**jonathan.haas** wrote:\n\nUsing the current Firefox 27 alpha (Aurora build), the problem seems to be much worse, as the pawn appears reliably in step 2 just after pressing ""a"".', ""Maybe it's a different issue, but maybe it helps debugging this one."", 'TBH, this pawn stuff seems to be very weird and unstable to me.', 'Why can they appear in the first place?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244333,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"I can occasionally reproduce this in Chrome and Firefox, but not reliably (roughly 1 in 10 replacements). Race condition on the change stack or something?",task_subcomment,"['I can occasionally reproduce this in Chrome and Firefox, but not reliably (roughly 1 in 10 replacements).', 'Race condition on the change stack or something?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244325,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"**p.selitskas** wrote:
+
+I could reproduce this with cyrillic letters in be-x-old.wikipedia.org, at least a few weeks ago.",task_subcomment,"['**p.selitskas** wrote:\n\nI could reproduce this with cyrillic letters in be-x-old.wikipedia.org, at least a few weeks ago.']",['OBSERVED BUG BEHAVIOR']
+244318,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),I can't reproduce after about 20 tries in Firefox 23/Linux/Monobook,task_subcomment,"[""I can't reproduce after about 20 tries in Firefox 23/Linux/Monobook""]",['OBSERVED BUG BEHAVIOR']
+244313,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"**jonathan_haas** wrote:
+
+Screenshot
+
+Also managed to reproduce in Chrome 28.
+
+No error in javascript console in both browsers.
+
+**Attached**: {F11523}",task_subcomment,"['**jonathan_haas** wrote:\n\nScreenshot\n\nAlso managed to reproduce in Chrome 28.', 'No error in javascript console in both browsers.', '**Attached**: {F11523}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244307,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"**jonathan_haas** wrote:
+
+I still can (FF23). Just managed on first try.",task_subcomment,"['**jonathan_haas** wrote:\n\nI still can (FF23).', 'Just managed on first try.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+244301,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),Can't reproduce in Chrome or FF,task_subcomment,"[""Can't reproduce in Chrome or FF""]",['OBSERVED BUG BEHAVIOR']
+244295,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),This is possibly bug 51532,task_subcomment,['This is possibly bug 51532'],['OBSERVED BUG BEHAVIOR']
+244291,VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),Reproduced; I havent looked to see if this scenario has been reported already.,task_subcomment,['Reproduced; I havent looked to see if this scenario has been reported already.'],['OBSERVED BUG BEHAVIOR']
+54181,"Be able to add or remove tables, table rows and table columns","**Author:** `jonathan_haas`
+
+**Description:**
+I can't find a possible way to add or edit tables, except changing the content of cells.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52641",task_description,"[""Be able to add or remove tables, table rows and table columns\n\n**Author:** CODE\n\n**Description:**\nI can't find a possible way to add or edit tables, except changing the content of cells."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+244077,"Be able to add or remove tables, table rows and table columns",post-deploy testing in test2 - VisualEditor has added functiona lity to insert/remove tables and modify tables - insert columns and rows  in tables.,task_subcomment,['post-deploy testing in test2 - VisualEditor has added functiona lity to insert/remove tables and modify tables - insert columns and rows  in tables.'],['INVESTIGATION AND EXPLORATION']
+244074,"Be able to add or remove tables, table rows and table columns",Done in gerrit 159310 and related stack.,task_subcomment,['Done in gerrit 159310 and related stack.'],['SOLUTION DISCUSSION']
+244068,"Be able to add or remove tables, table rows and table columns","Swedish Wikipedian Sebbes333 [1] reports here [2] that he ""would like to insert a new column in a 2D table, [however] do not think it will go into beta editor yet."" 
+
+[1]
+https://sv.wikipedia.org/wiki/Anv%C3%A4ndare:Sebbes333
+
+[2]
+https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#Infoga_ny_kolumn_i_en_2D_tabell_i_beta_redigeraren.",task_subcomment,"['Swedish Wikipedian Sebbes333 [1] reports here [2] that he ""would like to insert a new column in a 2D table, [however] do not think it will go into beta editor yet.""', '[1]\nURL\n\n[2]\nURL']","['MOTIVATION', 'SOLUTION DISCUSSION']"
+244063,"Be able to add or remove tables, table rows and table columns",*** Bug 53325 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53325 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244058,"Be able to add or remove tables, table rows and table columns","Ok, will move it elsewhere. Thanks.",task_subcomment,"['Ok, will move it elsewhere.', 'Thanks.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+244054,"Be able to add or remove tables, table rows and table columns","**jonathan_haas** wrote:
+
+(In reply to comment #2)
+> < of a
+> table with an empty cell, VE seemed to move the two pipes inside the cell on
+> the left, and the empty cell didn't show. -- t numbermaniac c 03:02, 6 August
+> 2013 (UTC)>> (first line of the Redirect table in
+> http://en.wikipedia.org/wiki/User:Numbermaniac?veaction=edit ).
+
+Confirmed, but I think this deserves another, separate bug report.",task_subcomment,"['**jonathan_haas** wrote:\n\n(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nConfirmed, but I think this deserves another, separate bug report.']",['INVESTIGATION AND EXPLORATION']
+244051,"Be able to add or remove tables, table rows and table columns","<> (first line of the Redirect table in http://en.wikipedia.org/wiki/User:Numbermaniac?veaction=edit ).",task_subcomment,"[""<> (first line of the Redirect table in URL ).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244047,"Be able to add or remove tables, table rows and table columns",I couldnt find another bug for creating tables.,task_subcomment,['I couldnt find another bug for creating tables.'],['OBSERVED BUG BEHAVIOR']
+54175,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings","screenshot
+
+When using German language (on German and English Wikipedia, but also likely everywhere else), the layout of the minor changes & watchlist checkboxes on the save dialog is not appropriate when viewed in Firefox.  Attached is Vector; same problem exists in Monobook.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52176
+
+//attachment VE_de_Firefox_save_dialog .png ignored as obsolete//",task_description,"[""VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings\n\nscreenshot\n\nWhen using German language (on German and English Wikipedia, but also likely everywhere else), the layout of the minor changes & watchlist checkboxes on the save dialog is not appropriate when viewed in Firefox."", 'Attached is Vector; same problem exists in Monobook.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL\n\n//attachment VE_de_Firefox_save_dialog .png ignored as obsolete//']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243771,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings",The line-height is too large and the second line is offset to left.,task_subcomment,['The line-height is too large and the second line is offset to left.'],['OBSERVED BUG BEHAVIOR']
+243764,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings",Reset as FIXED. The screenshot you attach looks normal - could you annotate the parts you think aren't correct? Probably as a new bug…,task_subcomment,"['Reset as FIXED.', ""The screenshot you attach looks normal - could you annotate the parts you think aren't correct?"", 'Probably as a new bug…']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243757,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings","Created attachment 13820
+Screenshot, 2013-11-17 (in Polish)
+
+This appears to still not fixed :( I'm adding an up-to-date screenshot.
+
+**Attached**: {F11479}",task_subcomment,"[""Created attachment 13820\nScreenshot, 2013-11-17 (in Polish)\n\nThis appears to still not fixed :( I'm adding an up-to-date screenshot."", '**Attached**: {F11479}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243750,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings","The fix for this is now merged and will be deployed on Thursday 10 October to MediaWiki.org, and to Wikipedias on Thursday 17 October.",task_subcomment,"['The fix for this is now merged and will be deployed on Thursday 10 October to MediaWiki.org, and to Wikipedias on Thursday 17 October.']",['SOLUTION USAGE']
+243742,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings","Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",task_subcomment,['Change 81876 merged by jenkins-bot:\nMake the save dialog an actual dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+243735,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings",*** Bug 54802 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54802 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243729,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings","Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",task_subcomment,['Change 81876 had a related patch set uploaded by Jforrester:\nMake the save dialog an actual dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+243722,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings","Created attachment 13242
+pl.wp screenshot
+
+It breaks particularly badly on wikis with FlaggedRevs.
+
+//attachment 2013-09-04 22_07_50-Edytujesz Rafał Kosik - Wikipedia - Opera.png ignored as obsolete//",task_subcomment,"['Created attachment 13242\npl.wp screenshot\n\nIt breaks particularly badly on wikis with FlaggedRevs.', '//attachment 2013-09-04 22_07_50-Edytujesz Rafał Kosik - Wikipedia - Opera.png ignored as obsolete//']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243716,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings",*** Bug 52176 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52176 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243710,"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings","Created attachment 12997
+Windows 7 screenshot
+
+Font is obviously a contributing factor here; on Windows the layout problem almost disappears.
+
+//attachment VE_de_save_dialog_checkboxes_Firefox_on_Windows.png ignored as obsolete//",task_subcomment,"['Created attachment 12997\nWindows 7 screenshot\n\nFont is obviously a contributing factor here; on Windows the layout problem almost disappears.', '//attachment VE_de_save_dialog_checkboxes_Firefox_on_Windows.png ignored as obsolete//']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54171,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,"**Author:** `jonathan_haas`
+
+**Description:**
+To reproduce:
+
+1. Goto http://de.wikipedia.org/wiki/Hint
+2. Open visual editor
+3. Select all (ctrl+a)
+4. Enter ""foobar"" (without quotation marks)
+
+Expected: 
+
+- page contains ""foobar""
+
+Actual:
+
+- page contains
+
+ffoffoffoffoofbar|foffoffof
+foo
+
+
+| = cursor position
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox\n\n**Author:** CODE\n\n**Description:**\nTo reproduce:\n\n1.', 'Goto URL\n2.', 'Open visual editor\n3.', 'Select all (ctrl+a)\n4.', 'Enter ""foobar"" (without quotation marks)\n\nExpected: \n\n- page contains ""foobar""\n\nActual:\n\n- page contains\n\nffoffoffoffoofbar|foffoffof\nfoo\n\n\n| = cursor position\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+243512,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Confirmed now fixed.,task_subcomment,['Confirmed now fixed.'],['BUG REPRODUCTION']
+243505,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,WFM in Firefox,task_subcomment,['WFM in Firefox'],['OBSERVED BUG BEHAVIOR']
+243501,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,"(In reply to Jonathan Haas from comment #4)
+> The underlying bug doesn't seem to be fixed.
+> 
+> To reproduce (Linux, Firefox):
+> 
+> 1. Copy the Text ""Foundation"" (without quotation marks) to the clipboard
+> 2. Open: https://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit
+> 3. Select all (Ctrl+A)
+> 4. Paste Clipboard (Ctrl+V)
+> 5. Type ""foobar""
+> 
+> Expected result:
+> 
+> Page contains ""Foundationfoobar""
+> 
+> Actual result:
+> 
+> Page contains:
+> 
+> obar|
+> 
+> oo
+> 
+> fo
+> Foundationf
+
+
+Interesting. This worked for me when I tested it, but doesn't now; perhaps it's content-driven (as well as being a symptom of how broken bits of Firefox are).",task_subcomment,"['(In reply to Jonathan Haas from comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n\nInteresting.', ""This worked for me when I tested it, but doesn't now; perhaps it's content-driven (as well as being a symptom of how broken bits of Firefox are).""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+243495,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,"**jonathan_haas** wrote:
+
+The underlying bug doesn't seem to be fixed.
+
+To reproduce (Linux, Firefox):
+
+1. Copy the Text ""Foundation"" (without quotation marks) to the clipboard
+2. Open: https://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit
+3. Select all (Ctrl+A)
+4. Paste Clipboard (Ctrl+V)
+5. Type ""foobar""
+
+Expected result:
+
+Page contains ""Foundationfoobar""
+
+Actual result:
+
+Page contains:
+
+obar|
+
+oo
+
+fo
+Foundationf",task_subcomment,"[""**jonathan_haas** wrote:\n\nThe underlying bug doesn't seem to be fixed."", 'To reproduce (Linux, Firefox):\n\n1.', 'Copy the Text ""Foundation"" (without quotation marks) to the clipboard\n2.', 'Open: URL\n3.', 'Select all (Ctrl+A)\n4.', 'Paste Clipboard (Ctrl+V)\n5.', 'Type ""foobar""\n\nExpected result:\n\nPage contains ""Foundationfoobar""\n\nActual result:\n\nPage contains:\n\nobar|\n\noo\n\nfo\nFoundationf']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+243488,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Was fixed by something Ed did a while ago.,task_subcomment,['Was fixed by something Ed did a while ago.'],['SOLUTION DISCUSSION']
+243481,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,"**jonathan_haas** wrote:
+
+Note that the above result was created using Firefox 23.
+
+Chrome 28 produces the following (equally wrong) result:
+
+fbar|ofo
+o
+foo",task_subcomment,"['**jonathan_haas** wrote:\n\nNote that the above result was created using Firefox 23.', 'Chrome 28 produces the following (equally wrong) result:\n\nfbar|ofo\no\nfoo']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243475,VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Reproduced.,task_subcomment,['Reproduced.'],['OBSERVED BUG BEHAVIOR']
+54160,VisualEditor: [Regression] Reference list not being updated during editing session,"When a reference is edited, the updated version will not appear in the reference list when attempting to insert an existing reference. Instead, the reference that will appear in the reference list will be the reference as it was when the page editing started.
+
+To reproduce, go to a page with references. Edit one of the references, and don't save. Then, do as if you wanted to insert an existing reference and look at the list of existing references. The edit to the reference you have edited will not appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: [Regression] Reference list not being updated during editing session\n\nWhen a reference is edited, the updated version will not appear in the reference list when attempting to insert an existing reference.', 'Instead, the reference that will appear in the reference list will be the reference as it was when the page editing started.', 'To reproduce, go to a page with references.', ""Edit one of the references, and don't save."", 'Then, do as if you wanted to insert an existing reference and look at the list of existing references.', 'The edit to the reference you have edited will not appear.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242786,VisualEditor: [Regression] Reference list not being updated during editing session,"@Cainamarques, please see https://bugzilla.wikimedia.org/show_bug.cgi?id=57209 and comment there if you really manage to properly see and choose from the list of reusable references. Thanks.",task_subcomment,"['SCREEN_NAME, please see URL and comment there if you really manage to properly see and choose from the list of reusable references.', 'Thanks.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+242781,VisualEditor: [Regression] Reference list not being updated during editing session,"This bug seems to be fixed, I can perfectly edit and reuse references using Firefox 25.0",task_subcomment,"['This bug seems to be fixed, I can perfectly edit and reuse references using Firefox 25.0']",['OBSERVED BUG BEHAVIOR']
+242778,VisualEditor: [Regression] Reference list not being updated during editing session,(Wondering if this is related to https://bugzilla.wikimedia.org/show_bug.cgi?id=51689.),task_subcomment,['(Wondering if this is related to URL'],['OBSERVED BUG BEHAVIOR']
+242776,VisualEditor: [Regression] Reference list not being updated during editing session,"Likewise, the reference list is not updated if I add a new reference to the page, thus being unable to reuse it in the current edit.",task_subcomment,"['Likewise, the reference list is not updated if I add a new reference to the page, thus being unable to reuse it in the current edit.']",['OBSERVED BUG BEHAVIOR']
+242774,VisualEditor: [Regression] Reference list not being updated during editing session,"Confirmed.  Use existing reference shows original references, before they were modified.",task_subcomment,"['Confirmed.', 'Use existing reference shows original references, before they were modified.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+54159,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","When an existing reference is inserted, it is put at the start of the paragraph the cursor is currently in, regardless of where it is in that paragraph. This has happened to me while I was attempting to use in a paragraph a reference that was already used in that paragraph: the reference got inserted at the start of the paragraph and I was not able to move it. I tried again some times but it still did not work and I had to use the wikitext editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is\n\nWhen an existing reference is inserted, it is put at the start of the paragraph the cursor is currently in, regardless of where it is in that paragraph.', 'This has happened to me while I was attempting to use in a paragraph a reference that was already used in that paragraph: the reference got inserted at the start of the paragraph and I was not able to move it.', 'I tried again some times but it still did not work and I had to use the wikitext editor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242730,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is",*** Bug 52594 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52594 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242728,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","Should now be fixed; we will deploy this earlier than scheduled, later today.",task_subcomment,"['Should now be fixed; we will deploy this earlier than scheduled, later today.']",['ACTION ON ISSUE']
+242726,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","Change 80056 merged by jenkins-bot:
+Preserve selection when inserting references
+
+https://gerrit.wikimedia.org/r/80056",task_subcomment,['Change 80056 merged by jenkins-bot:\nPreserve selection when inserting references\n\nGERRIT_URL'],['ACTION ON ISSUE']
+242723,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","Change 80056 had a related patch set uploaded by Esanders:
+Preserve selection when inserting references
+
+https://gerrit.wikimedia.org/r/80056",task_subcomment,['Change 80056 had a related patch set uploaded by Esanders:\nPreserve selection when inserting references\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+242717,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","AFAICT this only happens in the first paragraph (and only in Firefox).
+
+This is throwing an error in Rangy:
+
+  TypeError: sel.nativeSelection is null
+  sel._ranges.length = sel.rangeCount = sel.nativeSelection.rangeCount;
+
+… but for some reason I can't get Firebug to give me a trace.",task_subcomment,"['AFAICT this only happens in the first paragraph (and only in Firefox).', ""This is throwing an error in Rangy:\n\n  TypeError: sel.nativeSelection is null\n  sel._ranges.length = sel.rangeCount = sel.nativeSelection.rangeCount;\n\n… but for some reason I can't get Firebug to give me a trace.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242711,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","At en.wp WhatamIdoing reports:
+I was just trying to add the ref to the other sentences. It misplaced two copies at the start of the paragraph when I wanted one at the end of the first line of the first paragraph (perhaps I clicked too high on the top line of the edit window?). After I removed those, I couldn't add any more. Clicking the ref button did nothing."" He gives the following URL:
+https://en.wikipedia.org/w/index.php?title=Swing_%28seat%29&diff=568557479&oldid=568556853",task_subcomment,"['At en.wp WhatamIdoing reports:\nI was just trying to add the ref to the other sentences.', 'It misplaced two copies at the start of the paragraph when I wanted one at the end of the first line of the first paragraph (perhaps I clicked too high on the top line of the edit window?).', ""After I removed those, I couldn't add any more."", 'Clicking the ref button did nothing.""', 'He gives the following URL:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242707,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","I have done similar manipulations in other articles at some moments, and it seems it sometimes works and sometimes doesn't. There are many things that are strange concerning how the existing references system works.
+
+Regardless, I set up a sandbox page on my user space, added a reference and then tried to re-use that reference using the VisualEditor. The reference was added at the start of the paragraph. I've done some more experimenting, and I've written steps to reproduce the bug; the first block reproduces the bug and the following blocks are other experimentations that give more strange results.
+
+1. Go to [[User:Rastus Vernon/VisualEditor Sandbox]].
+2. Edit the page with the VisualEditor.
+3. Click somewhere in the first paragraph, not at the start.
+4. Click on the reference button and re-use the reference (there is only one).
+5. Note how the reference was inserted at the start of the paragraph instead of being inserted where your cursor was.
+
+6. Click in another paragraph, not at the start.
+7. Insert the same reference again.
+8. Note how the reference was inserted at the right position.
+
+9. Perform steps 7 and 8 again.
+10. Note how it was again inserted at the right position, although the reference is already in that paragraph.
+
+11. Try inserting it again in the first paragraph.
+12. Note how it still inserts it at the start of the paragraph instead of inserting it in the right location.
+
+13. Be confused because you don't understand anything about this inconsistent behavior.",task_subcomment,"[""I have done similar manipulations in other articles at some moments, and it seems it sometimes works and sometimes doesn't."", 'There are many things that are strange concerning how the existing references system works.', 'Regardless, I set up a sandbox page on my user space, added a reference and then tried to re-use that reference using the VisualEditor.', 'The reference was added at the start of the paragraph.', ""I've done some more experimenting, and I've written steps to reproduce the bug; the first block reproduces the bug and the following blocks are other experimentations that give more strange results."", '1.', 'Go to [[User:Rastus Vernon/VisualEditor Sandbox]].', '2.', 'Edit the page with the VisualEditor.', '3.', 'Click somewhere in the first paragraph, not at the start.', '4.', 'Click on the reference button and re-use the reference (there is only one).', '5.', 'Note how the reference was inserted at the start of the paragraph instead of being inserted where your cursor was.', '6.', 'Click in another paragraph, not at the start.', '7.', 'Insert the same reference again.', '8.', 'Note how the reference was inserted at the right position.', '9.', 'Perform steps 7 and 8 again.', '10.', 'Note how it was again inserted at the right position, although the reference is already in that paragraph.', '11.', 'Try inserting it again in the first paragraph.', '12.', 'Note how it still inserts it at the start of the paragraph instead of inserting it in the right location.', '13.', ""Be confused because you don't understand anything about this inconsistent behavior.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242702,"VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is","I did only a quick test, and could not reproduce this bug.  Could you give more detailed instructions?",task_subcomment,"['I did only a quick test, and could not reproduce this bug.', 'Could you give more detailed instructions?']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION']"
+54127,VisualEditor: Editing a link spanning a comment splits the link,"Tested on Firefox 22 (Monobook) and Chrome 28 (Vector)
+
+Steps to reproduce:
+- Edit the [[Nodeulseom]] page in the visual editor.
+- Click reference [1] and edit it.
+- Click the hyperlink in the reference and point it to ""http://www.koreatimes.co.kr/"" (Eg: Just remove the last part from the reference)
+- Apply the change.
+- Hit ""Save Page"" and review the changes.
+
+Instead of replacing the old link, it seems that the preview suggest that the link will be duplicated, leaving both the old and new link in the reference.
+
+(Diff)
+[http://www.koreatimes.co.kr/ (The Korea Times)][http://www.koreatimes.co.kr/www/news/nation/nation_view.asp?newsIdx=5635&categoryCode=115 ]
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Editing a link spanning a comment splits the link\n\nTested on Firefox 22 (Monobook) and Chrome 28 (Vector)\n\nSteps to reproduce:\n- Edit the [[Nodeulseom]] page in the visual editor.', '- Click reference [1] and edit it.', '- Click the hyperlink in the reference and point it to ""URL (Eg: Just remove the last part from the reference)\n- Apply the change.', '- Hit ""Save Page"" and review the changes.', 'Instead of replacing the old link, it seems that the preview suggest that the link will be duplicated, leaving both the old and new link in the reference.', '(Diff)\n[URL (The Korea Times)][URL ]\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241067,VisualEditor: Editing a link spanning a comment splits the link,"This is now fixed because comments are editable (finally), but there's a wider, lower-priority issue for non-comments, for which I have created bug 68779 to track.",task_subcomment,"[""This is now fixed because comments are editable (finally), but there's a wider, lower-priority issue for non-comments, for which I have created bug 68779 to track.""]",['SOLUTION DISCUSSION']
+241062,VisualEditor: Editing a link spanning a comment splits the link,"(In reply to Gerrit Notification Bot from comment #3)
+> Change 141063 merged by jenkins-bot:
+> Also annotate metadata in TransactionProcessor
+> 
+> https://gerrit.wikimedia.org/r/141063
+
+Helpfully, this doesn't actually fix the bug (just a number of related bugs where the comment isn't on the edge of the link). Assigned.",task_subcomment,"[""(In reply to Gerrit Notification Bot from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nHelpfully, this doesn't actually fix the bug (just a number of related bugs where the comment isn't on the edge of the link)."", 'Assigned.']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+241055,VisualEditor: Editing a link spanning a comment splits the link,"Change 141063 merged by jenkins-bot:
+Also annotate metadata in TransactionProcessor
+
+https://gerrit.wikimedia.org/r/141063",task_subcomment,['Change 141063 merged by jenkins-bot:\nAlso annotate metadata in TransactionProcessor\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241049,VisualEditor: Editing a link spanning a comment splits the link,"Change 141063 had a related patch set uploaded by Catrope:
+Also annotate metadata in TransactionProcessor
+
+https://gerrit.wikimedia.org/r/141063",task_subcomment,['Change 141063 had a related patch set uploaded by Catrope:\nAlso annotate metadata in TransactionProcessor\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+241044,VisualEditor: Editing a link spanning a comment splits the link,"This is a more general problem. We never unannotate comments or any other metadata. For instance:
+
+* If you have [[Foo|BarQuux]] and change the link target, you'll split the link: [[Foo2|Bar]][[Foo|]][[Foo2|Quux]] (that's also what happened here)
+* If you have FooBaz, it renders as ""FooBar"". If you then make that italic, you'll get ''Foo''''Baz''
+
+The root of the problem is that ve.dm.TransactionProcessor#applyAnnotations doesn't annotate/unannotate metadata. Tomorrow I'll see if I can write a failing test case and fix applyAnnotations()",task_subcomment,"['This is a more general problem.', 'We never unannotate comments or any other metadata.', 'For instance:\n\n* If you have [[Foo|BarQuux]] and change the link target, you\'ll split the link: [[Foo2|Bar]][[Foo|]][[Foo2|Quux]] (that\'s also what happened here)\n* If you have FooBaz, it renders as ""FooBar"".', ""If you then make that italic, you'll get ''Foo''''Baz''\n\nThe root of the problem is that ve.dm.TransactionProcessor#applyAnnotations doesn't annotate/unannotate metadata."", ""Tomorrow I'll see if I can write a failing test case and fix applyAnnotations()""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+54120,browsertests: triggers for ULS,"This makes sense for ULS because they have a reasonable number of merges in a day, see https://gerrit.wikimedia.org/r/#/q/status:merged+project:mediawiki/extensions/UniversalLanguageSelector,n,z 
+
+This would entail: 
+
+* Put the ULS tests into their own Jenkins build, and possibly into their own code repo the way Mobile is
+
+* Have Jenkins kick off the build of ULS tests targeting beta labs upon code merged in the ULS branch
+
+* Report the build status after each run
+
+This came up because we found Bug 52115 in a timely way.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52890
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53691
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57560",task_description,"['browsertests: triggers for ULS\n\nThis makes sense for ULS because they have a reasonable number of merges in a day, see URL \n\nThis would entail: \n\n* Put the ULS tests into their own Jenkins build, and possibly into their own code repo the way Mobile is\n\n* Have Jenkins kick off the build of ULS tests targeting beta labs upon code merged in the ULS branch\n\n* Report the build status after each run\n\nThis came up because we found Bug 52115 in a timely way.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+240724,browsertests: triggers for ULS,The job got fixed yesterday and browser tests are passing right now. It is not blocking changes yet though.,task_subcomment,"['The job got fixed yesterday and browser tests are passing right now.', 'It is not blocking changes yet though.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+240715,browsertests: triggers for ULS,"The trigger has been added in Zuul with https://gerrit.wikimedia.org/r/97741
+
+The job will success whenever ULS change https://gerrit.wikimedia.org/r/#/c/97487/ is merged in.",task_subcomment,['The trigger has been added in Zuul with GERRIT_URL\n\nThe job will success whenever ULS change URL is merged in.'],['INVESTIGATION AND EXPLORATION']
+240708,browsertests: triggers for ULS,"Change 97741 merged by jenkins-bot:
+ULS browsertests on check pipeline
+
+https://gerrit.wikimedia.org/r/97741",task_subcomment,['Change 97741 merged by jenkins-bot:\nULS browsertests on check pipeline\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+240702,browsertests: triggers for ULS,"Change 97741 had a related patch set uploaded by Hashar:
+ULS browsertests on check pipeline
+
+https://gerrit.wikimedia.org/r/97741",task_subcomment,['Change 97741 had a related patch set uploaded by Hashar:\nULS browsertests on check pipeline\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+240695,browsertests: triggers for ULS,"The browser tests manage to pass with above change:
+
+https://integration.wikimedia.org/ci/job/mwext-browsertests-UniversalLanguageSelector-phantomjs/27/consoleFull
+
+With a nice HTML report:
+https://integration.wikimedia.org/ci/job/mwext-browsertests-UniversalLanguageSelector-phantomjs/27/artifact/report.html
+
+Whenever the change in comment #5 is merged in, I will validate with i18n team how to get it triggered by Zuul.",task_subcomment,"['The browser tests manage to pass with above change:\n\nURL\n\nWith a nice HTML report:\nURL\n\nWhenever the change in comment #5 is merged in, I will validate with i18n team how to get it triggered by Zuul.']",['WORKAROUNDS']
+240687,browsertests: triggers for ULS,"Following a pair session with Željko, the tests can be flagged with a tag which we can then exclude when running tests. For ULS, I have introduced the tag @specific-settings which let us skip any tests that are not going to pass on a fresh wiki installation: https://gerrit.wikimedia.org/r/#/c/97487/",task_subcomment,"['Following a pair session with Željko, the tests can be flagged with a tag which we can then exclude when running tests.', 'For ULS, I have introduced the tagSCREEN_NAME-settings which let us skip any tests that are not going to pass on a fresh wiki installation: URL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+240680,browsertests: triggers for ULS,Moving this under Continuous Integration radar.,task_subcomment,['Moving this under Continuous Integration radar.'],['ACTION ON ISSUE']
+240672,browsertests: triggers for ULS,Have added bug 53691 for the same for the VisualEditor repo.,task_subcomment,['Have added bug 53691 for the same for the VisualEditor repo.'],['BUG REPRODUCTION']
+240665,browsertests: triggers for ULS,What about running the tests on patch submission?,task_subcomment,['What about running the tests on patch submission?'],['SOLUTION DISCUSSION']
+240659,browsertests: triggers for ULS,"Is this still something we want to do? ULS tests are now in ULS repo, so this should be doable. The only problem is that ULS tests are not stable enough:
+
+https://wmf.ci.cloudbees.com/view/r-uls/",task_subcomment,"['Is this still something we want to do?', 'ULS tests are now in ULS repo, so this should be doable.', 'The only problem is that ULS tests are not stable enough:\n\nURL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+54113,VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),"Tested on Firefox 22 (Monobook) and Chrome 28 (Vector)
+
+Steps to reproduce:
+- Open any random page in the visual editor. Personally i used [[Botnet]].
+- Add the word ""Test"" to the page.
+- Press Ctrl + Z to undo the edit. Keep pressing till the edit is gone, then press it once more.
+
+Once you have done this, the Redo button and the Redo shortcut (Ctrl+Shift+Z) no longer seem to restore the previous edits. Any subsequent edit seems to reset the undo / redo buttons to an ""There were no previous edits"" state.
+
+Inconsistent results:
+
+Besides the above result that i can always reproduce using these steps, i have seen various other results. I have seen each of these at least twice but no matter what i try, i cannot seem to find any method of reproducing these reliably.
+
+- An entry in the console log stating ""Error: Cannot roll back a transaction that has not been committed ""
+- An entry in the console log stating ""Error: Range error: Range is no longer valid after DOM mutation ([WrappedRange(""Zz"":1, ""Zz"":1)]) ""
+- The redo button suddenly inserting ""♙"" once in Chrome.
+- The undo button suddenly inserting an endless steam ""♙"" in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51532
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52185",task_description,"['VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun)\n\nTested on Firefox 22 (Monobook) and Chrome 28 (Vector)\n\nSteps to reproduce:\n- Open any random page in the visual editor.', 'Personally i used [[Botnet]].', '- Add the word ""Test"" to the page.', '- Press Ctrl + Z to undo the edit.', 'Keep pressing till the edit is gone, then press it once more.', 'Once you have done this, the Redo button and the Redo shortcut (Ctrl+Shift+Z) no longer seem to restore the previous edits.', 'Any subsequent edit seems to reset the undo / redo buttons to an ""There were no previous edits"" state.', 'Inconsistent results:\n\nBesides the above result that i can always reproduce using these steps, i have seen various other results.', 'I have seen each of these at least twice but no matter what i try, i cannot seem to find any method of reproducing these reliably.', '- An entry in the console log stating ""Error: Cannot roll back a transaction that has not been committed ""\n- An entry in the console log stating ""Error: Range error: Range is no longer valid after DOM mutation ([WrappedRange(""Zz"":1, ""Zz"":1)]) ""\n- The redo button suddenly inserting ""♙"" once in Chrome.', '- The undo button suddenly inserting an endless steam ""♙"" in Firefox.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240258,VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),Now merged into master; will be deployed in the next push.,task_subcomment,['Now merged into master; will be deployed in the next push.'],['SOLUTION USAGE']
+240252,VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),"Change 79049 merged by jenkins-bot:
+Check for past/future state in undo/redo before setting breakpoint
+
+https://gerrit.wikimedia.org/r/79049",task_subcomment,['Change 79049 merged by jenkins-bot:\nCheck for past/future state in undo/redo before setting breakpoint\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+240247,VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),"Change 79049 had a related patch set uploaded by Esanders:
+Check for past/future state in undo/redo before setting breakpoint
+
+https://gerrit.wikimedia.org/r/79049",task_subcomment,['Change 79049 had a related patch set uploaded by Esanders:\nCheck for past/future state in undo/redo before setting breakpoint\n\nGERRIT_URL'],['ACTION ON ISSUE']
+240245,VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),It's obviusly inviting you to play chess :),task_subcomment,"[""It's obviusly inviting you to play chess :)""]",['SOLUTION DISCUSSION']
+240242,VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),I've reproduced a few of these permutations.,task_subcomment,"[""I've reproduced a few of these permutations.""]",['OBSERVED BUG BEHAVIOR']
+54112,VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),"Firefox 22 - Error console.
+
+Tested on Firefox 22 (Monobook) and Chrome 28 (Vector)
+
+Steps to reproduce:
+1) Open the [[Martin J. Silverstein]] in the visual editor.
+2) Click on the empty line between the ""Diplomatic posts"" and ""United States Ambassadors to Uruguay Uruguay"" template
+3) Click the ""Transclusions"" button, add the ""Botnets"" template and apply the edit.
+4) Try to use any button on the visual toolbar that creates a window, or try to open any existing item that creates a window. This will no longer be possible.
+
+Console log:
+- The added screenshot is the error console as seen in Firefox. On step 3 the ""DOM Offset"" error is added.
+- On step 4 (And after every subsequent click on an element that creates a window) the ""Cannot create a window"" error will be added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11357}",task_description,"['VisualEditor: Inserting template into slug throws JS error (causing dialogs to break)\n\nFirefox 22 - Error console.', 'Tested on Firefox 22 (Monobook) and Chrome 28 (Vector)\n\nSteps to reproduce:\n1) Open the [[Martin J. Silverstein]] in the visual editor.', '2) Click on the empty line between the ""Diplomatic posts"" and ""United States Ambassadors to Uruguay Uruguay"" template\n3) Click the ""Transclusions"" button, add the ""Botnets"" template and apply the edit.', '4) Try to use any button on the visual toolbar that creates a window, or try to open any existing item that creates a window.', 'This will no longer be possible.', 'Console log:\n- The added screenshot is the error console as seen in Firefox.', 'On step 3 the ""DOM Offset"" error is added.', '- On step 4 (And after every subsequent click on an element that creates a window) the ""Cannot create a window"" error will be added.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11357}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240216,VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),This appears to now be fixed - marking as WORKSFORME.,task_subcomment,['This appears to now be fixed - marking as WORKSFORME.'],['WORKAROUNDS']
+240215,VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),I can't reproduce this.,task_subcomment,"[""I can't reproduce this.""]",['OBSERVED BUG BEHAVIOR']
+240214,VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),Thought we had fixed insertion into slugs in bug 44084 - has this re-surfaced?,task_subcomment,['Thought we had fixed insertion into slugs in bug 44084 - has this re-surfaced?'],['OBSERVED BUG BEHAVIOR']
+240212,VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),"Having tested a few more scenario's it would seem that editing near templates in general causes console errors, though none of these seem to cause any lasting issues.
+
+- Selecting the line mentioned in step 2 and pressing enter will return the console error ""TypeError: outermostNode is null""
+- Typing a text under the bottom template of the page and then pressing backpace till the text and that template are gone will cause an error if that edit is undone afterwards:
+-- ""Error: Range error: Range is no longer valid after DOM mutation ""
+-- ""Error: Offset could not be translated to a DOM element and offset: 1405""
+
+As mentioned before, neither of these errors seem to impact anything in the editor or the edit itself.",task_subcomment,"[""Having tested a few more scenario's it would seem that editing near templates in general causes console errors, though none of these seem to cause any lasting issues."", '- Selecting the line mentioned in step 2 and pressing enter will return the console error ""TypeError: outermostNode is null""\n- Typing a text under the bottom template of the page and then pressing backpace till the text and that template are gone will cause an error if that edit is undone afterwards:\n-- ""Error: Range error: Range is no longer valid after DOM mutation ""\n-- ""Error: Offset could not be translated to a DOM element and offset: 1405""\n\nAs mentioned before, neither of these errors seem to impact anything in the editor or the edit itself.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+240209,VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),"Relevant error: ""Error: Offset could not be translated to a DOM element and offset: 1407""
+
+The inability to open other dialogs is because the error causes the first dialog to never close, and so opening other dialogs fails because VE thinks you've already got a dialog open.
+
+Is this due to adding a transclusion in a slug, perhaps?",task_subcomment,"['Relevant error: ""Error: Offset could not be translated to a DOM element and offset: 1407""\n\nThe inability to open other dialogs is because the error causes the first dialog to never close, and so opening other dialogs fails because VE thinks you\'ve already got a dialog open.', 'Is this due to adding a transclusion in a slug, perhaps?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+54102,VisualEditor: Write newFromDocumentReplace so editing document slices is simple,"
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,['VisualEditor: Write newFromDocumentReplace so editing document slices is simple\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: major'],['OBSERVED BUG BEHAVIOR']
+239685,VisualEditor: Write newFromDocumentReplace so editing document slices is simple,"Change 82790 merged by jenkins-bot:
+Introduce newFromDocumentReplace() transaction builder
+
+https://gerrit.wikimedia.org/r/82790",task_subcomment,['Change 82790 merged by jenkins-bot:\nIntroduce newFromDocumentReplace() transaction builder\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239683,VisualEditor: Write newFromDocumentReplace so editing document slices is simple,"Change 82790 had a related patch set uploaded by Jforrester:
+Introduce newFromDocumentReplace() transaction builder
+
+https://gerrit.wikimedia.org/r/82790",task_subcomment,['Change 82790 had a related patch set uploaded by Jforrester:\nIntroduce newFromDocumentReplace() transaction builder\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239682,VisualEditor: Write newFromDocumentReplace so editing document slices is simple,"Change 71661 abandoned by Catrope:
+[WIP] ve.dm.Transaction: Implement newFromDocumentInsertion, take 2
+
+Reason:
+Superseded by https://gerrit.wikimedia.org/r/82790
+
+https://gerrit.wikimedia.org/r/71661",task_subcomment,"['Change 71661 abandoned by Catrope:\n[WIP] ve.dm.Transaction: Implement newFromDocumentInsertion, take 2\n\nReason:\nSuperseded by GERRIT_URL\n\nGERRIT_URL']",['INVESTIGATION AND EXPLORATION']
+239678,VisualEditor: Write newFromDocumentReplace so editing document slices is simple,"Change 71661 had a related patch set uploaded by Jforrester:
+[WIP] ve.dm.Transaction: Implement newFromDocumentInsertion, take 2
+
+https://gerrit.wikimedia.org/r/71661",task_subcomment,"['Change 71661 had a related patch set uploaded by Jforrester:\n[WIP] ve.dm.Transaction: Implement newFromDocumentInsertion, take 2\n\nGERRIT_URL']",['WORKAROUNDS']
+54093,"VisualEditor: Make the ""wikitext"" link of the popup open in a new window","From bug 49820 comment 27:
+John Broughton 2013-07-25 23:13:48 UTC
+If it's not one thing, it's another ... The popup message is now visible no
+matter where in a page the wikitext is being entered. So that's progress.
+
+The popup is still too inconspicuous for my tastes (and a great opportunity for
+A/B testing), but that's not what I'm posting about. My concern is with the
+link that the popup message includes (the label is ""wikitext""; the target is
+[[Help:Wiki markup]]). If that link is clicked, the system **asks the user
+whether he/she wants to leave the editing page**. That's a bit user-unfriendly.
+
+I realize that smarter users can right-click and then open the link in either
+another tab or a new page, avoiding the question of whether they want to leave
+their editing session. But if we're aiming at the average user, it would be
+great if this link were pre-defined as opening another window, so that a simple
+click on the link didn't result in a perturbed user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51585
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51122",task_description,"['VisualEditor: Make the ""wikitext"" link of the popup open in a new window\n\nFrom bug 49820 comment 27:\nJohn Broughton 2013-07-25 23:13:48 UTC\nIf it\'s not one thing, it\'s another ...', 'The popup message is now visible no\nmatter where in a page the wikitext is being entered.', ""So that's progress."", ""The popup is still too inconspicuous for my tastes (and a great opportunity for\nA/B testing), but that's not what I'm posting about."", 'My concern is with the\nlink that the popup message includes (the label is ""wikitext""; the target is\n[[Help:Wiki markup]]).', 'If that link is clicked, the system **asks the user\nwhether he/she wants to leave the editing page**.', ""That's a bit user-unfriendly."", 'I realize that smarter users can right-click and then open the link in either\nanother tab or a new page, avoiding the question of whether they want to leave\ntheir editing session.', ""But if we're aiming at the average user, it would be\ngreat if this link were pre-defined as opening another window, so that a simple\nclick on the link didn't result in a perturbed user."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+239240,"VisualEditor: Make the ""wikitext"" link of the popup open in a new window",This is now done and we'll get it deployed soon.,task_subcomment,"[""This is now done and we'll get it deployed soon.""]",['ACTION ON ISSUE']
+239235,"VisualEditor: Make the ""wikitext"" link of the popup open in a new window","Change 76701 merged by jenkins-bot:
+Set links in wikitext warning to load in new window
+
+https://gerrit.wikimedia.org/r/76701",task_subcomment,['Change 76701 merged by jenkins-bot:\nSet links in wikitext warning to load in new window\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239229,"VisualEditor: Make the ""wikitext"" link of the popup open in a new window","Change 76701 had a related patch set uploaded by Helder.wiki:
+Set links in wikitext warning to load in new window
+
+https://gerrit.wikimedia.org/r/76701",task_subcomment,['Change 76701 had a related patch set uploaded by Helder.wiki:\nSet links in wikitext warning to load in new window\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+54077,APIEditBeforeSave isn't replacing sections like the documentation claims,"Reported: https://en.wikipedia.org/wiki/Wikipedia_talk:Tags#Incorrect_tagging
+and
+https://en.wikipedia.org/wiki/Wikipedia:VPT#Blanking_filter_misfire
+
+**See Also**:
+* {T54049}
+* {T54062}",task_description,"[""APIEditBeforeSave isn't replacing sections like the documentation claims\n\nReported: URL\nand\nURL\n\n**See Also**:\n* {T54049}\n* {T54062}""]",['OBSERVED BUG BEHAVIOR']
+641845,APIEditBeforeSave isn't replacing sections like the documentation claims,"I think this really was a problem with AbuseFilter and not the hook; the hook documentation was unclear. My fix for T73947 fixes this too, so I proposed that the patch be reverted at https://gerrit.wikimedia.org/r/282101.",task_subcomment,"['I think this really was a problem with AbuseFilter and not the hook; the hook documentation was unclear.', 'My fix for T73947 fixes this too, so I proposed that the patch be reverted at GERRIT_URL.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+238424,APIEditBeforeSave isn't replacing sections like the documentation claims,*** Bug 52895 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52895 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238419,APIEditBeforeSave isn't replacing sections like the documentation claims,*** Bug 52062 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52062 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238414,APIEditBeforeSave isn't replacing sections like the documentation claims,"Change 76082 merged by jenkins-bot:
+Make APIEditBeforeSave give the whole revision
+
+https://gerrit.wikimedia.org/r/76082",task_subcomment,['Change 76082 merged by jenkins-bot:\nMake APIEditBeforeSave give the whole revision\n\nGERRIT_URL'],['ACTION ON ISSUE']
+238408,APIEditBeforeSave isn't replacing sections like the documentation claims,"See also:
+* [[Wikipedia talk:Edit filter#Abusefilter bug on mobile version]]",task_subcomment,['See also:\n* [[Wikipedia talk:Edit filter#Abusefilter bug on mobile version]]'],['BUG REPRODUCTION']
+238403,APIEditBeforeSave isn't replacing sections like the documentation claims,"Change 76082 had a related patch set uploaded by Hoo man:
+Make APIEditBeforeSave give the whole revision
+
+https://gerrit.wikimedia.org/r/76082",task_subcomment,['Change 76082 had a related patch set uploaded by Hoo man:\nMake APIEditBeforeSave give the whole revision\n\nGERRIT_URL'],['ACTION ON ISSUE']
+238396,APIEditBeforeSave isn't replacing sections like the documentation claims,"After some investigation it turns out, that this is an issue with the edit API. I'm just preparing a fix, but takes some time as both the API and EditPage itself are rather messy.",task_subcomment,"['After some investigation it turns out, that this is an issue with the edit API.', ""I'm just preparing a fix, but takes some time as both the API and EditPage itself are rather messy.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238389,APIEditBeforeSave isn't replacing sections like the documentation claims,Hoo suspects that this is a problem with VisualEditor. Copying a few folks accordingly.,task_subcomment,"['Hoo suspects that this is a problem with VisualEditor.', 'Copying a few folks accordingly.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+238385,APIEditBeforeSave isn't replacing sections like the documentation claims,"Marius, can you take a look at these? Chris is on vacation right now.",task_subcomment,"['Marius, can you take a look at these?', 'Chris is on vacation right now.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+238380,APIEditBeforeSave isn't replacing sections like the documentation claims,"The edits in question:
+https://en.wikipedia.org/w/index.php?title=Christoph_Waltz&diff=565783472&oldid=565445126
+
+and
+
+https://en.wikipedia.org/w/index.php?title=Stone_Gossard&diff=565724723&oldid=563438457",task_subcomment,['The edits in question:\nURL\n\nand\n\nURL'],['OBSERVED BUG BEHAVIOR']
+54029,"VisualEditor: Template parameters with ""autofill"" TemplateData status should be autofilled","If the TemplateData for a template specifies a default value for a given parameter (see bug 52028) then that value should be prefilled when that parameter is added to the template. 
+
+An example would be the current date for an accessdate parameter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Template parameters with ""autofill"" TemplateData status should be autofilled\n\nIf the TemplateData for a template specifies a default value for a given parameter (see bug 52028) then that value should be prefilled when that parameter is added to the template.', 'An example would be the current date for an accessdate parameter.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+234969,"VisualEditor: Template parameters with ""autofill"" TemplateData status should be autofilled","Change 146396 merged by jenkins-bot:
+Add 'autovalue' to TemplateData
+
+https://gerrit.wikimedia.org/r/146396",task_subcomment,"[""Change 146396 merged by jenkins-bot:\nAdd 'autovalue' to TemplateData\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+234964,"VisualEditor: Template parameters with ""autofill"" TemplateData status should be autofilled","Change 146396 had a related patch set uploaded by Jforrester:
+[wip] Add 'autovalue' to TemplateData
+
+https://gerrit.wikimedia.org/r/146396",task_subcomment,"[""Change 146396 had a related patch set uploaded by Jforrester:\n[wip] Add 'autovalue' to TemplateData\n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+234959,"VisualEditor: Template parameters with ""autofill"" TemplateData status should be autofilled","That's not the meaning of the ""default"" flag on parameters, but of the proposed ""autofill"" concept from bug 51428; relabelling for clarity.",task_subcomment,"['That\'s not the meaning of the ""default"" flag on parameters, but of the proposed ""autofill"" concept from bug 51428; relabelling for clarity.']",['INVESTIGATION AND EXPLORATION']
+54014,VisualEditor: floating toolbar causes scrolling of large pages to be very slow,"In Firefox, scrolling a large VE page is very slow, with visible pauses between repaints, predominantly because of the floating toolbar. Calling disableFloating() on the toolbar from the JS console causes scrolling to be roughly as fast as scrolling the non-VE page view.
+
+Timo says he knows how to fix this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: floating toolbar causes scrolling of large pages to be very slow\n\nIn Firefox, scrolling a large VE page is very slow, with visible pauses between repaints, predominantly because of the floating toolbar.', 'Calling disableFloating() on the toolbar from the JS console causes scrolling to be roughly as fast as scrolling the non-VE page view.', 'Timo says he knows how to fix this.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233509,VisualEditor: floating toolbar causes scrolling of large pages to be very slow,Merged and deployed.,task_subcomment,['Merged and deployed.'],['SOLUTION USAGE']
+233504,VisualEditor: floating toolbar causes scrolling of large pages to be very slow,"Change 76241 merged by jenkins-bot:
+ve.ui.Toolbar: Refactor floating logic for performance
+
+https://gerrit.wikimedia.org/r/76241",task_subcomment,['Change 76241 merged by jenkins-bot:\nve.ui.Toolbar: Refactor floating logic for performance\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233499,VisualEditor: floating toolbar causes scrolling of large pages to be very slow,"Change 76241 had a related patch set uploaded by Jforrester:
+ve.ui.Toolbar: Refactor floating logic for performance
+
+https://gerrit.wikimedia.org/r/76241",task_subcomment,['Change 76241 had a related patch set uploaded by Jforrester:\nve.ui.Toolbar: Refactor floating logic for performance\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233493,VisualEditor: floating toolbar causes scrolling of large pages to be very slow,https://gerrit.wikimedia.org/r/#/c/76241/,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+233486,VisualEditor: floating toolbar causes scrolling of large pages to be very slow,"(In reply to comment #1)
+> @Krinkle: How are you going to fix this? :-)
+
+ I already did, in a way. Earlier this week I re-used that logic for mw.notification (which now also has a floating mode, previously mw.notify messages weren't visible if you scroll down the page, which is a problem for VE). However I noticed a few things that could be optimised that I did 'right' from the get go for mw.notify. I should be able to apply that to ve as well
+ most notably the fact that floating calculation for ve toolbar calls offset() each time
+ which is a repaint for something that is unlikely to ever change
+ I realised it when I was doing mwnotify but never remembered to fix it in VE",task_subcomment,"['(In reply to comment #1)\nQUOTE\n\n I already did, in a way.', ""Earlier this week I re-used that logic for mw.notification (which now also has a floating mode, previously mw.notify messages weren't visible if you scroll down the page, which is a problem for VE)."", ""However I noticed a few things that could be optimised that I did 'right' from the get go for mw.notify."", 'I should be able to apply that to ve as well\n most notably the fact that floating calculation for ve toolbar calls offset() each time\n which is a repaint for something that is unlikely to ever change\n I realised it when I was doing mwnotify but never remembered to fix it in VE']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+233477,VisualEditor: floating toolbar causes scrolling of large pages to be very slow,@Krinkle: How are you going to fix this? :-),task_subcomment,"['SCREEN_NAME: How are you going to fix this?', ':-)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+54013,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Using the backspace or delete key to delete plain text on a large page takes hundreds of milliseconds per character, predominantly because ve.dm.Document.prototype.commit() is called, which leads to ve.ce.ContentBranchNode.prototype.onChildUpdate(), which leads to ve.dm.Converter.openAndCloseAnnotations(), which calls containsComparableForSerialization(), which is apparently O(N). 
+
+Bug 52012 also affects backspace performance.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Deleting plain text from a large page with backspace or delete is very slow\n\nUsing the backspace or delete key to delete plain text on a large page takes hundreds of milliseconds per character, predominantly because ve.dm.Document.prototype.commit() is called, which leads to ve.ce.ContentBranchNode.prototype.onChildUpdate(), which leads to ve.dm.Converter.openAndCloseAnnotations(), which calls containsComparableForSerialization(), which is apparently O(N).', 'Bug 52012 also affects backspace performance.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+233454,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,Merged and deployed.,task_subcomment,['Merged and deployed.'],['SOLUTION USAGE']
+233447,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Change 76110 merged by jenkins-bot:
+Speed up openAndCloseAnnotations by using store indexes
+
+https://gerrit.wikimedia.org/r/76110",task_subcomment,['Change 76110 merged by jenkins-bot:\nSpeed up openAndCloseAnnotations by using store indexes\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+233439,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Change 76100 merged by jenkins-bot:
+Quick optimisation to avoid containsComparableForSerialization
+
+https://gerrit.wikimedia.org/r/76100",task_subcomment,['Change 76100 merged by jenkins-bot:\nQuick optimisation to avoid containsComparableForSerialization\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233434,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,With these two patches ^^^ getDomFromData has sped up from 1150ms to 180ms on my local copy of en:Argentina.,task_subcomment,['With these two patches ^^^ getDomFromData has sped up from 1150ms to 180ms on my local copy of en:Argentina.'],['BUG REPRODUCTION']
+233430,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Change 76110 had a related patch set uploaded by Esanders:
+Further annotation optimisations
+
+https://gerrit.wikimedia.org/r/76110",task_subcomment,['Change 76110 had a related patch set uploaded by Esanders:\nFurther annotation optimisations\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233426,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Change 76100 had a related patch set uploaded by Esanders:
+Quick optimisation to avoid containsComparableForSerialization
+
+https://gerrit.wikimedia.org/r/76100",task_subcomment,['Change 76100 had a related patch set uploaded by Esanders:\nQuick optimisation to avoid containsComparableForSerialization\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233421,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"(In reply to comment #5)
+> Even further suggestion from Tim: make the IVStore use a binary search tree,
+> where the nodes are something like { index: number, value: Object } and the
+> comparison operates on the objects, something similar to oo.compare() but
+> returns < or >. This requires an ordering on the keys. We could do alphabetic
+> order like in keySortReplacer, but it would be more efficient to have the
+> ve.dm.Annotation object return an ordering on the keys. Or something. This is
+> an incomplete thought and requires experimentation.
+
+The point of this would be to reduce the memory usage of IVStore by eliminating the duplication caused by using the JSON as a key, and also to reduce the CPU overhead of ve.getHash(). But note that neither of these things are confirmed as performance issues in the profiling I have done so far.
+
+In any case, comparison of store indexes would obviously be faster than binary search followed by value comparison. So I think index comparison should be the priority, of the ideas discussed here, assuming it can be implemented in such a way that pressing backspace on plain text will predominantly hit index comparison rather than value comparison. After that is implemented, we can do more profiling and decide whether the use of ve.getHash() is a problem worthy of significant development time.",task_subcomment,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe point of this would be to reduce the memory usage of IVStore by eliminating the duplication caused by using the JSON as a key, and also to reduce the CPU overhead of ve.getHash().', 'But note that neither of these things are confirmed as performance issues in the profiling I have done so far.', 'In any case, comparison of store indexes would obviously be faster than binary search followed by value comparison.', 'So I think index comparison should be the priority, of the ideas discussed here, assuming it can be implemented in such a way that pressing backspace on plain text will predominantly hit index comparison rather than value comparison.', 'After that is implemented, we can do more profiling and decide whether the use of ve.getHash() is a problem worthy of significant development time.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+233415,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"(In reply to comment #3)
+> Suggestion from IRC, posting to the bug for prosperity:
+
+s/prosperity/posterity/ ;-)
+
+[cf. bug 49198 comment 5]",task_subcomment,"['(In reply to comment #3)\nQUOTE\n\ns/prosperity/posterity/ ;-)\n\n[cf.', 'bug 49198 comment 5]']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+233411,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Even further suggestion from Tim: make the IVStore use a binary search tree, where the nodes are something like { index: number, value: Object } and the comparison operates on the objects, something similar to oo.compare() but returns < or >. This requires an ordering on the keys. We could do alphabetic order like in keySortReplacer, but it would be more efficient to have the ve.dm.Annotation object return an ordering on the keys. Or something. This is an incomplete thought and requires experimentation.
+
+Giving this to Ed because he's a machine that turns vague incomplete suggestions into working code and fixes a few bugs in the process too ;)",task_subcomment,"['Even further suggestion from Tim: make the IVStore use a binary search tree, where the nodes are something like { index: number, value: Object } and the comparison operates on the objects, something similar to oo.compare() but returns < or >.', 'This requires an ordering on the keys.', 'We could do alphabetic order like in keySortReplacer, but it would be more efficient to have the ve.dm.Annotation object return an ordering on the keys.', 'Or something.', 'This is an incomplete thought and requires experimentation.', ""Giving this to Ed because he's a machine that turns vague incomplete suggestions into working code and fixes a few bugs in the process too ;)""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE']"
+233408,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Further suggestion: when we're comparing annotations, try to compare store indexes wherever possible. When we're comparing for identity, like when comparing for serialization when both annotations are generated, we could compare store indexes rather than using ve.compare(). And if we throw comparable objects into the store, we might be able to do index comparison there too.
+
+Maybe ve.dm.Annotation instances should have properties that track the store index of their this.element and their comparable objects?
+
+Ed, could you play with this?",task_subcomment,"[""Further suggestion: when we're comparing annotations, try to compare store indexes wherever possible."", ""When we're comparing for identity, like when comparing for serialization when both annotations are generated, we could compare store indexes rather than using ve.compare()."", 'And if we throw comparable objects into the store, we might be able to do index comparison there too.', 'Maybe ve.dm.Annotation instances should have properties that track the store index of their this.element and their comparable objects?', 'Ed, could you play with this?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+233404,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"Suggestion from IRC, posting to the bug for prosperity:
+
+[15:12]	 TimStarling: As a hack, could you try to set ve.compare = function ( a, b ) { return ve.getHash( a ) === ve.getHash( b ); }; instead of ve.compare = oo.compare; (in ve.js) and see how much that mitigates the problem?",task_subcomment,"['Suggestion from IRC, posting to the bug for prosperity:\n\n[15:12]\t TimStarling: As a hack, could you try to set ve.compare = function ( a, b ) { return ve.getHash( a ) === ve.getHash( b ); }; instead of ve.compare = oo.compare; (in ve.js) and see how much that mitigates the problem?']",['SOLUTION DISCUSSION']
+233398,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"(In reply to comment #1)
+> In both actions, on my favourite test case for today ([[Argentina]]), about
+> 10s of CPU usage is attributable to openAndCloseAnnotations(), and about 80%
+> of that is from oo.compare().
+
+Perhaps related to bug 51948.",task_subcomment,['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\n\nPerhaps related to bug 51948.'],['MOTIVATION']
+233391,VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,"The slowness of ve.dm.Converter.openAndCloseAnnotations() also dominates the performance of ve.dm.Converter.prototype.getDomFromData(), severely affecting both initial setup and ""review changes"". In both actions, on my favourite test case for today ([[Argentina]]), about 10s of CPU usage is attributable to openAndCloseAnnotations(), and about 80% of that is from oo.compare().",task_subcomment,"['The slowness of ve.dm.Converter.openAndCloseAnnotations() also dominates the performance of ve.dm.Converter.prototype.getDomFromData(), severely affecting both initial setup and ""review changes"".', 'In both actions, on my favourite test case for today ([[Argentina]]), about 10s of CPU usage is attributable to openAndCloseAnnotations(), and about 80% of that is from oo.compare().']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+54004,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"When a blocked users attempts to edit a page in the classic editor they see a large, red-bordered notice that tells them:
+*They are unable to edit, but they can still read
+*Who blocked them
+*Why they are blocked (shows them the block log extract)
+*When the block expires
+*That they can usually edit their talk page and email other editors and aministrators
+*What to do if the block is unclear or doesn't seem relevant
+*How to appeal a block (links to policy and guide)
+*That they can view and copy the source of a page
+
+In contrast when a blocked user attempts to edit a page in VE
+*No notice appears, and editing works as normal
+*When they click ""Save page"" they can review their changes and enter an edit summary as normal
+
+When they try to save their edits they see a small white box with a message that tells them:
+*There was a server problem
+*Their request was unsuccessful because they have been blocked
+They can then choose only ""OK"" which takes them back to the save page dialog.
+
+This is very bad because
+*The message they see appears to say they caused a server error - cue panic mode for non-technical users (""Help! I've broken Wikipedia!"" - that is exactly the reaction I would expect from my mother.)
+*They have wasted potentially lots of time on an edit they cannot save
+*It doesn't tell them what being blocked means
+*It doesn't tell them who blocked them or for what reason 
+*It doesn't tell them what they can do to get help - they can't ask questions at the page that seems to be about asking questions for example (see Bug 51875)
+*It doesn't tell them when the block expires, how they can appeal it or how they can contact anybody.
+
+For some users it is even worse that that - saving fails silently: Bug 51999
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51999
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51454
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51547
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53009",task_description,"['VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry\n\nWhen a blocked users attempts to edit a page in the classic editor they see a large, red-bordered notice that tells them:\n*They are unable to edit, but they can still read\n*Who blocked them\n*Why they are blocked (shows them the block log extract)\n*When the block expires\n*That they can usually edit their talk page and email other editors and aministrators\n*What to do if the block is unclear or doesn\'t seem relevant\n*How to appeal a block (links to policy and guide)\n*That they can view and copy the source of a page\n\nIn contrast when a blocked user attempts to edit a page in VE\n*No notice appears, and editing works as normal\n*When they click ""Save page"" they can review their changes and enter an edit summary as normal\n\nWhen they try to save their edits they see a small white box with a message that tells them:\n*There was a server problem\n*Their request was unsuccessful because they have been blocked\nThey can then choose only ""OK"" which takes them back to the save page dialog.', 'This is very bad because\n*The message they see appears to say they caused a server error - cue panic mode for non-technical users (""Help!', 'I\'ve broken Wikipedia!""', '- that is exactly the reaction I would expect from my mother.)', ""*They have wasted potentially lots of time on an edit they cannot save\n*It doesn't tell them what being blocked means\n*It doesn't tell them who blocked them or for what reason \n*It doesn't tell them what they can do to get help - they can't ask questions at the page that seems to be about asking questions for example (see Bug 51875)\n*It doesn't tell them when the block expires, how they can appeal it or how they can contact anybody."", 'For some users it is even worse that that - saving fails silently: Bug 51999\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+232641,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"Change 119204 merged by jenkins-bot:
+Show blockedtext message in edit notices
+
+https://gerrit.wikimedia.org/r/119204",task_subcomment,['Change 119204 merged by jenkins-bot:\nShow blockedtext message in edit notices\n\nGERRIT_URL'],['ACTION ON ISSUE']
+232635,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"Change 119204 had a related patch set uploaded by Alex Monk:
+Show blockedtext message in edit notices
+
+https://gerrit.wikimedia.org/r/119204",task_subcomment,['Change 119204 had a related patch set uploaded by Alex Monk:\nShow blockedtext message in edit notices\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+232630,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"(In reply to Roan Kattouw from comment #4)
+> We already put random junk in the paction=parse response, I wouldn't be
+> opposed to adding blocked-ness to that. Another paction would be OK too, but
+> then we'd have to make two API requests.
+> 
+> There are significant speed benefits in combining everything into one API
+> request. I think we should stop kidding ourselves that paction=parse is a
+> clean, only-does-one-thing action, and perhaps rename it if we want, rather
+> than trying to split it into separate actions, because the latter would just
+> make client-side performance worse.
+
+Yes, since writing that comment I decided to just add it in to paction=parse, especially since talking to James - he wants this to be an edit notice like the others. I probably should have left a new comment about it.
+
+The problem now is coming up with a nice way to fit the autoblockedtext message (blockedtext is okay) in to the edit notices popup.",task_subcomment,"['(In reply to Roan Kattouw from comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYes, since writing that comment I decided to just add it in to paction=parse, especially since talking to James - he wants this to be an edit notice like the others.', 'I probably should have left a new comment about it.', 'The problem now is coming up with a nice way to fit the autoblockedtext message (blockedtext is okay) in to the edit notices popup.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232627,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"(In reply to Alex Monk from comment #3)
+> James suggested I tackle this bug. I messed around with the API for a little
+> bit and assuming I didn't miss anything:
+> 
+> I think that if we tried to fill out the 'blockedtext' message properly on
+> the client we'd have to:
+> * Query the API for the user's blockinfo to determine whether or not they're
+> blocked. If they are:
+> ** Query the API for more info about this block which
+> meta=userinfo&uiprop=blockinfo doesn't provide but we need to substitute
+> into the message (expiry, user, timestamp).
+> ** Query the API to parse the blockedtext message because it can't be done
+> on the client (even the default message includes stuff mw.msg can't handle)
+> ** Substitute the data we have into the message (and we still won't have $3
+> - the current IP)
+> *** Mess around with dates/times because they won't be in the right format.
+> 
+> Another way we could do this is return the full warning from
+> action=visualeditor&paction=parse (therefore adding no extra API requests)
+> which would cause the client to stop loading. I don't like this idea because
+> obviously that paction is not intended for checking this kind of thing...
+> 
+> Or we could ignore the core blockedtext message and use our own ""Your
+> username or IP address has been blocked"", possibly with the info that just
+> meta=userinfo&uiprop=blockinfo provides (block ID, performer, reason).
+> 
+> Or we could add a new API module/paction that can be queried once and
+> provides all the relevant info. I don't like this idea either but it seems
+> the nicest.
+> 
+We already put random junk in the paction=parse response, I wouldn't be opposed to adding blocked-ness to that. Another paction would be OK too, but then we'd have to make two API requests.
+
+There are significant speed benefits in combining everything into one API request. I think we should stop kidding ourselves that paction=parse is a clean, only-does-one-thing action, and perhaps rename it if we want, rather than trying to split it into separate actions, because the latter would just make client-side performance worse.",task_subcomment,"[""(In reply to Alex Monk from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nWe already put random junk in the paction=parse response, I wouldn't be opposed to adding blocked-ness to that."", ""Another paction would be OK too, but then we'd have to make two API requests."", 'There are significant speed benefits in combining everything into one API request.', 'I think we should stop kidding ourselves that paction=parse is a clean, only-does-one-thing action, and perhaps rename it if we want, rather than trying to split it into separate actions, because the latter would just make client-side performance worse.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232624,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"James suggested I tackle this bug. I messed around with the API for a little bit and assuming I didn't miss anything:
+
+I think that if we tried to fill out the 'blockedtext' message properly on the client we'd have to:
+* Query the API for the user's blockinfo to determine whether or not they're blocked. If they are:
+** Query the API for more info about this block which meta=userinfo&uiprop=blockinfo doesn't provide but we need to substitute into the message (expiry, user, timestamp).
+** Query the API to parse the blockedtext message because it can't be done on the client (even the default message includes stuff mw.msg can't handle)
+** Substitute the data we have into the message (and we still won't have $3 - the current IP)
+*** Mess around with dates/times because they won't be in the right format.
+
+Another way we could do this is return the full warning from action=visualeditor&paction=parse (therefore adding no extra API requests) which would cause the client to stop loading. I don't like this idea because obviously that paction is not intended for checking this kind of thing...
+
+Or we could ignore the core blockedtext message and use our own ""Your username or IP address has been blocked"", possibly with the info that just meta=userinfo&uiprop=blockinfo provides (block ID, performer, reason).
+
+Or we could add a new API module/paction that can be queried once and provides all the relevant info. I don't like this idea either but it seems the nicest.
+
+Thoughts?",task_subcomment,"['James suggested I tackle this bug.', ""I messed around with the API for a little bit and assuming I didn't miss anything:\n\nI think that if we tried to fill out the 'blockedtext' message properly on the client we'd have to:\n* Query the API for the user's blockinfo to determine whether or not they're blocked."", ""If they are:\n** Query the API for more info about this block which meta=userinfo&uiprop=blockinfo doesn't provide but we need to substitute into the message (expiry, user, timestamp)."", ""** Query the API to parse the blockedtext message because it can't be done on the client (even the default message includes stuff mw.msg can't handle)\n** Substitute the data we have into the message (and we still won't have $3 - the current IP)\n*** Mess around with dates/times because they won't be in the right format."", 'Another way we could do this is return the full warning from action=visualeditor&paction=parse (therefore adding no extra API requests) which would cause the client to stop loading.', 'I don\'t like this idea because obviously that paction is not intended for checking this kind of thing...\n\nOr we could ignore the core blockedtext message and use our own ""Your username or IP address has been blocked"", possibly with the info that just meta=userinfo&uiprop=blockinfo provides (block ID, performer, reason).', 'Or we could add a new API module/paction that can be queried once and provides all the relevant info.', ""I don't like this idea either but it seems the nicest."", 'Thoughts?']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232621,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"Created attachment 12954
+What a blocked user sees immediately they the source editor loads
+
+**Attached**: {F11061}",task_subcomment,['Created attachment 12954\nWhat a blocked user sees immediately they the source editor loads\n\n**Attached**: {F11061}'],['INVESTIGATION AND EXPLORATION']
+232615,VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show  with log entry,"Created attachment 12953
+What a blocked user sees when they try to save an edit in VE
+
+**Attached**: {F11060}",task_subcomment,['Created attachment 12953\nWhat a blocked user sees when they try to save an edit in VE\n\n**Attached**: {F11060}'],['INVESTIGATION AND EXPLORATION']
+54000,VisualEditor: Can't re-use a reference belonging to non-default group,"Users can't reuse a reference belonging to non-default group. It's just not shown on the list and I've been unable to get such refs to show up there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51838",task_description,"[""VisualEditor: Can't re-use a reference belonging to non-default group\n\nUsers can't reuse a reference belonging to non-default group."", ""It's just not shown on the list and I've been unable to get such refs to show up there."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232338,VisualEditor: Can't re-use a reference belonging to non-default group,"Change 81964 merged by jenkins-bot:
+Re-build reference search index so they can be used mid-edit
+
+https://gerrit.wikimedia.org/r/81964",task_subcomment,['Change 81964 merged by jenkins-bot:\nRe-build reference search index so they can be used mid-edit\n\nGERRIT_URL'],['ACTION ON ISSUE']
+232332,VisualEditor: Can't re-use a reference belonging to non-default group,Now fixed in master and will be deployed next week.,task_subcomment,['Now fixed in master and will be deployed next week.'],['SOLUTION DISCUSSION']
+232323,VisualEditor: Can't re-use a reference belonging to non-default group,"Change 81964 had a related patch set uploaded by Trevor Parscal:
+Bug 51689 & 52000 - Reusing new references
+
+https://gerrit.wikimedia.org/r/81964",task_subcomment,['Change 81964 had a related patch set uploaded by Trevor Parscal:\nBug 51689 & 52000 - Reusing new references\n\nGERRIT_URL'],['BUG REPRODUCTION']
+232316,VisualEditor: Can't re-use a reference belonging to non-default group,"Change 81964 had a related patch set uploaded by Trevor Parscal:
+Bug 52000 - Reusing new reference groups
+
+https://gerrit.wikimedia.org/r/81964",task_subcomment,['Change 81964 had a related patch set uploaded by Trevor Parscal:\nBug 52000 - Reusing new reference groups\n\nGERRIT_URL'],['BUG REPRODUCTION']
+232311,VisualEditor: Can't re-use a reference belonging to non-default group,"This works if the group exists when VE loads the page, but if the group is added after load then it's items don't show up in the search.",task_subcomment,"[""This works if the group exists when VE loads the page, but if the group is added after load then it's items don't show up in the search.""]",['OBSERVED BUG BEHAVIOR']
+53999,VisualEditor: Saving fails silently for some blocked users,"A user on en.wp has reported the following:
+
+""Editing anonymously from my school computers is blocked, and for fun I tried editing a page using VE. It lets me edit the page fully, ''until'' I try to click the save page button. No matter how many times I click it it doesn't save, but there's no notification telling me why it doesn't save. A bit weird really""
+
+I blocked my legitimate alternate user and then tried to edit a page. The editor loaded fine but when I clicked to save the edit I saw the message:
+""Error loading data from server: Unsuccessful request: You have been blocked from editing.""
+
+I am on a shared connection so I do not want to do any testing of ipblocks, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52004",task_description,"['VisualEditor: Saving fails silently for some blocked users\n\nA user on en.wp has reported the following:\n\n""Editing anonymously from my school computers is blocked, and for fun I tried editing a page using VE.', ""It lets me edit the page fully, ''until'' I try to click the save page button."", ""No matter how many times I click it it doesn't save, but there's no notification telling me why it doesn't save."", 'A bit weird really""\n\nI blocked my legitimate alternate user and then tried to edit a page.', 'The editor loaded fine but when I clicked to save the edit I saw the message:\n""Error loading data from server: Unsuccessful request: You have been blocked from editing.""', 'I am on a shared connection so I do not want to do any testing of ipblocks, etc.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232271,VisualEditor: Saving fails silently for some blocked users,This was fixed in the fix for bug 52004.,task_subcomment,['This was fixed in the fix for bug 52004.'],['SOLUTION DISCUSSION']
+232260,VisualEditor: Saving fails silently for some blocked users,"The original reporter, numbermaniac, has done some additional testing and found that they do see the message when pressing save in Chrome on Windows 7. Their initial report was using iMac Safari.
+
+My testing was done using Firefox 22 on Xubuntu Linux",task_subcomment,"['The original reporter, numbermaniac, has done some additional testing and found that they do see the message when pressing save in Chrome on Windows 7.', 'Their initial report was using iMac Safari.', 'My testing was done using Firefox 22 on Xubuntu Linux']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53995,VisualEditor: Thumb images are missing appropriate CSS classes,"For instance instead of class 'tright' or 'tleft' just class 't' gets added. It is regression of this change: https://gerrit.wikimedia.org/r/#/c/75526/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Thumb images are missing appropriate CSS classes\n\nFor instance instead of class 'tright' or 'tleft' just class 't' gets added."", 'It is regression of this change: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232089,VisualEditor: Thumb images are missing appropriate CSS classes,Now fixed in master and will be deployed in a few minutes' time.,task_subcomment,"[""Now fixed in master and will be deployed in a few minutes' time.""]",['SOLUTION USAGE']
+232087,VisualEditor: Thumb images are missing appropriate CSS classes,"Change 75803 merged by jenkins-bot:
+Fix MWBlockImageNodes' default horizontal location code
+
+https://gerrit.wikimedia.org/r/75803",task_subcomment,"[""Change 75803 merged by jenkins-bot:\nFix MWBlockImageNodes' default horizontal location code\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+232084,VisualEditor: Thumb images are missing appropriate CSS classes,"Change 75803 had a related patch set uploaded by Jforrester:
+(bug 51995) Bugfix
+
+https://gerrit.wikimedia.org/r/75803",task_subcomment,['Change 75803 had a related patch set uploaded by Jforrester:\n(bug 51995) Bugfix\n\nGERRIT_URL'],['BUG REPRODUCTION']
+232080,VisualEditor: Thumb images are missing appropriate CSS classes,"Change 75803 had a related patch set uploaded by Inez:
+(bug 51995) Bugfix
+
+https://gerrit.wikimedia.org/r/75803",task_subcomment,['Change 75803 had a related patch set uploaded by Inez:\n(bug 51995) Bugfix\n\nGERRIT_URL'],['BUG REPRODUCTION']
+53987,VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?),"Firefox - Detected script lockup.
+
+Misplacing a bulleted / numbered list can cause a script lockup. Tested on both Firefox 22 and Chrome 28
+
+Steps to reproduce:
+- Navigate to [[Lauda Air Flight 004]] and open it with the visual editor.
+- Click the ""Lauda Air Flight 004"" infobox and make sure it remains selected.
+- Click the ""Bulleted List"" button. A list bullet is added to the article.
+- Click right after the bullet that was just inserted. Now click the ""Bulleted list"" button again.
+
+Normally this would remove the bullet again. Instead of that both Firefox and Chrome seem to lock up. Firefox will lock up entirely (All open tabs will freeze) and eventually an unresponsive script error will be displayed. Cancelling the script allows you to regain browser control. On Chrome the lockup seems isolated to the tab where we edit Wikipedia, but it only offers the option to close the tab after a while (Losing all changes)
+
+In practice one would never want to add a bulleted list this way, but actually ""crashing"" makes it severe enough to report i would assume.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11897}",task_description,"['VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?)', 'Firefox - Detected script lockup.', 'Misplacing a bulleted / numbered list can cause a script lockup.', 'Tested on both Firefox 22 and Chrome 28\n\nSteps to reproduce:\n- Navigate to [[Lauda Air Flight 004]] and open it with the visual editor.', '- Click the ""Lauda Air Flight 004"" infobox and make sure it remains selected.', '- Click the ""Bulleted List"" button.', 'A list bullet is added to the article.', '- Click right after the bullet that was just inserted.', 'Now click the ""Bulleted list"" button again.', 'Normally this would remove the bullet again.', 'Instead of that both Firefox and Chrome seem to lock up.', 'Firefox will lock up entirely (All open tabs will freeze) and eventually an unresponsive script error will be displayed.', 'Cancelling the script allows you to regain browser control.', 'On Chrome the lockup seems isolated to the tab where we edit Wikipedia, but it only offers the option to close the tab after a while (Losing all changes)\n\nIn practice one would never want to add a bulleted list this way, but actually ""crashing"" makes it severe enough to report i would assume.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11897}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255102,VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?),"Resetting to FIXED; this was a confirmed broken behaviour which has subsequently been FIXED, as far as we can tell - probably by the re-write of the Content Editable surface interaction model.",task_subcomment,"['Resetting to FIXED; this was a confirmed broken behaviour which has subsequently been FIXED, as far as we can tell - probably by the re-write of the Content Editable surface interaction model.']",['BUG REPRODUCTION']
+255097,VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?),"(In reply to comment #3)
+> Cannot reproduce it now with MAC OS using FireFox and Chrome.
+
+Please ALWAYS provide version information for browsers. 
+Note that comment 0 says ""Tested on both Firefox 22 and Chrome 28"".
+
+> So changing the status of the bug as resolved.
+
+No identifiable code commit, hence changing to WORKSFORME instead of FIXED. Also see https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle",task_subcomment,"['(In reply to comment #3)\nQUOTE\n\nPlease ALWAYS provide version information for browsers.', 'Note that comment 0 says ""Tested on both Firefox 22 and Chrome 28"".', 'QUOTE\n\nNo identifiable code commit, hence changing to WORKSFORME instead of FIXED.', 'Also see URL']","['CONTRIBUTION AND COMMITMENT', 'OBSERVED BUG BEHAVIOR', 'WORKSFORME', 'SOLUTION DISCUSSION']"
+255092,VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?),"Cannot reproduce it now with MAC OS using FireFox and Chrome.So changing the status of the bug as resolved.
+If you can still reproduce it ,please reopen the bug.",task_subcomment,"['Cannot reproduce it now with MAC OS using FireFox and Chrome.So changing the status of the bug as resolved.', 'If you can still reproduce it ,please reopen the bug.']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+255087,VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?),This is an infinite loop inside either Rangy or the bit of ContentEditable that calls it - lots of calls to sel.getRangeAt(index) which end up taking so long that the browser dies (?),task_subcomment,['This is an infinite loop inside either Rangy or the bit of ContentEditable that calls it - lots of calls to sel.getRangeAt(index) which end up taking so long that the browser dies (?)'],['OBSERVED BUG BEHAVIOR']
+255082,VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?),We should have a 'crash' or 'dataloss' keyword.  Bumping priority to get more attention/triaging in case the underlying cause is able to be triggered in other ways.,task_subcomment,"[""We should have a 'crash' or 'dataloss' keyword."", 'Bumping priority to get more attention/triaging in case the underlying cause is able to be triggered in other ways.']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+53986,"VisualEditor: Action buttons of the toolbar (including ""Save"") don't appear on some articles in Firefox because error is thrown","The particular article in the URL field of this bug report doesn't not display the Save button in Firefox.
+
+The Save button is displayed in Chrome, and it is displayed in other articles in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/%D7%A9%D7%93_%28%D7%9E%D7%99%D7%AA%D7%95%D7%9C%D7%95%D7%92%D7%99%D7%94%29?veaction=edit",task_description,"['VisualEditor: Action buttons of the toolbar (including ""Save"") don\'t appear on some articles in Firefox because error is thrown\n\nThe particular article in the URL field of this bug report doesn\'t not display the Save button in Firefox.', 'The Save button is displayed in Chrome, and it is displayed in other articles in Firefox.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255045,"VisualEditor: Action buttons of the toolbar (including ""Save"") don't appear on some articles in Firefox because error is thrown",This is now fixed in master; we will make sure it is deployed tomorrow.,task_subcomment,['This is now fixed in master; we will make sure it is deployed tomorrow.'],['ACTION ON ISSUE']
+255041,"VisualEditor: Action buttons of the toolbar (including ""Save"") don't appear on some articles in Firefox because error is thrown","Change 75785 merged by jenkins-bot:
+Fix the save button disappearing on certain pages in Firefox
+
+https://gerrit.wikimedia.org/r/75785",task_subcomment,['Change 75785 merged by jenkins-bot:\nFix the save button disappearing on certain pages in Firefox\n\nGERRIT_URL'],['ACTION ON ISSUE']
+255034,"VisualEditor: Action buttons of the toolbar (including ""Save"") don't appear on some articles in Firefox because error is thrown","Change 75785 had a related patch set uploaded by Catrope:
+Fix the save button disappearing on certain pages in Firefox
+
+https://gerrit.wikimedia.org/r/75785",task_subcomment,['Change 75785 had a related patch set uploaded by Catrope:\nFix the save button disappearing on certain pages in Firefox\n\nGERRIT_URL'],['ACTION ON ISSUE']
+255026,"VisualEditor: Action buttons of the toolbar (including ""Save"") don't appear on some articles in Firefox because error is thrown","Another article where this happens:
+
+https://he.wikipedia.org/wiki/%D7%A4%D7%9C%D7%99%D7%98%D7%99_%D7%9E%D7%9C%D7%97%D7%9E%D7%AA_%D7%94%D7%90%D7%96%D7%A8%D7%97%D7%99%D7%9D_%D7%91%D7%A1%D7%95%D7%A8%D7%99%D7%94?veaction=edit",task_subcomment,['Another article where this happens:\n\nURL'],['OBSERVED BUG BEHAVIOR']
+53984,VisualEditor: Clicking the hyper link button twice breaks the button.,"(Tested in Firefox 22 and Chrome 28)
+
+Steps to reproduce:
+- Open [[Portland Ice Arena (Oregon)]] with the visual editor.
+- Click the hyperlink button (Don't select anything). The hyperlink window should pop up.
+- Now click anywhere else in the article without entering any data in the hyperlink popup. 
+- An empty popup balloon will remain behind. There are no controls on that popup anymore.
+- Click around the article a bit - eventually that balloon will be removed. However, the link button will now fail to work no matter what you do.
+
+This may or may not be related to bug 48549, which seems to have been fixed in todays deployment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Clicking the hyper link button twice breaks the button.', '(Tested in Firefox 22 and Chrome 28)\n\nSteps to reproduce:\n- Open [[Portland Ice Arena (Oregon)]] with the visual editor.', ""- Click the hyperlink button (Don't select anything)."", 'The hyperlink window should pop up.', '- Now click anywhere else in the article without entering any data in the hyperlink popup.', '- An empty popup balloon will remain behind.', 'There are no controls on that popup anymore.', '- Click around the article a bit - eventually that balloon will be removed.', 'However, the link button will now fail to work no matter what you do.', 'This may or may not be related to bug 48549, which seems to have been fixed in todays deployment.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254940,VisualEditor: Clicking the hyper link button twice breaks the button.,"
+
+*** This bug has been marked as a duplicate of bug 51404 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51404 ***'],['ISSUE CONTENT MANAGEMENT']
+254935,VisualEditor: Clicking the hyper link button twice breaks the button.,"most likely duplicate of bug 51404, which should be subsequently renamed from ""crashing when inserting link without selection"" to ""crashing when inserting link on non-linkable or empty selection""",task_subcomment,"['most likely duplicate of bug 51404, which should be subsequently renamed from ""crashing when inserting link without selection"" to ""crashing when inserting link on non-linkable or empty selection""']",['OBSERVED BUG BEHAVIOR']
+254930,VisualEditor: Clicking the hyper link button twice breaks the button.,"Addendum:
+After some more testing it would seem that the link button will always break whenever the user selects an element that normally wouldn't be hyperlinked. If one does select a non linkable element and presses the hyperlink button the empty balloon popup will always occur.  
+
+These elements include - among others - images, templates, references and objects that cannot be edited in the visual editor yet. Unfortunately there seems to be no way restore the link buttons functionality without reloading the editor itself.",task_subcomment,"[""Addendum:\nAfter some more testing it would seem that the link button will always break whenever the user selects an element that normally wouldn't be hyperlinked."", 'If one does select a non linkable element and presses the hyperlink button the empty balloon popup will always occur.', 'These elements include - among others - images, templates, references and objects that cannot be edited in the visual editor yet.', 'Unfortunately there seems to be no way restore the link buttons functionality without reloading the editor itself.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+254925,VisualEditor: Clicking the hyper link button twice breaks the button.,I was able to reproduce following the steps in comment 3.,task_subcomment,['I was able to reproduce following the steps in comment 3.'],['OBSERVED BUG BEHAVIOR']
+254918,VisualEditor: Clicking the hyper link button twice breaks the button.,"Chrome 28 - Error console
+
+And last: A screenshot of chrome's console. It seems to be a tad more in depth than the error Firefox displays.
+
+**Attached**: {F11891}",task_subcomment,"[""Chrome 28 - Error console\n\nAnd last: A screenshot of chrome's console."", 'It seems to be a tad more in depth than the error Firefox displays.', '**Attached**: {F11891}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254911,VisualEditor: Clicking the hyper link button twice breaks the button.,"Yep, one pops up on step 3:
+
+[23:46:29.770] Error: No class registered by that name: undefined @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=monobook&version=20130724T164530Z&*:2
+
+The above screenshot displays what occurs on the page. Also, a more specific set of steps that might help to reproduce this:
+
+1) Edit the [[Portland Ice Arena (Oregon)]] page in the visual editor.
+2) Place the cursor directly after reference [2]. 
+3) Click the hyperlink button. It should create the regular hyperlink balloon as seen in the left side of the attached screenshot.
+4) Click the 'Not to be confused with Portland Ice Arena (Maine).' template. This will cause the template to ""blank"" itself as seen in the right side of the screenshot. 
+5) Click the 'Not to be confused with Portland Ice Arena (Maine).' template another time. This will cause the empty edit balloon to disappear. 
+6) Try the edit link button anywhere in the page itself - it will no longer work (Not on existing links nor on new ones)
+
+Note that it is not required to click the template - clicking elsewhere will work as well.",task_subcomment,"['Yep, one pops up on step 3:\n\n[23:46:29.770] Error: No class registered by that name: undefined @ URL\n\nThe above screenshot displays what occurs on the page.', 'Also, a more specific set of steps that might help to reproduce this:\n\n1) Edit the [[Portland Ice Arena (Oregon)]] page in the visual editor.', '2) Place the cursor directly after reference [2].', '3) Click the hyperlink button.', 'It should create the regular hyperlink balloon as seen in the left side of the attached screenshot.', ""4) Click the 'Not to be confused with Portland Ice Arena (Maine).'"", 'template.', 'This will cause the template to ""blank"" itself as seen in the right side of the screenshot.', ""5) Click the 'Not to be confused with Portland Ice Arena (Maine).'"", 'template another time.', 'This will cause the empty edit balloon to disappear.', '6) Try the edit link button anywhere in the page itself - it will no longer work (Not on existing links nor on new ones)\n\nNote that it is not required to click the template - clicking elsewhere will work as well.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+254906,VisualEditor: Clicking the hyper link button twice breaks the button.,"Error screenshot.
+
+**Attached**: {F11890}",task_subcomment,"['Error screenshot.', '**Attached**: {F11890}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254902,VisualEditor: Clicking the hyper link button twice breaks the button.,I can't reproduce this. Do you see any errors in your JS console?,task_subcomment,"[""I can't reproduce this."", 'Do you see any errors in your JS console?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53978,VisualEditor: A template with the RLM control character doesn't work when editing in VE,"The Hebrew Wikipedia frequently uses the template {{כ}} ( https://he.wikipedia.orgw/wiki/Template:Rlm ), which inserts the ‏ entity. This entity translates to an invisible zero-width control character, the [[right-to-left mark]]. This template works correctly when the article is rendered to the reader, but when the article is being edited in VE, the text behaves as if it's not there.
+
+For reference, see https://en.wikipedia.org/wiki/Right-to-left_mark .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/User:Amire80/ve-rlm",task_description,"[""VisualEditor: A template with the RLM control character doesn't work when editing in VE\n\nThe Hebrew Wikipedia frequently uses the template {{כ}} ( URL ), which inserts the ‏ entity."", 'This entity translates to an invisible zero-width control character, the [[right-to-left mark]].', ""This template works correctly when the article is rendered to the reader, but when the article is being edited in VE, the text behaves as if it's not there."", 'For reference, see URL .', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+254594,VisualEditor: A template with the RLM control character doesn't work when editing in VE,"(In reply to Amir E. Aharoni from comment #6)
+> At Wikimania Moriel, Roan and I found that the bug, as originally reported,
+> appears to be fixed. I don't know when exactly did the fix happen.
+> 
+> Using the {{כ}} template works correctly while editing articles, and the
+> original test page https://he.wikipedia.org/wiki/User:Amire80/ve-rlm shows
+> everything correctly.
+
+This would probably have been fixed by Ed's work on unwrapping generated content nodes.
+
+> That said, there are issues with handling this template after it's inserted:
+> * The bubble that shows its name appears in a wrong location.
+
+Yeah, the context seems to find the nearest thing that actually displays and attaches to that. Probably the same issue as the below.
+
+> * It's hard to know that it's there while editing in visual mode, because it
+> is zero-width. Showing some kind of a flag there, as it's done with single
+> line breaks, would be a nice idea.
+
+That's bug 49806.
+
+> Should I close this bug and open separate bugs for these issues?
+
+Have done so. Yay.",task_subcomment,"[""(In reply to Amir E. Aharoni from comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis would probably have been fixed by Ed's work on unwrapping generated content nodes."", 'QUOTE\nQUOTE\n\nYeah, the context seems to find the nearest thing that actually displays and attaches to that.', 'Probably the same issue as the below.', ""QUOTE\nQUOTE\nQUOTE\n\nThat's bug 49806."", 'QUOTE\n\nHave done so.', 'Yay.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254590,VisualEditor: A template with the RLM control character doesn't work when editing in VE,"At Wikimania Moriel, Roan and I found that the bug, as originally reported, appears to be fixed. I don't know when exactly did the fix happen.
+
+Using the {{כ}} template works correctly while editing articles, and the original test page https://he.wikipedia.org/wiki/User:Amire80/ve-rlm shows everything correctly.
+
+That said, there are issues with handling this template after it's inserted:
+* The bubble that shows its name appears in a wrong location.
+* It's hard to know that it's there while editing in visual mode, because it is zero-width. Showing some kind of a flag there, as it's done with single line breaks, would be a nice idea.
+
+Should I close this bug and open separate bugs for these issues?",task_subcomment,"['At Wikimania Moriel, Roan and I found that the bug, as originally reported, appears to be fixed.', ""I don't know when exactly did the fix happen."", 'Using the {{כ}} template works correctly while editing articles, and the original test page URL shows everything correctly.', ""That said, there are issues with handling this template after it's inserted:\n* The bubble that shows its name appears in a wrong location."", ""* It's hard to know that it's there while editing in visual mode, because it is zero-width."", ""Showing some kind of a flag there, as it's done with single line breaks, would be a nice idea."", 'Should I close this bug and open separate bugs for these issues?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254586,VisualEditor: A template with the RLM control character doesn't work when editing in VE,"(In reply to comment #4)
+> 2. Language definition to assign directionality rather than RLM is good
+> approach, but it isn't possible to replace all the RLM uses:
+> A. for normal users it is annoying to meet wiki-text editing HTML code of
+>  dir="""">...
+
+That's why Moriel invested so much time in an easy graphical way to do it :)
+
+It's still in the ""finishing touches"" stage.
+
+The trouble is that while bidi isolation replaces most or all of the uses of RLM, it doesn't work in IE. Saw it coming? :)
+
+In fact, IE 10 and 11 (!) even show some elements with bidi isolation very incorrectly. Test the following page:
+https://en.wikipedia.org/wiki/User:Amire80/bidi-isolate
+
+> Regarding the issue of ""invisible template"" which the VE users don't know it
+> is
+> there - I think it will be nice (and maybe there is already exist) to add
+> ability to add text that appears only in VE editing mode [either with CSS
+> which
+> tells the content to display:none, and only in VE it appears, or with
+> dedicated
+> parser tag . This solution may be useful for other cases of
+> ""invisible
+> templates"".
+
+I love this proposal.",task_subcomment,"['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat\'s why Moriel invested so much time in an easy graphical way to do it :)\n\nIt\'s still in the ""finishing touches"" stage.', ""The trouble is that while bidi isolation replaces most or all of the uses of RLM, it doesn't work in IE."", 'Saw it coming?', ':)\n\nIn fact, IE 10 and 11 (!)', 'even show some elements with bidi isolation very incorrectly.', 'Test the following page:\nURL\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI love this proposal.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+254583,VisualEditor: A template with the RLM control character doesn't work when editing in VE,"1. I think that adding display:inline-block by the VE (to any transclusion node - and particularly to this template)  is a bug, We should consider either removing this css or changing it to inline instead of inline-block
+2. Language definition to assign directionality rather than RLM is good approach, but it isn't possible to replace all the RLM uses:
+A. for normal users it is annoying to meet wiki-text editing HTML code of ...
+B. Sometimes specifying direction/language is overkill and the simple and best solution is to use RLM. 
+
+Regarding the issue of ""invisible template"" which the VE users don't know it is there - I think it will be nice (and maybe there is already exist) to add ability to add text that appears only in VE editing mode [either with CSS which tells the content to display:none, and only in VE it appears, or with dedicated parser tag . This solution may be useful for other cases of ""invisible templates"".",task_subcomment,"['1.', 'I think that adding display:inline-block by the VE (to any transclusion node - and particularly to this template)  is a bug, We should consider either removing this css or changing it to inline instead of inline-block\n2.', 'Language definition to assign directionality rather than RLM is good approach, but it isn\'t possible to replace all the RLM uses:\nA. for normal users it is annoying to meet wiki-text editing HTML code of ...\nB.', 'Sometimes specifying direction/language is overkill and the simple and best solution is to use RLM.', 'Regarding the issue of ""invisible template"" which the VE users don\'t know it is there - I think it will be nice (and maybe there is already exist) to add ability to add text that appears only in VE editing mode [either with CSS which tells the content to display:none, and only in VE it appears, or with dedicated parser tag .', 'This solution may be useful for other cases of ""invisible templates"".']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254578,VisualEditor: A template with the RLM control character doesn't work when editing in VE,"This is a bit more complicated than removing a css definition.
+
+As far as I understand this is what happens -- 
+
+1. Parsoid recognizes {{כ}} as a template (expected) and sends it to VE as a transclusion object. 
+2. VE treats it as transclusion object (as expected) --- but this means that-
+3. The content of the transclusion/template is wrapped with transclusion node markup. This means that the RLM code is now wrapped with html markup, which effectively alienates it from the string it is supposed to affect.
+
+In most other templates the above behavior is exactly what we want, so this template is an exception. We need to figure out a way to recognize these exceptional templates and then deal with them.
+
+But there is another issue - this is going to be a design challenge, too. 
+
+""RLM"" is an invisible character, so when we look at the article itself we have no indication that there is any special notation or character inside a sentence or a word. So, when we let users edit this in VisualEditor, we have to see how we can allow RLM to affect the word (so, it needs to not be encapsulated with html) *but* we also have to make sure a user can see it is there and, hopefully, interact with it.
+
+We need to come up with creative ways on how to allow user interaction. 
+
+What happens, for example, if a user removes the string the RLM was attached to without removing the RLM character itself? The user may not know about it if it is invisible, and it can cause problems in the edit and later edit in that sentence.
+
+
+I think we might want to consider shifting from RLM templates, that provide directionality change in a string, to language annotations, that provide the same thing *plus* language definition. This is what we're moving towards anyways. It provides more information and it lets the user interact with the language definition. 
+
+I understand that if we do it we will get dirty diffs, but I am not entirely sure how we can deal with RLM properly in the editor -- and is it not in any case preferable to use full-information language annotation instead of a limited-behavior RLM character?",task_subcomment,"['This is a bit more complicated than removing a css definition.', 'As far as I understand this is what happens -- \n\n1.', 'Parsoid recognizes {{כ}} as a template (expected) and sends it to VE as a transclusion object.', '2.', 'VE treats it as transclusion object (as expected) --- but this means that-\n3.', 'The content of the transclusion/template is wrapped with transclusion node markup.', 'This means that the RLM code is now wrapped with html markup, which effectively alienates it from the string it is supposed to affect.', 'In most other templates the above behavior is exactly what we want, so this template is an exception.', 'We need to figure out a way to recognize these exceptional templates and then deal with them.', 'But there is another issue - this is going to be a design challenge, too.', '""RLM"" is an invisible character, so when we look at the article itself we have no indication that there is any special notation or character inside a sentence or a word.', 'So, when we let users edit this in VisualEditor, we have to see how we can allow RLM to affect the word (so, it needs to not be encapsulated with html) *but* we also have to make sure a user can see it is there and, hopefully, interact with it.', 'We need to come up with creative ways on how to allow user interaction.', 'What happens, for example, if a user removes the string the RLM was attached to without removing the RLM character itself?', 'The user may not know about it if it is invisible, and it can cause problems in the edit and later edit in that sentence.', 'I think we might want to consider shifting from RLM templates, that provide directionality change in a string, to language annotations, that provide the same thing *plus* language definition.', ""This is what we're moving towards anyways."", 'It provides more information and it lets the user interact with the language definition.', 'I understand that if we do it we will get dirty diffs, but I am not entirely sure how we can deal with RLM properly in the editor -- and is it not in any case preferable to use full-information language annotation instead of a limited-behavior RLM character?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+254573,VisualEditor: A template with the RLM control character doesn't work when editing in VE,"Hint: when disabling inline-block display for the template 
+(e.g removing:
+.ve-ce-mwTransclusionInlineNode {
+    display: inline-block;
+}
+)
+it behaves properly.",task_subcomment,['Hint: when disabling inline-block display for the template \n(e.g removing:\n.ve-ce-mwTransclusionInlineNode {\n    display: inline-block;\n}\n)\nit behaves properly.'],['OBSERVED BUG BEHAVIOR']
+254567,VisualEditor: A template with the RLM control character doesn't work when editing in VE,See https://he.wikipedia.org/wiki/User:Amire80/ve-rlm for a demostration.,task_subcomment,['See URL for a demostration.'],['INVESTIGATION AND EXPLORATION']
+53957,"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (, , etc), leading to corruption, and prevents down arrow button navigation","1. https://en.wikipedia.org/wiki/User:Raymond/Gallery?veaction=edit
+2. Put the cursor after the first ':'
+3. Press the down arrow - cursor should now be far right of window, beside the gallery
+4. Type 'a'
+5. Press Control-Z
+
+Results vary.
+
+1. Sometimes two characters will appear: 'A'  'a', and 'Save page' is enabled.  Control-Z removes only one of them, and the 'Save page' button returns to disabled, with one added character still on the screen.
+
+2. Sometimes a pawn appears.
+
+3. Sometimes only one character appears, and the 'Save page' button remains disabled.
+
+On the gallery at the bottom of https://de.wikipedia.org/wiki/Hollenegg?veaction=edit , option (3) happens most often.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53750
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56248",task_description,"['VisualEditor: Firefox allows cursor to get into illegal position around wide objects (, , etc), leading to corruption, and prevents down arrow button navigation\n\n1.', 'URL\n2.', ""Put the cursor after the first ':'\n3."", 'Press the down arrow - cursor should now be far right of window, beside the gallery\n4.', ""Type 'a'\n5."", 'Press Control-Z\n\nResults vary.', '1.', ""Sometimes two characters will appear: 'A'  'a', and 'Save page' is enabled."", ""Control-Z removes only one of them, and the 'Save page' button returns to disabled, with one added character still on the screen."", '2.', 'Sometimes a pawn appears.', '3.', ""Sometimes only one character appears, and the 'Save page' button remains disabled."", 'On the gallery at the bottom of URL , option (3) happens most often.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253605,"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (, , etc), leading to corruption, and prevents down arrow button navigation","I believe that this is now fixed, after the Firefox CE re-write, though I could be wrong – please re-open if so.",task_subcomment,"['I believe that this is now fixed, after the Firefox CE re-write, though I could be wrong –\xa0please re-open if so.']",['BUG REPRODUCTION']
+253601,"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (, , etc), leading to corruption, and prevents down arrow button navigation","In addition to , and corruption, a less significant problem is that the down cursor becomes stuck at any block that consumes the entire page with (such as the references block or navbars); pressing the down arrow on the keyboard does not move the cursor to the next item underneath the block.
+
+Steps to reproduce:
+1. Load any page in VE with a references block and something underneath it. e.g.
+   https://en.wikipedia.org/wiki/Jos%C3%A9_Cl%C3%A1udio_Ribeiro_da_Silva?veaction=edit
+   https://en.wikipedia.org/wiki/Marty_Callaghan?veaction=edit
+
+   or a similar block like in this article
+
+   https://en.wikipedia.org/w/index.php?title=Mary_Louise_Smith_%28Republican_Party_leader%29&veaction=edit
+
+2. Repeat pressing down key to reach the bottom of the article
+
+Expected results:
+Down key continues to step down through the article until it reaches the bottom.
+
+Actual results:
+Down key works until the references block.  It becomes stuck on the right hand side of the block.
+
+Im adding this here as it appears to be the exact same underlying problem, as typing when the cursor is on the right-hand side of other wide objects, such as references, also produces unexpected results.",task_subcomment,"['In addition to , and corruption, a less significant problem is that the down cursor becomes stuck at any block that consumes the entire page with (such as the references block or navbars); pressing the down arrow on the keyboard does not move the cursor to the next item underneath the block.', 'Steps to reproduce:\n1.', 'Load any page in VE with a references block and something underneath it.', 'e.g.', 'URL\n   URL\n\n   or a similar block like in this article\n\n   URL\n\n2.', 'Repeat pressing down key to reach the bottom of the article\n\nExpected results:\nDown key continues to step down through the article until it reaches the bottom.', 'Actual results:\nDown key works until the references block.', 'It becomes stuck on the right hand side of the block.', 'Im adding this here as it appears to be the exact same underlying problem, as typing when the cursor is on the right-hand side of other wide objects, such as references, also produces unexpected results.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253598,"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (, , etc), leading to corruption, and prevents down arrow button navigation","Confirmed bug in Firefox. Specifically:
+
+(In reply to comment #0)
+> 1. https://en.wikipedia.org/wiki/User:Raymond/Gallery?veaction=edit
+> 2. Put the cursor after the first ':'
+> 3. Press the down arrow - cursor should now be far right of window, beside
+> the gallery
+
+No, it really shouldn't - it should be in the next heading (""Anzahl Bilder pro Reihe: perrow=2""). See the behaviour in Chrome/Safari for reference. This is a bug specific to Firefox AFAICT.",task_subcomment,"['Confirmed bug in Firefox.', 'Specifically:\n\n(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo, it really shouldn\'t - it should be in the next heading (""Anzahl Bilder pro Reihe: perrow=2"").', 'See the behaviour in Chrome/Safari for reference.', 'This is a bug specific to Firefox AFAICT.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253595,"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (, , etc), leading to corruption, and prevents down arrow button navigation","Reliable snowmen
+
+1. https://de.wikipedia.org/wiki/Benutzer:John_Vandenberg/test?veaction=edit
+2. Place the cursor above the image (which is inside a template)
+3. press down so that the cursor is beside the image/template
+4. press 'a'
+
+Win: snowman + 'a'",task_subcomment,"['Reliable snowmen\n\n1.', 'URL\n2.', ""Place the cursor above the image (which is inside a template)\n3. press down so that the cursor is beside the image/template\n4. press 'a'\n\nWin: snowman + 'a'""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+53933,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,"Overlapping template selection box in Firefox 22 on Linux
+
+When templates do not have a defined width the blue selection box extends the whole width of the window, regardless of whether the template does. This means that in some cases, e.g. at [[Where Does This Door Go]], the transclusion editor icon is displayed not on top of the template.
+
+More seriously it also means that smaller templates to the right of larger ones are difficult of impossible to access because they are completely covered by the other template's selection box. At the same article, the ""Professional ratings"" translcusion is difficult to select (you need to click it in line with the slug between the templates on the left) and the tooltip icon does not appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49922
+
+**Attached**: {F11785}",task_description,"['VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access\n\nOverlapping template selection box in Firefox 22 on Linux\n\nWhen templates do not have a defined width the blue selection box extends the whole width of the window, regardless of whether the template does.', 'This means that in some cases, e.g.', 'at [[Where Does This Door Go]], the transclusion editor icon is displayed not on top of the template.', ""More seriously it also means that smaller templates to the right of larger ones are difficult of impossible to access because they are completely covered by the other template's selection box."", 'At the same article, the ""Professional ratings"" translcusion is difficult to select (you need to click it in line with the slug between the templates on the left) and the tooltip icon does not appear.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\n\n**Attached**: {F11785}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+252427,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,Both of the examples linked to work now.,task_subcomment,['Both of the examples linked to work now.'],['SOLUTION USAGE']
+252422,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,Partially mitigated by the above but I believe not fixed. Resetting.,task_subcomment,"['Partially mitigated by the above but I believe not fixed.', 'Resetting.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+252420,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,"Change 138338 merged by jenkins-bot:
+Special case for shielding of generated content wrappers
+
+https://gerrit.wikimedia.org/r/138338",task_subcomment,['Change 138338 merged by jenkins-bot:\nSpecial case for shielding of generated content wrappers\n\nGERRIT_URL'],['ACTION ON ISSUE']
+252416,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,"Change 138338 had a related patch set uploaded by Esanders:
+Special case for shielding of generated content wrappers
+
+https://gerrit.wikimedia.org/r/138338",task_subcomment,['Change 138338 had a related patch set uploaded by Esanders:\nSpecial case for shielding of generated content wrappers\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+252411,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,*** Bug 54301 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54301 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252405,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,*** Bug 50970 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50970 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252398,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,The edit icon showing up in random places is also mentioned at https://bugzilla.wikimedia.org/show_bug.cgi?id=51548 .,task_subcomment,['The edit icon showing up in random places is also mentioned at URL .'],['OBSERVED BUG BEHAVIOR']
+252392,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,"*overlapping blocks, or templates, or whatever, you understood me :)",task_subcomment,"['*overlapping blocks, or templates, or whatever, you understood me :)']",['SOLUTION DISCUSSION']
+252385,VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,"I arrived here to document the same situation. A user at en.wp reports he's not able to edit reviews with VE at http://en.wikipedia.org/wiki/X_(Def_Leppard_album) because of the overlapping windows. While for me this is certainly the case with FF, with Chrome instead I am able to select the template if I click on the Review Scores line. This said, the icon to actually edit contents only appears... at the top of the Infobox album - definitely not where one would expect it to.",task_subcomment,"['I arrived here to document the same situation.', ""A user at en.wp reports he's not able to edit reviews with VE at URL because of the overlapping windows."", 'While for me this is certainly the case with FF, with Chrome instead I am able to select the template if I click on the Review Scores line.', 'This said, the icon to actually edit contents only appears... at the top of the Infobox album - definitely not where one would expect it to.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+53918,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"Cloning from bug 50897 comment 2:
+
+In the old editor, I would simply use TAB to reach the edit summary, type my
+edit summary and press ENTER to activate the ""Save page"" button and save. If I
+wanted to mark the edit minor, then I could type my edit summary, press TAB,
+SPACE, and then ENTER to ""Save page"".
+
+I can see that the new box for entering an edit summary allows newlines to be
+entered. I am not sure this is a good idea, because I just used a WSYIWYG
+editor and now ""What I see"" - well-formatted paragraphs describing my edit - is
+not going to be ""what I get"" - everything smashed on one line in the article
+history. But that is perhaps grist for another bug mill.
+
+It seems that the ""Save page"" button never receives caret focus if I use TAB to
+try to get there. This would seem to have accessibility ramifications.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Change tab order in save dialog to be more like the wikitext editor\'s save form\n\nCloning from bug 50897 comment 2:\n\nIn the old editor, I would simply use TAB to reach the edit summary, type my\nedit summary and press ENTER to activate the ""Save page"" button and save.', 'If I\nwanted to mark the edit minor, then I could type my edit summary, press TAB,\nSPACE, and then ENTER to ""Save page"".', 'I can see that the new box for entering an edit summary allows newlines to be\nentered.', 'I am not sure this is a good idea, because I just used a WSYIWYG\neditor and now ""What I see"" - well-formatted paragraphs describing my edit - is\nnot going to be ""what I get"" - everything smashed on one line in the article\nhistory.', 'But that is perhaps grist for another bug mill.', 'It seems that the ""Save page"" button never receives caret focus if I use TAB to\ntry to get there.', 'This would seem to have accessibility ramifications.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+251362,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"At least for me, this is not browser-specific: I get the problem in both Chrome and FFox. (The other problem is, I agree, browser-specific.)",task_subcomment,"['At least for me, this is not browser-specific: I get the problem in both Chrome and FFox.', '(The other problem is, I agree, browser-specific.)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251354,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"(In reply to Luis Villa (personal-for work use lvilla@wikimedia.org) from comment #11)
+> This is broken (again?) The three license links come up before the action
+> buttons (and save page never comes up, but that is bug 50047 I think?)
+
+Was going to re-open, but because it's a browser-specific issue I've instead opened bug 65554 to get this fixed.",task_subcomment,"[""(In reply to Luis Villa (personal-for work use lvilla@wikimedia.org) from comment #11)\nQUOTE\nQUOTE\n\nWas going to re-open, but because it's a browser-specific issue I've instead opened bug 65554 to get this fixed.""]",['ACTION ON ISSUE']
+251348,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"This is broken (again?) The three license links come up before the action buttons (and save page never comes up, but that is bug 50047 I think?)",task_subcomment,"['This is broken (again?)', 'The three license links come up before the action buttons (and save page never comes up, but that is bug 50047 I think?)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251345,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,*** Bug 53257 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53257 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251340,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"The fix for this is now merged and will be deployed on Thursday 10 October to MediaWiki.org, and to Wikipedias on Thursday 17 October.",task_subcomment,"['The fix for this is now merged and will be deployed on Thursday 10 October to MediaWiki.org, and to Wikipedias on Thursday 17 October.']",['SOLUTION USAGE']
+251335,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",task_subcomment,['Change 81876 merged by jenkins-bot:\nMake the save dialog an actual dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+251331,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",task_subcomment,['Change 81876 had a related patch set uploaded by Jforrester:\nMake the save dialog an actual dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+251327,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,*** Bug 53257 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53257 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251322,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"Dcoetzee at en.wp reports that the tab order differs in different browsers, and that at a certain point in firefox the focus gets stuck and neither tab nor shift-tab can move it.
+
+The full comment is below:
+    ""On Chrome Version 28.0.1500.95 m on Windows 7 x64: It starts in the edit summary field, goes to the ""minor edit"" link (not the checkbox), then the Save page button, then the Review your changes button (moving right to left), then the three links in the small text at the bottom, then the address bar, then the Search box, then the minor edit checkbox, then the ""Interactions"" menu drop down on the left sidebar (???), then the Watch this page checkbox. If I use SHIFT+TAB it goes to Edit summary link, then jumps straight to the Mediawiki logo way in the bottom right.
+
+    On Firefox 22.0 and 23.0 on Windows 7 x64: It starts in the edit summary field, goes to the ""minor edit"" link (not the checkbox), then the Save page button, then thereafter neither TAB nor SHIFT+TAB do anything (focus is stuck - this is a serious problem as it may require reloading the page and losing edits). SHIFT+TAB is same as in Chrome.
+
+Conventionally, tab order is supposed to go in a logical reading order: left-to-right, top-to-bottom. My expected order was something like this:
+
+    Starts in edit summary field, goes to minor edit checkbox, then minor edit link, then Watch this page checkbox, then Review your changes button, then Save page button, then the three links at the bottom. If I use SHIFT+TAB to tab backwards, I expect to visit the Edit summary link, then (if possible) the arrow to collapse/abort the Save, then the Search box.""",task_subcomment,"['Dcoetzee at en.wp reports that the tab order differs in different browsers, and that at a certain point in firefox the focus gets stuck and neither tab nor shift-tab can move it.', 'The full comment is below:\n    ""On Chrome Version 28.0.1500.95 m on Windows 7 x64: It starts in the edit summary field, goes to the ""minor edit"" link (not the checkbox), then the Save page button, then the Review your changes button (moving right to left), then the three links in the small text at the bottom, then the address bar, then the Search box, then the minor edit checkbox, then the ""Interactions"" menu drop down on the left sidebar (???', '), then the Watch this page checkbox.', 'If I use SHIFT+TAB it goes to Edit summary link, then jumps straight to the Mediawiki logo way in the bottom right.', 'On Firefox 22.0 and 23.0 on Windows 7 x64: It starts in the edit summary field, goes to the ""minor edit"" link (not the checkbox), then the Save page button, then thereafter neither TAB nor SHIFT+TAB do anything (focus is stuck - this is a serious problem as it may require reloading the page and losing edits).', 'SHIFT+TAB is same as in Chrome.', 'Conventionally, tab order is supposed to go in a logical reading order: left-to-right, top-to-bottom.', 'My expected order was something like this:\n\n    Starts in edit summary field, goes to minor edit checkbox, then minor edit link, then Watch this page checkbox, then Review your changes button, then Save page button, then the three links at the bottom.', 'If I use SHIFT+TAB to tab backwards, I expect to visit the Edit summary link, then (if possible) the arrow to collapse/abort the Save, then the Search box.""']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+251314,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"There has been a slight change to this recently but it is still wrong.
+
+Current behaviour: Pressing tab from the summary box leads to the minor edit link
+Desired behaviour: It should lead to the minor edit checkbox (not the link)",task_subcomment,"['There has been a slight change to this recently but it is still wrong.', 'Current behaviour: Pressing tab from the summary box leads to the minor edit link\nDesired behaviour: It should lead to the minor edit checkbox (not the link)']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+251308,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,*** Bug 52080 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52080 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251300,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"That is an enhancement MZMcBride.
+
+*** This bug has been marked as a duplicate of bug 50047 ***",task_subcomment,"['That is an enhancement MZMcBride.', '*** This bug has been marked as a duplicate of bug 50047 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+251292,VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form,"Yeah, VisualEditor is kind of disruptive in this way. I'd like some further thought here.",task_subcomment,"['Yeah, VisualEditor is kind of disruptive in this way.', ""I'd like some further thought here.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53915,VisualEditor: Return of the invalid token on save attempt problem?,"(This sounds exactly like bug 50424, but that was marked fixed on 2013-07-15 with ""deployed within the hour"".)
+
+I had made source edits to a mediawiki.org page over https. Looking at it 30+ minutes later I wanted to make one more quick edit, so I clicked [Edit].  VE worked fine, Save dialog, [Review your changes] worked, but the final [Save page] drew blue bars before doing nothing.
+
+Firebug's network console showed the API requst visualeditoredit with 
+  basetimestamp	20130723212405
+  format	json
+  minor	1
+  oldid	745108
+  page	Manual:How_to_debug
+  starttimestamp	20130723232059
+was failing with 
+  {""servedby"":""mw1139"",""error"":{""code"":""badtoken"",""info"":""Invalid token""}}
+
+I had a similar occurrence a few days ago where the API reported badtoken. I can't remember the specifics of that, but I assumed it was my mistake because I was using multiple accounts on different wikis.  This time I wasn't doing anything special.  Connecting to https://www.mediawiki.org/wiki/Special:Version in another tab shows me as still logged in.
+
+Maybe there are two bugs here: VE's inability to recover from this, and the lack of a ""VE had an internal error"" with suggestion as to how to what to do (e.g. copy the right-hand column of [Review changes]. Regarding the former, when I've lost state with source editing I usually find [Show preview] brings it back, maybe VE can implement something like this internally.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Return of the invalid token on save attempt problem?', '(This sounds exactly like bug 50424, but that was marked fixed on 2013-07-15 with ""deployed within the hour"".)', 'I had made source edits to a mediawiki.org page over https.', 'Looking at it 30+ minutes later I wanted to make one more quick edit, so I clicked [Edit].', 'VE worked fine, Save dialog, [Review your changes] worked, but the final [Save page] drew blue bars before doing nothing.', 'Firebug\'s network console showed the API requst visualeditoredit with \n  basetimestamp\t20130723212405\n  format\tjson\n  minor\t1\n  oldid\t745108\n  page\tManual:How_to_debug\n  starttimestamp\t20130723232059\nwas failing with \n  {""servedby"":""mw1139"",""error"":{""code"":""badtoken"",""info"":""Invalid token""}}\n\nI had a similar occurrence a few days ago where the API reported badtoken.', ""I can't remember the specifics of that, but I assumed it was my mistake because I was using multiple accounts on different wikis."", ""This time I wasn't doing anything special."", 'Connecting to URL in another tab shows me as still logged in.', 'Maybe there are two bugs here: VE\'s inability to recover from this, and the lack of a ""VE had an internal error"" with suggestion as to how to what to do (e.g.', 'copy the right-hand column of [Review changes].', ""Regarding the former, when I've lost state with source editing I usually find [Show preview] brings it back, maybe VE can implement something like this internally."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+251119,VisualEditor: Return of the invalid token on save attempt problem?,This was fixed in gerrit 76859 which was merged yesterday and will go out today.,task_subcomment,['This was fixed in gerrit 76859 which was merged yesterday and will go out today.'],['SOLUTION USAGE']
+251112,VisualEditor: Return of the invalid token on save attempt problem?,"**mael.leguevel** wrote:
+
+I had the same message with the following scenario:
+Edit an article, not logged in. Then, log in from another tab. Trying to save the article from the first tab, I get the same error message.",task_subcomment,"['**mael.leguevel** wrote:\n\nI had the same message with the following scenario:\nEdit an article, not logged in.', 'Then, log in from another tab.', 'Trying to save the article from the first tab, I get the same error message.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+251105,VisualEditor: Return of the invalid token on save attempt problem?,"en.wp editor Rpyle731 has just reported an occurrence of this:
+""While putting in stub templates in article ""[[Zhang Shi (prince)]]"" using the visual editor, when trying to save I got the text 
+
+""Error loading data from server. Unsuccessful request: Invalid token.""""",task_subcomment,"['en.wp editor Rpyle731 has just reported an occurrence of this:\n""While putting in stub templates in article ""[[Zhang Shi (prince)]]"" using the visual editor, when trying to save I got the text \n\n""Error loading data from server.', 'Unsuccessful request: Invalid token.""""']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251098,VisualEditor: Return of the invalid token on save attempt problem?,"(In reply to comment #1)
+FWIW when I investigated this by clicking the final [Save page] again, I only saw the one visualeditoredit API request in Firebug's Network tab.",task_subcomment,"[""(In reply to comment #1)\nFWIW when I investigated this by clicking the final [Save page] again, I only saw the one visualeditoredit API request in Firebug's Network tab.""]",['OBSERVED BUG BEHAVIOR']
+251091,VisualEditor: Return of the invalid token on save attempt problem?,"When the API responds with badtoken, VE *should* refetch the token and try again. I'm fairly sure that was implemented, but not 100% sure.",task_subcomment,"['When the API responds with badtoken, VE *should* refetch the token and try again.', ""I'm fairly sure that was implemented, but not 100% sure.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+53902,VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog,"If you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog\n\nIf you look at page settings under URL you\'ll see the category ""Wikipedia"".', ""This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+250163,VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog,Now fixed in master.,task_subcomment,['Now fixed in master.'],['SOLUTION DISCUSSION']
+250157,VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog,"Change 75859 merged by jenkins-bot:
+Parse category names correctly
+
+https://gerrit.wikimedia.org/r/75859",task_subcomment,['Change 75859 merged by jenkins-bot:\nParse category names correctly\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250151,VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog,"Change 75859 had a related patch set uploaded by Esanders:
+Parse category names correctly
+
+https://gerrit.wikimedia.org/r/75859",task_subcomment,['Change 75859 had a related patch set uploaded by Esanders:\nParse category names correctly\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250147,VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog,"This style of category name also appears at de.wikipedia, e.g., [[:de:Kategorie:Wikipedia:Schnelllöschen]].",task_subcomment,"['This style of category name also appears at de.wikipedia, e.g., [[:de:Kategorie:Wikipedia:Schnelllöschen]].']",['OBSERVED BUG BEHAVIOR']
+53883,VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia,"The error can be seen at http://ja.wikipedia.org/w/index.php?title=ロマン主義&diff=prev&oldid=48242310
+
+Each language template in the lead sentence (e.g., {{lang-en}}, used for providing translations of the article title into English) was replaced by two snowmen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://ja.wikipedia.org/w/index.php?title=ロマン主義&diff=prev&oldid=48242310",task_description,"['VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia\n\nThe error can be seen at URL\n\nEach language template in the lead sentence (e.g., {{lang-en}}, used for providing translations of the article title into English) was replaced by two snowmen.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+249259,VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia,I think that this was finally fixed in Roan's great re-working of snowmen.,task_subcomment,"[""I think that this was finally fixed in Roan's great re-working of snowmen.""]",['SOLUTION DISCUSSION']
+249255,VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia,"I have just duplicated this in Thai wikipedia.  Not only does the {{lang-en}} template turn into snowmen, the surrounding text gets rendered into (bolded) English upon saving. 
+
+Diff:https://th.wikipedia.org/w/index.php?title=%E0%B8%81%E0%B8%8E%E0%B8%AB%E0%B8%A1%E0%B8%B2%E0%B8%A2%E0%B8%9B%E0%B8%B4%E0%B8%94%E0%B8%9B%E0%B8%B2%E0%B8%81&diff=5062666&oldid=4871033
+
+Chrome 28.0.1500.71, OS 10.6.8",task_subcomment,"['I have just duplicated this in Thai wikipedia.', 'Not only does the {{lang-en}} template turn into snowmen, the surrounding text gets rendered into (bolded) English upon saving.', 'Diff:URL\n\nChrome 28.0.1500.71, OS 10.6.8']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249249,VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia,"I quickly tried to reproduce this, and failed.  It might have been fixed by improvements to the code.  It would be good if someone can ask B637pcgt what they did to cause this issue.
+
+jawp still has only a few VE edits per day
+https://ja.wikipedia.org/wiki/special:recentchanges?tagfilter=visualeditor&days=30&limit=500",task_subcomment,"['I quickly tried to reproduce this, and failed.', 'It might have been fixed by improvements to the code.', 'It would be good if someone can ask B637pcgt what they did to cause this issue.', 'jawp still has only a few VE edits per day\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53851,"VisualEditor: By default, images should not set the alignment","The VisualEditor explicitly sets all images that are inserted using the dialog as thumb and right. ""thumb"" is fine, because it's not default, but that's what people want most of the time, but ""right"" shouldn't be there. ""right"" is the default for left-to-right Wikipedias, so it's redundant in English. The default for right-to-left Wikipedias is ""left"", so for these languages this behavior is unexpected.
+
+The best solution is simply not to set the alignment and let the user change if it is needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: By default, images should not set the alignment\n\nThe VisualEditor explicitly sets all images that are inserted using the dialog as thumb and right.', '""thumb"" is fine, because it\'s not default, but that\'s what people want most of the time, but ""right"" shouldn\'t be there.', '""right"" is the default for left-to-right Wikipedias, so it\'s redundant in English.', 'The default for right-to-left Wikipedias is ""left"", so for these languages this behavior is unexpected.', 'The best solution is simply not to set the alignment and let the user change if it is needed.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+247432,"VisualEditor: By default, images should not set the alignment","Change 75526 merged by jenkins-bot:
+Image insertion alignment fix
+
+https://gerrit.wikimedia.org/r/75526",task_subcomment,['Change 75526 merged by jenkins-bot:\nImage insertion alignment fix\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247429,"VisualEditor: By default, images should not set the alignment","Change 75526 had a related patch set uploaded by Mooeypoo:
+Image insertion alignment fix
+
+https://gerrit.wikimedia.org/r/75526",task_subcomment,['Change 75526 had a related patch set uploaded by Mooeypoo:\nImage insertion alignment fix\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+247426,"VisualEditor: By default, images should not set the alignment",*** Bug 51295 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51295 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247423,"VisualEditor: By default, images should not set the alignment","Unless I'm missing something, just remove if it's the default anyway. See an example:
+https://en.wikipedia.org/wiki/User:Amire80/ve_default_image_alignment",task_subcomment,"[""Unless I'm missing something, just remove if it's the default anyway."", 'See an example:\nURL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+247417,"VisualEditor: By default, images should not set the alignment",Should we remove the alignment completely (and risk people not putting one in? what's the potential side-effect of that?) or change the 'right' to 'left' on RTL wikis?,task_subcomment,"['Should we remove the alignment completely (and risk people not putting one in?', ""what's the potential side-effect of that?)"", ""or change the 'right' to 'left' on RTL wikis?""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+53828,VisualEditor: Autocompletion for template names doesn't work in RTL,"Given that I'm editing an article in an RTL wiki: https://he.wikipedia.org/wiki/ASCII
+   And I press the ""Transclude"" button in the toolbar (puzzle piece)
+   And I type ""A""
+Then I should see a list of autocompletions of templates that start with A
+
+Currently I don't see a list of autocompletions.
+
+This bug is quite similar to Bug 51490.
+
+[This was an experiment with writing bug reports as Cucumber-style test scenarios. Let me know if you don't like it.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Autocompletion for template names doesn\'t work in RTL\n\nGiven that I\'m editing an article in an RTL wiki: URL\n   And I press the ""Transclude"" button in the toolbar (puzzle piece)\n   And I type ""A""\nThen I should see a list of autocompletions of templates that start with A\n\nCurrently I don\'t see a list of autocompletions.', 'This bug is quite similar to Bug 51490.', '[This was an experiment with writing bug reports as Cucumber-style test scenarios.', ""Let me know if you don't like it.]"", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+246135,VisualEditor: Autocompletion for template names doesn't work in RTL,"Done and will be deployed tomorrow. Thanks, Moriel!",task_subcomment,"['Done and will be deployed tomorrow.', 'Thanks, Moriel!']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+246130,VisualEditor: Autocompletion for template names doesn't work in RTL,"This bug will be fixed with this patchset: https://gerrit.wikimedia.org/r/#/c/74835/
+
+See also https://bugzilla.wikimedia.org/show_bug.cgi?id=51490",task_subcomment,['This bug will be fixed with this patchset: URL\n\nSee also URL'],['SOLUTION USAGE']
+53819,VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis,"screenshot
+
+When you click an infobox template in an RTL wiki, the puzzle piece icon is supposed to appear somewhere on the transparent blue background to make the template editable.
+
+In an RTL wiki, this template appears outside of the transparent blue area on the other side of the screen.
+
+You can test it with the following article:
+https://he.wikipedia.org/wiki/%D7%9C%D7%95%D7%93?veaction=edit
+
+See also the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11560}",task_description,"['VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis\n\nscreenshot\n\nWhen you click an infobox template in an RTL wiki, the puzzle piece icon is supposed to appear somewhere on the transparent blue background to make the template editable.', 'In an RTL wiki, this template appears outside of the transparent blue area on the other side of the screen.', 'You can test it with the following article:\nURL\n\nSee also the screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11560}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+245647,VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis,Merged and will go out tomorrow.,task_subcomment,['Merged and will go out tomorrow.'],['SOLUTION DISCUSSION']
+245641,VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis,"Change 75246 merged by jenkins-bot:
+Quickfix for Transclusion icon in RTL wikis
+
+https://gerrit.wikimedia.org/r/75246",task_subcomment,['Change 75246 merged by jenkins-bot:\nQuickfix for Transclusion icon in RTL wikis\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245636,VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis,"Change 75246 had a related patch set uploaded by Mooeypoo:
+Quickfix for Transclusion icon in RTL wikis
+
+https://gerrit.wikimedia.org/r/75246",task_subcomment,['Change 75246 had a related patch set uploaded by Mooeypoo:\nQuickfix for Transclusion icon in RTL wikis\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53739,VisualEditor: [Regression] Dialog panels not scrollable,"TempalteData-provided parameter list in template editor is not scrollable.
+
+For example, try adding [[pl:Template:Okręt infobox]] to any article there.
+
+Confirmed on latest versions of Firefox and Opera.
+
+Screenshot: http://i.imgur.com/e3VSqVs.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51672",task_description,"['VisualEditor: [Regression] Dialog panels not scrollable\n\nTempalteData-provided parameter list in template editor is not scrollable.', 'For example, try adding [[pl:Template:Okręt infobox]] to any article there.', 'Confirmed on latest versions of Firefox and Opera.', 'Screenshot: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240973,VisualEditor: [Regression] Dialog panels not scrollable,Done and will be deployed tomorrow.,task_subcomment,['Done and will be deployed tomorrow.'],['ACTION ON ISSUE']
+240969,VisualEditor: [Regression] Dialog panels not scrollable,"Change 74836 merged by jenkins-bot:
+Ensure ve-ui-panelLayout-scrollable is actually scrollable
+
+https://gerrit.wikimedia.org/r/74836",task_subcomment,['Change 74836 merged by jenkins-bot:\nEnsure ve-ui-panelLayout-scrollable is actually scrollable\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+240964,VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51810 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51810 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240959,VisualEditor: [Regression] Dialog panels not scrollable,Patch by Rillke from bug 51793: https://gerrit.wikimedia.org/r/75083,task_subcomment,['Patch by Rillke from bug 51793: GERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+240955,VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51793 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51793 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240947,VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51671 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51671 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240939,VisualEditor: [Regression] Dialog panels not scrollable,"Change 74836 had a related patch set uploaded by Matmarex:
+Ensure ve-ui-panelLayout-scrollable is actually scrollable
+
+https://gerrit.wikimedia.org/r/74836",task_subcomment,['Change 74836 had a related patch set uploaded by Matmarex:\nEnsure ve-ui-panelLayout-scrollable is actually scrollable\n\nGERRIT_URL'],['ACTION ON ISSUE']
+240931,VisualEditor: [Regression] Dialog panels not scrollable,Caused by 8409d16f0f2392cea321aa3d8d6bc692f3f04f27,task_subcomment,['Caused by 8409d16f0f2392cea321aa3d8d6bc692f3f04f27'],['OBSERVED BUG BEHAVIOR']
+53734,TemplateData: Create an editor for template data (in the wikitext editor),"GUI for the existing TemplateDataEditor
+
+Not the same as bug 50964: it would be really nice to provide a tool for editing TemplateData also outside VisualEditor (I even think it's better than inside VisualEditor because VE doesn't work on Template namespace right now).
+
+The existing TemplateDataEditor script (created by Ltrlg on frwiki, translated for enwiki by me), can be a good start. Benefits for including some equivalent in TemplateData extensions are important :
+* Available to all wikis
+* Translations can be done like they are done for TemplateData
+
+Links :
+* http://en.wikipedia.org/wiki/User:NicoV/TemplateDataEditor
+* http://fr.wikipedia.org/wiki/Utilisateur:Ltrlg/scripts/TemplateDataEditor.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50169
+
+**Attached**: {F11375}",task_description,"[""TemplateData: Create an editor for template data (in the wikitext editor)\n\nGUI for the existing TemplateDataEditor\n\nNot the same as bug 50964: it would be really nice to provide a tool for editing TemplateData also outside VisualEditor (I even think it's better than inside VisualEditor because VE doesn't work on Template namespace right now)."", 'The existing TemplateDataEditor script (created by Ltrlg on frwiki, translated for enwiki by me), can be a good start.', 'Benefits for including some equivalent in TemplateData extensions are important :\n* Available to all wikis\n* Translations can be done like they are done for TemplateData\n\nLinks :\n* URL\n* URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\n\n**Attached**: {F11375}']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+240753,TemplateData: Create an editor for template data (in the wikitext editor),Follow-up in 60158.,task_subcomment,['Follow-up in 60158.'],['OBSERVED BUG BEHAVIOR']
+240749,TemplateData: Create an editor for template data (in the wikitext editor),"Created attachment 14428
+TemplateDataGenertor screenshot
+
+I made a screenshot. I’ve cropped it to show only TemplateDataGenerator: it is a jQuery UI dialog centered on the screen.
+
+**Attached**: {F11377}",task_subcomment,"['Created attachment 14428\nTemplateDataGenertor screenshot\n\nI made a screenshot.', 'I’ve cropped it to show only TemplateDataGenerator: it is a jQuery UI dialog centered on the screen.', '**Attached**: {F11377}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240739,TemplateData: Create an editor for template data (in the wikitext editor),"As I said, the current information (or lack of) is confusing. Is there any wiki page or screenshot or anything we can link to?
+
+In any case, ca.wiki wants to try it.  :)",task_subcomment,"['As I said, the current information (or lack of) is confusing.', 'Is there any wiki page or screenshot or anything we can link to?', 'In any case, ca.wiki wants to try it.', ':)']","['OBSERVED BUG BEHAVIOR', 'CONTRIBUTION AND COMMITMENT', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+240733,TemplateData: Create an editor for template data (in the wikitext editor),"$wgTemplateDataUseGUI activates neither TemplateDataEditor nor TDSkell but TemplateDataGenerator. The two screenshots attached to this bug are for 'TemplateDataEditor' and 'TemplateData Editor', so the one you gave on cawiki is not correct.",task_subcomment,"['$wgTemplateDataUseGUI activates neither TemplateDataEditor nor TDSkell but TemplateDataGenerator.', ""The two screenshots attached to this bug are for 'TemplateDataEditor' and 'TemplateData Editor', so the one you gave on cawiki is not correct.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240726,TemplateData: Create an editor for template data (in the wikitext editor),"ca.wiki is also happy to test it, see https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Propostes#Activar_TemplateDataEditor",task_subcomment,"['ca.wiki is also happy to test it, see URL']",['INVESTIGATION AND EXPLORATION']
+240718,TemplateData: Create an editor for template data (in the wikitext editor),"**M8R-0p6s0d** wrote:
+
+Hi, we would like to try the TempalteDataEditor on NL wiki, see https://nl.wikipedia.org/wiki/Wikipedia:De_kroeg#Aanzetten_TemplateData-editor_op_nl-wiki",task_subcomment,"['**M8R-0p6s0d** wrote:\n\nHi, we would like to try the TempalteDataEditor on NL wiki, see URL']",['ACTION ON ISSUE']
+240712,TemplateData: Create an editor for template data (in the wikitext editor),"No, this is the GUI we developed hidden behind $wgTemplateDataUseGUI.",task_subcomment,"['No, this is the GUI we developed hidden behind $wgTemplateDataUseGUI.']",['SOLUTION DISCUSSION']
+240705,TemplateData: Create an editor for template data (in the wikitext editor),"(In reply to comment #11)
+> If
+> a particular wiki is happy to be a guinea pig we can switch it on there for a
+> little for some real-world testing.
+
+Sound interesting, but I'm missing a bit of background...
+
+Do you mean ""switch on"" https://en.wikipedia.org/wiki/User:Salix_alba/TDSkell ? Would it be enabled to all users of a wiki or can it be restricted to a certain user group in order limit the experiment a bit?
+
+There is clear interest in improving template data coverage in Catalan Wikipedia but, guess what, nobody really enjoys editing JSON syntax.  :)",task_subcomment,"['(In reply to comment #11)\nQUOTE\nQUOTE\nQUOTE\n\nSound interesting, but I\'m missing a bit of background...\n\nDo you mean ""switch on"" URL ?', 'Would it be enabled to all users of a wiki or can it be restricted to a certain user group in order limit the experiment a bit?', 'There is clear interest in improving template data coverage in Catalan Wikipedia but, guess what, nobody really enjoys editing JSON syntax.', ':)']","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+240697,TemplateData: Create an editor for template data (in the wikitext editor),"This is done in I863a8199c0b08cc52b320ed00dcba912dd2aeefc (though it's not yet deployed, as it is currently hidden behind a feature flag). Closing for now. If a particular wiki is happy to be a guinea pig we can switch it on there for a little for some real-world testing.",task_subcomment,"[""This is done in I863a8199c0b08cc52b320ed00dcba912dd2aeefc (though it's not yet deployed, as it is currently hidden behind a feature flag)."", 'Closing for now.', 'If a particular wiki is happy to be a guinea pig we can switch it on there for a little for some real-world testing.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+240691,TemplateData: Create an editor for template data (in the wikitext editor),"Change 85400 had a related patch set uploaded by Jforrester:
+TemplateData Generator GUI
+
+https://gerrit.wikimedia.org/r/85400",task_subcomment,['Change 85400 had a related patch set uploaded by Jforrester:\nTemplateData Generator GUI\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+240683,TemplateData: Create an editor for template data (in the wikitext editor),"Skeleton generator now in javascript and at http://en.wikipedia.org/wiki/User:Salix_alba/TDSkell
+its quite handy for getting a complete list of parameters. The human written documentation is not always upto date.",task_subcomment,"['Skeleton generator now in javascript and at URL\nits quite handy for getting a complete list of parameters.', 'The human written documentation is not always upto date.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+240675,TemplateData: Create an editor for template data (in the wikitext editor),"I don't know how I messed up with the bug number (probably several bugzilla windows opened and I paste the wrong one) ;-) Sorry, bug 50169 of course.
+
+I also think having a button in the toolbar would be a better place than the sidebar.
+
+
+Other possible optimization: combine it with the ""Skeleton generator"" so that parameter names are automatically retrieved from the template source code for initializing the templatedata the first time. Care must be taken since the templatedata will often be on the documentation page.
+
+http://singsurf.org/things/TemplateData.php?Source=true",task_subcomment,"[""I don't know how I messed up with the bug number (probably several bugzilla windows opened and I paste the wrong one) ;-) Sorry, bug 50169 of course."", 'I also think having a button in the toolbar would be a better place than the sidebar.', 'Other possible optimization: combine it with the ""Skeleton generator"" so that parameter names are automatically retrieved from the template source code for initializing the templatedata the first time.', 'Care must be taken since the templatedata will often be on the documentation page.', 'URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+240667,TemplateData: Create an editor for template data (in the wikitext editor),"(In reply to comment #0)
+> Created attachment 12900 [details]
+> GUI for the existing TemplateDataEditor
+> 
+> Not the same as bug 50964
+
+Indeed, bug 50964 is not the same, but also (apparently) completely unrelated. I assume you meant bug 50169.
+
+If this should not (also) be inside VisualEditor, can we be specific in what we want it to be then?
+
+e.g. WikiEditor, legacy toolbar, ...
+
+The referenced gadget 'parses' the wikitext textarea and adds a link in the sidebar toolbox that opens a dialog. I don't think the sidebar would be an acceptable entry point to edit the wikitext. Should be something in the toolbar.
+
+I agree we should re-use the data logic between these 2 or 3 different things. At least we can expose the data logic separately from the plugin we make for VisualEditor so that other ones can be created as gadget (until (if) we make one of the WikiEditor and/or legacy toolbar).
+
+**Attached**: {F11375}",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIndeed, bug 50964 is not the same, but also (apparently) completely unrelated.', 'I assume you meant bug 50169.', 'If this should not (also) be inside VisualEditor, can we be specific in what we want it to be then?', 'e.g.', 'WikiEditor, legacy toolbar, ...', ""The referenced gadget 'parses' the wikitext textarea and adds a link in the sidebar toolbox that opens a dialog."", ""I don't think the sidebar would be an acceptable entry point to edit the wikitext."", 'Should be something in the toolbar.', 'I agree we should re-use the data logic between these 2 or 3 different things.', 'At least we can expose the data logic separately from the plugin we make for VisualEditor so that other ones can be created as gadget (until (if) we make one of the WikiEditor and/or legacy toolbar).', '**Attached**: {F11375}']","['MOTIVATION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+240661,TemplateData: Create an editor for template data (in the wikitext editor),"Created attachment 12957
+Screenshot of http://tools.wikimedia.pl/~mlazowik/templatedata/
+
+**Attached**: {F11376}",task_subcomment,['Created attachment 12957\nScreenshot of URL\n\n**Attached**: {F11376}'],['ATTACHMENT']
+240656,TemplateData: Create an editor for template data (in the wikitext editor),"This is, indeed, not a duplicate of bug 50169, though it might as well be done in one go. Relabelling as such.",task_subcomment,"['This is, indeed, not a duplicate of bug 50169, though it might as well be done in one go.', 'Relabelling as such.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+240654,TemplateData: Create an editor for template data (in the wikitext editor),"(In reply to comment #1)
+> Could you please define what that ""tool"" would exactly do? 
+> Otherwise it will be extremely hard to define when this bug report could be
+> considered ""fixed"" at some point. :)
+
+Being able to edit a  tag in a user frienly way, much like what TemplateDataEditor allows (see the attached screenshot in my first comment). JSON is not very friendly for human editors.
+Basically, a window showing all the informations in the  and allowing a human editor to modify them easily.
+
+Extra advantage of including this in the TemplateData extension :
+* Users don't have to modify their common.js to have access to an editor",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\n\nBeing able to edit a  tag in a user frienly way, much like what TemplateDataEditor allows (see the attached screenshot in my first comment).', 'JSON is not very friendly for human editors.', 'Basically, a window showing all the informations in the  and allowing a human editor to modify them easily.', ""Extra advantage of including this in the TemplateData extension :\n* Users don't have to modify their common.js to have access to an editor""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+240649,TemplateData: Create an editor for template data (in the wikitext editor),"(In reply to comment #0)
+...
+> editing TemplateData also outside VisualEditor (I even think it's better than
+> inside VisualEditor because VE doesn't work on Template namespace right now).
+
+BTW: depending on the resolution of bug 50512, the data might be migrated from Template namespace to a specific one.",task_subcomment,"['(In reply to comment #0)\n...\nQUOTE\nQUOTE\n\nBTW: depending on the resolution of bug 50512, the data might be migrated from Template namespace to a specific one.']",['FUTURE PLAN']
+240644,TemplateData: Create an editor for template data (in the wikitext editor),Tool = something at least as good as the TemplateDataEditor linked above.,task_subcomment,['Tool = something at least as good as the TemplateDataEditor linked above.'],['SOLUTION DISCUSSION']
+240640,TemplateData: Create an editor for template data (in the wikitext editor),"Could you please define what that ""tool"" would exactly do? 
+Otherwise it will be extremely hard to define when this bug report could be considered ""fixed"" at some point. :)",task_subcomment,"['Could you please define what that ""tool"" would exactly do?', 'Otherwise it will be extremely hard to define when this bug report could be considered ""fixed"" at some point.', ':)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53708,"VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items","In Visual Editor edit screen templates that produce a single line of displayed text (regardless of the length of that line) do not wrap on word boundaries.
+
+Steps to reproduce:
+1. Insert a picture or other right-aligned object that text should wrap around.
+2. Transclude a template that produces a single line of text. {{EW charity|123456|This charity has got a long name to make it easy to test this bug}} is an example
+3. Reduce the width of your browser window until the text produced by the template is longer than the avaialble space between the left margin and the picture.
+
+Expected behaviour: The last word(s) of the text produced by the template wraps onto a second line.
+Actual behaviour: The entire line moves to below the picture as a single unit.
+
+Any template that produces two or more lines of displayed text (on an infinitely wide window) does not exhibit this behaviour and wraps correctly. For example:
+
+""Long text
    1"" wraps correctly
+
+""Long text
+1""
+""Long text
    "" and
+""Long text
    
+"" all exhibit this bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52445
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50395",task_description,"[""VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items\n\nIn Visual Editor edit screen templates that produce a single line of displayed text (regardless of the length of that line) do not wrap on word boundaries."", 'Steps to reproduce:\n1.', 'Insert a picture or other right-aligned object that text should wrap around.', '2.', 'Transclude a template that produces a single line of text.', '{{EW charity|123456|This charity has got a long name to make it easy to test this bug}} is an example\n3.', 'Reduce the width of your browser window until the text produced by the template is longer than the avaialble space between the left margin and the picture.', 'Expected behaviour: The last word(s) of the text produced by the template wraps onto a second line.', 'Actual behaviour: The entire line moves to below the picture as a single unit.', 'Any template that produces two or more lines of displayed text (on an infinitely wide window) does not exhibit this behaviour and wraps correctly.', 'For example:\n\n""Long text
    1"" wraps correctly\n\n""Long text\n1""\n""Long text
    "" and\n""Long text
    \n"" all exhibit this bug.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239329,"VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items","Change 139806 merged by jenkins-bot:
+Remove display:inline-block highlight hacks
+
+https://gerrit.wikimedia.org/r/139806",task_subcomment,['Change 139806 merged by jenkins-bot:\nRemove display:inline-block highlight hacks\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239325,"VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items","Change 139806 had a related patch set uploaded by Esanders:
+Remove display:inline-block highlight hacks
+
+https://gerrit.wikimedia.org/r/139806",task_subcomment,['Change 139806 had a related patch set uploaded by Esanders:\nRemove display:inline-block highlight hacks\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239319,"VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items","Inline templates are overridden to inline-block, but setting them back to inline would mean we have to calculate the highlights using getClientRects. Might want to wait for the much discussed SVG highlights for this?",task_subcomment,"['Inline templates are overridden to inline-block, but setting them back to inline would mean we have to calculate the highlights using getClientRects.', 'Might want to wait for the much discussed SVG highlights for this?']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239313,"VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items",*** Bug 62800 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 62800 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239306,"VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items",*** Bug 52320 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52320 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53679,VisualEditor: unlinking via linking tool triggers weird behaviors,"See http://it.wikipedia.org/wiki/File:Pic_-_VE_-_it_-_18_July_2013.png .
+
+http://it.wikipedia.org/wiki/Tellururo_di_mercurio_e_cadmio
+
+My understanding is that unlinking can be both done by the clear formatting button or by the trash button in the linking tool.
+
+If you don't select exactly the word that you want to unlink (so if you include even just a space, which I guess can surely happen), you'll be able to unlink via the linking tool by clicking on the garbage can: but then, a weird cursor appears and you can no longer edit links or templates. 
+
+According to me and itwp users that happens with both FF and Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: unlinking via linking tool triggers weird behaviors\n\nSee URL .', 'URL\n\nMy understanding is that unlinking can be both done by the clear formatting button or by the trash button in the linking tool.', ""If you don't select exactly the word that you want to unlink (so if you include even just a space, which I guess can surely happen), you'll be able to unlink via the linking tool by clicking on the garbage can: but then, a weird cursor appears and you can no longer edit links or templates."", 'According to me and itwp users that happens with both FF and Chrome.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237554,VisualEditor: unlinking via linking tool triggers weird behaviors,"Worksforus, at it.wp. Will re-open if necessary.",task_subcomment,"['Worksforus, at it.wp.', 'Will re-open if necessary.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+237551,VisualEditor: unlinking via linking tool triggers weird behaviors,"Switching to Unconfirmed, since I can no longer reproduce this. Will ask other Italian testers if they can, otherwise I'll mark it as Resolved.",task_subcomment,"['Switching to Unconfirmed, since I can no longer reproduce this.', ""Will ask other Italian testers if they can, otherwise I'll mark it as Resolved.""]","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+237548,VisualEditor: unlinking via linking tool triggers weird behaviors,"Another user reports getting the weird cursor but being still able to work regularly after that (his specs, Firefox on W7 64bit, Monobook).
+I'm looking for the quickest way to produce screencasts for you (Chrome does not seem to have valid plugins for that unfortunately).",task_subcomment,"['Another user reports getting the weird cursor but being still able to work regularly after that (his specs, Firefox on W7 64bit, Monobook).', ""I'm looking for the quickest way to produce screencasts for you (Chrome does not seem to have valid plugins for that unfortunately).""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+237545,VisualEditor: unlinking via linking tool triggers weird behaviors,"Don't even mention it, James :)
+Sorry I can't provide a video today ;)
+but will try to explain more carefully.
+It definitely still occurs, it was just reported (among other things) in
+
+http://it.wikipedia.org/wiki/Rodney .
+
+The clear formatting works fine.
+Properly unlinking a single word works fine.
+In this article, if I just select, say, from ""toponimo"" to ""antica"" and use the linking tool to unlink, I will be able to do it the first time but then I'll get the limited functionalities listed above.
+The same if I just select ""adespota,"" .
+I don't do anything else before or after that.
+It happens with both Monobook and Vector and on en.wp as well, I just tried editing the article ""Penguin"".
+
+Thanks.",task_subcomment,"[""Don't even mention it, James :)\nSorry I can't provide a video today ;)\nbut will try to explain more carefully."", 'It definitely still occurs, it was just reported (among other things) in\n\nURL .', 'The clear formatting works fine.', 'Properly unlinking a single word works fine.', 'In this article, if I just select, say, from ""toponimo"" to ""antica"" and use the linking tool to unlink, I will be able to do it the first time but then I\'ll get the limited functionalities listed above.', 'The same if I just select ""adespota,"" .', ""I don't do anything else before or after that."", 'It happens with both Monobook and Vector and on en.wp as well, I just tried editing the article ""Penguin"".', 'Thanks.']","['SOCIAL CONVERSATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+237542,VisualEditor: unlinking via linking tool triggers weird behaviors,"I can't reproduce this in either Chrome or Firefox - by drag-selecting the word with the mouse, right-clicking, double-clicking; and by selection with the keyboard or drag-clicking with the mouse to select more than the word, using both the link inspector and its remove (""trash"") icon and the general ""clear formatting"" tool. :-(
+
+Does this occur on every page? What about after a hard-refresh? Can you make a video/screencast of you doing this so I can see exactly how it occurs? Sorry to ask so much!",task_subcomment,"['I can\'t reproduce this in either Chrome or Firefox - by drag-selecting the word with the mouse, right-clicking, double-clicking; and by selection with the keyboard or drag-clicking with the mouse to select more than the word, using both the link inspector and its remove (""trash"") icon and the general ""clear formatting"" tool.', ':-(\n\nDoes this occur on every page?', 'What about after a hard-refresh?', 'Can you make a video/screencast of you doing this so I can see exactly how it occurs?', 'Sorry to ask so much!']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'ACTION ON ISSUE']"
+53670,VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label,"Two screenshots showing the search function applied to {{cite book}} on en.wp
+
+A user on the English Wikipedia reports that when entering a template using the transclusion editor, the search for parameters fails when the parameter includes a space:
+
+""when I start typing ""Source date"" (without quotes, of course) into the search box, something interesting happens when I get to the ""d"" - the search results say ""Unknown parameter"". That is, at the point where I've typed ""Source d"", then - essentially - the search fails; the search software decides that there are no matching entries.""
+
+I've tested this with both {{cite web}} and {{cite book}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51822
+
+**Attached**: {F11265}",task_description,"['VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label\n\nTwo screenshots showing the search function applied to {{cite book}} on en.wp\n\nA user on the English Wikipedia reports that when entering a template using the transclusion editor, the search for parameters fails when the parameter includes a space:\n\n""when I start typing ""Source date"" (without quotes, of course) into the search box, something interesting happens when I get to the ""d"" - the search results say ""Unknown parameter"".', 'That is, at the point where I\'ve typed ""Source d"", then - essentially - the search fails; the search software decides that there are no matching entries.""', ""I've tested this with both {{cite web}} and {{cite book}}\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\n\n**Attached**: {F11265}""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+237017,VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label,"Will this allow searching on instring matches of both title and label? 
+
+If not, will that be covered by bug 51822 or is a new bug required?",task_subcomment,"['Will this allow searching on instring matches of both title and label?', 'If not, will that be covered by bug 51822 or is a new bug required?']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+237013,VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label,"This is now fixed in master, and will be released to MediaWiki.org on Thursday 5 September, and to Wikipedias on Thursday 12 September. Sorry for the disruption.",task_subcomment,"['This is now fixed in master, and will be released to MediaWiki.org on Thursday 5 September, and to Wikipedias on Thursday 12 September.', 'Sorry for the disruption.']","['SOLUTION USAGE', 'ACTION ON ISSUE']"
+237007,VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label,"Change 82055 merged by jenkins-bot:
+Include param label in search index
+
+https://gerrit.wikimedia.org/r/82055",task_subcomment,['Change 82055 merged by jenkins-bot:\nInclude param label in search index\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237002,VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label,"Change 82055 had a related patch set uploaded by Trevor Parscal:
+Include param label in search index
+
+https://gerrit.wikimedia.org/r/82055",task_subcomment,['Change 82055 had a related patch set uploaded by Trevor Parscal:\nInclude param label in search index\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+236994,VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label,"A user on Wikipedia has determined that the cause is that the data the search function searches on is the internal parameter name, which is invisible to the user, not the visible label. This is very wrong. 
+
+""So VE users have learned that the only way, in the Transclusion/Template dialog, to add a parameter is to type the parameter name, then press Enter. But that just changed - now you click the parameter name to select it. That's more obvious - but if, for some reason, having learned the old way, you continue to use it - that's trouble.
+
+Example: Cite web. Let's suppose I want to add the parameter ""Month of publication"". I type that, hit Enter, and there it is, on the left. Except, not really. VE thinks this is a parameter not on its list - you can tell that because there is no description just above the input box where you enter the value of that parameter. (Compare to entering a value for the parameter ""Source title"").
+
+Under the hood, here's what happens: VE knows that ""Source title"" is the label (via TemplateData) for the parameter ""title"". (Similarly, ""URL"" is the label for the parameter ""url"" - and yes, parameters are case sensitive.) But VE doesn't know that ""Month of publication"" (typed) is the label for the parameter ""month"". So the template code that VE actually stores is this:
+
+    {{Cite web|url = http://example.com|title = Whatever the title is|Month of publication = June}}
+
+That doesn't cause a visible problem on the VE edit page. However, in this case, after saving the page, what is displayed to readers is ""Unknown parameter |Month of publication= ignored (help) ""
+
+Recommendation: If a person types the name of a parameter and presses Enter, VE should check the typed name against the list of labels in TemplateData, for that template, and if there is a match, handle the new parameter just as if the person had clicked the matching parameter rather than typed it.""",task_subcomment,"['A user on Wikipedia has determined that the cause is that the data the search function searches on is the internal parameter name, which is invisible to the user, not the visible label.', 'This is very wrong.', '""So VE users have learned that the only way, in the Transclusion/Template dialog, to add a parameter is to type the parameter name, then press Enter.', 'But that just changed - now you click the parameter name to select it.', ""That's more obvious - but if, for some reason, having learned the old way, you continue to use it - that's trouble."", 'Example: Cite web.', 'Let\'s suppose I want to add the parameter ""Month of publication"".', 'I type that, hit Enter, and there it is, on the left.', 'Except, not really.', 'VE thinks this is a parameter not on its list - you can tell that because there is no description just above the input box where you enter the value of that parameter.', '(Compare to entering a value for the parameter ""Source title"").', 'Under the hood, here\'s what happens: VE knows that ""Source title"" is the label (via TemplateData) for the parameter ""title"".', '(Similarly, ""URL"" is the label for the parameter ""url"" - and yes, parameters are case sensitive.)', 'But VE doesn\'t know that ""Month of publication"" (typed) is the label for the parameter ""month"".', ""So the template code that VE actually stores is this:\n\n    {{Cite web|url = URL = Whatever the title is|Month of publication = June}}\n\nThat doesn't cause a visible problem on the VE edit page."", 'However, in this case, after saving the page, what is displayed to readers is ""Unknown parameter |Month of publication= ignored (help) ""\n\nRecommendation: If a person types the name of a parameter and presses Enter, VE should check the typed name against the list of labels in TemplateData, for that template, and if there is a match, handle the new parameter just as if the person had clicked the matching parameter rather than typed it.""']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53636,VisualEditor: Saving fails silently when the database is locked,"**Author:** `kwang`
+
+**Description:**
+This shows the article and the visual editor save dialog
+
+I added a link to a new page but it wouldn't let me save my edit. Every time I saved it would load but then display the save page dialog again.
+
+I ended up creating the link in the source.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53093
+
+**Attached**: {F11178}",task_description,"[""VisualEditor: Saving fails silently when the database is locked\n\n**Author:** CODE\n\n**Description:**\nThis shows the article and the visual editor save dialog\n\nI added a link to a new page but it wouldn't let me save my edit."", 'Every time I saved it would load but then display the save page dialog again.', 'I ended up creating the link in the source.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\n\n**Attached**: {F11178}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+235136,VisualEditor: Saving fails silently when the database is locked,Fixed and will get deployed in a few minutes' time.,task_subcomment,"[""Fixed and will get deployed in a few minutes' time.""]",['SOLUTION USAGE']
+235128,VisualEditor: Saving fails silently when the database is locked,"Change 75561 merged by jenkins-bot:
+Show error when trying to save in read-only mode
+
+https://gerrit.wikimedia.org/r/75561",task_subcomment,['Change 75561 merged by jenkins-bot:\nShow error when trying to save in read-only mode\n\nGERRIT_URL'],['ACTION ON ISSUE']
+235121,VisualEditor: Saving fails silently when the database is locked,"Change 75561 had a related patch set uploaded by Esanders:
+Show when trying to save in read-only mode
+
+https://gerrit.wikimedia.org/r/75561",task_subcomment,['Change 75561 had a related patch set uploaded by Esanders:\nShow when trying to save in read-only mode\n\nGERRIT_URL'],['ACTION ON ISSUE']
+235115,VisualEditor: Saving fails silently when the database is locked,"Two other users have reported the same thing on en.wikipedia, so the cause was the database being locked.
+
+Could be related to Bug 50472 which is marked as fixed but has apparently not yet been deployed?",task_subcomment,"['Two other users have reported the same thing on en.wikipedia, so the cause was the database being locked.', 'Could be related to Bug 50472 which is marked as fixed but has apparently not yet been deployed?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235109,VisualEditor: Saving fails silently when the database is locked,"**kwang** wrote:
+
+error while editing source code.
+
+**Attached**: {F11179}",task_subcomment,"['**kwang** wrote:\n\nerror while editing source code.', '**Attached**: {F11179}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235103,VisualEditor: Saving fails silently when the database is locked,"**kwang** wrote:
+
+More details: when I edited the source it said that the database was locked. This is likely the issue that was happening, but the error wasn't showing up in the visual editor.",task_subcomment,"['**kwang** wrote:\n\nMore details: when I edited the source it said that the database was locked.', ""This is likely the issue that was happening, but the error wasn't showing up in the visual editor.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53596,VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome,"Browser: Chrome any version.
+
+1. Open VE
+2. Type or copy-paste സന്തോഷ്
+3. Move the cursor to the end of that word.
+4. Press left arrow to move the caret backwards.
+5. In the second keypress onwards cursor is stuck.(like സന്തോ|ഷ് )
+
+Expected: cursor keep moving to left. 
+
+Observed. cursor stuck.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome\n\nBrowser: Chrome any version.', '1.', 'Open VE\n2.', 'Type or copy-paste സന്തോഷ്\n3.', 'Move the cursor to the end of that word.', '4.', 'Press left arrow to move the caret backwards.', '5.', 'In the second keypress onwards cursor is stuck.', '(like സന്തോ|ഷ് )\n\nExpected: cursor keep moving to left.', 'Observed.', 'cursor stuck.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233027,VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome,"Change 80689 merged by jenkins-bot:
+Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",task_subcomment,['Change 80689 merged by jenkins-bot:\nRevert model to use simple UTF-16 code units\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233021,VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome,"Change 80689 had a related patch set uploaded by Divec:
+DONTMERGE:Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",task_subcomment,['Change 80689 had a related patch set uploaded by Divec:\nDONTMERGE:Revert model to use simple UTF-16 code units\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233015,VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome,There's code in progress to fix this in gerrit 80689 which is currently a work-in-progress.,task_subcomment,"[""There's code in progress to fix this in gerrit 80689 which is currently a work-in-progress.""]",['SOLUTION DISCUSSION']
+233007,VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome,"There's code to address this bug in the following patch, which is due to go live on mediawiki.org by 13 September 2013:
+
+https://gerrit.wikimedia.org/r/#/c/82858/
+
+It does not fix this completely, but it does make it possible to cursor left through the cluster with repeated consecutive keypresses.",task_subcomment,"[""There's code to address this bug in the following patch, which is due to go live on mediawiki.org by 13 September 2013:\n\nURL\n\nIt does not fix this completely, but it does make it possible to cursor left through the cluster with repeated consecutive keypresses.""]",['BUG REPRODUCTION']
+233001,VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome,"Debug Information:
+
+Grapheme breaks as per unicodejs:
+0: ""സ""
+1: ""ന്""
+2: ""തോ""
+3: ""ഷ്""
+
+Ligature break 1 and 2 logically wrong because they form a single cluster ന്തോ. You cannot place a cursor in between this cluster. It is a single syllable too. Firefox allows you to place the cursor at all of these breaks anyway. Infact Firefox allows you to place the cursor even inside ligature programatically. Chrome allows cursor positioning only at logical positions.
+
+In this specific case. VE is asking Chrome to place the cursor at end of  grapheme break #1(ന്). but Chrome does not obey it and place it at the end of #2 (തോ). This repeats in every left cursor movement and it looks like cursor is stuck at the end of തോ.
+
+In my quick observation those logical positions does not match with the grapheme cluster boundary specification of Unicode (www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries).
+
+That causes lot of inconstancy in the offset known to the data model of VE and the actual offset appearing in browser. It will lead to many unexpected behavior of cursor positioning and text selections.",task_subcomment,"['Debug Information:\n\nGrapheme breaks as per unicodejs:\n0: ""സ""\n1: ""ന്""\n2: ""തോ""\n3: ""ഷ്""\n\nLigature break 1 and 2 logically wrong because they form a single cluster ന്തോ.', 'You cannot place a cursor in between this cluster.', 'It is a single syllable too.', 'Firefox allows you to place the cursor at all of these breaks anyway.', 'Infact Firefox allows you to place the cursor even inside ligature programatically.', 'Chrome allows cursor positioning only at logical positions.', 'In this specific case.', 'VE is asking Chrome to place the cursor at end of  grapheme break #1(ന്).', 'but Chrome does not obey it and place it at the end of #2 (തോ).', 'This repeats in every left cursor movement and it looks like cursor is stuck at the end of തോ.', 'In my quick observation those logical positions does not match with the grapheme cluster boundary specification of Unicode (www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries).', 'That causes lot of inconstancy in the offset known to the data model of VE and the actual offset appearing in browser.', 'It will lead to many unexpected behavior of cursor positioning and text selections.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53569,Reduce number of load.php calls on VisualEditor open (down from 3),"On a regular page load:
+
+* http://en.wikipedia.org/wiki/Roadblock_(disambiguation)
+* Logged-out (Chromium Incognito mode)
+
+We get this (did a full analysis while I had the data in front of me, but focus on ""On Edit"":
+
+Top:
+ - [core]   load.php?modules=startup
+ - [misc]   load.php?modules=.. top queue ...
+ - [vector] load.php?modules=ext.vector.footerCleanup (bug 51564)
+ * [ve]     load.php?modules=ext.visualEditor.viewPageTarget.init
+ - [core]   load.php?modules=site
+
+Bottom:
+ - [misc]   load.php?modules=.. bottom queue ...
+ - [vector] load.php?modules=ext.vector.collapsibleNav (bug 51564)
+ - [misc]   load.php?modules=.. jquery.ui ...
+    (dependency of something in the bottom queue, separate cache group)
+
+On Edit:
+ * [ve]     load.php?modules=ext.visualEditor.base,mediawiki,viewPageTarget|jquery.visibleText|oojs|unicodejs.wordbreak
+ * [ve]     load.php?modules=jquery.byteLength,byteLimit|mediawiki.api.edit|mediawiki.feedback|ext.visualEditor.core,icons-vector|ext.visualEditor.viewPageTarget.icons-vector|rangy
+ * [ve]     load.php?modules=ext.visualEditor.specialMessages
+ - [ve]     api.php POST action=visualeditor & paction=parse
+ - [ve]     api.php?action=query&meta=userinfo
+
+These shouldn't be 3 separate load.php requests. Ideally it'd be 1, but we should at least cut it down to 2. We should figure out why they are split.",task_description,"['Reduce number of load.php calls on VisualEditor open (down from 3)\n\nOn a regular page load:\n\n* URL\n* Logged-out (Chromium Incognito mode)\n\nWe get this (did a full analysis while I had the data in front of me, but focus on ""On Edit"":\n\nTop:\n - [core]   load.php?modules=startup\n - [misc]   load.php?modules=.. top queue ...\n - [vector] load.php?modules=ext.vector.footerCleanup (bug 51564)\n * [ve]     load.php?modules=ext.visualEditor.viewPageTarget.init\n - [core]   load.php?modules=site\n\nBottom:\n - [misc]   load.php?modules=.. bottom queue ...\n - [vector] load.php?modules=ext.vector.collapsibleNav (bug 51564)\n - [misc]   load.php?modules=.. jquery.ui ...\n    (dependency of something in the bottom queue, separate cache group)\n\nOn Edit:\n * [ve]     load.php?modules=ext.visualEditor.base,mediawiki,viewPageTarget|jquery.visibleText|oojs|unicodejs.wordbreak\n * [ve]     load.php?modules=jquery.byteLength,byteLimit|mediawiki.api.edit|mediawiki.feedback|ext.visualEditor.core,icons-vector|ext.visualEditor.viewPageTarget.icons-vector|rangy\n * [ve]     load.php?modules=ext.visualEditor.specialMessages\n - [ve]     api.php POST action=visualeditor & paction=parse\n - [ve]     api.php?action=query&meta=userinfo\n\nThese shouldn\'t be 3 separate load.php requests.', ""Ideally it'd be 1, but we should at least cut it down to 2."", 'We should figure out why they are split.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+427961,Reduce number of load.php calls on VisualEditor open (down from 3),"Change 197402 merged by jenkins-bot:
+Load RL modules in one load.php request, rather than in two stages
+
+[[https://gerrit.wikimedia.org/r/197402]]",task_subcomment,"['Change 197402 merged by jenkins-bot:\nLoad RL modules in one load.php request, rather than in two stages\n\n[[GERRIT_URL]]']",['GERRIT_URL']
+427918,Reduce number of load.php calls on VisualEditor open (down from 3),"Change 197402 had a related patch set uploaded (by Jforrester):
+Load RL modules in one load.php request, rather than in two stages
+
+[[https://gerrit.wikimedia.org/r/197402]]
+",task_subcomment,"['Change 197402 had a related patch set uploaded (by Jforrester):\nLoad RL modules in one load.php request, rather than in two stages\n\n[[GERRIT_URL]]']",['GERRIT_URL']
+426507,Reduce number of load.php calls on VisualEditor open (down from 3),"Change 193026 merged by jenkins-bot:
+Load RL modules in one load.php request, rather than in two stages
+
+[[https://gerrit.wikimedia.org/r/193026]]",task_subcomment,"['Change 193026 merged by jenkins-bot:\nLoad RL modules in one load.php request, rather than in two stages\n\n[[GERRIT_URL]]']",['GERRIT_URL']
+449826,Reduce number of load.php calls on VisualEditor open (down from 3),"Saves 1 request and 3KB.
+
+From 20 total request (521KB), to 19 total requests (518KB).
+
+Tested on localhost. (Page view + load editor; includes two EventLogging requests and some images).",task_subcomment,"['Saves 1 request and 3KB.', 'From 20 total request (521KB), to 19 total requests (518KB).', 'Tested on localhost.', '(Page view + load editor; includes two EventLogging requests and some images).']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+426504,Reduce number of load.php calls on VisualEditor open (down from 3),"Saves 1 request and 3KB.
+
+From 20 total request (512KB), to 19 total requests (518KB).
+
+Tested on localhost. (Page view + load editor; includes two EventLogging requests and some images).",task_subcomment,"['Saves 1 request and 3KB.', 'From 20 total request (512KB), to 19 total requests (518KB).', 'Tested on localhost.', '(Page view + load editor; includes two EventLogging requests and some images).']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+419493,Reduce number of load.php calls on VisualEditor open (down from 3),"Change 193026 had a related patch set uploaded (by Jforrester):
+[WIP] Factor out loading code into TargetLoader
+
+[[https://gerrit.wikimedia.org/r/193026]]
+",task_subcomment,['Change 193026 had a related patch set uploaded (by Jforrester):\n[WIP] Factor out loading code into TargetLoader\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+53538,VisualEditor: Reverse selections break copy paste functionality,"* Select some text forwards and copy-paste it, everything is great.
+* Select some text backwards and copy-paste it, you now have an extra linebreak.
+
+?!???!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Reverse selections break copy paste functionality\n\n* Select some text forwards and copy-paste it, everything is great.', '* Select some text backwards and copy-paste it, you now have an extra linebreak.', '?', '!???!', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254160,VisualEditor: Reverse selections break copy paste functionality,Now merged; will go out with next push.,task_subcomment,['Now merged; will go out with next push.'],['SOLUTION USAGE']
+254154,VisualEditor: Reverse selections break copy paste functionality,"Change 80299 merged by jenkins-bot:
+Fix copy and paste of backwards selction
+
+https://gerrit.wikimedia.org/r/80299",task_subcomment,['Change 80299 merged by jenkins-bot:\nFix copy and paste of backwards selction\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+254147,VisualEditor: Reverse selections break copy paste functionality,"Change 80299 had a related patch set uploaded by Esanders:
+Fix copy and paste of backwards selction
+
+https://gerrit.wikimedia.org/r/80299",task_subcomment,['Change 80299 had a related patch set uploaded by Esanders:\nFix copy and paste of backwards selction\n\nGERRIT_URL'],['BUG REPRODUCTION']
+254140,VisualEditor: Reverse selections break copy paste functionality,I can confirm this is still happening in Firefox 23/linux,task_subcomment,['I can confirm this is still happening in Firefox 23/linux'],['OBSERVED BUG BEHAVIOR']
+53532,VisualEditor: CTRL+Z occasionally inserts a pawn,"When typing in visual editor, sometimes pressing CTRL+Z will replace the last entered character with a pawn (♙).
+
+I've encountered this most frequently when undoing text that appeared as a link when I didn't want it to (see bug 51531) but occasionally when undoing other text as well.
+
+There are numerous other pawn insertion bugs, other editors have suggested possible relationships with bug 49732, bug 48346 or bug 51140, but none seem quite the same (e.g. there is no non-ASCII text, bold or italics involved) and all are marked as fixed. I encountered this yesterday and today (16 and 17 July).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51762
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52113",task_description,"['VisualEditor: CTRL+Z occasionally inserts a pawn\n\nWhen typing in visual editor, sometimes pressing CTRL+Z will replace the last entered character with a pawn (♙).', ""I've encountered this most frequently when undoing text that appeared as a link when I didn't want it to (see bug 51531) but occasionally when undoing other text as well."", 'There are numerous other pawn insertion bugs, other editors have suggested possible relationships with bug 49732, bug 48346 or bug 51140, but none seem quite the same (e.g.', 'there is no non-ASCII text, bold or italics involved) and all are marked as fixed.', 'I encountered this yesterday and today (16 and 17 July).', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253776,VisualEditor: CTRL+Z occasionally inserts a pawn,I believe these issues are now fixed.,task_subcomment,['I believe these issues are now fixed.'],['SOLUTION USAGE']
+253769,VisualEditor: CTRL+Z occasionally inserts a pawn,"This is still happening occasionally, and almost always associated with undoing text added to a link. However I can't reproduce it every time.",task_subcomment,"['This is still happening occasionally, and almost always associated with undoing text added to a link.', ""However I can't reproduce it every time.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253762,VisualEditor: CTRL+Z occasionally inserts a pawn,en.wp thread for reference https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564648446#Adding_text_after_a_link_includes_that_text_in_the_link._Undoing_sometimes_gives_a_pawn,task_subcomment,['en.wp thread for reference URL'],['OBSERVED BUG BEHAVIOR']
+53526,"VisualEditor: Fix ""Uncaught Error: Offset could not be translated to a DOM element and offset: 2409""","Screenshot of problem
+
+1. Open https://en.wikipedia.org/wiki/Pancytopenia?veaction=edit#External_links
+2. Select Commonscat template block
+3. Put cursor in heading after ""External links""
+4. Arrow keys to navigate down (to after text in list item ""* [[CDC]]"")
+5. Arrow keys to navigate right
+
+
+> Uncaught Error: Offset could not be translated to a DOM element and offset: 2409
+ve.ce.Document.getNodeAndOffset
+ve.ce.Surface.showSelection
+ve.ce.Surface.onChange
+oo.EventEmitter.emit
+ve.dm.Surface.change
+ve.ce.Surface.handleLeftOrRightArrowKey
+ve.ce.Surface.onDocumentKeyDown
+proxy
+jQuery.event.dispatch
+elemData.handle.eventHandle
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11838}",task_description,"['VisualEditor: Fix ""Uncaught Error: Offset could not be translated to a DOM element and offset: 2409""\n\nScreenshot of problem\n\n1.', 'Open URL\n2.', 'Select Commonscat template block\n3.', 'Put cursor in heading after ""External links""\n4.', 'Arrow keys to navigate down (to after text in list item ""* [[CDC]]"")\n5.', 'Arrow keys to navigate right\n\n\nQUOTE\nve.ce.Document.getNodeAndOffset\nve.ce.Surface.showSelection\nve.ce.Surface.onChange\noo.EventEmitter.emit\nve.dm.Surface.change\nve.ce.Surface.handleLeftOrRightArrowKey\nve.ce.Surface.onDocumentKeyDown\nproxy\njQuery.event.dispatch\nelemData.handle.eventHandle\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11838}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION']"
+574335,"VisualEditor: Fix ""Uncaught Error: Offset could not be translated to a DOM element and offset: 2409""","I just got that same error (""Uncaught Error: Offset could not be translated to a DOM element and offset: 458"") on Meta. Sadly, I don't know what caused it.",task_subcomment,"['I just got that same error (""Uncaught Error: Offset could not be translated to a DOM element and offset: 458"") on Meta.', ""Sadly, I don't know what caused it.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253489,"VisualEditor: Fix ""Uncaught Error: Offset could not be translated to a DOM element and offset: 2409""","This appears to now be fixed. Marking as such, though can't determine exactly what fixed fixed it (probably Ed's cursoring changes?).",task_subcomment,"['This appears to now be fixed.', ""Marking as such, though can't determine exactly what fixed fixed it (probably Ed's cursoring changes?"", ').']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+253483,"VisualEditor: Fix ""Uncaught Error: Offset could not be translated to a DOM element and offset: 2409""",Confirmed still happening.,task_subcomment,['Confirmed still happening.'],['OBSERVED BUG BEHAVIOR']
+53525,VisualEditor: Block slug deletion causing very odd corruption/skipping/repeat/pawns,"When doing the steps outlined below, strange '9' character plus a newline appears and input it jumped backwards after 3 character.
+
+See http://youtu.be/A7MWIdu3dtk for how it looks; Using http://en.wikipedia.org/wiki/Ansaldo_Poggi as test ground.
+
+1. Place marker under ""References"" header
+2. hit ""backspace""
+3. type ""foobar""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://en.wikipedia.org/wiki/Ansaldo_Poggi",task_description,"[""VisualEditor: Block slug deletion causing very odd corruption/skipping/repeat/pawns\n\nWhen doing the steps outlined below, strange '9' character plus a newline appears and input it jumped backwards after 3 character."", 'See URL for how it looks; Using URL as test ground.', '1.', 'Place marker under ""References"" header\n2. hit ""backspace""\n3. type ""foobar""\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+253442,VisualEditor: Block slug deletion causing very odd corruption/skipping/repeat/pawns,"Resetting to FIXED; this was a confirmed broken behaviour which has subsequently been FIXED, as far as we can tell - probably by the re-write of the Content Editable surface interaction model.",task_subcomment,"['Resetting to FIXED; this was a confirmed broken behaviour which has subsequently been FIXED, as far as we can tell - probably by the re-write of the Content Editable surface interaction model.']",['BUG REPRODUCTION']
+253436,VisualEditor: Block slug deletion causing very odd corruption/skipping/repeat/pawns,"(In reply to comment #2)
+> Cannot reproduce it now on betalabs.
+
+Where ""on betalabs""? Tested how exactly (which browsers and versions)? Current steps aren't transparent so somebody else couldn't recreate your conditions...
+
+> It might got fixed.
+
+""Might"" = no identifiable code commit = WORKSFORME instead of FIXED. See https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle",task_subcomment,"['(In reply to comment #2)\nQUOTE\n\nWhere ""on betalabs""?', 'Tested how exactly (which browsers and versions)?', 'Current steps aren\'t transparent so somebody else couldn\'t recreate your conditions...\n\nQUOTE\n\n""Might"" = no identifiable code commit = WORKSFORME instead of FIXED.', 'See URL']","['ACTION ON ISSUE', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253430,VisualEditor: Block slug deletion causing very odd corruption/skipping/repeat/pawns,"Cannot reproduce it now on betalabs.It might got fixed.So changing the status as resolved and fixed.
+If you can still reproduce it, please reopen it.",task_subcomment,"['Cannot reproduce it now on betalabs.It might got fixed.So changing the status as resolved and fixed.', 'If you can still reproduce it, please reopen it.']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+253425,VisualEditor: Block slug deletion causing very odd corruption/skipping/repeat/pawns,"TypeError: node.getParent(...) is null
+http://bits.wikimedia.org/static-1.22wmf9/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js
+Line 1267",task_subcomment,['TypeError: node.getParent(...) is null\nURL\nLine 1267'],['OBSERVED BUG BEHAVIOR']
+53523,VisualEditor: Too many clicks needed to dismiss inlink editor,"I use the ""link"" tool from the toolbar to in-link to other articles. However, after adding the link, the editor doesn't disappear. I have to click again, outside it, to make it go away.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Too many clicks needed to dismiss inlink editor\n\nI use the ""link"" tool from the toolbar to in-link to other articles.', ""However, after adding the link, the editor doesn't disappear."", 'I have to click again, outside it, to make it go away.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253365,VisualEditor: Too many clicks needed to dismiss inlink editor,This is now merged and will be deployed later.,task_subcomment,['This is now merged and will be deployed later.'],['ACTION ON ISSUE']
+253362,VisualEditor: Too many clicks needed to dismiss inlink editor,"Change 76839 merged by jenkins-bot:
+Link inspector bug fixes
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 merged by jenkins-bot:\nLink inspector bug fixes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+253359,VisualEditor: Too many clicks needed to dismiss inlink editor,"Change 76839 had a related patch set uploaded by Trevor Parscal:
+The greatest commit in the history of the world*
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 had a related patch set uploaded by Trevor Parscal:\nThe greatest commit in the history of the world*\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+53507,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","I think ""Clear formatting"" is important enough to justify a keyboard shortcut.  For example, there are cases where the formatting can unintentionally continue longer than you want, such as when you add a link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53682
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56453",task_description,"['VisualEditor: Add a keyboard shortcut for ""Clear formatting""\n\nI think ""Clear formatting"" is important enough to justify a keyboard shortcut.', 'For example, there are cases where the formatting can unintentionally continue longer than you want, such as when you add a link.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+252473,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""",Re-closing; have made bug 56453 for the suggestion to add a new one for other keyboards.,task_subcomment,['Re-closing; have made bug 56453 for the suggestion to add a new one for other keyboards.'],['ACTION ON ISSUE']
+252470,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","(In reply to comment #7)
+> Except there is no \ key on keyboards like the French one, so the shortcut is
+> reported as not working (also, provoking weird behaviour I'll report
+> elsewhere), since they should type CTRL + Alt Gr + 8. Can we do something
+> about this? Thanks.
+
+Weird behaviour reported on https://bugzilla.wikimedia.org/show_bug.cgi?id=53682",task_subcomment,['(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWeird behaviour reported on URL'],['OBSERVED BUG BEHAVIOR']
+252466,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","Except there is no \ key on keyboards like the French one, so the shortcut is reported as not working (also, provoking weird behaviour I'll report elsewhere), since they should type CTRL + Alt Gr + 8. Can we do something about this? Thanks.",task_subcomment,"[""Except there is no \\ key on keyboards like the French one, so the shortcut is reported as not working (also, provoking weird behaviour I'll report elsewhere), since they should type CTRL + Alt Gr + 8."", 'Can we do something about this?', 'Thanks.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+252463,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","Now merged and will go out with the next production push, probably tomorrow.",task_subcomment,"['Now merged and will go out with the next production push, probably tomorrow.']",['ACTION ON ISSUE']
+252458,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","Change 76666 merged by jenkins-bot:
+Add keyboard shortcut for 'clear' button
+
+https://gerrit.wikimedia.org/r/76666",task_subcomment,"[""Change 76666 merged by jenkins-bot:\nAdd keyboard shortcut for 'clear' button\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+252452,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","Change 76666 had a related patch set uploaded by Jforrester:
+Add keyboard shortcut for 'clear' button
+
+https://gerrit.wikimedia.org/r/76666",task_subcomment,"[""Change 76666 had a related patch set uploaded by Jforrester:\nAdd keyboard shortcut for 'clear' button\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+252447,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""",Ctrl + M might be a little friendlier.  I know from experience people confuse backslash and forward slash.  But I don't feel strongly about it.,task_subcomment,"['Ctrl + M might be a little friendlier.', 'I know from experience people confuse backslash and forward slash.', ""But I don't feel strongly about it.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+252438,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","I can see wanting to use Ctrl + Spacebar for a general whitespace inserter menu (nbsp/tab/etc.), so how about we go with Ctrl + \?",task_subcomment,"['I can see wanting to use Ctrl + Spacebar for a general whitespace inserter menu (nbsp/tab/etc.', '), so how about we go with Ctrl + \\?']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+252433,"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","Shortcuts used in other programs are:
+
+Ctrl + Spacebar - Used by Word for ""Remove paragraph or character formatting.""/""Remove manual character formatting"" (http://support.microsoft.com/kb/290938).
+Ctrl + \ - Used by Google Docs for ""Clear formatting"" (https://support.google.com/drive/answer/179738?hl=en)
+Ctrl + M - Used by LibreOffice for ""Clear direct formatting"" (https://help.libreoffice.org/Common/General_Shortcut_Keys_in)",task_subcomment,"['Shortcuts used in other programs are:\n\nCtrl + Spacebar - Used by Word for ""Remove paragraph or character formatting.', '""/""Remove manual character formatting"" (URL\nCtrl + \\ - Used by Google Docs for ""Clear formatting"" (URL\nCtrl + M - Used by LibreOffice for ""Clear direct formatting"" (URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+53502,VisualEditor: Reduce event rapid fire in CE,"Right now the SurfaceObserver locks and unlocks a lot, firing a lot of events and stopping and restarting a lot. We should make locks wider so that this doesn't happen.
+
+We should also eliminate cases where the SurfaceObserver responds to a DOM change that was actually made by VE itself, and we should change pawning to no longer go through the model.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Reduce event rapid fire in CE\n\nRight now the SurfaceObserver locks and unlocks a lot, firing a lot of events and stopping and restarting a lot.', ""We should make locks wider so that this doesn't happen."", 'We should also eliminate cases where the SurfaceObserver responds to a DOM change that was actually made by VE itself, and we should change pawning to no longer go through the model.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+252199,VisualEditor: Reduce event rapid fire in CE,Yes.,task_subcomment,['Yes.'],['OBSERVED BUG BEHAVIOR']
+252194,VisualEditor: Reduce event rapid fire in CE,Can we now deem this to have been done?,task_subcomment,['Can we now deem this to have been done?'],['SOLUTION DISCUSSION']
+53477,VisualEditor: Typing in Devanagari puts vowels in unexpected places,"Typing in the Devanagari script causes very unusual placement of vowels in relation to consonants. The correct place to put the vowels is always after the preceding consonant, but the VisualEditor causes very strange placement.
+
+To try, I used the standard Hindi InScript keyboard (not ULS IME, but the operating system's InScript keyboard). I tried to type the word ""अंग्रेज़ी"" (the Hindi name of the English language).
+
+To get that word with the InScript keyboard, type the following keys on the English-US keyboard:
+
+Dxidjs;]r
+
+The expected result is ""अंग्रेज़ी"".
+
+The actual result on Firefox 22 is ""अंग्ेच़ीर"".
+
+The actual result on Chrome 28 is ""्रेची"".
+
+I tried this with Firefox 22 on Fedora 18.
+
+I mark this as blocker, because in this state the VisualEditor must not be widely deployed on a Wikipedia that uses the Devanagari script, such as Hindi (hi), Marathi (mr), Nepali (ne) or Sanskrit (sa) (there are a few more languages that use it). It's OK to have it as opt-in for testing on these wikis, though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",task_description,"['VisualEditor: Typing in Devanagari puts vowels in unexpected places\n\nTyping in the Devanagari script causes very unusual placement of vowels in relation to consonants.', 'The correct place to put the vowels is always after the preceding consonant, but the VisualEditor causes very strange placement.', ""To try, I used the standard Hindi InScript keyboard (not ULS IME, but the operating system's InScript keyboard)."", 'I tried to type the word ""अंग्रेज़ी"" (the Hindi name of the English language).', 'To get that word with the InScript keyboard, type the following keys on the English-US keyboard:\n\nDxidjs;]r\n\nThe expected result is ""अंग्रेज़ी"".', 'The actual result on Firefox 22 is ""अंग्ेच़ीर"".', 'The actual result on Chrome 28 is ""्रेची"".', 'I tried this with Firefox 22 on Fedora 18.', 'I mark this as blocker, because in this state the VisualEditor must not be widely deployed on a Wikipedia that uses the Devanagari script, such as Hindi (hi), Marathi (mr), Nepali (ne) or Sanskrit (sa) (there are a few more languages that use it).', ""It's OK to have it as opt-in for testing on these wikis, though."", '--------------------------\n**Version**: unspecified\n**Severity**: blocker']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+250407,VisualEditor: Typing in Devanagari puts vowels in unexpected places,master looks good to me. Thanks!,task_subcomment,"['master looks good to me.', 'Thanks!']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250400,VisualEditor: Typing in Devanagari puts vowels in unexpected places,"Given that this is now merged, I'm going to mark this as fixed. However, this is provisional - please re-open if you think that this has not worked!",task_subcomment,"[""Given that this is now merged, I'm going to mark this as fixed."", 'However, this is provisional - please re-open if you think that this has not worked!']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+250395,VisualEditor: Typing in Devanagari puts vowels in unexpected places,"Change 80080 merged by jenkins-bot:
+Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",task_subcomment,"[""Change 80080 merged by jenkins-bot:\nDon't emit Surface changes back to the Surface\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+250390,VisualEditor: Typing in Devanagari puts vowels in unexpected places,"Change 80080 had a related patch set uploaded by Jforrester:
+WIP:Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",task_subcomment,"[""Change 80080 had a related patch set uploaded by Jforrester:\nWIP:Don't emit Surface changes back to the Surface\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+250387,VisualEditor: Typing in Devanagari puts vowels in unexpected places,"Hi, thanks for the detailed error description with the en-US key equivalents -- it really helps!
+
+I *think* this is resolved by the following patch: https://gerrit.wikimedia.org/r/#/c/79451 . At least, the patch seems to fix the ""hindi inscript (m17n)"" ibus method on Linux.",task_subcomment,"['Hi, thanks for the detailed error description with the en-US key equivalents -- it really helps!', 'I *think* this is resolved by the following patch: URL .', 'At least, the patch seems to fix the ""hindi inscript (m17n)"" ibus method on Linux.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+53472,VisualEditor: Backspace deletes combined character clusters together with diacritics,"Some scripts, among them Arabic, Hebrew, and most scripts of India and SE Asia, are written as combinations of consonants and vowel marks that combine with them.
+
+In most text editors and word processors, when the cursor is after a combination of a consonant and a vowel, and the backspace key s pressed, the vowel is deleted first and the the consonant.
+
+For example if you have the Devanagari combination गा (ग [g] + ा [a]), these are two Unicode characters, which the font joins automatically. If the cursor is after them and you press the backspace key, then the second character ( ा) is supposed to be deleted, and only then the first (ग). That is what happens in most text editors, including MediaWiki's source editor.
+
+In the VisualEditor, backspace immediately deletes the whole cluster. This behavior is unexpected for most users.
+
+To complicate things, when the cursor is before the combined character and the Delete key is pressed, the expected behavior is to delete the whole cluster. This is what happens in the VisualEditor now, and this must be kept like that. For cursor movement, back and forth, the cluster must also be treated as one character, so if the cursor is before गा and the right-pointing arrow is pressed, the cursor is supposed to immediately go after the गा. This also works correctly now, and must be kept.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49233
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53757",task_description,"['VisualEditor: Backspace deletes combined character clusters together with diacritics\n\nSome scripts, among them Arabic, Hebrew, and most scripts of India and SE Asia, are written as combinations of consonants and vowel marks that combine with them.', 'In most text editors and word processors, when the cursor is after a combination of a consonant and a vowel, and the backspace key s pressed, the vowel is deleted first and the the consonant.', 'For example if you have the Devanagari combination गा (ग [g] + ा [a]), these are two Unicode characters, which the font joins automatically.', 'If the cursor is after them and you press the backspace key, then the second character ( ा) is supposed to be deleted, and only then the first (ग).', ""That is what happens in most text editors, including MediaWiki's source editor."", 'In the VisualEditor, backspace immediately deletes the whole cluster.', 'This behavior is unexpected for most users.', 'To complicate things, when the cursor is before the combined character and the Delete key is pressed, the expected behavior is to delete the whole cluster.', 'This is what happens in the VisualEditor now, and this must be kept like that.', 'For cursor movement, back and forth, the cluster must also be treated as one character, so if the cursor is before गा and the right-pointing arrow is pressed, the cursor is supposed to immediately go after the गा.', 'This also works correctly now, and must be kept.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+250125,VisualEditor: Backspace deletes combined character clusters together with diacritics,"Change 80689 merged by jenkins-bot:
+Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",task_subcomment,['Change 80689 merged by jenkins-bot:\nRevert model to use simple UTF-16 code units\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250118,VisualEditor: Backspace deletes combined character clusters together with diacritics,"Change 80689 had a related patch set uploaded by Divec:
+DONTMERGE:Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",task_subcomment,['Change 80689 had a related patch set uploaded by Divec:\nDONTMERGE:Revert model to use simple UTF-16 code units\n\nGERRIT_URL'],['ACTION ON ISSUE']
+250110,VisualEditor: Backspace deletes combined character clusters together with diacritics,There's code in progress to fix this in gerrit 80689 which is currently a work-in-progress.,task_subcomment,"[""There's code in progress to fix this in gerrit 80689 which is currently a work-in-progress.""]",['SOLUTION DISCUSSION']
+250100,VisualEditor: Backspace deletes combined character clusters together with diacritics,"This is how we expect backspace to work with our current support of grapheme clusters. As Denis points out, being able to delete combining marks separately would have to be enabled on a per script basis, as we wouldn't want to require multiple keystrokes to remove e-acute, or a Jamo-constructed Hangul character.",task_subcomment,"['This is how we expect backspace to work with our current support of grapheme clusters.', ""As Denis points out, being able to delete combining marks separately would have to be enabled on a per script basis, as we wouldn't want to require multiple keystrokes to remove e-acute, or a Jamo-constructed Hangul character.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250091,VisualEditor: Backspace deletes combined character clusters together with diacritics,"(In reply to comment #1)
+> Could this be a dupe of -
+> https://bugzilla.wikimedia.org/show_bug.cgi?id=49233  ?
+
+Well, that one is marked as FIXED, and this one is definitely not fixed on master.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\n\nWell, that one is marked as FIXED, and this one is definitely not fixed on master.']",['BUG REPRODUCTION']
+250081,VisualEditor: Backspace deletes combined character clusters together with diacritics,"The expected behaviour of backspace can be different with different writing systems.
+
+In Indic scripts, as explained in the bug description, the most common behaviour is that backspace should erase one characters and delete should erase a cluster. See http://publib.boulder.ibm.com/infocenter/hodhelp/v10r0/topic/com.ibm.hod.doc/help/hindi.html#hindispecialkeys
+http://www-archive.mozilla.org/projects/ctl/tests/#indiceditoper
+
+For other scripts it might be different, particularly for Latin, Greek and Cyrillic where, because of the precomposed accented characters, it is expected that characters and character sequences (base character + combining diacritic) that represent units will behave the same way, i.e. backspace and delete erase the base and diacritic, for example the single character à and the two characters ɛ̀ should be treated the same way.
+
+http://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries talks about this.",task_subcomment,"['The expected behaviour of backspace can be different with different writing systems.', 'In Indic scripts, as explained in the bug description, the most common behaviour is that backspace should erase one characters and delete should erase a cluster.', 'See URL\nURL\n\nFor other scripts it might be different, particularly for Latin, Greek and Cyrillic where, because of the precomposed accented characters, it is expected that characters and character sequences (base character + combining diacritic) that represent units will behave the same way, i.e.', 'backspace and delete erase the base and diacritic, for example the single character à and the two characters ɛ̀ should be treated the same way.', 'URL talks about this.']","['EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250071,VisualEditor: Backspace deletes combined character clusters together with diacritics,"Could this be a dupe of -
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49233  ?",task_subcomment,['Could this be a dupe of -\nURL  ?'],['OBSERVED BUG BEHAVIOR']
+53463,VisualEditor: Don't extend links over wordbreaks,"With bug 49931 we currently extend link annotations when typing at the end. This makes it very difficult to type plain text after a link at the end of a paragraph.
+
+We should change the logic to stop extending the annotation once a character is added that produces a new wordbreak.
+
+There may be some odd cases as wordbreak logic can depend on more that two characters, e.g. a' has a wordbreak but a's doesn't, so trying to add ""'s"" to the end of a link label would break after the ""'"" even though it wouldn't if ""'s"" was added as one operation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51442",task_description,"[""VisualEditor: Don't extend links over wordbreaks\n\nWith bug 49931 we currently extend link annotations when typing at the end."", 'This makes it very difficult to type plain text after a link at the end of a paragraph.', 'We should change the logic to stop extending the annotation once a character is added that produces a new wordbreak.', 'There may be some odd cases as wordbreak logic can depend on more that two characters, e.g.', 'a\' has a wordbreak but a\'s doesn\'t, so trying to add ""\'s"" to the end of a link label would break after the ""\'"" even though it wouldn\'t if ""\'s"" was added as one operation.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+249675,VisualEditor: Don't extend links over wordbreaks,*** Bug 51531 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51531 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249667,VisualEditor: Don't extend links over wordbreaks,Fixed and will get deployed in a few minutes.,task_subcomment,['Fixed and will get deployed in a few minutes.'],['SOLUTION USAGE']
+249660,VisualEditor: Don't extend links over wordbreaks,"Change 74168 merged by jenkins-bot:
+Split continued link annotations on wordbreaks
+
+https://gerrit.wikimedia.org/r/74168",task_subcomment,['Change 74168 merged by jenkins-bot:\nSplit continued link annotations on wordbreaks\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249654,VisualEditor: Don't extend links over wordbreaks,"Change 74168 had a related patch set uploaded by Esanders:
+[WIP] Split continued link annotations on wordbreaks
+
+https://gerrit.wikimedia.org/r/74168",task_subcomment,['Change 74168 had a related patch set uploaded by Esanders:\n[WIP] Split continued link annotations on wordbreaks\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53462,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"See, for example, https://en.wikipedia.org/w/index.php?title=Peaches_Does_Herself&diff=prev&oldid=564544238 and https://en.wikipedia.org/w/index.php?title=Carl_Rogers&diff=prev&oldid=564544061 - this is kinda a problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T53509}",task_description,"['VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid\n\nSee, for example, URL and URL - this is kinda a problem.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T53509}']","['OBSERVED BUG BEHAVIOR', 'ISSUE CONTENT MANAGEMENT']"
+249632,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"(In reply to comment #12)
+> Reopening as this is still happening:
+> first nowiki after line 133 in
+> https://en.wikipedia.org/w/index.
+> php?title=Pet&diff=570614739&oldid=570586939 .
+
+That's almost certainly using a cached version of the code; I can't reproduce that on Chrome/Firefox/Safari/Opera on Mac or Linux.
+
+(In reply to comment #13)
+> I am also filing a related common problem we meet at it.wp.
+> If this is not the right place, just tell me and I'll copy/paste my report
+> elsewhere.
+
+Yeah, if you could file this as a new bug please - this is not related to removing whitespace from the start of paragraphs.",task_subcomment,"[""(In reply to comment #12)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's almost certainly using a cached version of the code; I can't reproduce that on Chrome/Firefox/Safari/Opera on Mac or Linux."", '(In reply to comment #13)\nQUOTE\nQUOTE\nQUOTE\n\nYeah, if you could file this as a new bug please - this is not related to removing whitespace from the start of paragraphs.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+249627,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"I am also filing a related common problem we meet at it.wp.
+If this is not the right place, just tell me and I'll copy/paste my report elsewhere.
+
+We had troubles with nowikis being thrown right after some templates when the user did not add an extra space there, but simply edited something in that page. See https://it.wikipedia.org/w/index.php?title=Wikipedia&diff=61171396&oldid=61171228 .
+
+We actually found a workaround for this: https://it.wikipedia.org/w/index.php?title=Template:Quote&curid=224372&diff=61173726&oldid=60749506 but since this addition is apparently a nonsense, users demand that VE prevents that behaviour instead.
+
+They also think this is related to templates featuring some kind of table.
+
+I did some tests as well.
+I was able to reproduce an unwanted situation where the first line and the table (which is actually a template) were mingled in a non-editable block https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61181542&oldid=61181524 .
+
+But I was also able to avoid nowikis, even if the extra span tags were not added to the template: as you can see here https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&diff=prev&oldid=61181473, if the first letter of the line is actually closer to the template's final brace (with no space between), VEditing that page will result in the text getting automatically placed in a better position, and no nowikis in sight, even after multiple saves of the page.
+
+Thanks.",task_subcomment,"['I am also filing a related common problem we meet at it.wp.', ""If this is not the right place, just tell me and I'll copy/paste my report elsewhere."", 'We had troubles with nowikis being thrown right after some templates when the user did not add an extra space there, but simply edited something in that page.', 'See URL .', 'We actually found a workaround for this: URL but since this addition is apparently a nonsense, users demand that VE prevents that behaviour instead.', 'They also think this is related to templates featuring some kind of table.', 'I did some tests as well.', 'I was able to reproduce an unwanted situation where the first line and the table (which is actually a template) were mingled in a non-editable block URL .', ""But I was also able to avoid nowikis, even if the extra span tags were not added to the template: as you can see here URL if the first letter of the line is actually closer to the template's final brace (with no space between), VEditing that page will result in the text getting automatically placed in a better position, and no nowikis in sight, even after multiple saves of the page."", 'Thanks.']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'WORKAROUNDS', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+249623,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"Reopening as this is still happening:
+first nowiki after line 133 in https://en.wikipedia.org/w/index.php?title=Pet&diff=570614739&oldid=570586939 .",task_subcomment,['Reopening as this is still happening:\nfirst nowiki after line 133 in URL .'],['OBSERVED BUG BEHAVIOR']
+249618,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"Now fixed in the code; next scheduled deployment is not until 15 August,
+however. :-(",task_subcomment,"['Now fixed in the code; next scheduled deployment is not until 15 August,\nhowever.', ':-(']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+249615,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"Change 77287 merged by jenkins-bot:
+Remove inserted leading whitespace
+
+https://gerrit.wikimedia.org/r/77287",task_subcomment,['Change 77287 merged by jenkins-bot:\nRemove inserted leading whitespace\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249613,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"So I just implemented a fix for this, but it broke a test that asserts that whitespace inside a pre is untouched. I'll put it a check for 
     elements but we should be aware that this is broken, because any element can have white-space:pre attached to it, e.g.
+
+    Foo
+
+Will now normalise to
+
+Foo
+
+Long term we should look into just warning the user.",task_subcomment,"['So I just implemented a fix for this, but it broke a test that asserts that whitespace inside a pre is untouched.', ""I'll put it a check for 
     elements but we should be aware that this is broken, because any element can have white-space:pre attached to it, e.g."", '    Foo\n\nWill now normalise to\n\nFoo\n\nLong term we should look into just warning the user.']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+249611,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"Change 77287 had a related patch set uploaded by Esanders:
+[WIP] Remove inserted leading whitepsace
+
+https://gerrit.wikimedia.org/r/77287",task_subcomment,['Change 77287 had a related patch set uploaded by Esanders:\n[WIP] Remove inserted leading whitepsace\n\nGERRIT_URL'],['BUG REPRODUCTION']
+249608,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"(In reply to comment #5)
+> With bug 50841 we now convert 
+> 
+> [space]Foo
+> 
+> to
+> 
+>  Foo
+> 
+> (previously  Foo)
+> 
+> This is the correct behaviour.
+
+Also, with gerrit 76223 VisualEditor users can now edit through s transparently.
+
+> Perhaps this, and other whitespace issues (e.g. double
+> spaces), should be flagged up to the user (with a wiggle underline?)
+
+That would be one solution that is quite generalisable, but could be a great deal more work.",task_subcomment,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAlso, with gerrit 76223 VisualEditor users can now edit through s transparently.', 'QUOTE\nQUOTE\n\nThat would be one solution that is quite generalisable, but could be a great deal more work.']","['SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+249605,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,*** Bug 52252 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52252 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249601,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"With bug 50841 we now convert 
+
+[space]Foo
+
+to
+
+ Foo
+
+(previously  Foo)
+
+This is the correct behaviour.
+
+We should be careful going do the road of automatically correcting what we believe to be typos. Perhaps this, and other whitespace issues (e.g. double spaces), should be flagged up to the user (with a wiggle underline?)",task_subcomment,"['With bug 50841 we now convert \n\n[space]Foo\n\nto\n\n Foo\n\n(previously  Foo)\n\nThis is the correct behaviour.', 'We should be careful going do the road of automatically correcting what we believe to be typos.', 'Perhaps this, and other whitespace issues (e.g.', 'double spaces), should be flagged up to the user (with a wiggle underline?)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+249598,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,*** Bug 51509 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51509 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249594,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"Without whitespace stripping (either in VE or Parsoid) and no nowiki, that text will become 
    -formatted.
+
+Quickly discussed with Gabriel on IRC. It is probably better fixed in VE since Parsoid doesn't have contextual information about where the space is meaningful or not.
+
+If leading whitespace at start of line is desired by the editor, then VE should convert them to   or if nowikis are acceptable, the spaces can be left alone.  In either case, this kind of edits should hopefully be rare.",task_subcomment,"['Without whitespace stripping (either in VE or Parsoid) and no nowiki, that text will become 
    -formatted.', 'Quickly discussed with Gabriel on IRC.', ""It is probably better fixed in VE since Parsoid doesn't have contextual information about where the space is meaningful or not."", 'If leading whitespace at start of line is desired by the editor, then VE should convert them to   or if nowikis are acceptable, the spaces can be left alone.', 'In either case, this kind of edits should hopefully be rare.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+249587,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"If VE can strip leading whitespace in paragraphs, that will eliminate these errors.  Alternatively, Parsoid can do that normalization. Unclear where this should be done.  Will discuss on IRC.",task_subcomment,"['If VE can strip leading whitespace in paragraphs, that will eliminate these errors.', 'Alternatively, Parsoid can do that normalization.', 'Unclear where this should be done.', 'Will discuss on IRC.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+249579,VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,and https://en.wikipedia.org/w/index.php?title=John_Altoon&diff=prev&oldid=564536250,task_subcomment,['and URL'],['SOLUTION DISCUSSION']
+53459,VisualEditor: Show the  message when creating a new article,"When creating a new article in the source editor, a box with the message newarticletext appears at the top. It doesn't appear in the VisualEditor.
+
+Compare:
+
+source: https://en.wikipedia.org/w/index.php?title=Aklotspa&action=edit
+
+VE: https://en.wikipedia.org/wiki/Aklotspa?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",task_description,"['VisualEditor: Show the  message when creating a new article\n\nWhen creating a new article in the source editor, a box with the message newarticletext appears at the top.', ""It doesn't appear in the VisualEditor."", 'Compare:\n\nsource: URL\n\nVE: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: trivial']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249429,VisualEditor: Show the  message when creating a new article,Fixed and will get deployed in a few minutes.,task_subcomment,['Fixed and will get deployed in a few minutes.'],['SOLUTION USAGE']
+249420,VisualEditor: Show the  message when creating a new article,"Change 75563 merged by jenkins-bot:
+Show newarticletext(anon) when creating a new page
+
+https://gerrit.wikimedia.org/r/75563",task_subcomment,['Change 75563 merged by jenkins-bot:\nShow newarticletext(anon) when creating a new page\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249414,VisualEditor: Show the  message when creating a new article,"Change 75563 had a related patch set uploaded by Esanders:
+Show newarticletext(anon) when creating a new page
+
+https://gerrit.wikimedia.org/r/75563",task_subcomment,['Change 75563 had a related patch set uploaded by Esanders:\nShow newarticletext(anon) when creating a new page\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+249409,VisualEditor: Show the  message when creating a new article,"The resolution of Bug 51160 gives me hope. French Wikipedia transcludes Talk:.../Suppression subpages for some deleted articles.
+ 
+https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial%3ARecherche&profile=advanced&search=Suppression&fulltext=Search&ns1=1&redirs=1&profile=advanced",task_subcomment,"['The resolution of Bug 51160 gives me hope.', 'French Wikipedia transcludes Talk:.../Suppression subpages for some deleted articles.', 'URL']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+249406,VisualEditor: Show the  message when creating a new article,"@James, before marking this trivial, I hope you did an impact assessment on
+1. https://de.wikipedia.org/wiki/MediaWiki:Newarticletext-0
+2. https://es.wikipedia.org/wiki/MediaWiki:Newarticletext
+3. https://fr.wikipedia.org/wiki/MediaWiki:Newarticletext
+4. https://he.wikipedia.org/wiki/MediaWiki:Newarticletext
+5. https://it.wikipedia.org/wiki/MediaWiki:Newarticletext
+6. https://nl.wikipedia.org/wiki/MediaWiki:Newarticletext
+7. https://pl.wikipedia.org/wiki/MediaWiki:Newarticletext
+8. https://ru.wikipedia.org/wiki/MediaWiki:Newarticletext
+9. https://sv.wikipedia.org/wiki/MediaWiki:Newarticletext
+
+I know you didn't, because on at least one of those projects there is critical functionality in this message.  Since you and O Keyes (on a different bug about missing interface messages) are being so rude, I'll let you find out the hard way.",task_subcomment,"['SCREEN_NAME, before marking this trivial, I hope you did an impact assessment on\n1.', 'URL\n2.', 'URL\n3.', 'URL\n4.', 'URL\n5.', 'URL\n6.', 'URL\n7.', 'URL\n8.', 'URL\n9.', ""URL\n\nI know you didn't, because on at least one of those projects there is critical functionality in this message."", ""Since you and O Keyes (on a different bug about missing interface messages) are being so rude, I'll let you find out the hard way.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOCIAL CONVERSATION']"
+249404,VisualEditor: Show the  message when creating a new article,"(In reply to comment #1)
+> This is something that obviously must be fixed before VE is enabled by
+> default, which is planned for Real Soon Now(tm).
+
+By default for whom on which wiki? It's been enabled by default on enwiki since 1 July for logged-in users and since 15 July for anonymous users too.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\n\nBy default for whom on which wiki?', ""It's been enabled by default on enwiki since 1 July for logged-in users and since 15 July for anonymous users too.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+249401,VisualEditor: Show the  message when creating a new article,"This is something that obviously must be fixed before VE is enabled by default, which is planned for Real Soon Now(tm).",task_subcomment,"['This is something that obviously must be fixed before VE is enabled by default, which is planned for Real Soon Now(tm).']",['SOLUTION DISCUSSION']
+53439,VisualEditor: Inspectors and context menu should close when blurring the document and/or when opening the save dialog,"1. Edit page
+2. Focus a link and open the link inspector, have the link input widget focussed
+3. Make a change (or don't) and click ""Save page"".
+
+The surface dims, but the inspector stays open and at full opacity.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Inspectors and context menu should close when blurring the document and/or when opening the save dialog\n\n1.', 'Edit page\n2.', 'Focus a link and open the link inspector, have the link input widget focussed\n3.', 'Make a change (or don\'t) and click ""Save page"".', 'The surface dims, but the inspector stays open and at full opacity.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248279,VisualEditor: Inspectors and context menu should close when blurring the document and/or when opening the save dialog,"Confirmed, the link and language inspectors close on triggering the save dialog.",task_subcomment,"['Confirmed, the link and language inspectors close on triggering the save dialog.']",['OBSERVED BUG BEHAVIOR']
+248274,VisualEditor: Inspectors and context menu should close when blurring the document and/or when opening the save dialog,"Is this fixed now? I can't reproduce this any more. Clicking Save page closes the link inspector for me, and it seems to save the changes correctly too.",task_subcomment,"['Is this fixed now?', ""I can't reproduce this any more."", 'Clicking Save page closes the link inspector for me, and it seems to save the changes correctly too.']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+248268,VisualEditor: Inspectors and context menu should close when blurring the document and/or when opening the save dialog,*** Bug 63050 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 63050 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248263,VisualEditor: Inspectors and context menu should close when blurring the document and/or when opening the save dialog,"Same for context menu (e.g. focus a link, but don't open the inspector yet)",task_subcomment,"['Same for context menu (e.g.', ""focus a link, but don't open the inspector yet)""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53415,"VisualEditor: Link inspector ignores typed text if user presses [enter] too quickly, explodes with new links","The link inspector ignores the text entered when the user does not wait for the ""matching page"" results to appear (Chrome/Ubuntu) before pressing ""enter"". If the user is adding a completely new link, the selection appears offscreen and we get a JavaScript error:
+
+Uncaught Error: No class registered by that name: undefined 
+
+This behavior is similar to earlier issues such as bug 42278 and bug 49941.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Link inspector ignores typed text if user presses [enter] too quickly, explodes with new links\n\nThe link inspector ignores the text entered when the user does not wait for the ""matching page"" results to appear (Chrome/Ubuntu) before pressing ""enter"".', 'If the user is adding a completely new link, the selection appears offscreen and we get a JavaScript error:\n\nUncaught Error: No class registered by that name: undefined \n\nThis behavior is similar to earlier issues such as bug 42278 and bug 49941.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+246849,"VisualEditor: Link inspector ignores typed text if user presses [enter] too quickly, explodes with new links",This is now merged and will be deployed later.,task_subcomment,['This is now merged and will be deployed later.'],['ACTION ON ISSUE']
+246845,"VisualEditor: Link inspector ignores typed text if user presses [enter] too quickly, explodes with new links","Change 76839 merged by jenkins-bot:
+Link inspector bug fixes
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 merged by jenkins-bot:\nLink inspector bug fixes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+246840,"VisualEditor: Link inspector ignores typed text if user presses [enter] too quickly, explodes with new links",*** Bug 52344 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52344 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246834,"VisualEditor: Link inspector ignores typed text if user presses [enter] too quickly, explodes with new links","Change 76839 had a related patch set uploaded by Trevor Parscal:
+The greatest commit in the history of the world*
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 had a related patch set uploaded by Trevor Parscal:\nThe greatest commit in the history of the world*\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+53406,VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases),"Templates should not have identically named parameters  (""url="", ""url="", for example). Can VisualEditor be configured to note when this happens, if not outright prevent it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases)\n\nTemplates should not have identically named parameters  (""url="", ""url="", for example).', 'Can VisualEditor be configured to note when this happens, if not outright prevent it?', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+246302,VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases),"I'm going to assume ""yes"" given testing.",task_subcomment,"['I\'m going to assume ""yes"" given testing.']",['OBSERVED BUG BEHAVIOR']
+246297,VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases),Works for me... Has this been fixed since it was reported?,task_subcomment,['Works for me... Has this been fixed since it was reported?'],['BUG REPRODUCTION']
+53404,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"* Edit a page
+* Put cursor at the end of a line
+* Go to toolbar and Insert new link
+* The input field is focussed, blur it by clicking somewhere inside the inspector outside the input field
+* Click the trash can (since there is no ""x"" close button, that's the closest I can find in the top left or right corner)
+* The inspector clears itself but stays behind (crashes half-way closing)
+
+
+Uncaught Error: No class registered by that name: undefined ve.Factory.js:62
+ve.Factory.create ve.Factory.js:62
+ve.dm.SurfaceFragment.annotateContent ve.dm.SurfaceFragment.js:518
+ve.ui.AnnotationInspector.onClose ve.ui.AnnotationInspector.js:162
+ve.ui.Window.close ve.ui.Window.js:281
+ve.ui.Inspector.onRemoveButtonClick ve.ui.Inspector.js:89
+oo.EventEmitter.emit oo.js:421
+ve.ui.IconButtonWidget.onClick ve.ui.IconButtonWidget.js:61
+proxy load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20130715T175253Z:775
+jQuery.event.dispatch load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20130715T175253Z:3058
+elemData.handle.eventHandle
+
+
+An empty inspector stays behind and the user can no longer interact with any links at this point. When doing anything (scrolling, typing) the inspector will hide. Except the bubble tip on top, that one stays behind...
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",task_description,"['VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection\n\n* Edit a page\n* Put cursor at the end of a line\n* Go to toolbar and Insert new link\n* The input field is focussed, blur it by clicking somewhere inside the inspector outside the input field\n* Click the trash can (since there is no ""x"" close button, that\'s the closest I can find in the top left or right corner)\n* The inspector clears itself but stays behind (crashes half-way closing)\n\n\nUncaught Error: No class registered by that name: undefined ve.Factory.js:62\nve.Factory.create ve.Factory.js:62\nve.dm.SurfaceFragment.annotateContent ve.dm.SurfaceFragment.js:518\nve.ui.AnnotationInspector.onClose ve.ui.AnnotationInspector.js:162\nve.ui.Window.close ve.ui.Window.js:281\nve.ui.Inspector.onRemoveButtonClick ve.ui.Inspector.js:89\noo.EventEmitter.emit oo.js:421\nve.ui.IconButtonWidget.onClick ve.ui.IconButtonWidget.js:61\nproxy load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20130715T175253Z:775\njQuery.event.dispatch load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20130715T175253Z:3058\nelemData.handle.eventHandle\n\n\nAn empty inspector stays behind and the user can no longer interact with any links at this point.', 'When doing anything (scrolling, typing) the inspector will hide.', 'Except the bubble tip on top, that one stays behind...\n\n--------------------------\n**Version**: unspecified\n**Severity**: critical']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246201,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,*** Bug 51984 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51984 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246197,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,This is now merged and will be deployed later.,task_subcomment,['This is now merged and will be deployed later.'],['ACTION ON ISSUE']
+246192,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"Change 76839 merged by jenkins-bot:
+Link inspector bug fixes
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 merged by jenkins-bot:\nLink inspector bug fixes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+246187,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"Change 76839 had a related patch set uploaded by Trevor Parscal:
+The greatest commit in the history of the world*
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 had a related patch set uploaded by Trevor Parscal:\nThe greatest commit in the history of the world*\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+246178,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"I can reproduce this by putting the cursor on a blank line (such as an empty page), clicking link inspector icon, then pressing key 'Esc'.",task_subcomment,"[""I can reproduce this by putting the cursor on a blank line (such as an empty page), clicking link inspector icon, then pressing key 'Esc'.""]",['OBSERVED BUG BEHAVIOR']
+246171,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"Bug 51415 is reporting the same JS error in the same component, with different steps to reproduce.",task_subcomment,"['Bug 51415 is reporting the same JS error in the same component, with different steps to reproduce.']",['OBSERVED BUG BEHAVIOR']
+246165,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,I've just tested this and can reproduce it except for comment 3 - in my test I was able to do everything except link and the save worked as expected.,task_subcomment,"[""I've just tested this and can reproduce it except for comment 3 - in my test I was able to do everything except link and the save worked as expected.""]",['BUG REPRODUCTION']
+246159,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"It could be just be, but I run into this quite often. Every time it happens the interface crashes unrecoverably and all work is lost.",task_subcomment,"['It could be just be, but I run into this quite often.', 'Every time it happens the interface crashes unrecoverably and all work is lost.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246153,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"Created attachment 12854
+Screenshot of problem
+
+**Attached**: {F11587}",task_subcomment,['Created attachment 12854\nScreenshot of problem\n\n**Attached**: {F11587}'],['ATTACHMENT']
+246147,VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"Note, this doesn't seem a race condition or anything. I'm giving it at least half a second to a second of time between each distinct action.",task_subcomment,"[""Note, this doesn't seem a race condition or anything."", ""I'm giving it at least half a second to a second of time between each distinct action.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53403,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property","Screenshot of problem in local VisualEditor dev
+
+The code [1] is using $status->getHtml() but apparently it doesn't work as expected because I'm getting raw wikitext.
+
+        ""edit"": {
+            ""code"": ""abusefilter-warning"",
+            ""info"": ""Hit AbuseFilter: Blanking articles"",
+            ""warning"": ""'''Warning:''' This action has been automatically identified as harmful.\nUnconstructive edits will be quickly reverted,\nand egregious or repeated unconstructive editing will result in your account or IP address being blocked.\nIf you believe this action to be constructive, you may submit it again to confirm it.\nA brief description of the abuse rule which your action matched is: Blanking articles"",
+            ""result"": ""Failure""
+        }
+
+To import the filter, use ""Special:AbuseFilter/import"" on your localwiki with:
+
+{""row"":{""af_id"":""1"",""af_pattern"":""!\""autoconfirmed\"" in user_groups\r\n& new_size < 50\r\n& old_size > 500\r\n& article_namespace == 0"",""af_user"":""1"",""af_user_text"":""Root"",""af_timestamp"":""20130715214820"",""af_enabled"":""1"",""af_comments"":"""",""af_public_comments"":""Blanking articles"",""af_hidden"":""0"",""af_hit_count"":""9"",""af_throttled"":""1"",""af_deleted"":""0"",""af_actions"":""warn,disallow,tag"",""af_global"":""0"",""af_group"":""default""},""actions"":{""disallow"":{""action"":""disallow"",""parameters"":[""""]},""tag"":{""action"":""tag"",""parameters"":[""blanking""]},""warn"":{""action"":""warn"",""parameters"":[""abusefilter-warning""]}}}
+
+
+
+[1] https://github.com/wikimedia/mediawiki-extensions-AbuseFilter/blob/a6b1dade840841ff7adf2ff289b6428f930d6796/AbuseFilter.hooks.php#L22-L57
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11585}",task_description,"['AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property\n\nScreenshot of problem in local VisualEditor dev\n\nThe code [1] is using $status->getHtml() but apparently it doesn\'t work as expected because I\'m getting raw wikitext.', '""edit"": {\n            ""code"": ""abusefilter-warning"",\n            ""info"": ""Hit AbuseFilter: Blanking articles"",\n            ""warning"": ""\'\'\'Warning:\'\'\' This action has been automatically identified as harmful.\\nUnconstructive edits will be quickly reverted,\\nand egregious or repeated unconstructive editing will result in your account or IP address being blocked.\\nIf you believe this action to be constructive, you may submit it again to confirm it.\\nA brief description of the abuse rule which your action matched is: Blanking articles"",\n            ""result"": ""Failure""\n        }\n\nTo import the filter, use ""Special:AbuseFilter/import"" on your localwiki with:\n\n{""row"":{""af_id"":""1"",""af_pattern"":""!\\""autoconfirmed\\"" in user_groups\\r\\n& new_size < 50\\r\\n& old_size > 500\\r\\n& article_namespace == 0"",""af_user"":""1"",""af_user_text"":""Root"",""af_timestamp"":""20130715214820"",""af_enabled"":""1"",""af_comments"":"""",""af_public_comments"":""Blanking articles"",""af_hidden"":""0"",""af_hit_count"":""9"",""af_throttled"":""1"",""af_deleted"":""0"",""af_actions"":""warn,disallow,tag"",""af_global"":""0"",""af_group"":""default""},""actions"":{""disallow"":{""action"":""disallow"",""parameters"":[""""]},""tag"":{""action"":""tag"",""parameters"":[""blanking""]},""warn"":{""action"":""warn"",""parameters"":[""abusefilter-warning""]}}}\n\n\n\n[1] URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11585}']","['MOTIVATION', '1']"
+246097,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property",We will deploy this fix today.,task_subcomment,['We will deploy this fix today.'],['ACTION ON ISSUE']
+246089,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property","Change 73895 merged by jenkins-bot:
+Really parse the API warning in the APIEditBeforeSave hook
+
+https://gerrit.wikimedia.org/r/73895",task_subcomment,['Change 73895 merged by jenkins-bot:\nReally parse the API warning in the APIEditBeforeSave hook\n\nGERRIT_URL'],['ACTION ON ISSUE']
+246082,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property","(Sorry, if my last comment was unlcear:) Showing the full warning message, I mean.",task_subcomment,"['(Sorry, if my last comment was unlcear:) Showing the full warning message, I mean.']",['SOLUTION DISCUSSION']
+246074,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property","(In reply to comment #2)
+> I don't think this is really what people want to be doing (regardless of
+> whether HTML is being presented by this call or not). Take a look at filter
+> 554
+> on English Wikipedia (http://en.wikipedia.org/wiki/Special:AbuseFilter/554).
+> Note how it triggers a message of abusefilter-top100. That causes the
+> standard
+> wikitext editor to display
+> http://en.wikipedia.org/w/index.php?title=MediaWiki:abusefilter-top100 which
+> explains what's wrong with the edit. That's what you need to display, not the
+> short description (in this case ""top100 blog charts"", which doesn't mean
+> squat
+> to a new editor).
+
+That's exactly what we're trying to do.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's exactly what we're trying to do.""]",['SOLUTION DISCUSSION']
+246065,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property","Change 73895 had a related patch set uploaded by Hoo man:
+Really parse the API warning in the APIEditBeforeSave hook
+
+https://gerrit.wikimedia.org/r/73895",task_subcomment,['Change 73895 had a related patch set uploaded by Hoo man:\nReally parse the API warning in the APIEditBeforeSave hook\n\nGERRIT_URL'],['ACTION ON ISSUE']
+246055,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property","**kwwilliams** wrote:
+
+I don't think this is really what people want to be doing (regardless of whether HTML is being presented by this call or not). Take a look at filter 554 on English Wikipedia (http://en.wikipedia.org/wiki/Special:AbuseFilter/554). Note how it triggers a message of abusefilter-top100. That causes the standard wikitext editor to display http://en.wikipedia.org/w/index.php?title=MediaWiki:abusefilter-top100 which explains what's wrong with the edit. That's what you need to display, not the short description (in this case ""top100 blog charts"", which doesn't mean squat to a new editor).",task_subcomment,"[""**kwwilliams** wrote:\n\nI don't think this is really what people want to be doing (regardless of whether HTML is being presented by this call or not)."", 'Take a look at filter 554 on English Wikipedia (URL Note how it triggers a message of abusefilter-top100.', ""That causes the standard wikitext editor to display URL which explains what's wrong with the edit."", 'That\'s what you need to display, not the short description (in this case ""top100 blog charts"", which doesn\'t mean squat to a new editor).']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+246047,"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property",That's because Status::getHTML isn't actually doing real parsing... going to look at this tomorrow,task_subcomment,"[""That's because Status::getHTML isn't actually doing real parsing... going to look at this tomorrow""]",['OBSERVED BUG BEHAVIOR']
+53375,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)\n\nSometimes for templates, you have a pre-defined set of values to use for a parameter.', 'Perhaps it could be a nice thing to expose valid values to the user in a drop down or something.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1841604,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)","If I have a template that accepts three values for `foo` and renders an error if given anything else, would the user be able to enter a disallowed value using the ""suggested values"" user interface in such a way that they will not be surprised or dissapointed to see an error in the rendering – after they have saved their changes in the template dialog?
+
+If I understand correctly, the ""suggested value"" feature is about autocompleting and/or recommending values in a free-form input field, and does not intend to add friction, make impossible, or ""power-user only"" to enter other free-form values, e.g. a basic HTML select field with no easy way to break out of it, unless the page had a pre-existing unexpected value that VE would need to accomodate for roundtrip. That is what an ""options"" or ""ENUM"" feature would be like in the end, I think.
+
+Having said that, implementing suggested values first is fine of course. And depending on the kind of user experience you want to deliver, it might even make sense to provide both of these as part of the same single input type, with a toggleable restriction for free-form values (`allowOther: false`?). There are many ways to implement these two features differently and I don't think it's obvious that they'll be similar in logic and look, but it is also possible to make them similar/shared. Whether that's the best UX, I don't know. Something to consider I suppose :)",task_subcomment,"['If I have a template that accepts three values for CODE and renders an error if given anything else, would the user be able to enter a disallowed value using the ""suggested values"" user interface in such a way that they will not be surprised or dissapointed to see an error in the rendering – after they have saved their changes in the template dialog?', 'If I understand correctly, the ""suggested value"" feature is about autocompleting and/or recommending values in a free-form input field, and does not intend to add friction, make impossible, or ""power-user only"" to enter other free-form values, e.g.', 'a basic HTML select field with no easy way to break out of it, unless the page had a pre-existing unexpected value that VE would need to accomodate for roundtrip.', 'That is what an ""options"" or ""ENUM"" feature would be like in the end, I think.', 'Having said that, implementing suggested values first is fine of course.', 'And depending on the kind of user experience you want to deliver, it might even make sense to provide both of these as part of the same single input type, with a toggleable restriction for free-form values (CODE?).', ""There are many ways to implement these two features differently and I don't think it's obvious that they'll be similar in logic and look, but it is also possible to make them similar/shared."", ""Whether that's the best UX, I don't know."", 'Something to consider I suppose :)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1684652,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)",">>! In T53375#5769182, @Tacsipacsi wrote:
+> ```lang=json
+> 			{""label"": ..., ""value"": ...},
+> ```
+where the label should be an InterfaceText (i.e. localizable) or null; like all other InterfaceTexts, plain string input should be accepted and transformed by the extension. The value is a plain string, of course.",task_subcomment,"['QUOTE\nQUOTE\nwhere the label should be an InterfaceText (i.e.', 'localizable) or null; like all other InterfaceTexts, plain string input should be accepted and transformed by the extension.', 'The value is a plain string, of course.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1417852,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)","Change 263655 restored by Krinkle:
+[WIP] Add a parameter key to limit possible valid values to a given set
+
+[[https://gerrit.wikimedia.org/r/263655]]",task_subcomment,['Change 263655 restored by Krinkle:\n[WIP] Add a parameter key to limit possible valid values to a given set\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+962355,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)",It would also be useful to be able to use a set of possible values provided by some template/module.,task_subcomment,['It would also be useful to be able to use a set of possible values provided by some template/module.'],['SOLUTION DISCUSSION']
+955145,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)","Change 263655 abandoned by Alex Monk:
+[WIP] Add a parameter key to limit possible valid values to a given set
+
+[[https://gerrit.wikimedia.org/r/263655]]",task_subcomment,['Change 263655 abandoned by Alex Monk:\n[WIP] Add a parameter key to limit possible valid values to a given set\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+589170,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)",">>! In T53375#564935, @Krinkle wrote:
+>  params: {
+>   ""key"": {
+>     ""type"": ...
+>     ""values"": [ .. ]
+
+Seems a good way of specifying it, +1",task_subcomment,"['QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nSeems a good way of specifying it, +1']",['SOLUTION DISCUSSION']
+1658584,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)","Yeah, we should add this. Though it doesn't have to be as a parameter type. I imagine we could also do it more generically.
+
+ params: {
+  ""key"": {
+    ""type"": ...
+    ""values"": [ .. ]
+
+The upside is that this is easier to specify and validate.
+
+An nice bonus is that it would allow one to preserve types regardless of whether the possible values are finite or not (e.g. freeform strings, numbers, dates, page names).
+
+Down side is that it's tricky for consumers like VisualEditor to have a dropdown menu for values that aren't simple strings.
+
+But I think that's fine. Those consumers can choose to support it however they like. E.g. they could support ""values"" only for string values.
+
+As a nice bonus this would allow VisualEditor to make dedicated select interfaces much better. E.g. a colour picker with limited values could be a row with squares and you visually pick one of those colours (like radio buttons). And a parameter that takes file names (e.g. for icons), could have live previews for the 10 different icons it supports.
+
+The type-restricted implementation would look something like this:
+
+ params: {
+  ""key"": {
+    ""type"": ""options""
+    ""values"": [ .. ]
+
+And would treat them as type: 'string' with no further type association.
+
+It also has the downside of having a ""param"" property (values) that only makes sense in combination with another. Making it slightly less intuitive.",task_subcomment,"['Yeah, we should add this.', ""Though it doesn't have to be as a parameter type."", 'I imagine we could also do it more generically.', 'params: {\n  ""key"": {\n    ""type"": ...\n    ""values"": [ .. ]\n\nThe upside is that this is easier to specify and validate.', 'An nice bonus is that it would allow one to preserve types regardless of whether the possible values are finite or not (e.g.', 'freeform strings, numbers, dates, page names).', ""Down side is that it's tricky for consumers like VisualEditor to have a dropdown menu for values that aren't simple strings."", ""But I think that's fine."", 'Those consumers can choose to support it however they like.', 'E.g.', 'they could support ""values"" only for string values.', 'As a nice bonus this would allow VisualEditor to make dedicated select interfaces much better.', 'E.g.', 'a colour picker with limited values could be a row with squares and you visually pick one of those colours (like radio buttons).', 'And a parameter that takes file names (e.g.', 'for icons), could have live previews for the 10 different icons it supports.', 'The type-restricted implementation would look something like this:\n\n params: {\n  ""key"": {\n    ""type"": ""options""\n    ""values"": [ .. ]\n\nAnd would treat them as type: \'string\' with no further type association.', 'It also has the downside of having a ""param"" property (values) that only makes sense in combination with another.', 'Making it slightly less intuitive.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+244445,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)",*** Bug 52754 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52754 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244435,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)",*** Bug 50760 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50760 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244420,"TemplateData: Add parameter type for selecting one of predefined values (like """" or ENUM)","See ""bug 50760 - Support suggested values"" which is quite similar.
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50760",task_subcomment,"['See ""bug 50760 - Support suggested values"" which is quite similar.', 'URL']","['MOTIVATION', 'SOLUTION DISCUSSION']"
+53330,VisualEditor: Set i18n toolbar icons for bold/italics,"Forked from T53314#557160 (bug 51314 comment 2):
+
+The following should be set to use B/I, rather than the generic:
+
+* cs Czech
+* he Hebrew
+* pl Polish
+
+The following should be set to use F/K, rather than the generic:
+
+* da Danish
+* no Norwegian (and nn?)
+* sv Swedish
+",task_description,"['VisualEditor: Set i18n toolbar icons for bold/italics\n\nForked from T53314#557160 (bug 51314 comment 2):\n\nThe following should be set to use B/I, rather than the generic:\n\n* cs Czech\n* he Hebrew\n* pl Polish\n\nThe following should be set to use F/K, rather than the generic:\n\n* da Danish\n* no Norwegian (and nn?)', '* sv Swedish']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+241917,VisualEditor: Set i18n toolbar icons for bold/italics,This is now done; we'll deploy this within the hour.,task_subcomment,"[""This is now done; we'll deploy this within the hour.""]",['ACTION ON ISSUE']
+241914,VisualEditor: Set i18n toolbar icons for bold/italics,"Change 73850 merged by jenkins-bot:
+Set bold/italics icons for cs/he/pl; da/no/nn/sv
+
+https://gerrit.wikimedia.org/r/73850",task_subcomment,['Change 73850 merged by jenkins-bot:\nSet bold/italics icons for cs/he/pl; da/no/nn/sv\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241910,VisualEditor: Set i18n toolbar icons for bold/italics,"Change 73850 had a related patch set uploaded by Jforrester:
+Set bold/italics icons for cs/he/pl; da/no/nn/sv
+
+https://gerrit.wikimedia.org/r/73850",task_subcomment,['Change 73850 had a related patch set uploaded by Jforrester:\nSet bold/italics icons for cs/he/pl; da/no/nn/sv\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53322,VisualEditor: Handle 'meta' templates better,"Some templates are only used to include metadata, e.g. categories. In this example http://en.wikipedia.org/w/index.php?title=Ashton_Agar&oldid=564224425&veaction=edit the document starts with two such categories, producing linebreak characters, with templates spanning 0 characters in between (accessible still be cursoring). An uninitiated user may just decide to delete this whole line at the the top, thus removing the hidden templates.
+
+Perhaps we need to detect if a template contains no meaningful content and then move it into the metadata so it can't be accidentally deleted. We'd also need a UI for editing them though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51420",task_description,"[""VisualEditor: Handle 'meta' templates better\n\nSome templates are only used to include metadata, e.g."", 'categories.', 'In this example URL the document starts with two such categories, producing linebreak characters, with templates spanning 0 characters in between (accessible still be cursoring).', 'An uninitiated user may just decide to delete this whole line at the the top, thus removing the hidden templates.', ""Perhaps we need to detect if a template contains no meaningful content and then move it into the metadata so it can't be accidentally deleted."", ""We'd also need a UI for editing them though."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+241551,VisualEditor: Handle 'meta' templates better,Additional issue with empty HTML elements produced by templates (which are used for metadata) in bug 52551.,task_subcomment,['Additional issue with empty HTML elements produced by templates (which are used for metadata) in bug 52551.'],['OBSERVED BUG BEHAVIOR']
+241545,VisualEditor: Handle 'meta' templates better,Fixed and will get deployed in a few minutes.,task_subcomment,['Fixed and will get deployed in a few minutes.'],['SOLUTION USAGE']
+241538,VisualEditor: Handle 'meta' templates better,"Change 75331 merged by jenkins-bot:
+Handle meta-only transclusions as meta items
+
+https://gerrit.wikimedia.org/r/75331",task_subcomment,['Change 75331 merged by jenkins-bot:\nHandle meta-only transclusions as meta items\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241530,VisualEditor: Handle 'meta' templates better,"I marked this as a dup of bug 49806, not dup of 51420.",task_subcomment,"['I marked this as a dup of bug 49806, not dup of 51420.']",['OBSERVED BUG BEHAVIOR']
+241522,VisualEditor: Handle 'meta' templates better,"Change 75331 had a related patch set uploaded by Esanders:
+Handle meta-only transculsions as meta items
+
+https://gerrit.wikimedia.org/r/75331",task_subcomment,['Change 75331 had a related patch set uploaded by Esanders:\nHandle meta-only transculsions as meta items\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241514,VisualEditor: Handle 'meta' templates better,This is not the same as bug 51420. This specifically concerns templates which only produce 'metadata' in the VE-data-model meaning of the term.,task_subcomment,"['This is not the same as bug 51420.', ""This specifically concerns templates which only produce 'metadata' in the VE-data-model meaning of the term.""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+241505,VisualEditor: Handle 'meta' templates better,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49806 ***'],['ISSUE CONTENT MANAGEMENT']
+241499,VisualEditor: Handle 'meta' templates better,Another example given on WP:VEF is {{Link FA}},task_subcomment,['Another example given on WP:VEF is {{Link FA}}'],['SOLUTION DISCUSSION']
+241490,VisualEditor: Handle 'meta' templates better,"To help searching: the cited examples are {{Use dmy dates}} and {{Use Australian English}}.
+
+Increasing importance/priority because they can be deleted unintentionally, and it is very unlikely a new user will know how to add them back before they click save.",task_subcomment,"['To help searching: the cited examples are {{Use dmy dates}} and {{Use Australian English}}.', 'Increasing importance/priority because they can be deleted unintentionally, and it is very unlikely a new user will know how to add them back before they click save.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+53304,"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues","**Author:** `wmdv`
+
+**Description:**
+I changed the word ""you"" to ""your"" by inserting an ""r,"" in [[Gerrit/Tutorial]], but the edit summary said I inserted 10 characters, and the [https://www.mediawiki.org/w/index.php?title=Gerrit/Tutorial&diff=prev&oldid=732497 diff report] showed about 15 lines, with various things shifted around.  I was using Chrom on Windows 8.
+
+I reported this on the support page, and 88.130.86.210‎17:17, July 13, 2013 reverted my edit, and suggested I file a bug report. [https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Extensive_diff_report. Support desk resolution.]
+
+I have also been noticing that when a change comes up on my Wikipedia watch list, I sometimes have difficulty telling what an editor did, because the diff report is full of unmodified content.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Extensive_diff_report%2E",task_description,"['VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues\n\n**Author:** CODE\n\n**Description:**\nI changed the word ""you"" to ""your"" by inserting an ""r,"" in [[Gerrit/Tutorial]], but the edit summary said I inserted 10 characters, and the [URL diff report] showed about 15 lines, with various things shifted around.', 'I was using Chrom on Windows 8.', 'I reported this on the support page, and 88.130.86.210\u200e17:17, July 13, 2013 reverted my edit, and suggested I file a bug report.', '[URL Support desk resolution.]', 'I have also been noticing that when a change comes up on my Wikipedia watch list, I sometimes have difficulty telling what an editor did, because the diff report is full of unmodified content.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+399859,"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues",No ability to track this down and no recurrence in over a year; closing.,task_subcomment,['No ability to track this down and no recurrence in over a year; closing.'],['ACTION ON ISSUE']
+240387,"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues",Very odd corruption; assigning.,task_subcomment,['Very odd corruption; assigning.'],['OBSERVED BUG BEHAVIOR']
+240380,"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues","Trying to manually encode the dot again... It didn't work even on the URL field.
+
+https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Extensive_diff_report%2E",task_subcomment,"['Trying to manually encode the dot again...', ""It didn't work even on the URL field."", 'URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+240375,"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues","**wmdv** wrote:
+
+I am unable to enter the correct url, because it ends with a period, which seems to confuse bugzilla.",task_subcomment,"['**wmdv** wrote:\n\nI am unable to enter the correct url, because it ends with a period, which seems to confuse bugzilla.']",['OBSERVED BUG BEHAVIOR']
+240371,"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues","**wmdv** wrote:
+
+The url for the support desk case is [https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Extensive_diff_report.]",task_subcomment,['**wmdv** wrote:\n\nThe url for the support desk case is [URL'],['WORKAROUNDS']
+53293,VisualEditor: Set image alignment in the media dialog,"From English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):
+
+Inserted images are formatted as right-aligned, and they can't be move to the left side of the page. Similarly, existing images that are left-aligned can't be moved to the right side of the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: Set image alignment in the media dialog\n\nFrom English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):\n\nInserted images are formatted as right-aligned, and they can't be move to the left side of the page."", ""Similarly, existing images that are left-aligned can't be moved to the right side of the page."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239795,VisualEditor: Set image alignment in the media dialog,"Change 105225 merged by jenkins-bot:
+Adding position setting to media edit dialog
+
+https://gerrit.wikimedia.org/r/105225",task_subcomment,['Change 105225 merged by jenkins-bot:\nAdding position setting to media edit dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239789,VisualEditor: Set image alignment in the media dialog,"Change 105225 had a related patch set uploaded by Jforrester:
+Adding position setting to media edit dialog
+
+https://gerrit.wikimedia.org/r/105225",task_subcomment,['Change 105225 had a related patch set uploaded by Jforrester:\nAdding position setting to media edit dialog\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239782,VisualEditor: Set image alignment in the media dialog,"It's not a problem with right-to-left languages ;)
+
+Removing the tracking bug.",task_subcomment,"[""It's not a problem with right-to-left languages ;)\n\nRemoving the tracking bug.""]",['ACTION ON ISSUE']
+239777,VisualEditor: Set image alignment in the media dialog,"Permanent diff: 
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564362312#Issues_with_images",task_subcomment,['Permanent diff: \nURL'],['OBSERVED BUG BEHAVIOR']
+239774,VisualEditor: Set image alignment in the media dialog,"I've copied his words verbatim as part of a long string of issues, but if it is helpful for you to see these word in context, it will be here until it archives:
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Templates_not_aligned",task_subcomment,"[""I've copied his words verbatim as part of a long string of issues, but if it is helpful for you to see these word in context, it will be here until it archives:\nURL""]",['OBSERVED BUG BEHAVIOR']
+239771,VisualEditor: Set image alignment in the media dialog,"Is bug 51295 a duplicate?
+
+(In reply to comment #0)
+> From English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):
+
+An URL is always highly welcome.",task_subcomment,"['Is bug 51295 a duplicate?', '(In reply to comment #0)\nQUOTE\n\nAn URL is always highly welcome.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+53292,"VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g. into the middle of a word, middle of a paragraph)","From English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):
+
+VE allows the image to be dropped into the middle of a word. I moved the test image perhaps a dozen times, and this happened twice - that shouldn't be possible, yes? [The words that were split were ""addition"" and ""Israel""; when I moved the image again, the words remained split (with an end-of-line inserted).]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g.', 'into the middle of a word, middle of a paragraph)\n\nFrom English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):\n\nVE allows the image to be dropped into the middle of a word.', ""I moved the test image perhaps a dozen times, and this happened twice - that shouldn't be possible, yes?"", '[The words that were split were ""addition"" and ""Israel""; when I moved the image again, the words remained split (with an end-of-line inserted).]', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+239739,"VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g. into the middle of a word, middle of a paragraph)","51666 is the more general bug for relocating block items.
+
+*** This bug has been marked as a duplicate of bug 51666 ***",task_subcomment,"['51666 is the more general bug for relocating block items.', '*** This bug has been marked as a duplicate of bug 51666 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239737,"VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g. into the middle of a word, middle of a paragraph)",The initial plan is to try bug 65883 and see whether this is a good enough solution.,task_subcomment,['The initial plan is to try bug 65883 and see whether this is a good enough solution.'],['SOLUTION DISCUSSION']
+239735,"VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g. into the middle of a word, middle of a paragraph)",*** Bug 52657 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52657 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239731,"VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g. into the middle of a word, middle of a paragraph)",So what is the way to fix this?,task_subcomment,['So what is the way to fix this?'],['SOLUTION DISCUSSION']
+239729,"VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g. into the middle of a word, middle of a paragraph)","en.wp user Fram comments:
+""it should be made impossible that when people move images in VE (which is very easy), they put it (inadvertently) in the middle of a word. Preferably, images should only be movable to spaces between paragraphs, but they certainly shouldn't be movable to the middle of a word. Example: [https://en.wikipedia.org/w/index.php?title=Egypt%E2%80%93United_States_relations&curid=15982815&diff=566841885&oldid=565660404]
+
+The problem seems to be that when you move a picture, the final location is not decided by the upper left corner of the image (which seems more intuitive to me), but by the location of your cursor somewhere in the middle of the picture.""",task_subcomment,"['en.wp user Fram comments:\n""it should be made impossible that when people move images in VE (which is very easy), they put it (inadvertently) in the middle of a word.', ""Preferably, images should only be movable to spaces between paragraphs, but they certainly shouldn't be movable to the middle of a word."", 'Example: [URL\n\nThe problem seems to be that when you move a picture, the final location is not decided by the upper left corner of the image (which seems more intuitive to me), but by the location of your cursor somewhere in the middle of the picture.""']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+239723,"VisualEditor: It should be clearer to users that they are inserting a media item in an odd place (e.g. into the middle of a word, middle of a paragraph)",*** Bug 52178 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52178 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53270,VisualEditor: Mobile Google Chrome text cursor hides link object icon,"On Google Chrome on Galaxy Note 2
+
+1. open VE
+2. 'click' on a link
+
+Results:
+The text cursor appears at the character of text selected.
+The link editor icon appears below the character of text selected.
+The text cursor makes it impossible? to click on the link editor icon.
+
+One solution would be to place the link editor icon above the linked text, and ideally place it always at the end of the linked text instead of at the character where the text cursor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Mobile Google Chrome text cursor hides link object icon\n\nOn Google Chrome on Galaxy Note 2\n\n1. open VE\n2.', ""'click' on a link\n\nResults:\nThe text cursor appears at the character of text selected."", 'The link editor icon appears below the character of text selected.', 'The text cursor makes it impossible?', 'to click on the link editor icon.', 'One solution would be to place the link editor icon above the linked text, and ideally place it always at the end of the linked text instead of at the character where the text cursor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238455,VisualEditor: Mobile Google Chrome text cursor hides link object icon,The mobile version of VisualEditor doesn't do text over-lays to avoid issues like this bug. Closing as INVALID now that work there is progressing.,task_subcomment,"[""The mobile version of VisualEditor doesn't do text over-lays to avoid issues like this bug."", 'Closing as INVALID now that work there is progressing.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+238451,VisualEditor: Mobile Google Chrome text cursor hides link object icon,"Clicking the link icon at the top of the article works, which is a reasonable workaround. Dropping priority.",task_subcomment,"['Clicking the link icon at the top of the article works, which is a reasonable workaround.', 'Dropping priority.']","['WORKAROUNDS', 'ACTION ON ISSUE']"
+238444,VisualEditor: Mobile Google Chrome text cursor hides link object icon,"The link icon moves when the text cursor is moved.
+
+It is possible to zoom in to press the link icon, but it is very fiddly.",task_subcomment,"['The link icon moves when the text cursor is moved.', 'It is possible to zoom in to press the link icon, but it is very fiddly.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+53254,tag_summary missing records,"tag_summary duplicates data in change_tag, but is missing some records. 
+
+Eg:
+
+select * from change_tag where ct_rev_id = 563615370;
++-----------+-----------+-----------+--------------+-----------+
+| ct_rc_id  | ct_log_id | ct_rev_id | ct_tag       | ct_params |
++-----------+-----------+-----------+--------------+-----------+
+| 589674173 |      NULL | 563615370 | visualeditor | NULL      |
++-----------+-----------+-----------+--------------+-----------+
+
+select * from tag_summary where ts_rev_id = 563615370;
+Empty set (0.01 sec)
+
+Cause unknown at time of writing.
+
+Relevant recent activity:
+
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_tag_not_working_correctly
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=40867
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['tag_summary missing records\n\ntag_summary duplicates data in change_tag, but is missing some records.', 'Eg:\n\nselect * from change_tag where ct_rev_id = 563615370;\n+-----------+-----------+-----------+--------------+-----------+\n| ct_rc_id  | ct_log_id | ct_rev_id | ct_tag       | ct_params |\n+-----------+-----------+-----------+--------------+-----------+\n| 589674173 |      NULL | 563615370 | visualeditor | NULL      |\n+-----------+-----------+-----------+--------------+-----------+\n\nselect * from tag_summary where ts_rev_id = 563615370;\nEmpty set (0.01 sec)\n\nCause unknown at time of writing.', 'Relevant recent activity:\n\nURL\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237406,tag_summary missing records,That was bug 52077. Closing this.,task_subcomment,"['That was bug 52077.', 'Closing this.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+237398,tag_summary missing records,"Whatever is causing that (maybe just a misconfigured local filter?), it's most likely not related to this bug.",task_subcomment,"['Whatever is causing that (maybe just a misconfigured local filter?', ""), it's most likely not related to this bug.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237392,tag_summary missing records,"**swalling** wrote:
+
+(In reply to comment #16)
+> Much better, but I'm still seeing some issues:
+> 
+> Looking for 500 ""blanking"" tags gives 498 ""blanking"" plus 2 labeled as just
+> ""mobile edit"".
+> 
+> http://en.wikipedia.org/w/api.
+> php?action=query&list=recentchanges&rctag=blanking&rclimit=500&rcprop=user%7C
+> comment%7Ctitle%7Ctags%7Ctimestamp
+
+There are other strange things going on with tags... 
+
+http://en.wikipedia.org/wiki/Wikipedia_talk:Tags#Incorrect_tagging
+
+Not sure if it's related or if we should file a separate bug for incorrect tagging. I think mobile is also suffering from this issue (or was as of yesterday).",task_subcomment,"[""**swalling** wrote:\n\n(In reply to comment #16)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThere are other strange things going on with tags... \n\nURL\n\nNot sure if it's related or if we should file a separate bug for incorrect tagging."", 'I think mobile is also suffering from this issue (or was as of yesterday).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237386,tag_summary missing records,"As a follow up, the two problematic tags I note in Comment 16 are both recent.  It is possible they have a different underlying cause than the previous corruption.  For example, this might represent a logic error in how the ""mobile edit"" tag is being recorded.",task_subcomment,"['As a follow up, the two problematic tags I note in Comment 16 are both recent.', 'It is possible they have a different underlying cause than the previous corruption.', 'For example, this might represent a logic error in how the ""mobile edit"" tag is being recorded.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237381,tag_summary missing records,"Much better, but I'm still seeing some issues:
+
+Looking for 500 ""blanking"" tags gives 498 ""blanking"" plus 2 labeled as just ""mobile edit"".
+
+http://en.wikipedia.org/w/api.php?action=query&list=recentchanges&rctag=blanking&rclimit=500&rcprop=user%7Ccomment%7Ctitle%7Ctags%7Ctimestamp",task_subcomment,"['Much better, but I\'m still seeing some issues:\n\nLooking for 500 ""blanking"" tags gives 498 ""blanking"" plus 2 labeled as just ""mobile edit"".', 'URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+237376,tag_summary missing records,"(In reply to comment #14)
+> Rebuild #2 of tag_summary has completed and the reports in comment 8 look
+> better (to me). Anyone care to verify...
+
+Appears to work for me, yes. Might be worth waiting for others to weigh-in, but from my POV this is fixed.",task_subcomment,"['(In reply to comment #14)\nQUOTE\nQUOTE\n\nAppears to work for me, yes.', 'Might be worth waiting for others to weigh-in, but from my POV this is fixed.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237372,tag_summary missing records,Rebuild #2 of tag_summary has completed and the reports in comment 8 look better (to me). Anyone care to verify...,task_subcomment,"['Rebuild #2 of tag_summary has completed and the reports in comment 8 look better (to me).', 'Anyone care to verify...']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237367,tag_summary missing records,"Btw, change_tag still looks complete to me; the binlog shows no problems there. Should just be the tag_summary rebuild logic at fault.",task_subcomment,"['Btw, change_tag still looks complete to me; the binlog shows no problems there.', 'Should just be the tag_summary rebuild logic at fault.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237364,tag_summary missing records,"As Robert suggested in comment 8, the rebuild process missed some rows where revisions had multiple tags.
+
+The script has been fixed and will run in batches on enwiki today. More info shortly...",task_subcomment,"['As Robert suggested in comment 8, the rebuild process missed some rows where revisions had multiple tags.', 'The script has been fixed and will run in batches on enwiki today.', 'More info shortly...']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237358,tag_summary missing records,"Am investigating whether the tag_summary rebuild was conceptually flawed with regard to revisions with multiple tags, or not.
+
+Also dumping enwiki binlogs on a slave (we have a month's worth) and pulling out all change_tag queries. Will reload them offline and join against a copy of change_tag to prove whether it is, in fact, completely intact.",task_subcomment,"['Am investigating whether the tag_summary rebuild was conceptually flawed with regard to revisions with multiple tags, or not.', ""Also dumping enwiki binlogs on a slave (we have a month's worth) and pulling out all change_tag queries."", 'Will reload them offline and join against a copy of change_tag to prove whether it is, in fact, completely intact.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237353,tag_summary missing records,"Lowering priority a bit since I don't there is data loss here (the table that was used to recreate the data still exists).
+
+James: Assigning to you to determine the priority for getting around to fixing this data (since it affects VE related data, and you know what metrics are being tracked).",task_subcomment,"[""Lowering priority a bit since I don't there is data loss here (the table that was used to recreate the data still exists)."", 'James: Assigning to you to determine the priority for getting around to fixing this data (since it affects VE related data, and you know what metrics are being tracked).']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+237348,tag_summary missing records,"(In reply to comment #8)
+> A API query of 200 revisions tags as flagged as ""blanking"":
+> While this query returns 200 entries, we find that only 188 of them report as
+> actually having the ""blanking"" tag.
+
+That's still the case today.",task_subcomment,"[""(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\n\nThat's still the case today.""]",['INVESTIGATION AND EXPLORATION']
+237342,tag_summary missing records,"Sorry to add to what I'm sure was a bit of a hectic day for someone, but I'm still seeing lingering bits of corruption.  Perhaps some sort of edge case that wasn't handled correctly by the rebuild?  99.9% of tags may be okay at this point, but here are some example that still seem to be errors.
+
+A API query of 200 revisions tags as flagged as ""blanking"":
+
+http://en.wikipedia.org/w/api.php?action=query&list=recentchanges&rctag=blanking&rclimit=200&rcprop=user%7Ccomment%7Ctitle%7Ctags%7Ctimestamp|ids&rccontinue=2013-07-12T22:20:40Z|589061595
+
+While this query returns 200 entries, we find that only 188 of them report as actually having the ""blanking"" tag.
+
+The remainder are things like 
+  rcid=""590123889"" timestamp=""2013-07-12T14:30:16Z""
+  visualeditor
+  
+  rcid=""590032703"" timestamp=""2013-07-12T00:33:31Z"" 
+  mobile edit
+
+Where some other tag is reported but the expected ""blanking"" tag is not reported.
+
+For another example of this issue see the API query for the ""visualeditor-needcheck"" tag:
+
+http://en.wikipedia.org/w/api.php?action=query&list=recentchanges&rctag=visualeditor-needcheck&rclimit=200&rcprop=user%7Ccomment%7Ctitle%7Ctags%7Ctimestamp|ids
+
+This tag should only be applied if the ""visualeditor"" tag is also present, but we observe that most of the results have either ""visualeditor"" or ""visualeditor-needcheck"" but not both.  A few entries even have other tags entirely.
+
+
+What appears to have happened is that rebuild didn't correctly handle cases where a single revision was subject to multiple tags.  Instead it looks as though the rebuilt table applies at most one tag to each of the historical revisions.  Most of the time that's okay since few revisions actually have multiple tags, but it still leaves a bit of corruption and missing data on the rare cases when a revision is expected to have multiple tags.",task_subcomment,"[""Sorry to add to what I'm sure was a bit of a hectic day for someone, but I'm still seeing lingering bits of corruption."", ""Perhaps some sort of edge case that wasn't handled correctly by the rebuild?"", '99.9% of tags may be okay at this point, but here are some example that still seem to be errors.', 'A API query of 200 revisions tags as flagged as ""blanking"":\n\nURL\n\nWhile this query returns 200 entries, we find that only 188 of them report as actually having the ""blanking"" tag.', 'The remainder are things like \n  rcid=""590123889"" timestamp=""2013-07-12T14:30:16Z""\n  visualeditor\n  \n  rcid=""590032703"" timestamp=""2013-07-12T00:33:31Z"" \n  mobile edit\n\nWhere some other tag is reported but the expected ""blanking"" tag is not reported.', 'For another example of this issue see the API query for the ""visualeditor-needcheck"" tag:\n\nURL\n\nThis tag should only be applied if the ""visualeditor"" tag is also present, but we observe that most of the results have either ""visualeditor"" or ""visualeditor-needcheck"" but not both.', 'A few entries even have other tags entirely.', ""What appears to have happened is that rebuild didn't correctly handle cases where a single revision was subject to multiple tags."", 'Instead it looks as though the rebuilt table applies at most one tag to each of the historical revisions.', ""Most of the time that's okay since few revisions actually have multiple tags, but it still leaves a bit of corruption and missing data on the rare cases when a revision is expected to have multiple tags.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237336,tag_summary missing records,"**swalling** wrote:
+
+Just checked this on-wiki as well. Seems fixed.",task_subcomment,"['**swalling** wrote:\n\nJust checked this on-wiki as well.', 'Seems fixed.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+237329,tag_summary missing records,enwiki.tag_summary rebuild is complete.,task_subcomment,['enwiki.tag_summary rebuild is complete.'],['OBSERVED BUG BEHAVIOR']
+237322,tag_summary missing records,"Firstly, we've determined this problem occurred due to an (apparent) bug in pt-online-schema-change when using a combination of:
+
+- A table without primary key
+- A table with unique indexes that all include nullable columns
+- An unfortunately timed REPLACE statement in normal db traffic
+
+Posc does online table alteration by:
+
+- Creating a copy of the table with altered schema
+- Setting triggers on the original table to keep the copy updated
+- Copying data across using a batch process
+
+In this case, posc set a DELETE trigger on tag_summary using a poor UNIQUE index (ts_log_id) with low cardinality and a nullable field. Then during the batching process, an external REPLACE statement with ts_log_id=NULL caused many too many rows to be deleted in the temporary table being altered. Given that many rows in tag_summary have ts_log_id=NULL, the table was massively reduced in size.
+
+Now to the fix:
+
+We've checked the other wikis and found no problems; only enwiki was affected.
+
+Furthermore, only enwiki.tag_summary was affected. We've verified that enwiki.change_tag is complete and did not suffer the same problem. This was based on:
+
+- Index cardinality and table size information collected before running the schema migration
+- An investigation of the events in the binary log surrounding the migration period
+
+Currently we are rebuilding tag_summary based on change_tag data. That will complete within 30 mins at the time of writing this comment.",task_subcomment,"[""Firstly, we've determined this problem occurred due to an (apparent) bug in pt-online-schema-change when using a combination of:\n\n- A table without primary key\n- A table with unique indexes that all include nullable columns\n- An unfortunately timed REPLACE statement in normal db traffic\n\nPosc does online table alteration by:\n\n- Creating a copy of the table with altered schema\n- Setting triggers on the original table to keep the copy updated\n- Copying data across using a batch process\n\nIn this case, posc set a DELETE trigger on tag_summary using a poor UNIQUE index (ts_log_id) with low cardinality and a nullable field."", 'Then during the batching process, an external REPLACE statement with ts_log_id=NULL caused many too many rows to be deleted in the temporary table being altered.', 'Given that many rows in tag_summary have ts_log_id=NULL, the table was massively reduced in size.', ""Now to the fix:\n\nWe've checked the other wikis and found no problems; only enwiki was affected."", 'Furthermore, only enwiki.tag_summary was affected.', ""We've verified that enwiki.change_tag is complete and did not suffer the same problem."", 'This was based on:\n\n- Index cardinality and table size information collected before running the schema migration\n- An investigation of the events in the binary log surrounding the migration period\n\nCurrently we are rebuilding tag_summary based on change_tag data.', 'That will complete within 30 mins at the time of writing this comment.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237314,tag_summary missing records,"(In reply to comment #3)
+> Was it determined if any other databases apart from en.wp's one were
+> affected?
+
+Not sure. The wikis that potentially may have this issue are:
+
++       'arwiki' => true,
++       'commonswiki' => true,
++       'cswiki' => true,
++       'dewiki' => true,
++       'elwiki' => true,
++       'enwiki' => true,
++       'enwikisource' => true,
++       'enwiktionary' => true,
++       'eswiki' => true,
++       'etwiki' => true,
++       'fawiki' => true,
++       'fiwiki' => true,
++       'frwiki' => true,
++       'hewiki' => true,
++       'huwiki' => true,
++       'idwiki' => true,
++       'itwiki' => true,
++       'jawiki' => true,
++       'ltwiki' => true,
++       'mrwiki' => true,
++       'nlwiki' => true,
++       'plwiki' => true,
++       'ptwiki' => true,
++       'rowiki' => true,
++       'ruwiki' => true,
++       'simplewiki' => true,
++       'svwiki' => true,
++       'trwiki' => true,
++       'ukwiki' => true,
++       'zhwiki' => true,
+
+cf bug 40867#c6",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\n\nNot sure.', ""The wikis that potentially may have this issue are:\n\n+       'arwiki' => true,\n+       'commonswiki' => true,\n+       'cswiki' => true,\n+       'dewiki' => true,\n+       'elwiki' => true,\n+       'enwiki' => true,\n+       'enwikisource' => true,\n+       'enwiktionary' => true,\n+       'eswiki' => true,\n+       'etwiki' => true,\n+       'fawiki' => true,\n+       'fiwiki' => true,\n+       'frwiki' => true,\n+       'hewiki' => true,\n+       'huwiki' => true,\n+       'idwiki' => true,\n+       'itwiki' => true,\n+       'jawiki' => true,\n+       'ltwiki' => true,\n+       'mrwiki' => true,\n+       'nlwiki' => true,\n+       'plwiki' => true,\n+       'ptwiki' => true,\n+       'rowiki' => true,\n+       'ruwiki' => true,\n+       'simplewiki' => true,\n+       'svwiki' => true,\n+       'trwiki' => true,\n+       'ukwiki' => true,\n+       'zhwiki' => true,\n\ncf bug 40867#c6""]","['ACTION ON ISSUE', 'BUG REPRODUCTION']"
+237308,tag_summary missing records,Was it determined if any other databases apart from en.wp's one were affected?,task_subcomment,"[""Was it determined if any other databases apart from en.wp's one were affected?""]",['OBSERVED BUG BEHAVIOR']
+237301,tag_summary missing records,"Sean and Asher narrowed this down to a problem with the schema change tool that we use, and are working on a strategy to fix the data.  This looks like it's strictly a db-related problem that once fixed should stay fixed (assuming we don't try another similar schema migration before an upstream fix is made to the migration tool)",task_subcomment,"['Sean and Asher narrowed this down to a problem with the schema change tool that we use, and are working on a strategy to fix the data.', ""This looks like it's strictly a db-related problem that once fixed should stay fixed (assuming we don't try another similar schema migration before an upstream fix is made to the migration tool)""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237297,tag_summary missing records,"Only seems to affect en.wp right now (works correctly on pl.wp and mw.org, for example).",task_subcomment,"['Only seems to affect en.wp right now (works correctly on pl.wp and mw.org, for example).']",['OBSERVED BUG BEHAVIOR']
+53235,VisualEditor: Annotated element metadata inside wrapper paragraphs being discarded,"I'm not entirely sure if this is a VE bug or a user bug, but it shows up under the needscheck tag, so presumably the VE knows something is wrong. We have several instances of categories being stripped from articles, including:
+
+*https://en.wikipedia.org/w/index.php?title=2013%E2%80%9314_Juventus_F.C._season&curid=39905874&diff=563942424&oldid=563942210
+*https://en.wikipedia.org/w/index.php?title=A._Dakshinamurthy&curid=16805989&diff=563911982&oldid=563853744
+*https://en.wikipedia.org/w/index.php?title=Body_Party&curid=38681444&diff=563891098&oldid=563879499
+
+In the last 12 hours or so.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Annotated element metadata inside wrapper paragraphs being discarded\n\nI'm not entirely sure if this is a VE bug or a user bug, but it shows up under the needscheck tag, so presumably the VE knows something is wrong."", 'We have several instances of categories being stripped from articles, including:\n\n*URL\n*URL\n*URL\n\nIn the last 12 hours or so.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236203,VisualEditor: Annotated element metadata inside wrapper paragraphs being discarded,"Change 73404 merged by jenkins-bot:
+Fix annotated element alien metadata inside wrapped paragraph
+
+https://gerrit.wikimedia.org/r/73404",task_subcomment,['Change 73404 merged by jenkins-bot:\nFix annotated element alien metadata inside wrapped paragraph\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+236198,VisualEditor: Annotated element metadata inside wrapper paragraphs being discarded,"Change 73404 had a related patch set uploaded by Esanders:
+Fix annotated element alien metadata inside wrapped paragraph
+
+https://gerrit.wikimedia.org/r/73404",task_subcomment,['Change 73404 had a related patch set uploaded by Esanders:\nFix annotated element alien metadata inside wrapped paragraph\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+236193,VisualEditor: Annotated element metadata inside wrapper paragraphs being discarded,"Looks like those pages have unclosed big/small annotations, which are wrapping all the content beneath them, including the categories. This is triggering a previously unseen bug in the converter.",task_subcomment,"['Looks like those pages have unclosed big/small annotations, which are wrapping all the content beneath them, including the categories.', 'This is triggering a previously unseen bug in the converter.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53234,VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''''bar'' -> ''foobar''),"See https://en.wikipedia.org/w/index.php?title=Hungarian_algorithm&curid=2609001&diff=563951525&oldid=561480423 - another instance at https://en.wikipedia.org/w/index.php?title=Shannon_capacity_of_a_graph&curid=39932177&diff=563933550&oldid=563846095
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: VE/Parsoid (?)', ""merging unnecessary annotations together (''foo''''bar'' -> ''foobar'')\n\nSee URL - another instance at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236146,VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''''bar'' -> ''foobar''),"
+
+*** This bug has been marked as a duplicate of bug 49873 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 49873 ***'],['ACTION ON ISSUE']
+236140,VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''''bar'' -> ''foobar''),Also https://en.wikipedia.org/w/index.php?title=Frobenius_solution_to_the_hypergeometric_equation&curid=16407499&diff=563915886&oldid=561013687,task_subcomment,['Also URL'],['OBSERVED BUG BEHAVIOR']
+53215,VisualEditor: Protected page warning message should include log entry,"Following on from bug 50415, the old warning/error messages included the most recent & relevant log entry, and a link to view the full log.
+
+That functionality does not exist in the VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50415",task_description,"['VisualEditor: Protected page warning message should include log entry\n\nFollowing on from bug 50415, the old warning/error messages included the most recent & relevant log entry, and a link to view the full log.', 'That functionality does not exist in the VisualEditor.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+235070,VisualEditor: Protected page warning message should include log entry,"Change 119210 merged by jenkins-bot:
+Show last protection log entry and link to full protection log on protection notice
+
+https://gerrit.wikimedia.org/r/119210",task_subcomment,['Change 119210 merged by jenkins-bot:\nShow last protection log entry and link to full protection log on protection notice\n\nGERRIT_URL'],['ACTION ON ISSUE']
+235065,VisualEditor: Protected page warning message should include log entry,"Change 119210 had a related patch set uploaded by Alex Monk:
+Show last protection log entry and link to full protection log on protection notice
+
+https://gerrit.wikimedia.org/r/119210",task_subcomment,['Change 119210 had a related patch set uploaded by Alex Monk:\nShow last protection log entry and link to full protection log on protection notice\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53160,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"The source editor transcludes [[MediaWiki:Editpage-head-copy-warn]] above the edit window. But this does not appear anywhere when using the visual editor.
+
+Note this is distinct from [[Mediawiki:Copyrightwarning]] which appears (in a tiny font) in the edit summary tool. The two messages are not the same and do different jobs - the first is a warning that copyrighted content is not acceptable and content must be verifiable, the second is a statement that by saving you release your contributions under cc-by-sa.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary\n\nThe source editor transcludes [[MediaWiki:Editpage-head-copy-warn]] above the edit window.', 'But this does not appear anywhere when using the visual editor.', 'Note this is distinct from [[Mediawiki:Copyrightwarning]] which appears (in a tiny font) in the edit summary tool.', 'The two messages are not the same and do different jobs - the first is a warning that copyrighted content is not acceptable and content must be verifiable, the second is a statement that by saving you release your contributions under cc-by-sa.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+232197,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"Er. What?
+
+As I've said, VE is an extension. Parsoid is an extension. This page is not /based/ on a MediaWiki namespace page, it is based on a string in the i8on file. To fully deprecate it we'd have to find some way of fully suppressing it or remove it completely from mediawiki. This would impact not only wikis with the VE but also those without.
+
+Moreover, I'm not sure how users receiving less information is, in this case, a problem, because I've never seen any evidence users actually /read/ those notices. I've been patrolling new pages since 2010; if CITE YOUR SOURCES! and the warning not to submit copyrighted content actually worked to inform people, I'd be the first person to hold my hands up and go ""this is awesome and we need to keep it"". They don't.
+
+I'm (again) closing this as a WONTFIX. If people want to dispute that, I welcome an argument made as to how having this message helps - or how silently removing it from every Wikimedia instance of MediaWiki and dealing with the resulting fallout would be an effective use of our time.",task_subcomment,"['Er.', 'What?', ""As I've said, VE is an extension."", 'Parsoid is an extension.', 'This page is not /based/ on a MediaWiki namespace page, it is based on a string in the i8on file.', ""To fully deprecate it we'd have to find some way of fully suppressing it or remove it completely from mediawiki."", 'This would impact not only wikis with the VE but also those without.', ""Moreover, I'm not sure how users receiving less information is, in this case, a problem, because I've never seen any evidence users actually /read/ those notices."", ""I've been patrolling new pages since 2010; if CITE YOUR SOURCES!"", 'and the warning not to submit copyrighted content actually worked to inform people, I\'d be the first person to hold my hands up and go ""this is awesome and we need to keep it"".', ""They don't."", ""I'm (again) closing this as a WONTFIX."", 'If people want to dispute that, I welcome an argument made as to how having this message helps - or how silently removing it from every Wikimedia instance of MediaWiki and dealing with the resulting fallout would be an effective use of our time.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+232194,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"major->minor, so it isnt red anymore.",task_subcomment,"['major->minor, so it isnt red anymore.']",['SOLUTION DISCUSSION']
+232192,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"The problem doesnt go away because itwp deleted the message.
+
+It still exists in enwp, zhwp, viwp & hrwp, of wikis above 100,000+ pages. (fawp has a commented out notice)  Possibly many more with less pages.
+These messages informed the user about verifiability as well as licensing issues.
+
+But if this message is truly not going to be displayed in VE, and VE is the way of the future, then the message should be deprecated and deleted from those wikis (with community consensus after explaining to them they have no other option :P), otherwise user's of VE receive less information then those of SE, for good or ill.  (in this case this bug should be moved over the core component)",task_subcomment,"['The problem doesnt go away because itwp deleted the message.', 'It still exists in enwp, zhwp, viwp & hrwp, of wikis above 100,000+ pages.', '(fawp has a commented out notice)  Possibly many more with less pages.', 'These messages informed the user about verifiability as well as licensing issues.', ""But if this message is truly not going to be displayed in VE, and VE is the way of the future, then the message should be deprecated and deleted from those wikis (with community consensus after explaining to them they have no other option :P), otherwise user's of VE receive less information then those of SE, for good or ill.  (in this case this bug should be moved over the core component)""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+232189,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"(In reply to comment #7)
+> Resolved-Fixed -> Resolved->Invalid.  What the?!
+
+Not a bug in VisualEditor; itwiki had removed the licence information from the, err, licence information message. Oliver fixed it by editing the message to restore the licence warning. No changes to VisualEditor actually happened.
+
+We are fixing enough bugs without having to artificially inflate the numbers of how much we're doing. :-)",task_subcomment,"['(In reply to comment #7)\nQUOTE\n\nNot a bug in VisualEditor; itwiki had removed the licence information from the, err, licence information message.', 'Oliver fixed it by editing the message to restore the licence warning.', 'No changes to VisualEditor actually happened.', ""We are fixing enough bugs without having to artificially inflate the numbers of how much we're doing."", ':-)']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232183,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,Resolved-Fixed -> Resolved->Invalid.  What the?!,task_subcomment,"['Resolved-Fixed -> Resolved->Invalid.', 'What the?', '!']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232176,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,Now resolved; thanks all :).,task_subcomment,['Now resolved; thanks all :).'],['SOLUTION DISCUSSION']
+232170,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"PS: (it's not just about copyright, in our case) http://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Legal_issue:_copyright_and_other_warnings_must_be_visible_above_the_%22save%22_button
+
+Thanks.",task_subcomment,"[""PS: (it's not just about copyright, in our case) URL\n\nThanks.""]",['SOLUTION DISCUSSION']
+232164,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"On the Italian Wikipedia that does not happen though, please tell me if there is anything I can do to fix this ASAP.
+
+In the past some users at itwp asked if the copyright/warning notices we use (https://it.wikipedia.org/wiki/MediaWiki:Wikimedia-editpage-tos-summary ) under the edit windows could be removed for experienced users, but the option was always discarded on the basis that a more prominent notice than the one in the footer was necessary for ""legal"" reasons (yes, people don't usually read or understand what it says anyway, but certainly they can't complain they don't get enough notice about this. And we do care a lot about this topic.)
+I can see the notice when I try to save on en.wp, although it is so small I almost can't read it with Monobook on Chrome, but it does not show up on it.wiki, and since I don't want patrollers to report additional copyright issues after deployment, I'd ask for advice about this. Thanks.",task_subcomment,"['On the Italian Wikipedia that does not happen though, please tell me if there is anything I can do to fix this ASAP.', 'In the past some users at itwp asked if the copyright/warning notices we use (URL ) under the edit windows could be removed for experienced users, but the option was always discarded on the basis that a more prominent notice than the one in the footer was necessary for ""legal"" reasons (yes, people don\'t usually read or understand what it says anyway, but certainly they can\'t complain they don\'t get enough notice about this.', 'And we do care a lot about this topic.)', ""I can see the notice when I try to save on en.wp, although it is so small I almost can't read it with Monobook on Chrome, but it does not show up on it.wiki, and since I don't want patrollers to report additional copyright issues after deployment, I'd ask for advice about this."", 'Thanks.']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+232158,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"I'm confused. Because it's part of MediaWiki core, it can't be overridden or suppressed by an extension? A large chunk of the extensions we practically use suppresses elements of core. This would seem to conflict with the practical use and applications of our extensions. Similarly, removing it would be rather unfair to, for example, third-party users, since VisualEditor and Parsoid are both extensions. We do not include them in the standard tarball.
+
+The message is useful, yes, but replicated in a form in the VE. If you've used the VE, you'll know the ToS link and release are given prominent placement, not ""tucked away down the bottom of the page"". The only occasions on which the ToS /are/ tucked away down the bottom of the page is in namespaces and wikis without VisualEditor/Parsoid....where editpage-head-copy-warn is not suppressed.",task_subcomment,"[""I'm confused."", ""Because it's part of MediaWiki core, it can't be overridden or suppressed by an extension?"", 'A large chunk of the extensions we practically use suppresses elements of core.', 'This would seem to conflict with the practical use and applications of our extensions.', 'Similarly, removing it would be rather unfair to, for example, third-party users, since VisualEditor and Parsoid are both extensions.', 'We do not include them in the standard tarball.', 'The message is useful, yes, but replicated in a form in the VE.', 'If you\'ve used the VE, you\'ll know the ToS link and release are given prominent placement, not ""tucked away down the bottom of the page"".', 'The only occasions on which the ToS /are/ tucked away down the bottom of the page is in namespaces and wikis without VisualEditor/Parsoid....where editpage-head-copy-warn is not suppressed.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+232152,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"This message is part of mediawiki.  If the message is extraneous, it should be removed.  Until that happens, it should be part of the VE.
+
+On English Wikipedia this message includes ""Encyclopedic content must be verifiable."" and a prominent link to the ToS, which is otherwise tucked away down the bottom of the page.",task_subcomment,"['This message is part of mediawiki.', 'If the message is extraneous, it should be removed.', 'Until that happens, it should be part of the VE.', 'On English Wikipedia this message includes ""Encyclopedic content must be verifiable.""', 'and a prominent link to the ToS, which is otherwise tucked away down the bottom of the page.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+232145,VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"I would argue that this is somewhat extraneous; I don't think anyone actually reads it. Really it exists primarily so that when someone whines about their content being deleted, we can go ""there was a notice"". It undoubtedly did serve a purpose on the Good Old Days {{cn}} when our terms of service were written on a napkin - but these days Geoff and the team have produced the rather concise and all-encompassing https://wikimediafoundation.org/wiki/Terms_of_Use, which covers (amongst other things) copyright infringements and redistribution - and is linked to in the interface.
+
+I appreciate it's slightly more obscure than an editnotice, but it's also the approach taken by every other website on the planet: users can't really claim they were ignorant unless we're the only place on the internet they visit.",task_subcomment,"[""I would argue that this is somewhat extraneous; I don't think anyone actually reads it."", 'Really it exists primarily so that when someone whines about their content being deleted, we can go ""there was a notice"".', 'It undoubtedly did serve a purpose on the Good Old Days {{cn}} when our terms of service were written on a napkin - but these days Geoff and the team have produced the rather concise and all-encompassing URL which covers (amongst other things) copyright infringements and redistribution - and is linked to in the interface.', ""I appreciate it's slightly more obscure than an editnotice, but it's also the approach taken by every other website on the planet: users can't really claim they were ignorant unless we're the only place on the internet they visit.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53145,VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext,"1. Go to
+https://pt.wikipedia.org/wiki/Associação_Médico-Espírita_do_Brasil?oldid=36199569&veaction=edit
+2. Click in the box in the top of the page and delete it
+3. Click on ""Save page"" and then ""Review your changes""
+The editor will add the code
+
    
+in the bottom of the page, as in this diff:
+https://pt.wikipedia.org/wiki/Associação_Médico-Espírita_do_Brasil?diff=36364362&uselang=en
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51260",task_description,"['VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext\n\n1.', 'Go to\nURL\n2.', 'Click in the box in the top of the page and delete it\n3.', 'Click on ""Save page"" and then ""Review your changes""\nThe editor will add the code\n
    \nin the bottom of the page, as in this diff:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+231053,VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext,"I was NOT able to reproduce it following the steps from comment 0 and of comment 3, and also in the case of comment 4. Moreover, I don't remember seeing any new reports on this, so I'm marking this as FIXED (but I don't know which code change fixed the bug).",task_subcomment,"['I was NOT able to reproduce it following the steps from comment 0 and of comment 3, and also in the case of comment 4.', ""Moreover, I don't remember seeing any new reports on this, so I'm marking this as FIXED (but I don't know which code change fixed the bug).""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+231047,VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext,I can't reproduce this now using a simple test case.  Has it still been happening on pt.wp?,task_subcomment,"[""I can't reproduce this now using a simple test case."", 'Has it still been happening on pt.wp?']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+231043,VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext,"This happened again:
+https://pt.wikipedia.org/wiki/Haroldo_Palo_Jr.?diff=36430552",task_subcomment,['This happened again:\nURL'],['OBSERVED BUG BEHAVIOR']
+231038,VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext,"This little devil can be reproduced at
+https://pt.wikipedia.org/wiki/User:John_Vandenberg/demo?veaction=edit
+(remove the template at the top and click save)
+
+It is a very common case, and VE cant be used safely on pt.wp until this is fixed.
+
+Im guessing this is related to the high priority Cite enhancement bug 51260.",task_subcomment,"['This little devil can be reproduced at\nURL\n(remove the template at the top and click save)\n\nIt is a very common case, and VE cant be used safely on pt.wp until this is fixed.', 'Im guessing this is related to the high priority Cite enhancement bug 51260.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+231032,VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext,"(In reply to comment #1)
+> I don't know if this is relevant, but the same code ""{{referências}}"" expands
+> to something different on [[pt:special:ExpandTemplates]]:
+> 
+> 
     Edite a página toda em vez disso."">Referências
    
+> 
     group="""">
    
+> 
+> 
+> Direct link:
+> https://pt.wikipedia.org/w/index.php?title=Especial:
+> Expandir_predefini%C3%A7%C3%B5es&input=%7B%7Brefer%C3%AAncias%7D%7D&contextti
+> tle=Associa%C3%A7%C3%A3o+M%C3%A9dico-
+> Esp%C3%ADrita+do+Brasil&removecomments=true&removenowiki=true
+
+That's pretty much the same as the expansion that leaks into the article, except for the first tag (the 
    ).",task_subcomment,"[""(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's pretty much the same as the expansion that leaks into the article, except for the first tag (the 
    ).""]",['SOLUTION DISCUSSION']
+231028,VisualEditor: {{referências}} injects additional HTML (
    ) into wikitext,"I don't know if this is relevant, but the same code ""{{referências}}"" expands to something different on [[pt:special:ExpandTemplates]]:
+
+
    Referências
    
+
    
+
+
+Direct link:
+https://pt.wikipedia.org/w/index.php?title=Especial:Expandir_predefini%C3%A7%C3%B5es&input=%7B%7Brefer%C3%AAncias%7D%7D&contexttitle=Associa%C3%A7%C3%A3o+M%C3%A9dico-Esp%C3%ADrita+do+Brasil&removecomments=true&removenowiki=true",task_subcomment,"['I don\'t know if this is relevant, but the same code ""{{referências}}"" expands to something different on [[pt:special:ExpandTemplates]]:\n\n
    Referências
    \n
    \n\n\nDirect link:\nURL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+53143,VisualEditor: Double-click on a parameter in the selection menu should insert it,"From English Wikipedia:
+
+In the template dialog, in the add parameter view, I would expect double-clicking on a parameter would add it, instead of having to find the add parameter button at the end of the list (which should, by the way, not be at the end of a scrolling 
+
+list, but always visible in a fixed place). --WS (talk) 12:17, 9 July 2013 (UTC)
+Agree with this - it took me a while to figure out that I had to scroll to the bottom of a long list of reference parameters to find the button. GoingBatty (talk) 04:58, 10 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Double-click on a parameter in the selection menu should insert it\n\nFrom English Wikipedia:\n\nIn the template dialog, in the add parameter view, I would expect double-clicking on a parameter would add it, instead of having to find the add parameter button at the end of the list (which should, by the way, not be at the end of a scrolling \n\nlist, but always visible in a fixed place).', '--WS (talk) 12:17, 9 July 2013 (UTC)\nAgree with this - it took me a while to figure out that I had to scroll to the bottom of a long list of reference parameters to find the button.', 'GoingBatty (talk) 04:58, 10 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+255495,VisualEditor: Double-click on a parameter in the selection menu should insert it,*** Bug 51165 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51165 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255489,VisualEditor: Double-click on a parameter in the selection menu should insert it,"This is now done (as a single-click-to-insert), and will be deployed in the next few minutes.",task_subcomment,"['This is now done (as a single-click-to-insert), and will be deployed in the next few minutes.']",['SOLUTION USAGE']
+255482,VisualEditor: Double-click on a parameter in the selection menu should insert it,"Change 73865 merged by jenkins-bot:
+Single-click insertion
+
+https://gerrit.wikimedia.org/r/73865",task_subcomment,['Change 73865 merged by jenkins-bot:\nSingle-click insertion\n\nGERRIT_URL'],['ACTION ON ISSUE']
+255475,VisualEditor: Double-click on a parameter in the selection menu should insert it,"Change 73865 had a related patch set uploaded by Trevor Parscal:
+Single-click insertion
+
+https://gerrit.wikimedia.org/r/73865",task_subcomment,['Change 73865 had a related patch set uploaded by Trevor Parscal:\nSingle-click insertion\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53140,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,"Seems to happen specifically in https://en.wikipedia.org/wiki/Jabhala?veaction=edit for no apparent reason; try it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text\n\nSeems to happen specifically in URL for no apparent reason; try it.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255245,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,*** Bug 51112 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51112 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255238,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,Fixed and merged.,task_subcomment,['Fixed and merged.'],['SOLUTION USAGE']
+255231,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,"Change 73874 merged by jenkins-bot:
+Replace text strings with grapheme arrays in onContentChange
+
+https://gerrit.wikimedia.org/r/73874",task_subcomment,['Change 73874 merged by jenkins-bot:\nReplace text strings with grapheme arrays in onContentChange\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+255224,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,"Change 73874 had a related patch set uploaded by Esanders:
+Replace text strings with grapheme arrays in onContentChange
+
+https://gerrit.wikimedia.org/r/73874",task_subcomment,['Change 73874 had a related patch set uploaded by Esanders:\nReplace text strings with grapheme arrays in onContentChange\n\nGERRIT_URL'],['ACTION ON ISSUE']
+255217,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,"**weskaggs** wrote:
+
+Further observations:  the ""pawn"" has utf-8 hex code E2 99 99.  The multibyte characters that provoke this behavior are either of:
+
+devangiri letter LA, unicode 0x2354, utf-8 hex E0 A4 B2
+devangiri letter BHA, unicode 0x2349, utf-8 hex E0 A4 AD",task_subcomment,"['**weskaggs** wrote:\n\nFurther observations:  the ""pawn"" has utf-8 hex code E2 99 99.', 'The multibyte characters that provoke this behavior are either of:\n\ndevangiri letter LA, unicode 0x2354, utf-8 hex E0 A4 B2\ndevangiri letter BHA, unicode 0x2349, utf-8 hex E0 A4 AD']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255207,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,"Turns out that it happens when inserting any character after the link, but only at the position immediately after the link (so the second character isn't pawned because there's something (the first pawn) between it and the link), and only if there is multibyte text in the same paragraph preceding the link.
+
+The article's first and only paragraph starts with ""Jabhala (Hindi:जभाला) is..."" and so this bug affects every link on that article. But it doesn't affect any links before जभाला (there aren't any right now but you can create them), and if you use Enter to break the paragraph after the Hindi text, it doesn't affect any links in the second paragraph either.
+
+Assigning to Ed because this is a multibyte issue.",task_subcomment,"[""Turns out that it happens when inserting any character after the link, but only at the position immediately after the link (so the second character isn't pawned because there's something (the first pawn) between it and the link), and only if there is multibyte text in the same paragraph preceding the link."", 'The article\'s first and only paragraph starts with ""Jabhala (Hindi:जभाला) is..."" and so this bug affects every link on that article.', ""But it doesn't affect any links before जभाला (there aren't any right now but you can create them), and if you use Enter to break the paragraph after the Hindi text, it doesn't affect any links in the second paragraph either."", 'Assigning to Ed because this is a multibyte issue.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'ACTION ON ISSUE']"
+255199,VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,"**weskaggs** wrote:
+
+In case it may be helpful, the character produced is a white chess pawn, unicode 0x2659 (html ♙).  This character is produced if any character is added immediately after any of the three links in the first sentence, but not if a character is added after a link in the second sentence.  If the Hindi text in the first sentence is deleted, then characters entered after a link produce the correct result.",task_subcomment,"['**weskaggs** wrote:\n\nIn case it may be helpful, the character produced is a white chess pawn, unicode 0x2659 (html ♙).', 'This character is produced if any character is added immediately after any of the three links in the first sentence, but not if a character is added after a link in the second sentence.', 'If the Hindi text in the first sentence is deleted, then characters entered after a link produce the correct result.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53135,"VisualEditor: Should ""remove template"" be under a label such as ""actions"" instead of options?","An English Wikipedia editor suggests that the ""remove template"" button should be in a section labeled ""actions"", not options. A non-native speaker, he does not find the ""options"" label intuitive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51672",task_description,"['VisualEditor: Should ""remove template"" be under a label such as ""actions"" instead of options?', 'An English Wikipedia editor suggests that the ""remove template"" button should be in a section labeled ""actions"", not options.', 'A non-native speaker, he does not find the ""options"" label intuitive.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+254945,"VisualEditor: Should ""remove template"" be under a label such as ""actions"" instead of options?","This has now been moved from the ""options"" section to a small rubbish bin icon next to each template's name, and duplicated in the control section in the left navigation bar.",task_subcomment,"['This has now been moved from the ""options"" section to a small rubbish bin icon next to each template\'s name, and duplicated in the control section in the left navigation bar.']",['SOLUTION USAGE']
+254938,"VisualEditor: Should ""remove template"" be under a label such as ""actions"" instead of options?","We don't like the ""Options"" label either (it's a standard part of dialog panes in VE, but here it doesn't add anything).",task_subcomment,"['We don\'t like the ""Options"" label either (it\'s a standard part of dialog panes in VE, but here it doesn\'t add anything).']",['SOLUTION DISCUSSION']
+53112,VisualEditor: replacing the first character in the link text inserts ♙ instead of a proper symbol,"**Author:** `p.selitskas`
+
+**Description:**
+Page where issue occures: https://be-x-old.wikipedia.org/wiki/%D0%93%D1%80%D1%8D%D0%B3%D0%B0%D1%80%D1%8B%D1%8F%D0%BD%D1%81%D0%BA%D1%96_%D0%BA%D0%B0%D0%BB%D1%8F%D0%BD%D0%B4%D0%B0%D1%80
+
+When I change the first character of the link text by selecting it first and then typing, chess symbol ♙ replaces the original character. Due to bug 50678 not being resolved yet, I tried this way and revealed such behaviour. For the point, it's no matter how many characters are selected, chess symbol arrives if the first character in the link text is included in the selection.
+
+It seems to take place in the lead part of the article only. When I change links in the tables and other sections of the page, it all looks fine.
+
+Worth noticing: after I enter the editing mode and change the link in the first table header (text: Апошні дзень Юліянскага календару), it works like a charm, but as I press Ctrl+Z, it turns to «Апошні дзень ♙ліянскага календару», and I have to press Ctrl+Z once again to fix it back to the original state.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: replacing the first character in the link text inserts ♙ instead of a proper symbol\n\n**Author:** CODE\n\n**Description:**\nPage where issue occures: URL\n\nWhen I change the first character of the link text by selecting it first and then typing, chess symbol ♙ replaces the original character.', 'Due to bug 50678 not being resolved yet, I tried this way and revealed such behaviour.', ""For the point, it's no matter how many characters are selected, chess symbol arrives if the first character in the link text is included in the selection."", 'It seems to take place in the lead part of the article only.', 'When I change links in the tables and other sections of the page, it all looks fine.', 'Worth noticing: after I enter the editing mode and change the link in the first table header (text: Апошні дзень Юліянскага календару), it works like a charm, but as I press Ctrl+Z, it turns to «Апошні дзень ♙ліянскага календару», and I have to press Ctrl+Z once again to fix it back to the original state.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+253838,VisualEditor: replacing the first character in the link text inserts ♙ instead of a proper symbol,"
+
+*** This bug has been marked as a duplicate of bug 51140 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 51140 ***'],['ACTION ON ISSUE']
+53075,"VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line","Create a link and hit return before the input field in the link inspector is focused and the text in the surface will be replaced with a new line.  Not linked text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line\n\nCreate a link and hit return before the input field in the link inspector is focused and the text in the surface will be replaced with a new line.', 'Not linked text.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251893,"VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line",This code has been fixed and we'll get it deployed tomorrow.,task_subcomment,"[""This code has been fixed and we'll get it deployed tomorrow.""]",['ACTION ON ISSUE']
+251889,"VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line","Change 72852 merged by jenkins-bot:
+Lock surface while inspectors are animating open
+
+https://gerrit.wikimedia.org/r/72852",task_subcomment,['Change 72852 merged by jenkins-bot:\nLock surface while inspectors are animating open\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+251885,"VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line","Change 72849 merged by jenkins-bot:
+Be sure lookupMenu input is focused before showing
+
+https://gerrit.wikimedia.org/r/72849",task_subcomment,['Change 72849 merged by jenkins-bot:\nBe sure lookupMenu input is focused before showing\n\nGERRIT_URL'],['ACTION ON ISSUE']
+251881,"VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line","Change 72849 had a related patch set uploaded by Jforrester:
+Be sure lookupMenu input is focused before showing.
+
+https://gerrit.wikimedia.org/r/72849",task_subcomment,"['Change 72849 had a related patch set uploaded by Jforrester:\nBe sure lookupMenu input is focused before showing.', 'GERRIT_URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+251877,"VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line","Change 72852 had a related patch set uploaded by Robmoen:
+Decrease the time it takes to focus the input element.
+
+https://gerrit.wikimedia.org/r/72852",task_subcomment,"['Change 72852 had a related patch set uploaded by Robmoen:\nDecrease the time it takes to focus the input element.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+53026,VisualEditor: Resizing an image without an explicit size doesn't work,"If an image is formatted as [[File:foo.jpg|thumb]] rather than |BARpx, image resizing does not work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"[""VisualEditor: Resizing an image without an explicit size doesn't work\n\nIf an image is formatted as [[File:foo.jpg|thumb]] rather than |BARpx, image resizing does not work."", '--------------------------\n**Version**: unspecified\n**Severity**: major']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+249201,VisualEditor: Resizing an image without an explicit size doesn't work,"
+
+*** This bug has been marked as a duplicate of bug 50645 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50645 ***'],['ISSUE CONTENT MANAGEMENT']
+53000,VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Attaching screenshot...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor: Heading overlays toolbar in non-HD Vector integration\n\nAttaching screenshot...\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+247515,VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Change 109491 merged by jenkins-bot:
+Fix toolbar margins in vector
+
+https://gerrit.wikimedia.org/r/109491",task_subcomment,['Change 109491 merged by jenkins-bot:\nFix toolbar margins in vector\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+247510,VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Change 109491 had a related patch set uploaded by Esanders:
+Fix toolbar margins in vector
+
+https://gerrit.wikimedia.org/r/109491",task_subcomment,['Change 109491 had a related patch set uploaded by Esanders:\nFix toolbar margins in vector\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+247503,VisualEditor: Heading overlays toolbar in non-HD Vector integration,*** Bug 52205 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52205 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247498,VisualEditor: Heading overlays toolbar in non-HD Vector integration,Same as bug 52205?,task_subcomment,['Same as bug 52205?'],['MOTIVATION']
+247492,VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Steps to reproduce:
+1. Reduce the screen width until the toolbar wraps. You should now see something like attachment 12793
+2. Reduce the screen width even more until the screen is too narrow for the HD stylesheet. The skin elements will animate and you'll end up with something that looks like attachment 12794.",task_subcomment,"['Steps to reproduce:\n1.', 'Reduce the screen width until the toolbar wraps.', 'You should now see something like attachment 12793\n2.', 'Reduce the screen width even more until the screen is too narrow for the HD stylesheet.', ""The skin elements will animate and you'll end up with something that looks like attachment 12794.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247485,VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Created attachment 12794
+
     protrudes into wrapped toolbar in non-HD stylesheet
+
+**Attached**: {F11631}",task_subcomment,['Created attachment 12794\n
     protrudes into wrapped toolbar in non-HD stylesheet\n\n**Attached**: {F11631}'],['BUG REPRODUCTION']
+247475,VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Created attachment 12793
+Wrapping toolbar correctly pushes down 
     in HD stylesheet
+
+**Attached**: {F11630}",task_subcomment,['Created attachment 12793\nWrapping toolbar correctly pushes down 
     in HD stylesheet\n\n**Attached**: {F11630}'],['ATTACHMENT']
+52964,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Not sure if this is TemplateData or VisualEditor, please move it if I’m wrong.
+
+If I edit a page where a redirection to a template is used, I don’t see the available parameters and other data that TemplateData provides, but the redirection works like the real template, so it should use the same data.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['TemplateData: TemplateData is not available to VisualEditor if the template is a redirect\n\nNot sure if this is TemplateData or VisualEditor, please move it if I’m wrong.', 'If I edit a page where a redirection to a template is used, I don’t see the available parameters and other data that TemplateData provides, but the redirection works like the real template, so it should use the same data.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245509,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,Per report. ;-),task_subcomment,"['Per report.', ';-)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+245502,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Confirmed fixed in 1.24wmf7, yay :-)",task_subcomment,"['Confirmed fixed in 1.24wmf7, yay :-)']",['SOLUTION USAGE']
+245495,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Change 135065 merged by jenkins-bot:
+Follow redirects when looking up template data
+
+https://gerrit.wikimedia.org/r/135065",task_subcomment,['Change 135065 merged by jenkins-bot:\nFollow redirects when looking up template data\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245487,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Change 135064 merged by jenkins-bot:
+Allow following of redirects via API
+
+https://gerrit.wikimedia.org/r/135064",task_subcomment,['Change 135064 merged by jenkins-bot:\nAllow following of redirects via API\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245480,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Change 135065 had a related patch set uploaded by Alex Monk:
+Follow redirects when looking up template data
+
+https://gerrit.wikimedia.org/r/135065",task_subcomment,['Change 135065 had a related patch set uploaded by Alex Monk:\nFollow redirects when looking up template data\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245473,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Change 135064 had a related patch set uploaded by Alex Monk:
+Allow following of redirects via API
+
+https://gerrit.wikimedia.org/r/135064",task_subcomment,['Change 135064 had a related patch set uploaded by Alex Monk:\nAllow following of redirects via API\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245467,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"(In reply to Krinkle from comment #3)
+> Both VE and TemplateData should address this in their own way. Both parties
+> need to do something.
+> 
+> 1) Resolve redirects in API interaction:
+>   - TemplateData should have an option to resolve redirects in the given
+> titles (like action=query). the mapping will be added similarly to how we
+> normalise titles.
+
+This is a built-in feature in ApiPageSet, which is used by ApiQuery modules, as well as by ApiTemplateData. When enabled, passing &redirects to the request resolves redirects.",task_subcomment,"['(In reply to Krinkle from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis is a built-in feature in ApiPageSet, which is used by ApiQuery modules, as well as by ApiTemplateData.', 'When enabled, passing &redirects to the request resolves redirects.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+245461,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,This is still a major usability issue with templatedata as template redirects are quite common. Any update?,task_subcomment,"['This is still a major usability issue with templatedata as template redirects are quite common.', 'Any update?']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+245455,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"We have been talking about returning more metadata like the list of used templates from the PHP preprocessor, and use that for dependency tracking. Even with that info I'm not convinced that we should attempt to directly skip redirects in Parsoid, as that would add a lot of complexity and unexpected behavior.
+
+It should not be that hard to handle this in TemplateData itself, and to me it looks like the best place to do it.",task_subcomment,"['We have been talking about returning more metadata like the list of used templates from the PHP preprocessor, and use that for dependency tracking.', ""Even with that info I'm not convinced that we should attempt to directly skip redirects in Parsoid, as that would add a lot of complexity and unexpected behavior."", 'It should not be that hard to handle this in TemplateData itself, and to me it looks like the best place to do it.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+245448,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"This is a little tricky on the Parsoid end since Parsoid gets the PHP preprocessor to expand template source for us (which we then parse and process). So, Parsoid never sees the redirect that are embedded in templates (like {{cn}}). So, this will require us to instrument the PHP preprocessor to provide Parsoid with this information. Offhand, I cannot think of any efficient trick that will solve this.
+
+So, I think approach (1) above where TemplateData adds redirection info and VE uses that might work for the common case where the redirect target is not a function of template args.",task_subcomment,"['This is a little tricky on the Parsoid end since Parsoid gets the PHP preprocessor to expand template source for us (which we then parse and process).', 'So, Parsoid never sees the redirect that are embedded in templates (like {{cn}}).', 'So, this will require us to instrument the PHP preprocessor to provide Parsoid with this information.', 'Offhand, I cannot think of any efficient trick that will solve this.', 'So, I think approach (1) above where TemplateData adds redirection info and VE uses that might work for the common case where the redirect target is not a function of template args.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+245442,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Should a new bug for the Parsoid part be filed, so that the Parsoid team to do their part of this? This is a very big issues as some of the most common templates like the iconic {{cn}} are redirect and was asked about again at 
+http://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=575686867&oldid=575662727",task_subcomment,"['Should a new bug for the Parsoid part be filed, so that the Parsoid team to do their part of this?', 'This is a very big issues as some of the most common templates like the iconic {{cn}} are redirect and was asked about again at \nURL']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']"
+245435,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Both VE and TemplateData should address this in their own way. Both parties need to do something.
+
+1) Resolve redirects in API interaction:
+  - TemplateData should have an option to resolve redirects in the given titles (like action=query). the mapping will be added similarly to how we normalise titles.
+  - Then the VisualEditor needs to use this map as the API response will put the templatedata for the target title, not the title queried. We do this already with normalised titles, so we can extend that to include redirects in that ""aliasing"" logic for normalised titles.
+
+2) Parsoid giving TemplateData the transcluded page name instead of the wikitext invocation.
+  - Right now we sometimes get wikitext instead of a page name, or (in case of redirects) the sourced page name, not the one actually transcluded.
+  - If/when Parsoid is able to know what the wikitext expands too etc. (not a blind call to the PHP parser as it is essentially now) this will make that a lot easier and also solve generated transclusion target page names (e.g. {{ {{foo}} }} ).",task_subcomment,"['Both VE and TemplateData should address this in their own way.', 'Both parties need to do something.', '1) Resolve redirects in API interaction:\n  - TemplateData should have an option to resolve redirects in the given titles (like action=query).', 'the mapping will be added similarly to how we normalise titles.', '- Then the VisualEditor needs to use this map as the API response will put the templatedata for the target title, not the title queried.', 'We do this already with normalised titles, so we can extend that to include redirects in that ""aliasing"" logic for normalised titles.', '2) Parsoid giving TemplateData the transcluded page name instead of the wikitext invocation.', '- Right now we sometimes get wikitext instead of a page name, or (in case of redirects) the sourced page name, not the one actually transcluded.', '- If/when Parsoid is able to know what the wikitext expands too etc.', '(not a blind call to the PHP parser as it is essentially now) this will make that a lot easier and also solve generated transclusion target page names (e.g.', '{{ {{foo}} }} ).']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+245428,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Note from bug 51791 fwiw: this issue is being discussed at
+http://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor/TemplateData#What_about_redirected_templates",task_subcomment,['Note from bug 51791 fwiw: this issue is being discussed at\nURL'],['FUTURE PLAN']
+245420,TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,*** Bug 51791 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51791 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52947,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"To reproduce:
+
+* Edit a page with some existing content in VisualEditor.
+* Press Ctrl-A to select the whole text.
+* Press the Delete key.
+
+Observed: The page cannot be edited any more.
+
+Expected: The page doesn't have any text, but text can be added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox\n\nTo reproduce:\n\n* Edit a page with some existing content in VisualEditor.', '* Press Ctrl-A to select the whole text.', '* Press the Delete key.', 'Observed: The page cannot be edited any more.', ""Expected: The page doesn't have any text, but text can be added."", '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+244477,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"Change 86299 merged by jenkins-bot:
+ce.BranchNode: Insert slugs based on CE children length, not DM
+
+https://gerrit.wikimedia.org/r/86299",task_subcomment,"['Change 86299 merged by jenkins-bot:\nce.BranchNode: Insert slugs based on CE children length, not DM\n\nGERRIT_URL']",['ACTION ON ISSUE']
+244471,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"This bug has been fixed somewhere in the past week. The range is no longer (0,0) but (0,[document length]). The document no longer crashes and properly deletes all content.
+
+However this uncovered another bug, namely that in Firefox deleting the selection now leaves the document completely empty (not even a placeholder 
     to start typing again). That is what change 86299 (https://gerrit.wikimedia.org/r/86299) addresses.
+
+However this bug is fixed, though I don't know which commit fixed it.",task_subcomment,"['This bug has been fixed somewhere in the past week.', 'The range is no longer (0,0) but (0,[document length]).', 'The document no longer crashes and properly deletes all content.', 'However this uncovered another bug, namely that in Firefox deleting the selection now leaves the document completely empty (not even a placeholder 
     to start typing again).', 'That is what change 86299 (GERRIT_URL) addresses.', ""However this bug is fixed, though I don't know which commit fixed it.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+244466,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"Change 86299 had a related patch set uploaded by Krinkle:
+ce.BranchNode: Insert slugs based on CE children length, not DM
+
+https://gerrit.wikimedia.org/r/86299",task_subcomment,"['Change 86299 had a related patch set uploaded by Krinkle:\nce.BranchNode: Insert slugs based on CE children length, not DM\n\nGERRIT_URL']",['ACTION ON ISSUE']
+244461,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"When the document loads in Firefox (Firefox 24, Mac) ve.ce.Document#getNodeAndOffset gets called with offset=1 to show initial selection (range: 1,1).
+
+When selecting all and pressing backspace, ve.ce.Document#getNodeAndOffset gets called with offset = -1.
+
+It gets there from ve.ce.Surface#handleDelete, which has a rangeToRemove (from this.model.getSelection) of 0,0.
+
+The #handleDelete method then sees the range is collapsed, and since backspace=true, it will get a relative range on the document from the (collapsed) 0,0 rangeToRemove to -1.",task_subcomment,"['When the document loads in Firefox (Firefox 24, Mac) ve.ce.Document#getNodeAndOffset gets called with offset=1 to show initial selection (range: 1,1).', 'When selecting all and pressing backspace, ve.ce.Document#getNodeAndOffset gets called with offset = -1.', 'It gets there from ve.ce.Surface#handleDelete, which has a rangeToRemove (from this.model.getSelection) of 0,0.', 'The #handleDelete method then sees the range is collapsed, and since backspace=true, it will get a relative range on the document from the (collapsed) 0,0 rangeToRemove to -1.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+244456,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,This is still happening with Firefox 24 on Linux using the monobook skin (other combinations not tested),task_subcomment,['This is still happening with Firefox 24 on Linux using the monobook skin (other combinations not tested)'],['OBSERVED BUG BEHAVIOR']
+244451,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"**JohnCD67** wrote:
+
+Occurs with Vector/Win7/FF23.0. It doesn't matter whether Ctr-A or Right-click/Select all is used, or whether ""Delete"" or ""Backspace"" is used to delete.",task_subcomment,"['**JohnCD67** wrote:\n\nOccurs with Vector/Win7/FF23.0.', 'It doesn\'t matter whether Ctr-A or Right-click/Select all is used, or whether ""Delete"" or ""Backspace"" is used to delete.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244447,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,*** Bug 52125 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52125 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244444,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,Looking into it now.,task_subcomment,['Looking into it now.'],['OBSERVED BUG BEHAVIOR']
+244440,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"Example from Bug 51169, which also has a screenshot.
+
+https://en.wikipedia.org/w/index.php?title=List_of_American_Dad!_characters&curid=2082680&diff=564675517&oldid=564302759",task_subcomment,"['Example from Bug 51169, which also has a screenshot.', 'URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+244433,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,*** Bug 51169 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51169 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244426,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,*** Bug 50519 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50519 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244417,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,"Yes.
+
+In RL debug mode I got this:
+
+--
+[11:13:55.789] TypeError: node.getParent(...) is null @ https://bits.wikimedia.org/static-1.22wmf8/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js:1265
+
+It only happens in Firefox.",task_subcomment,"['Yes.', 'In RL debug mode I got this:\n\n--\n[11:13:55.789] TypeError: node.getParent(...) is null @ URL\n\nIt only happens in Firefox.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244410,VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,Do any JS errors appear in the console while you do this?,task_subcomment,['Do any JS errors appear in the console while you do this?'],['OBSERVED BUG BEHAVIOR']
+52945,VisualEditor: Wikilink editing does not permit easy alteration of display text,"From a conversation with an English Wikipedia editor user Thryduulf, he says that when it comes to editing existing links (as opposed to adding new one): 
+***
+there are three things you could want to do:
+
+(1) change the link without changing the text (e.g. [[Mercury]] → [[Mercury (planet)|Mercury]])
+(2) change the text without changing the link (e.g. [[Mercury (element)]] → [[Mercury (element)|Mercury]])
+(3) change both (e.g. [[Mercury]] → [[Freddie Mercury]])
+
+At present it seems that the visual editor always assumes you want to do 1, and unless you delete the link completely there is no way of doing otherwise..., but for beginners I'd say that 3 should be the default. There needs to be some way to set the target of a link independently of what is displayed, and I'm not sure how best to do that but maybe an option on the link dialog called ""display as"" or something like that would be the way to go.
+
+***
+
+(Please see http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563383564#Changing_link_text_often_results_in_bad_code.2C_wrong_links_and_unmatched_.3C.2Fnowki.3Es
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52240
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50678
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33091
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50452
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53973",task_description,"['VisualEditor: Wikilink editing does not permit easy alteration of display text\n\nFrom a conversation with an English Wikipedia editor user Thryduulf, he says that when it comes to editing existing links (as opposed to adding new one): \n***\nthere are three things you could want to do:\n\n(1) change the link without changing the text (e.g.', '[[Mercury]] → [[Mercury (planet)|Mercury]])\n(2) change the text without changing the link (e.g.', '[[Mercury (element)]] → [[Mercury (element)|Mercury]])\n(3) change both (e.g.', ""[[Mercury]] → [[Freddie Mercury]])\n\nAt present it seems that the visual editor always assumes you want to do 1, and unless you delete the link completely there is no way of doing otherwise..., but for beginners I'd say that 3 should be the default."", 'There needs to be some way to set the target of a link independently of what is displayed, and I\'m not sure how best to do that but maybe an option on the link dialog called ""display as"" or something like that would be the way to go.', '***\n\n(Please see URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL\nURL\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+244311,VisualEditor: Wikilink editing does not permit easy alteration of display text,"(In reply to Krinkle from comment #8)
+> (removed a couple duplicate see-alsos)
+> 
+> Unless I misunderstood the bug, we haven't really made any progress on this
+> since last year.
+
+Yes, you have mis-understood comment 7:
+
+(In reply to James Forrester from comment #7)
+> (In reply to Elitre from comment #6)
+> > What Chris described at comment#3 is still happening:
+> > https://fr.wikipedia.org/w/index.
+> > php?title=St%C3%A9phane_Bern&diff=100014868&oldid=98819232 .
+> 
+> That's now in bug 62819, which we believe we have just fixed this week (to
+> go out on Thursday). Closing this. The suggestion that there be two edit
+> fields in the link inspector (one for anchor, the other for target) is
+> tracked in bug 53973.
+
+The remaining parts of this bug that aren't fixed are a duplicate of bug 53973.",task_subcomment,"[""(In reply to Krinkle from comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYes, you have mis-understood comment 7:\n\n(In reply to James Forrester from comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe remaining parts of this bug that aren't fixed are a duplicate of bug 53973.""]",['ACTION ON ISSUE']
+244305,VisualEditor: Wikilink editing does not permit easy alteration of display text,"(removed a couple duplicate see-alsos)
+
+Unless I misunderstood the bug, we haven't really made any progress on this since last year.
+
+(In reply to Maggie Dennis from comment #0)
+> there are three things you could want to do:
+> 
+> (1) change the link without changing the text (e.g. [[Mercury]] → [[Mercury
+> (planet)|Mercury]])
+> (2) change the text without changing the link (e.g. [[Mercury (element)]] →
+> [[Mercury (element)|Mercury]])
+> (3) change both (e.g. [[Mercury]] → [[Freddie Mercury]])
+> 
+> At present it seems that the visual editor always assumes you want to do 1,
+> and unless you delete the link completely there is no way of doing
+> otherwise..., but for beginners I'd say that 3 should be the default. There
+> needs to be some way to set the target of a link independently of what is
+> displayed, and I'm not sure how best to do that but maybe an option on the
+> link dialog called ""display as"" or something like that would be the way to
+> go.
+
+#2 and #3 are still not possible without deleting everything and re-creating a link. The only other way is to basically type the new label somewhere within the existing label, and then strip away the old characters. That's not something any user can be expected to do.
+
+E.g. to change label from ""Foo"" to ""Bar"" of external link http://example.org:
+
+1. Type ""Bar"" inside ""Foo""
+   - Foo
+   + FoBaro
+2. Manually remove ""Fo"" and ""o""
+
+The main things lacking for this bug is a way to change the link label.
+
+Or in other words, to select the contents of the label without its boundaries. Right now selecting ""Foo"" and typing over it removes the link...
+
+Bug 37939 is also related (would make it easier to select it), but is not required.
+
+Right now users would probably be forced into removing it and re-creating it, which hits bug 67086 / bug 67088.",task_subcomment,"[""(removed a couple duplicate see-alsos)\n\nUnless I misunderstood the bug, we haven't really made any progress on this since last year."", '(In reply to Maggie Dennis from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n#2 and #3 are still not possible without deleting everything and re-creating a link.', 'The only other way is to basically type the new label somewhere within the existing label, and then strip away the old characters.', ""That's not something any user can be expected to do."", 'E.g.', 'to change label from ""Foo"" to ""Bar"" of external link URL\n\n1.', 'Type ""Bar"" inside ""Foo""\n   - Foo\n   + FoBaro\n2.', 'Manually remove ""Fo"" and ""o""\n\nThe main things lacking for this bug is a way to change the link label.', 'Or in other words, to select the contents of the label without its boundaries.', 'Right now selecting ""Foo"" and typing over it removes the link...\n\nBug 37939 is also related (would make it easier to select it), but is not required.', 'Right now users would probably be forced into removing it and re-creating it, which hits bug 67086 / bug 67088.']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+244299,VisualEditor: Wikilink editing does not permit easy alteration of display text,"(In reply to Elitre from comment #6)
+> What Chris described at comment#3 is still happening:
+> https://fr.wikipedia.org/w/index.
+> php?title=St%C3%A9phane_Bern&diff=100014868&oldid=98819232 .
+
+That's now in bug 62819, which we believe we have just fixed this week (to go out on Thursday). Closing this. The suggestion that there be two edit fields in the link inspector (one for anchor, the other for target) is tracked in bug 53973.",task_subcomment,"[""(In reply to Elitre from comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nThat's now in bug 62819, which we believe we have just fixed this week (to go out on Thursday)."", 'Closing this.', 'The suggestion that there be two edit fields in the link inspector (one for anchor, the other for target) is tracked in bug 53973.']","['SOLUTION USAGE', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+244293,VisualEditor: Wikilink editing does not permit easy alteration of display text,"What Chris described at comment#3 is still happening:
+https://fr.wikipedia.org/w/index.php?title=St%C3%A9phane_Bern&diff=100014868&oldid=98819232 .",task_subcomment,['What Chris described at comment#3 is still happening:\nURL .'],['OBSERVED BUG BEHAVIOR']
+244288,VisualEditor: Wikilink editing does not permit easy alteration of display text,"This is no longer true, since late July when editing of link anchors was made ""spanning""; closing.",task_subcomment,"['This is no longer true, since late July when editing of link anchors was made ""spanning""; closing.']",['OBSERVED BUG BEHAVIOR']
+244283,VisualEditor: Wikilink editing does not permit easy alteration of display text,"This is causing content corruption on the live wiki.
+
+A user apparently trying to change a link from [[Blackpool Grand Theatre]] to [[Grand Theatre, Blackpool]] over two edits failed to do this:
+
+1. ""[[Blackpool Grand Theatre]] and"" → ""[[Blackpool Grand Theatre|Blackpool Grand Theatre]] and""
+2. ""[[Blackpool Grand Theatre|Blackpool Grand Theatre]]"" → ""G[[Blackpool Grand theater|rand Theater, Blackpool, ]]and""
+
+https://en.wikipedia.org/w/index.php?title=Bernie_Nolan&diff=prev&oldid=564655203
+https://en.wikipedia.org/w/index.php?title=Bernie_Nolan&diff=next&oldid=564655203
+
+This should not be marked as an enhancement, changing links without mangling the text should be a core requirement of VE.",task_subcomment,"['This is causing content corruption on the live wiki.', 'A user apparently trying to change a link from [[Blackpool Grand Theatre]] to [[Grand Theatre, Blackpool]] over two edits failed to do this:\n\n1.', '""[[Blackpool Grand Theatre]] and"" → ""[[Blackpool Grand Theatre|Blackpool Grand Theatre]] and""\n2.', '""[[Blackpool Grand Theatre|Blackpool Grand Theatre]]"" → ""G[[Blackpool Grand theater|rand Theater, Blackpool, ]]and""\n\nURL\nURL\n\nThis should not be marked as an enhancement, changing links without mangling the text should be a core requirement of VE.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']"
+244278,VisualEditor: Wikilink editing does not permit easy alteration of display text,"It should be. However my testing showed that this was not reliable and sometimes resulted in odd wikicode, e.g. [[Ecuador|]][[Egypt|E]][[Egypt|gypt]] when changing ""Ecudor"" to ""Egypt"".
+
+See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&diff=563097916&oldid=563090562",task_subcomment,"['It should be.', 'However my testing showed that this was not reliable and sometimes resulted in odd wikicode, e.g.', '[[Ecuador|]][[Egypt|E]][[Egypt|gypt]] when changing ""Ecudor"" to ""Egypt"".', 'See URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+244273,VisualEditor: Wikilink editing does not permit easy alteration of display text,"""and unless you delete the link completely there is no way of doing otherwise...,""
+
+Isnt (2) and (3) possible by editing the text of the wikilink in the normal editor (i.e. not the link dialog), after selecting the link target?
+
+I must admit I was dumbfounded for a few minutes when trying to do (2), until it occurred to me that I can edit the text in the page.
+
+(3) is a bit harder, as the user must change the target from 'Mercury' to 'Freddie Mercury', then change the text to 'MFreddie Mercury', then remove the leading 'M'.",task_subcomment,"['""and unless you delete the link completely there is no way of doing otherwise...,""\n\nIsnt (2) and (3) possible by editing the text of the wikilink in the normal editor (i.e.', 'not the link dialog), after selecting the link target?', 'I must admit I was dumbfounded for a few minutes when trying to do (2), until it occurred to me that I can edit the text in the page.', ""(3) is a bit harder, as the user must change the target from 'Mercury' to 'Freddie Mercury', then change the text to 'MFreddie Mercury', then remove the leading 'M'.""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+244269,VisualEditor: Wikilink editing does not permit easy alteration of display text,"I'm guessing it would be possible for the display as thing to also have suggestions, e.g. in most cases on en.wp if a title has parentheses then you don't want to display what is in them as it is disambiguation. For example if you chose the link [[Mercury (planet)]] the software could say ""Do you want to display this as ""Mercury""?",task_subcomment,"[""I'm guessing it would be possible for the display as thing to also have suggestions, e.g."", ""in most cases on en.wp if a title has parentheses then you don't want to display what is in them as it is disambiguation."", 'For example if you chose the link [[Mercury (planet)]] the software could say ""Do you want to display this as ""Mercury""?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52944,Extension tags are not nowiki escaped during serialization.,"Typing certain tag based code into VE such as:
+
+1+2=3
+Hi
+
+Bug reported by [[User:Dragons flight|Dragons flight]] at https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Some_tags_are_not_properly_escaped
+
+Confirmed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Extension tags are not nowiki escaped during serialization.', 'Typing certain tag based code into VE such as:\n\n1+2=3\nHi\n\nBug reported by [[User:Dragons flight|Dragons flight]] at URL\n\nConfirmed.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+244239,Extension tags are not nowiki escaped during serialization.,"Change 72536 merged by jenkins-bot:
+(Bug 50944) Fix stale regexp in wikitext escaping for ext tags
+
+https://gerrit.wikimedia.org/r/72536",task_subcomment,['Change 72536 merged by jenkins-bot:\n(Bug 50944) Fix stale regexp in wikitext escaping for ext tags\n\nGERRIT_URL'],['BUG REPRODUCTION']
+244233,Extension tags are not nowiki escaped during serialization.,"Change 72536 had a related patch set uploaded by Subramanya Sastry:
+(Bug 50944) Fix stale regexp in wikitext escaping for ext tags
+
+https://gerrit.wikimedia.org/r/72536",task_subcomment,['Change 72536 had a related patch set uploaded by Subramanya Sastry:\n(Bug 50944) Fix stale regexp in wikitext escaping for ext tags\n\nGERRIT_URL'],['BUG REPRODUCTION']
+52913,VisualEditor: Selection highlight for templates/etc. mis-placed,"Copied from English Wikipedia, where it was added by TeamGale:
+""when I add the reference/template, if I want to edit it again it's not easy to choose it since the ""blue line"" that has to be on the text appears completely elsewhere and I can't click it. I took a screenshot""
+
+See:
+http://en.wikipedia.org/wiki/File:Misplaced_edit_for_a_template.jpg
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Selection highlight for templates/etc.', 'mis-placed\n\nCopied from English Wikipedia, where it was added by TeamGale:\n""when I add the reference/template, if I want to edit it again it\'s not easy to choose it since the ""blue line"" that has to be on the text appears completely elsewhere and I can\'t click it.', 'I took a screenshot""\n\nSee:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+242402,VisualEditor: Selection highlight for templates/etc. mis-placed,I believe that this has now been fixed given the changes to how the CSS is cached.,task_subcomment,['I believe that this has now been fixed given the changes to how the CSS is cached.'],['SOLUTION DISCUSSION']
+242399,VisualEditor: Selection highlight for templates/etc. mis-placed,"As noted in the duplicate bug 50991, this issue is somewhat elusive but definitely occurring for some users. Given the impact when it does, increasing severity and importance.",task_subcomment,"['As noted in the duplicate bug 50991, this issue is somewhat elusive but definitely occurring for some users.', 'Given the impact when it does, increasing severity and importance.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+242395,VisualEditor: Selection highlight for templates/etc. mis-placed,*** Bug 50991 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50991 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52905,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,"Replication steps:
+
+1. go here: https://he.wikipedia.org/wiki/%D7%A8%D7%97%D7%95%D7%91_%D7%99%D7%A8%D7%95%D7%A9%D7%9C%D7%99%D7%9D?veaction=edit
+
+2. Click the box on the left (a 'street' template in the hebrew wiki)
+
+3. The ""Transclusion"" icon appears on the right edge instead of the left. 
+
+Happens in Chrome and Firefox 22.0 under Windows.
+
+I suspect this is again a problem with the flipped position settings. I will take a look in the code.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis\n\nReplication steps:\n\n1. go here: URL\n\n2.', ""Click the box on the left (a 'street' template in the hebrew wiki)\n\n3."", 'The ""Transclusion"" icon appears on the right edge instead of the left.', 'Happens in Chrome and Firefox 22.0 under Windows.', 'I suspect this is again a problem with the flipped position settings.', 'I will take a look in the code.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241996,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,"Change 79165 merged by jenkins-bot:
+Fixing inspector popup position
+
+https://gerrit.wikimedia.org/r/79165",task_subcomment,['Change 79165 merged by jenkins-bot:\nFixing inspector popup position\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241992,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,*** Bug 53161 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53161 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241986,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,I posted a fix which seems to work but requires some testing and review. Also testing in RTL seems to work.,task_subcomment,"['I posted a fix which seems to work but requires some testing and review.', 'Also testing in RTL seems to work.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+241979,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,"Change 79165 had a related patch set uploaded by Mooeypoo:
+Fixing inspector popup position
+
+https://gerrit.wikimedia.org/r/79165",task_subcomment,['Change 79165 had a related patch set uploaded by Mooeypoo:\nFixing inspector popup position\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+241975,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,"(In reply to comment #2)
+> This may be an issue with the way the icon appears in general, not just
+> specifically RTL. It seems the transclusion icon pops up on the side of the
+> page, assuming the position is always on the side -- instead of, perhaps,
+> appearing where the template box is located regardless of alignment.
+> 
+> I am not sure if this fix shouldn't be a deeper VE fix rather than the
+> language-directionality specific fix.
+
+Yes, I think a deeper fix might be appropriate - would you want to do that, or should I ask Rob?",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYes, I think a deeper fix might be appropriate - would you want to do that, or should I ask Rob?']",['SOLUTION DISCUSSION']
+241970,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,"This may be an issue with the way the icon appears in general, not just specifically RTL. It seems the transclusion icon pops up on the side of the page, assuming the position is always on the side -- instead of, perhaps, appearing where the template box is located regardless of alignment.
+
+I am not sure if this fix shouldn't be a deeper VE fix rather than the language-directionality specific fix.",task_subcomment,"['This may be an issue with the way the icon appears in general, not just specifically RTL.', 'It seems the transclusion icon pops up on the side of the page, assuming the position is always on the side -- instead of, perhaps, appearing where the template box is located regardless of alignment.', ""I am not sure if this fix shouldn't be a deeper VE fix rather than the language-directionality specific fix.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+241964,VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,confirmed on Arch linux with FF 22.,task_subcomment,['confirmed on Arch linux with FF 22.'],['OBSERVED BUG BEHAVIOR']
+52902,VisualEditor: Add tooltip to byte count of save dialog explaining what it's for,"The character counter of the save dialog should have a tooltip/title explaining what the counter refers entails.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",task_description,"[""VisualEditor: Add tooltip to byte count of save dialog explaining what it's for\n\nThe character counter of the save dialog should have a tooltip/title explaining what the counter refers entails."", '--------------------------\n**Version**: unspecified\n**Severity**: trivial']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+241875,VisualEditor: Add tooltip to byte count of save dialog explaining what it's for,"Change 112318 had a related patch set uploaded by Alex Monk:
+Explain what the number on the edit summary screen means
+
+https://gerrit.wikimedia.org/r/112318",task_subcomment,['Change 112318 had a related patch set uploaded by Alex Monk:\nExplain what the number on the edit summary screen means\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+52888,VisualEditor cannot get full TemplateData on zhwiki (language variant issue?),"screenshot of the dialogue
+
+I added TemplateData to Template:X1 (this is a sandbox)
+Then, I go to my personal sandbox User:Waihorace/sandbox/VE to try adding Template X1 to that page.
+I pressed the button that allow me to add template (don't know its exact English wording)
+It prompt me to enter a template name, so I typed in X1
+Then, it comes out that the description is not shown, parma names are not shown, but the list of parma is given for me to choose.
+
+Why the description and the name and description of the parma is not shown, while https://zh.wikipedia.org/w/api.php?action=templatedata&titles=Template:X1&format=jsonfm works?
+
+( X1 is a template which will be cleared by a bot automatically. To reproduce, check if the content is still there or otherwise revent back to oldid=27156695 )
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50431
+
+**Attached**: {F11387}",task_description,"['VisualEditor cannot get full TemplateData on zhwiki (language variant issue?)', 'screenshot of the dialogue\n\nI added TemplateData to Template:X1 (this is a sandbox)\nThen, I go to my personal sandbox User:Waihorace/sandbox/VE to try adding Template X1 to that page.', ""I pressed the button that allow me to add template (don't know its exact English wording)\nIt prompt me to enter a template name, so I typed in X1\nThen, it comes out that the description is not shown, parma names are not shown, but the list of parma is given for me to choose."", 'Why the description and the name and description of the parma is not shown, while URL works?', '( X1 is a template which will be cleared by a bot automatically.', 'To reproduce, check if the content is still there or otherwise revent back to oldid=27156695 )\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\n\n**Attached**: {F11387}']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+241042,VisualEditor cannot get full TemplateData on zhwiki (language variant issue?),"Change 92826 merged by jenkins-bot:
+dm.MWTemplateSpecModel: Resolve translations through the TemplateData API
+
+https://gerrit.wikimedia.org/r/92826",task_subcomment,['Change 92826 merged by jenkins-bot:\ndm.MWTemplateSpecModel: Resolve translations through the TemplateData API\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241038,VisualEditor cannot get full TemplateData on zhwiki (language variant issue?),"Change 92826 had a related patch set uploaded by Krinkle:
+dm.MWTemplateSpecModel: Resolve translations through the TemplateData API
+
+https://gerrit.wikimedia.org/r/92826",task_subcomment,['Change 92826 had a related patch set uploaded by Krinkle:\ndm.MWTemplateSpecModel: Resolve translations through the TemplateData API\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241034,VisualEditor cannot get full TemplateData on zhwiki (language variant issue?),"(In reply to comment #1)
+> Created attachment 12774 [details]
+> API response
+> 
+> To make it easier, after I restored your edit at
+> https://zh.wikipedia.org/w/index.php?diff=27157124
+> the content of
+> https://zh.wikipedia.org/w/api.php?action=templatedata&titles=Template:
+> X1&format=jsonfm
+> was like in the attached file.
+> 
+> What was your user language preference when you tested this?
+> 
+> Does the problem happens on both of the following URLs?
+> https://zh.wikipedia.org/wiki/User:Waihorace/sandbox/
+> VE?veaction=edit&uselang=zh
+> https://zh.wikipedia.org/wiki/User:Waihorace/sandbox/
+> VE?veaction=edit&uselang=en
+> 
+> For me the bug only happens in the second one, and I think this is the same
+> as
+> bug 50431.
+
+The bug only happens in the second one. 
+I think the problem that I reported comes out because of the language conversion of Chinese Wikipedia. 
+
+The TemplateData only works on zh, but not any variant of Chinese (e.g. zh-hans, zh-hant, zh-tw, zh-cn, zh-hk, zh-sg, zh-mo). Should the data in zh be applied in those 7 variants, or otherwise, editors need to set the description for every variants which is time-wasting.
+
+**Attached**: {F11388}",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe bug only happens in the second one.', 'I think the problem that I reported comes out because of the language conversion of Chinese Wikipedia.', 'The TemplateData only works on zh, but not any variant of Chinese (e.g.', 'zh-hans, zh-hant, zh-tw, zh-cn, zh-hk, zh-sg, zh-mo).', 'Should the data in zh be applied in those 7 variants, or otherwise, editors need to set the description for every variants which is time-wasting.', '**Attached**: {F11388}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+241029,VisualEditor cannot get full TemplateData on zhwiki (language variant issue?),"Created attachment 12774
+API response
+
+To make it easier, after I restored your edit at
+https://zh.wikipedia.org/w/index.php?diff=27157124
+the content of
+https://zh.wikipedia.org/w/api.php?action=templatedata&titles=Template:X1&format=jsonfm
+was like in the attached file.
+
+What was your user language preference when you tested this?
+
+Does the problem happens on both of the following URLs?
+https://zh.wikipedia.org/wiki/User:Waihorace/sandbox/VE?veaction=edit&uselang=zh
+https://zh.wikipedia.org/wiki/User:Waihorace/sandbox/VE?veaction=edit&uselang=en
+
+For me the bug only happens in the second one, and I think this is the same as bug 50431.
+
+**Attached**: {F11388}",task_subcomment,"['Created attachment 12774\nAPI response\n\nTo make it easier, after I restored your edit at\nURL\nthe content of\nURL\nwas like in the attached file.', 'What was your user language preference when you tested this?', 'Does the problem happens on both of the following URLs?', 'URL\nURL\n\nFor me the bug only happens in the second one, and I think this is the same as bug 50431.', '**Attached**: {F11388}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52854,VisualEditor: Display the contextual menu for templates much more visibly,"I've noticed a couple of times that users on VE/Feedback have said that they 'couldn't change the block and that it became blue', which I think is an indication they were unable to spot the template edit button.
+
+Now I noticed that the edit button anchor for templates is always at the top right. On 100% width block elements, the content can often be completely left aligned however, and the button is then to the FAR right of the page, making it easy to miss.
+
+For instance, take the {{Refbegin}}-{{refend} block on this page https://en.wikipedia.org/wiki/Warehouse_control_system?veaction=edit on a fairly large monitor.
+
+It might be nice if we could come up with some idea to more intelligently place the button. if( block && !width && computedWidth > 160em && text_align == left) then align button left
+
+
+Point 2:
+Also, the white button on the blue mask on top of the white page is not the highest contrasting style. Styling it stronger might also make it easier to discover for users.
+
+Point 3:
+The puzzle piece in that context doesn't give the user much info. Why not a simple Edit logo ? I think that would be way easier to understand.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Display the contextual menu for templates much more visibly\n\nI've noticed a couple of times that users on VE/Feedback have said that they 'couldn't change the block and that it became blue', which I think is an indication they were unable to spot the template edit button."", 'Now I noticed that the edit button anchor for templates is always at the top right.', 'On 100% width block elements, the content can often be completely left aligned however, and the button is then to the FAR right of the page, making it easy to miss.', 'For instance, take the {{Refbegin}}-{{refend} block on this page URL on a fairly large monitor.', 'It might be nice if we could come up with some idea to more intelligently place the button.', 'if( block && !width && computedWidth > 160em && text_align == left) then align button left\n\n\nPoint 2:\nAlso, the white button on the blue mask on top of the white page is not the highest contrasting style.', 'Styling it stronger might also make it easier to discover for users.', ""Point 3:\nThe puzzle piece in that context doesn't give the user much info."", 'Why not a simple Edit logo ?', 'I think that would be way easier to understand.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+239068,VisualEditor: Display the contextual menu for templates much more visibly,Confirmed the fix in production - the templates' contextual menu is displayed either on the far right of the screen or at the middle as for 'Cite web' template.,task_subcomment,"[""Confirmed the fix in production - the templates' contextual menu is displayed either on the far right of the screen or at the middle as for 'Cite web' template.""]",['BUG REPRODUCTION']
+239065,VisualEditor: Display the contextual menu for templates much more visibly,"Sorry for having not responded on this ticket; we fixed this ages ago with the new contextual menu. There are still some issues with the context appearing off-screen if the template is taller than your screen and you're down-page of it, but that is covered by different bugs.",task_subcomment,"['Sorry for having not responded on this ticket; we fixed this ages ago with the new contextual menu.', ""There are still some issues with the context appearing off-screen if the template is taller than your screen and you're down-page of it, but that is covered by different bugs.""]","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+239061,VisualEditor: Display the contextual menu for templates much more visibly,"Screenshot of cs.wp Křivá Ves shows the wrong possition of edit button.
+
+I agree. Look at https://cs.wikipedia.org/wiki/Křivá_Ves. If you want to edit the infobox, the key/edit button goes completly to right, where you might not notice it.
+
+**Attached**: {F11331}",task_subcomment,"['Screenshot of cs.wp Křivá Ves shows the wrong possition of edit button.', 'I agree.', 'Look at URL If you want to edit the infobox, the key/edit button goes completly to right, where you might not notice it.', '**Attached**: {F11331}']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+52852,VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled,"I deliberately edited [[Roller coaster]], an article under Pending Changes that had an unreviewed change, using my administrator account, using VisualEditor. When editing source, there would be an edit notice advising of the pending change, which is not present with VisualEditor. Nonetheless, edits by an administrator account are supposed to be automatically accepted.  Instead, my edit was made subject to review. See screenshot at http://commons.wikimedia.org/wiki/File:CoasterCrop.png.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49699",task_description,"['VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled\n\nI deliberately edited [[Roller coaster]], an article under Pending Changes that had an unreviewed change, using my administrator account, using VisualEditor.', 'When editing source, there would be an edit notice advising of the pending change, which is not present with VisualEditor.', 'Nonetheless, edits by an administrator account are supposed to be automatically accepted.', 'Instead, my edit was made subject to review.', 'See screenshot at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+238984,VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled,"I mis-understood the bug as reported; my apologies. It is in fact entirely a duplicate of bug 49699. Marking as such.
+
+*** This bug has been marked as a duplicate of bug 49699 ***",task_subcomment,"['I mis-understood the bug as reported; my apologies.', 'It is in fact entirely a duplicate of bug 49699.', 'Marking as such.', '*** This bug has been marked as a duplicate of bug 49699 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238976,VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled,"Isn't this just how FlaggedRevs (this is a different name for the same thing AFAIK) work? Edits by reviewers are only autoflagged if the previous revision was flagged as well.
+
+Unless I'm misunderstanding something, the bug as described by the current summary (""VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled"") would be a blocker to deployment on Wikipedia using FlaggedRevs for all articles, like the Polish Wikipedia. However it seemed to behave corrently in my testing there.",task_subcomment,"[""Isn't this just how FlaggedRevs (this is a different name for the same thing AFAIK) work?"", 'Edits by reviewers are only autoflagged if the previous revision was flagged as well.', 'Unless I\'m misunderstanding something, the bug as described by the current summary (""VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled"") would be a blocker to deployment on Wikipedia using FlaggedRevs for all articles, like the Polish Wikipedia.', 'However it seemed to behave corrently in my testing there.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+238967,VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled,"Expanding on the above, when editing a PendingChanges article with actively pending changes using source code, admins/reviewers must either accept or revert the outstanding PCs before their own edit is saved. This is not happening under VisualEditor.",task_subcomment,"['Expanding on the above, when editing a PendingChanges article with actively pending changes using source code, admins/reviewers must either accept or revert the outstanding PCs before their own edit is saved.', 'This is not happening under VisualEditor.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+52850,VisualEditor: Inspecting image immediately after inserting it causes exception,"1. Put the cursor in the middle of a paragraph
+2. Insert an image
+3. The inserted image is now selected, and displays an inspector button
+4. Click the inspector button
+5. You get an empty image dialog and an exception because getFocusableNode() returned null
+
+It seems this happens because the post-insertion selection in step 3 covers something like 
     rather than just the image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Inspecting image immediately after inserting it causes exception\n\n1.', 'Put the cursor in the middle of a paragraph\n2.', 'Insert an image\n3.', 'The inserted image is now selected, and displays an inspector button\n4.', 'Click the inspector button\n5.', 'You get an empty image dialog and an exception because getFocusableNode() returned null\n\nIt seems this happens because the post-insertion selection in step 3 covers something like 
     rather than just the image.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238865,VisualEditor: Inspecting image immediately after inserting it causes exception,This is now INVALID because we don't select the node after insertion any more (should we?).,task_subcomment,"[""This is now INVALID because we don't select the node after insertion any more (should we?"", ').']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238857,VisualEditor: Inspecting image immediately after inserting it causes exception,*** Bug 51863 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51863 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52841," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Right now the following HTML entered by a user:
+
+
    Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].
    
+
+… turns into:
+
+
    Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].
    
+
+… whereas ideally it should be minimal rather than maximal:
+
+
    Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].
    
+
+This would significantly reduce issues with users accidentally inputting wikitext.  We're taking actions in VisualEditor-land to discourage such input, but if Parsoid could help it would be hugely useful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[' tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)\n\nRight now the following HTML entered by a user:\n\n
    Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].
    \n\n… turns into:\n\n
    Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].
    \n\n… whereas ideally it should be minimal rather than maximal:\n\n
    Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].
    \n\nThis would significantly reduce issues with users accidentally inputting wikitext.', ""We're taking actions in VisualEditor-land to discourage such input, but if Parsoid could help it would be hugely useful."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238268," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","There are still some scenarios where nowiki wrapping will be applied to a longer string than required.  I haven't tried to optimize it all, and if there are still issues, I can revisit it.",task_subcomment,"['There are still some scenarios where nowiki wrapping will be applied to a longer string than required.', ""I haven't tried to optimize it all, and if there are still issues, I can revisit it.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238264," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)",This will likely be deployed later today.,task_subcomment,['This will likely be deployed later today.'],['SOLUTION DISCUSSION']
+238261," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Change 74110 merged by jenkins-bot:
+Take #2: (Bug 50841) Reduce scope of nowiki tags
+
+https://gerrit.wikimedia.org/r/74110",task_subcomment,['Change 74110 merged by jenkins-bot:\nTake #2: (Bug 50841) Reduce scope of nowiki tags\n\nGERRIT_URL'],['ACTION ON ISSUE']
+238259," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Change 74110 had a related patch set uploaded by Subramanya Sastry:
+Take #2: (Bug 50841) Reduce scope of nowiki tags
+
+https://gerrit.wikimedia.org/r/74110",task_subcomment,['Change 74110 had a related patch set uploaded by Subramanya Sastry:\nTake #2: (Bug 50841) Reduce scope of nowiki tags\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+238256," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Change 72858 merged by jenkins-bot:
+(Bug 50841): First pass reducing scope of nowiki tags
+
+https://gerrit.wikimedia.org/r/72858",task_subcomment,['Change 72858 merged by jenkins-bot:\n(Bug 50841): First pass reducing scope of nowiki tags\n\nGERRIT_URL'],['BUG REPRODUCTION']
+238251," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Change 72858 had a related patch set uploaded by Subramanya Sastry:
+(Bug 50841): First pass reducing scope of nowiki tags
+
+https://gerrit.wikimedia.org/r/72858",task_subcomment,['Change 72858 had a related patch set uploaded by Subramanya Sastry:\n(Bug 50841): First pass reducing scope of nowiki tags\n\nGERRIT_URL'],['BUG REPRODUCTION']
+238246," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Possibly interesting nowiki watch list to monitor nowiki application in live edits:
+https://en.wikipedia.org/w/index.php?title=Special:AbuseLog&offset=&limit=500&wpSearchFilter=550",task_subcomment,['Possibly interesting nowiki watch list to monitor nowiki application in live edits:\nURL'],['OBSERVED BUG BEHAVIOR']
+238240," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","(In reply to comment #11)
+
+> Oh I got it. We want to have -{ }- work, so we can't place
+> -{
+> }- back until all other -{ }- markups have been processed, but this also mean
+> other text in nowiki misses the chance to be converted...
+
+I guess -{ and }- in nowiki could be escaped before applying language conversion.",task_subcomment,['(In reply to comment #11)\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI guess -{ and }- in nowiki could be escaped before applying language conversion.'],['SOLUTION DISCUSSION']
+238233," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","(In reply to comment #10)
+> (In reply to comment #8)
+> > For us it would be helpful if we could separate those two aspects. If little
+> > existing content relies on language conversion being disabled in nowiki, then
+> > that might actually be possible.
+> 
+> There shouldn't be much. It's the case just because in Parser.php,
+> 
+> $text = $this->mStripState->unstripNoWiki( $text );
+> 
+> is placed after
+> 
+> $text = $this->getConverterLanguage()->convert( $text );
+> 
+> but I'm not 100% sure this is just something accidental (or placed in this
+> order delibrately).
+
+Oh I got it. We want to have -{ }- work, so we can't place -{ }- back until all other -{ }- markups have been processed, but this also mean other text in nowiki misses the chance to be converted...",task_subcomment,"['(In reply to comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOh I got it.', ""We want to have -{ }- work, so we can't place -{ }- back until all other -{ }- markups have been processed, but this also mean other text in nowiki misses the chance to be converted...""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+238223," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","(In reply to comment #8)
+> For us it would be helpful if we could separate those two aspects. If little
+> existing content relies on language conversion being disabled in nowiki, then
+> that might actually be possible.
+
+There shouldn't be much. It's the case just because in Parser.php,
+
+$text = $this->mStripState->unstripNoWiki( $text );
+
+is placed after
+
+$text = $this->getConverterLanguage()->convert( $text );
+
+but I'm not 100% sure this is just something accidental (or placed in this order delibrately).",task_subcomment,"[""(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\n\nThere shouldn't be much."", ""It's the case just because in Parser.php,\n\n$text = $this->mStripState->unstripNoWiki( $text );\n\nis placed after\n\n$text = $this->getConverterLanguage()->convert( $text );\n\nbut I'm not 100% sure this is just something accidental (or placed in this order delibrately).""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+238215," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Gabriel and I discussed the entity solution on IRC, and Gabriel made a good observation that fixing those in 'edit source' will become much harder compared to nowiki tags.  So, entity-based escaping makes fixups harder using the source editor, but makes it easier with VE.  With nowiki, it is the opposite.  But, presumably the noneditability of nowiki sections in VE is temporary.
+
+I'll tackle this with nowikis today by only changing how identified text blocks are escaped without trying to optimize placement itself (Ex:, in reality it is sufficient to only escape ""[["" or ""]]"" in [[Foo]], but that requires more global knowledge which will complicate this).
+
+We'll try to wrap closely occurring wikitext chars in a single nowiki block.  So, ""[[foo]]"" will be wrapped as [[foo]].  ""Closely occurring"" will be heuristic based, say within X chars.",task_subcomment,"[""Gabriel and I discussed the entity solution on IRC, and Gabriel made a good observation that fixing those in 'edit source' will become much harder compared to nowiki tags."", 'So, entity-based escaping makes fixups harder using the source editor, but makes it easier with VE.', 'With nowiki, it is the opposite.', 'But, presumably the noneditability of nowiki sections in VE is temporary.', 'I\'ll tackle this with nowikis today by only changing how identified text blocks are escaped without trying to optimize placement itself (Ex:, in reality it is sufficient to only escape ""[["" or ""]]"" in [[Foo]], but that requires more global knowledge which will complicate this).', ""We'll try to wrap closely occurring wikitext chars in a single nowiki block."", 'So, ""[[foo]]"" will be wrapped as [[foo]].', '""Closely occurring"" will be heuristic based, say within X chars.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+238209," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","(In reply to comment #6)
+> Actually, why not use entities for escaping?  That will eliminate nowikis,
+> make
+> them editable, and display as text.
+> 
+> [[Foo]] ==> [[Foo]]
+> 
+> and the like.  Am I missing something that makes this problematic?
+
+Numeric entities are very hard for users to decipher. While unwanted nowiki tags can simply be removed, fixing up unwanted entity escapes is much more work.
+
+(In reply to comment #7)
+> (In reply to comment #5)
+> > Re language conversion:
+> > How often is nowiki used to suppress language conversion? Could -{ }- or some
+> > other syntax be used instead?
+> 
+> It's more like some side effect...
+
+For us it would be helpful if we could separate those two aspects. If little existing content relies on language conversion being disabled in nowiki, then that might actually be possible.",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNumeric entities are very hard for users to decipher.', 'While unwanted nowiki tags can simply be removed, fixing up unwanted entity escapes is much more work.', '(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nFor us it would be helpful if we could separate those two aspects.', 'If little existing content relies on language conversion being disabled in nowiki, then that might actually be possible.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+238202," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","(In reply to comment #5)
+> Re language conversion:
+> How often is nowiki used to suppress language conversion? Could -{ }- or some
+> other syntax be used instead?
+
+It's more like some side effect...",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\n\nIt's more like some side effect...""]",['OBSERVED BUG BEHAVIOR']
+238198," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Actually, why not use entities for escaping?  That will eliminate nowikis, make them editable, and display as text.
+
+[[Foo]] ==> [[Foo]]
+
+and the like.  Am I missing something that makes this problematic?",task_subcomment,"['Actually, why not use entities for escaping?', 'That will eliminate nowikis, make them editable, and display as text.', '[[Foo]] ==> [[Foo]]\n\nand the like.', 'Am I missing something that makes this problematic?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION']"
+238195," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Maybe we could still use a single wrapper but exclude unsuspicious leading / trailing text from the nowiki block. I agree with Subbu that escaping each run of dangerous characters individually would often result in too much nowiki noise.
+
+Re language conversion:
+How often is nowiki used to suppress language conversion? Could -{ }- or some other syntax be used instead?",task_subcomment,"['Maybe we could still use a single wrapper but exclude unsuspicious leading / trailing text from the nowiki block.', 'I agree with Subbu that escaping each run of dangerous characters individually would often result in too much nowiki noise.', 'Re language conversion:\nHow often is nowiki used to suppress language conversion?', 'Could -{ }- or some other syntax be used instead?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238191," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","It should be noted, that at present VE aggressively grabs normal text on either side of the offending elements as well.  For example, using VE to enter:
+
+- I am the very model of a modern [[Major-General]], I've information vegetable, animal, and mineral, I know the kings of England, and I quote the fights historical
+
+Becomes
+
+- I am the very model of a modern [[Major-General]], I've information vegetable, animal, and mineral, I know the kings of England, and I quote the fights historical
+
+Even though the plain text at either end of the wikilink could reasonably be ignored without increasing the number of nowikis.  Since VE can not currently handle nowiki elements, that also means that the entire sentence becomes uneditable in VE after saving.",task_subcomment,"['It should be noted, that at present VE aggressively grabs normal text on either side of the offending elements as well.', ""For example, using VE to enter:\n\n- I am the very model of a modern [[Major-General]], I've information vegetable, animal, and mineral, I know the kings of England, and I quote the fights historical\n\nBecomes\n\n- I am the very model of a modern [[Major-General]], I've information vegetable, animal, and mineral, I know the kings of England, and I quote the fights historical\n\nEven though the plain text at either end of the wikilink could reasonably be ignored without increasing the number of nowikis."", 'Since VE can not currently handle nowiki elements, that also means that the entire sentence becomes uneditable in VE after saving.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238187," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Actually, another way is to use the existing algorithm to detect contexts that would have been wrapped in .. and apply nowiki-escaping to all possible wikitext chars in there (which is safe, but excessive).  This will not complicate the algorithm anymore, but will also introduce more nowiki tags than strictly necessary.",task_subcomment,"['Actually, another way is to use the existing algorithm to detect contexts that would have been wrapped in .. and apply nowiki-escaping to all possible wikitext chars in there (which is safe, but excessive).', 'This will not complicate the algorithm anymore, but will also introduce more nowiki tags than strictly necessary.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+238182," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","I forgot whether I pointed this out or not: applying  on ""normal"" text disabled language conversion on it too; we may want to  wikitext meta characters only.",task_subcomment,"['I forgot whether I pointed this out or not: applying  on ""normal"" text disabled language conversion on it too; we may want to  wikitext meta characters only.']",['SOLUTION DISCUSSION']
+238177," tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)","Let us discuss more on irc monday, but the general problem of escaping minimal contexts can complicate the algorithm.  That said, we could implement some special cases maybe. 
+
+Also, a lot of nowiki-tags (as in this example) looks ugly to me (personally), and could potentially induce greater grumbling among editors.  So, my suggestion is to minimize incidences of nowiki contexts via VE (however you do it) first, and then implement a version of this proposal in Parsoid after that.
+
+Yet another (not fully thought out) alternative is to convert wikitext chars into HTML entities which eliminates nowikis altogether.  We currently use this entity-based solution when we have to escape pipes in url/ext. links in template arg contexts and can just use that more broadly.",task_subcomment,"['Let us discuss more on irc monday, but the general problem of escaping minimal contexts can complicate the algorithm.', 'That said, we could implement some special cases maybe.', 'Also, a lot of nowiki-tags (as in this example) looks ugly to me (personally), and could potentially induce greater grumbling among editors.', 'So, my suggestion is to minimize incidences of nowiki contexts via VE (however you do it) first, and then implement a version of this proposal in Parsoid after that.', 'Yet another (not fully thought out) alternative is to convert wikitext chars into HTML entities which eliminates nowikis altogether.', 'We currently use this entity-based solution when we have to escape pipes in url/ext.', 'links in template arg contexts and can just use that more broadly.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52836,Loading a page which requires many fonts causes high CPU load,"see report here:
+[[en:Wikipedia:Village_pump_(technical)#Heavy_Javascript_load_after_loading_some_articles.]] (bottom of [[en:WP:VPT]] on July 5 2013. if you don't find it there, look in the archives).
+
+Initial debugging of the issue points to the function injectCSS().
+as it turns out, ULS calls injectCSS() once for each required font, which, on some pages (methinks pages with many interwiki links, mainly) can be dozens of times.
+
+apparently, on some browsers injectCSS() can be expensive (maybe the browser re-renders the whole page, in light of the new stylesheet information?) and calling it dozens of times causes high CPU load.
+
+clearly, the right thing to do here is to collect all the different CSS bits and pieces you want to inject, and call injectCSS() exactly once.
+
+this piece of code demonstrate what some people already know: injecting stuff can be habit forming, and can be bad for your health, so you absolutely want to minimize it.
+
+
+(btw: the function itself is somewhat disgusting. how is it better than
+
+function injectCSS( css ) {
+	$( '
+
+
+
+
+
+
+
+
+
+
+	
+
+		
+		[a metric fuckton of HTML]
+
+		
+		
+		
+		
+		
+				
+	
+
+real	10m1.110s
+user	0m0.018s
+sys	0m0.028s",task_subcomment,"[""For the record, it doesn't seem to be completely down, just really slow to respond."", 'When I tried again, I got:\n\n$ time curl URL\n \n\n\t\n\t\n\t\t\n\t\t\n   \t\tWikimedia\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\n\n\n\n\n\n\n\n\n\n\n\t\n\n\t\t\n\t\t[a metric fuckton of HTML]\n\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\t\t\n\t\n\nreal\t10m1.110s\nuser\t0m0.018s\nsys\t0m0.028s']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', '1 or or or or or or or or or or or or and or and or or or or or or or or or or or or, or and or or or or or or or or or or or or or or or or and or and or and or and or and or and or the or or or or or or or or or or or or or or or or or or or or or or or or or or or or or or or or and or or or or and or and or or or or or and or and or or or or and or or or or and or and or or and and and and and and and and and and or or and or or or or or or or or or or or or or or or or or or, or, or, or, or, or, or, or and or or, or, or, or, or, and, or, or, and, or, or, or, or, or, or and or and or and or and or and or and or, or, or or, or, or, or and or, or, and or the or, or and or and or and and or and or and and and and and and and and and and and or and or and']"
+242552,git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"It's happening again. :-(
+
+$ time curl https://git.wikimedia.org
+
+
+502 Proxy Error
+
+
    Proxy Error
    
+
    The proxy server received an invalid
+response from an upstream server.
    
+The proxy server could not handle the request GET /.
    
+Reason: Error reading from remote server
    
+
+
+real	12m1.110s
+user	0m0.015s
+sys	0m0.021s",task_subcomment,"[""It's happening again."", ':-(\n\n$ time curl URL\n\n\n502 Proxy Error\n\n
    Proxy Error
    \n
    The proxy server received an invalid\nresponse from an upstream server.
    \nThe proxy server could not handle the request GET /.
    \nReason: Error reading from remote server
    \n\n\nreal\t12m1.110s\nuser\t0m0.015s\nsys\t0m0.021s']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242547,git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"Restarted the service. Two things:
+
+A) I'm doing some logging this time so I can figure out why it's crashing
+B) I'm going to finish puppetizing and packaging this starting tomorrow so it'll take care of this better
+
+Hopefully we can find an easy fix for this, but (B) is necessary anyway.",task_subcomment,"['Restarted the service.', ""Two things:\n\nA) I'm doing some logging this time so I can figure out why it's crashing\nB) I'm going to finish puppetizing and packaging this starting tomorrow so it'll take care of this better\n\nHopefully we can find an easy fix for this, but (B) is necessary anyway.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+242542,git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,git.wikimedia.org being down is highly disruptive to support work in #mediawiki.,task_subcomment,['git.wikimedia.org being down is highly disruptive to support work in #mediawiki.'],['OBSERVED BUG BEHAVIOR']
+242538,git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"This is probably a duplicate of bug 51656, but I'll just add that bug as a see also to this bug.
+
+Confirming the current issue:
+
+$ curl https://git.wikimedia.org/
+
+
+502 Proxy Error
+
+
    Proxy Error
    
+
    The proxy server received an invalid
+response from an upstream server.
    
+The proxy server could not handle the request GET /.
    
+Reason: Error reading from remote server
    
+",task_subcomment,"[""This is probably a duplicate of bug 51656, but I'll just add that bug as a see also to this bug."", 'Confirming the current issue:\n\n$ curl URL\n\n\n502 Proxy Error\n\n
    Proxy Error
    \n
    The proxy server received an invalid\nresponse from an upstream server.
    \nThe proxy server could not handle the request GET /.
    \nReason: Error reading from remote server
    \n']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53765,VisualEditor: Bypass browser blacklist,"Could we have a way to bypass the browser blacklist. e.g.
+1. a user preference to ignore the blacklist during initialisation, or
+2. ?debug=true bypasses blacklist,
+3. a test-wiki where the blacklist is empty/ignored, or
+4. a simple way to re-run VE init from JS console
+
+This will allow mere mortals to help identify bugs with unsupported browsers.
+
+For option four, we can modify the blacklist, like so:
+
+JS> delete mw.libs.ve.blacklist.opera;
+
+But im not sure what to do after that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55900",task_description,"['VisualEditor: Bypass browser blacklist\n\nCould we have a way to bypass the browser blacklist.', 'e.g.', '1. a user preference to ignore the blacklist during initialisation, or\n2.', '?debug=true bypasses blacklist,\n3. a test-wiki where the blacklist is empty/ignored, or\n4. a simple way to re-run VE init from JS console\n\nThis will allow mere mortals to help identify bugs with unsupported browsers.', 'For option four, we can modify the blacklist, like so:\n\nJS> delete mw.libs.ve.blacklist.opera;\n\nBut im not sure what to do after that.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+242341,VisualEditor: Bypass browser blacklist,"The code for this enhancement request had already been written before the bug rasied, but wasn't deployed at that time.
+https://gerrit.wikimedia.org/r/#/c/74574/
+Changing from INVALID to FIXED, but maybe it is a dup of another bug?",task_subcomment,"[""The code for this enhancement request had already been written before the bug rasied, but wasn't deployed at that time."", 'URL\nChanging from INVALID to FIXED, but maybe it is a dup of another bug?']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+242334,VisualEditor: Bypass browser blacklist,"You can already bypass the blacklist by using ?vewhitelist=1 - sorry, we should document this somewhere!",task_subcomment,"['You can already bypass the blacklist by using ?vewhitelist=1 - sorry, we should document this somewhere!']",['SOLUTION DISCUSSION']
+242328,VisualEditor: Bypass browser blacklist,"For anyone wanting to bypass it on browser with a decent JS debugger, set a breakpoint on the line 'mw.libs.ve = init' in 
+
+https://bits.wikimedia.org/static-1.22wmf10/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js
+
+Then execute
+JS> delete init.blacklist.opera
+
+And resume running the VE scripts.
+
+Im guessing this isnt possible on most mobile browsers, so one of option 1-3 or similar would be useful.",task_subcomment,"[""For anyone wanting to bypass it on browser with a decent JS debugger, set a breakpoint on the line 'mw.libs.ve = init' in \n\nURL\n\nThen execute\nJS> delete init.blacklist.opera\n\nAnd resume running the VE scripts."", 'Im guessing this isnt possible on most mobile browsers, so one of option 1-3 or similar would be useful.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53758,Visual editor: issues with removing leading space pre blocks,"When a page with blocks of pre-formatted text that use the leading space in wikitaxt is edited in Visual Editor there are various issues trying to remove the pre-formatted blocks. https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=565085889 can be used for testing.
+
+* It is not possible to delete a block on the first line of a page
+* When the pre-formatted block follows a mutli-line template, that template is deleted and the contents of the pre-formatted block becomes normal text on the line above where the template as, appended to any text that was already there.
+* When the pre-formatted block follows a normal line of text or a single line template the contents of the block are appended to the end of that line.
+* When the block follows indented text, the contents are appended to the last line of the indented block, even if that is a line that doesn't exist in wikitext (see {T52995})
+* When the block follows an ordered or unordered list, the text is appended to the last line of the last item in the list
+*When the block follows an image, the contents are appended to the image caption. This is probably depends on {T53624} and so I would expect the same behaviour with tables, but I have not tested that.
+*If the block follows another pre-formatted block, the contents gets appended to the end of that block.
+
+In all cases this can be worked around by inserting and then backspacing a new line at the start of the block.
+
+In cases when there is a line of normal text, a blank line or a single line template before the pre-formatted block then pressing delete at the end of that line appends the contents of the block at the cursor position as normal text.
+
+The differing behaviour of single and multi-line templates may be related to {T53708}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Visual editor: issues with removing leading space pre blocks\n\nWhen a page with blocks of pre-formatted text that use the leading space in wikitaxt is edited in Visual Editor there are various issues trying to remove the pre-formatted blocks.', 'URL can be used for testing.', '* It is not possible to delete a block on the first line of a page\n* When the pre-formatted block follows a mutli-line template, that template is deleted and the contents of the pre-formatted block becomes normal text on the line above where the template as, appended to any text that was already there.', '* When the pre-formatted block follows a normal line of text or a single line template the contents of the block are appended to the end of that line.', ""* When the block follows indented text, the contents are appended to the last line of the indented block, even if that is a line that doesn't exist in wikitext (see {T52995})\n* When the block follows an ordered or unordered list, the text is appended to the last line of the last item in the list\n*When the block follows an image, the contents are appended to the image caption."", 'This is probably depends on {T53624} and so I would expect the same behaviour with tables, but I have not tested that.', '*If the block follows another pre-formatted block, the contents gets appended to the end of that block.', 'In all cases this can be worked around by inserting and then backspacing a new line at the start of the block.', 'In cases when there is a line of normal text, a blank line or a single line template before the pre-formatted block then pressing delete at the end of that line appends the contents of the block at the cursor position as normal text.', 'The differing behaviour of single and multi-line templates may be related to {T53708}\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+496758,Visual editor: issues with removing leading space pre blocks,"Most of these workflows now work correctly. A few of them don't, so I've filed them separately as T106905 and T106902.",task_subcomment,"['Most of these workflows now work correctly.', ""A few of them don't, so I've filed them separately as T106905 and T106902.""]","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+455240,Visual editor: issues with removing leading space pre blocks,I also see instances where [[https://it.wikipedia.org/w/index.php?title=Giorgio_Summaripa&diff=72637884&oldid=72353193|a space pre was *added* ]] while inserting an image around a paragraph. Or maybe that's T68628?,task_subcomment,"['I also see instances where [[URL space pre was *added* ]] while inserting an image around a paragraph.', ""Or maybe that's T68628?""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+421326,Visual editor: issues with removing leading space pre blocks,">>! In T53758#1088912, @Aklapper wrote:
+>> * When the pre-formatted block follows a mutli-line template, that template is deleted and the contents of the pre-formatted block becomes normal text on the line above where the template as, appended to any text that was already there.
+> 
+> When exactly is ""that template deleted""? Already by loading the page in VisualEditor? If so I fail to reproduce...
+
+From memory, what I meant by that was that when you have a template that produces more than one line of text that is immediately followed by a block of pre-formatted text that uses the leading space method (i.e. not 
     tags), removing the leading space also deletes the preceding template and the linebreak between the template and the paragraph above the template. i.e.
+
+Paragraph one.
+Template
+[space]two
+
+becomes
+
+Paragraph one.two
+
+when you try to delete [space]. I don't have time now to test whether this still happens.",task_subcomment,"['QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nFrom memory, what I meant by that was that when you have a template that produces more than one line of text that is immediately followed by a block of pre-formatted text that uses the leading space method (i.e.', 'not 
     tags), removing the leading space also deletes the preceding template and the linebreak between the template and the paragraph above the template.', 'i.e.', 'Paragraph one.', 'Template\n[space]two\n\nbecomes\n\nParagraph one.two\n\nwhen you try to delete [space].', ""I don't have time now to test whether this still happens.""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+420822,Visual editor: issues with removing leading space pre blocks,"> * It is not possible to delete a block on the first line of a page
+
+I managed after removing the text and then putting the cursor in front of the ""Section 1"" heading and pressing Backspace.
+
+> * When the pre-formatted block follows a mutli-line template, that template is deleted and the contents of the pre-formatted block becomes normal text on the line above where the template as, appended to any text that was already there.
+
+When exactly is ""that template deleted""? Already by loading the page in VisualEditor? If so I fail to reproduce...",task_subcomment,"['QUOTE\n\nI managed after removing the text and then putting the cursor in front of the ""Section 1"" heading and pressing Backspace.', 'QUOTE\n\nWhen exactly is ""that template deleted""?', 'Already by loading the page in VisualEditor?', 'If so I fail to reproduce...']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242029,Visual editor: issues with removing leading space pre blocks,In this edit https://en.wikipedia.org/w/index.php?title=Morse_code&diff=571916446&oldid=571809074 the multiple leading spaces of a pre-formatted block have been removed while a totally unrelated line was being edited.  The edit summary gives no indication that this was done deliberately so I am assuming this was the result of a bug in VisEd.,task_subcomment,"['In this edit URL the multiple leading spaces of a pre-formatted block have been removed while a totally unrelated line was being edited.', 'The edit summary gives no indication that this was done deliberately so I am assuming this was the result of a bug in VisEd.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53751,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit","In my volunteer mode, I was removing content that was copied from an external site. I didn't add any content at all, but simply deleted text (and a template) and merged the resultant material into a single paragraph.
+
+VisualEditor flagged this as my adding wikimarkup and gave me the nowiki warning. :)
+
+See http://en.wikipedia.org/wiki/File:Wikimarkup_warning_without_case.png which is confusingly titled, because I missed the ""u"" in ""cause.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit\n\nIn my volunteer mode, I was removing content that was copied from an external site.', ""I didn't add any content at all, but simply deleted text (and a template) and merged the resultant material into a single paragraph."", 'VisualEditor flagged this as my adding wikimarkup and gave me the nowiki warning.', ':)\n\nSee URL which is confusingly titled, because I missed the ""u"" in ""cause.""', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+333246,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit",Verified in betalabs.,task_subcomment,['Verified in betalabs.'],['OBSERVED BUG BEHAVIOR']
+333197,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit","Change 175336 merged by jenkins-bot:
+Replace hacky wikitext warning listener with sequences
+
+[[https://gerrit.wikimedia.org/r/175336]]",task_subcomment,['Change 175336 merged by jenkins-bot:\nReplace hacky wikitext warning listener with sequences\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+333194,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit","Change 175336 had a related patch set uploaded (by Catrope):
+Replace hacky wikitext warning listener with sequences
+
+[[https://gerrit.wikimedia.org/r/175336]]
+
+#patch-for-review",task_subcomment,['Change 175336 had a related patch set uploaded (by Catrope):\nReplace hacky wikitext warning listener with sequences\n\n[[GERRIT_URL]]\n\n#patch-for-review'],['GERRIT_URL']
+241723,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit",Fixing this would cause a serious performance penalty for minor improvement in the user experience. WONTFIXing.,task_subcomment,"['Fixing this would cause a serious performance penalty for minor improvement in the user experience.', 'WONTFIXing.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+241718,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit","I get this error by adding anything to the second paragraph (beginning ""VisualEditor"" at https://office.wikimedia.org/w/index.php?title=User:Mdennis/sandbox&oldid=105896  There are preëxistng (intentional) nowiki's in this paragraph, which may the cause.",task_subcomment,"['I get this error by adding anything to the second paragraph (beginning ""VisualEditor"" at URL  There are preëxistng (intentional) nowiki\'s in this paragraph, which may the cause.']",['OBSERVED BUG BEHAVIOR']
+241712,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit","From bug 53661:
+The Wikitext warning is triggered in some circumstances without the user having
+entered Wikitext. The one cause I can reliably reproduce is where there is
+nowikied markup on the page from a previous edit.
+
+To reproduce:
+1. Load
+https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=571089410&veaction=edit
+2. Click anywhere on the last line of Section number two (the line that
+contains ""[[Manhatan]]"" and an ISBN, both of which are enclosed in nowiki
+tags). 
+
+It seems that the warning is triggered by the existence of wikitext markup in
+the VE editing surface, rather than by its addition.",task_subcomment,"['From bug 53661:\nThe Wikitext warning is triggered in some circumstances without the user having\nentered Wikitext.', 'The one cause I can reliably reproduce is where there is\nnowikied markup on the page from a previous edit.', 'To reproduce:\n1.', 'Load\nURL\n2.', 'Click anywhere on the last line of Section number two (the line that\ncontains ""[[Manhatan]]"" and an ISBN, both of which are enclosed in nowiki\ntags).', 'It seems that the warning is triggered by the existence of wikitext markup in\nthe VE editing surface, rather than by its addition.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241707,"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit",*** Bug 53661 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53661 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53744,Default whitespace for headings should include spaces before/after ==,"As a follow-up to bug 49428 and bug 50771, default whitespace for headings should includespaces before/after ==.
+
+Or in other words: prefer ""== Heading =="" to ""==Heading=="".
+
+(While this might seem minor, the first style was enforced at pl.wp with automated tools since ever and editors gets annoyed when VE changes it. Reported at https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#sprz.C4.85tanie_kodu )
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['Default whitespace for headings should include spaces before/after ==\n\nAs a follow-up to bug 49428 and bug 50771, default whitespace for headings should includespaces before/after ==.', 'Or in other words: prefer ""== Heading =="" to ""==Heading=="".', '(While this might seem minor, the first style was enforced at pl.wp with automated tools since ever and editors gets annoyed when VE changes it.', 'Reported at URL )\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+241360,Default whitespace for headings should include spaces before/after ==,"Change 101318 merged by GWicke:
+(Bug 51744) Add space around = chars in new headings
+
+https://gerrit.wikimedia.org/r/101318",task_subcomment,['Change 101318 merged by GWicke:\n(Bug 51744) Add space around = chars in new headings\n\nGERRIT_URL'],['BUG REPRODUCTION']
+241355,Default whitespace for headings should include spaces before/after ==,"Change 101275 merged by GWicke:
+Merge ""(Bug 51744) Add space around = chars in new headings""
+
+https://gerrit.wikimedia.org/r/101275",task_subcomment,"['Change 101275 merged by GWicke:\nMerge ""(Bug 51744) Add space around = chars in new headings""\n\nGERRIT_URL']",['ACTION ON ISSUE']
+241349,Default whitespace for headings should include spaces before/after ==,"Change 101318 had a related patch set uploaded by GWicke:
+(Bug 51744) Add space around = chars in new headings
+
+https://gerrit.wikimedia.org/r/101318",task_subcomment,['Change 101318 had a related patch set uploaded by GWicke:\n(Bug 51744) Add space around = chars in new headings\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241343,Default whitespace for headings should include spaces before/after ==,"Change 101275 had a related patch set uploaded by GWicke:
+Merge ""(Bug 51744) Add space around = chars in new headings""
+
+https://gerrit.wikimedia.org/r/101275",task_subcomment,"['Change 101275 had a related patch set uploaded by GWicke:\nMerge ""(Bug 51744) Add space around = chars in new headings""\n\nGERRIT_URL']",['ACTION ON ISSUE']
+241337,Default whitespace for headings should include spaces before/after ==,Yes. Will be deployed today. Closing this bug now.,task_subcomment,"['Yes.', 'Will be deployed today.', 'Closing this bug now.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'ACTION ON ISSUE']"
+241331,Default whitespace for headings should include spaces before/after ==,I assume this is fixed now? Thank you!,task_subcomment,"['I assume this is fixed now?', 'Thank you!']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+241328,Default whitespace for headings should include spaces before/after ==,"Change 96790 merged by jenkins-bot:
+(Bug 51744) Add space around = chars in new headings
+
+https://gerrit.wikimedia.org/r/96790",task_subcomment,['Change 96790 merged by jenkins-bot:\n(Bug 51744) Add space around = chars in new headings\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241326,Default whitespace for headings should include spaces before/after ==,"Change 96790 had a related patch set uploaded by Subramanya Sastry:
+(Bug 51744) Add space around = chars in new headings
+
+https://gerrit.wikimedia.org/r/96790",task_subcomment,['Change 96790 had a related patch set uploaded by Subramanya Sastry:\n(Bug 51744) Add space around = chars in new headings\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241322,Default whitespace for headings should include spaces before/after ==,"(In reply to comment #5)
+> I assume these
+> extra spaces will not be an issue on enwp and doesn't violate any style
+> guidelines there?
+
+No, per [[MOS:HEAD]], ""Spaces between the equal signs and the heading text are optional, and will not affect the way the heading is displayed"". It doesn't mention anything about them being uncool, and most of the wikis I frequent use them for readability.",task_subcomment,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\n\nNo, per [[MOS:HEAD]], ""Spaces between the equal signs and the heading text are optional, and will not affect the way the heading is displayed"".', ""It doesn't mention anything about them being uncool, and most of the wikis I frequent use them for readability.""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+241317,Default whitespace for headings should include spaces before/after ==,"Okay, I started to tackle this. The basic fix is quite simple, but it introduces a ton of noisy diffs in our parser tests and it will likely introduce a lot of noisy diffs in roundtrip testing as well. We could fix our testing infrastructure to ignore them, but a better solution is to leave existing headings untouched.
+
+I can instead add this rule on new headings and leave old headings untouched.
+
+But, looking at pages on enwp, I see (by clicking around on a about 10 ""random"" pages) that most headings don't use spaces after/before ""=="". I assume these extra spaces will not be an issue on enwp and doesn't violate any style guidelines there?",task_subcomment,"['Okay, I started to tackle this.', 'The basic fix is quite simple, but it introduces a ton of noisy diffs in our parser tests and it will likely introduce a lot of noisy diffs in roundtrip testing as well.', 'We could fix our testing infrastructure to ignore them, but a better solution is to leave existing headings untouched.', 'I can instead add this rule on new headings and leave old headings untouched.', 'But, looking at pages on enwp, I see (by clicking around on a about 10 ""random"" pages) that most headings don\'t use spaces after/before ""=="".', ""I assume these extra spaces will not be an issue on enwp and doesn't violate any style guidelines there?""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+241311,Default whitespace for headings should include spaces before/after ==,"The French Wikipedia would be interested in this change as well, since they use a lot of ""extra"" spaces, and the headers are no exception.",task_subcomment,"['The French Wikipedia would be interested in this change as well, since they use a lot of ""extra"" spaces, and the headers are no exception.']",['SOLUTION DISCUSSION']
+241306,Default whitespace for headings should include spaces before/after ==,"(In reply to comment #2)
+> (In reply to comment #1)
+> > It would be very helpful if you can provide a list of any other default
+> > whitespace rules for other wikitext elements.  It is simpler to implement
+> > this
+> > in one shot rather than piecemeal.
+> 
+> Sorry, I post these when I notice Parsoid is doing things not in my way :)
+
+Thats okay.  I was not complaining, just making a request. :).  
+
+You can test existing Parsoid behavior @ http://parsoid.wmflabs.org/_html/ and report what needs fixing.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThats okay.', 'I was not complaining, just making a request.', ':).', 'You can test existing Parsoid behavior @ URL and report what needs fixing.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+241302,Default whitespace for headings should include spaces before/after ==,"(In reply to comment #1)
+> It would be very helpful if you can provide a list of any other default
+> whitespace rules for other wikitext elements.  It is simpler to implement
+> this
+> in one shot rather than piecemeal.
+
+Sorry, I post these when I notice Parsoid is doing things not in my way :)
+
+
+> Right now, we cannot implement different rules for different wikipedias, but,
+> if necessary, something that we could consider at a later point.  So, can you
+> also include some information, if you have, about whether the style rules are
+> universal or specific to pl.wp?
+
+Yeah, of course. No idea if any other wikis use any similar cleanup tools as pl.wp, but in general more whitespace is more readable than less (wikitext is just like code in this regard :) ).
+
+The tools pl.wp uses is [[pl:MediaWiki:Gadget-sk.js]], but be aware that it also includes some non-code cleanup and some pl.wp-specific rules for template replacements etc.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nSorry, I post these when I notice Parsoid is doing things not in my way :)\n\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah, of course.', 'No idea if any other wikis use any similar cleanup tools as pl.wp, but in general more whitespace is more readable than less (wikitext is just like code in this regard :) ).', 'The tools pl.wp uses is [[pl:MediaWiki:Gadget-sk.js]], but be aware that it also includes some non-code cleanup and some pl.wp-specific rules for template replacements etc.']","['MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+241296,Default whitespace for headings should include spaces before/after ==,"It would be very helpful if you can provide a list of any other default whitespace rules for other wikitext elements.  It is simpler to implement this in one shot rather than piecemeal.
+
+Right now, we cannot implement different rules for different wikipedias, but, if necessary, something that we could consider at a later point.  So, can you also include some information, if you have, about whether the style rules are universal or specific to pl.wp?",task_subcomment,"['It would be very helpful if you can provide a list of any other default whitespace rules for other wikitext elements.', 'It is simpler to implement this in one shot rather than piecemeal.', 'Right now, we cannot implement different rules for different wikipedias, but, if necessary, something that we could consider at a later point.', 'So, can you also include some information, if you have, about whether the style rules are universal or specific to pl.wp?']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+53725,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed","**Author:** `lunarjam.mcgahan`
+
+**Description:**
+Wikipedia VE bug Reference with no parameter tags not editable in Chrome on Win7
+
+See attached Word document Wikipedia VE bug Reference with no parameter tags not editable in Chrome on Win7
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11354}",task_description,"['VisualEditor: Rich content copied from sub-documents (image captions, references, etc.)', 'down-cast to plain text when the sub-document is closed\n\n**Author:** CODE\n\n**Description:**\nWikipedia VE bug Reference with no parameter tags not editable in Chrome on Win7\n\nSee attached Word document Wikipedia VE bug Reference with no parameter tags not editable in Chrome on Win7\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11354}']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+1133416,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed","Indeed, this seems to no longer be a problem (testing the reproduction steps by @jayvdb). Rich text is correctly pasted.",task_subcomment,"['Indeed, this seems to no longer be a problem (testing the reproduction steps bySCREEN_NAME).', 'Rich text is correctly pasted.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+580858,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed","Today it seems to work well. (Firefox 42)
+Or I have not undestood.",task_subcomment,"['Today it seems to work well.', '(Firefox 42)\nOr I have not undestood.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240133,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed",*** Bug 65593 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 65593 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240127,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed","This is similar to bug 33105 and bug 41193, but this bug is more specific as it is within the same window.
+
+Steps to reproduce:
+1. Create a reference with '[http:example.com example], publisher, year'
+2. Open dialog for reference created in step 1
+3. Copy the richtext reference and close the dialog
+4. Insert reference anywhere, and paste the clipboard
+
+Results:
+Plain text paste 'example, publisher, year'
+
+Expected results:
+Richtext paste '[http:example.com example], publisher, year'",task_subcomment,"['This is similar to bug 33105 and bug 41193, but this bug is more specific as it is within the same window.', 'Steps to reproduce:\n1.', ""Create a reference with '[http:example.com example], publisher, year'\n2."", 'Open dialog for reference created in step 1\n3.', 'Copy the richtext reference and close the dialog\n4.', ""Insert reference anywhere, and paste the clipboard\n\nResults:\nPlain text paste 'example, publisher, year'\n\nExpected results:\nRichtext paste '[http:example.com example], publisher, year'""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+240123,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed","**lunarjam.mcgahan** wrote:
+
+Further information
+
+See attachment Bug 51725 further explanation
+
+**Attached**: {F11355}",task_subcomment,['**lunarjam.mcgahan** wrote:\n\nFurther information\n\nSee attachment Bug 51725 further explanation\n\n**Attached**: {F11355}'],['OBSERVED BUG BEHAVIOR']
+240118,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed","That ref is only on one page, in English and Thai
+https://www.google.com.au/search?q=""History of the Vardo""+site:wikipedia.org
+
+And I was able to do a basic edit to that ref on Chrome Version 28.0.1500.72 m/Windows 7 Enterprise SP1, in Vector and Monobook
+
+https://en.wikipedia.org/w/index.php?title=Recreational_vehicle&diff=565400866&oldid=565097139
+
+https://en.wikipedia.org/w/index.php?title=Recreational_vehicle&diff=565401640&oldid=565400866
+
+https://th.wikipedia.org/w/index.php?diff=5049776&oldid=4731458
+
+There must be something more specific needed to reproduce this.",task_subcomment,"['That ref is only on one page, in English and Thai\nURL of the Vardo""+site:wikipedia.org\n\nAnd I was able to do a basic edit to that ref on Chrome Version 28.0.1500.72 m/Windows 7 Enterprise SP1, in Vector and Monobook\n\nURL\n\nURL\n\nURL\n\nThere must be something more specific needed to reproduce this.']",['MOTIVATION']
+240112,"VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed","The contents of the attached Word document, to the extent that LibreOffice will display them, seem to be:
+
+The source code is as follows:
+[http://gypsywaggons.co.uk/varhistory.htm ""History of the Vardo (Gypsy Caravan)""], ValleyStream Media, 2009
+
+Was there a screenshot that you meant to include? Could you give us a link to the article? Could you explain the problem in more detail?",task_subcomment,"['The contents of the attached Word document, to the extent that LibreOffice will display them, seem to be:\n\nThe source code is as follows:\n[URL ""History of the Vardo (Gypsy Caravan)""], ValleyStream Media, 2009\n\nWas there a screenshot that you meant to include?', 'Could you give us a link to the article?', 'Could you explain the problem in more detail?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53698,Parsoid: Output MathJax rendering for Math tags instead of images,"When MathJax is enabled we should render a  containing TeX, instead of an image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Parsoid: Output MathJax rendering for Math tags instead of images\n\nWhen MathJax is enabled we should render a  containing TeX, instead of an image.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+529358,Parsoid: Output MathJax rendering for Math tags instead of images,MathJax support is discountinued T99369,task_subcomment,['MathJax support is discountinued T99369'],['OBSERVED BUG BEHAVIOR']
+238639,Parsoid: Output MathJax rendering for Math tags instead of images,Mathjax is interesting for ZIM files and Kiwix because this would allow to reduce bandwidth/storage usage. Hope this is still on the Parsoid roadmap.,task_subcomment,"['Mathjax is interesting for ZIM files and Kiwix because this would allow to reduce bandwidth/storage usage.', 'Hope this is still on the Parsoid roadmap.']","['SOLUTION DISCUSSION', 'FUTURE PLAN']"
+238630,Parsoid: Output MathJax rendering for Math tags instead of images,"(In reply to comment #12)
+
+Thanks, Gabriel! That's very helpful.
+
+> I'm also looking forward to learning more about LaTeXML vs. MathJax options.
+> No browser supports Content MathML currently. The question then is if it is
+> still useful to produce it for search while always rendering via Presentation
+> MathML and/or server-generated SVG.
+
+That's a good question. Especially, if Content MathML from TeX  can be good enough (with ""random"" authoring instead of firm semantic guidelines).
+
+> Copy&pasting entire formulas should be possible as long as our data-mw
+> attribute on the outer wrapper node is preserved. That has the TeX source,
+> which can be used to re-render the contents from scratch. This will enable
+> copy&pasting of entire sections including formulas.
+
+That would be awesome. Subexpressions seems impossible right now -- but one day, with shadowdom and a lot of great heuristics it might just work...
+
+> Are there popular screen readers that handle math? I agree that MathML is
+> probably better in the longer term, but for current screen readers a speech
+> string could still be a useful fall-back. At least if that would not prevent
+> a plugin like math player from using the MathML instead.
+
+A static speech string is never a bad idea for legacy screen readers. There are only two math accessibility solutions, MathPlayer and ChromeVox. AFAIK a number of screen readers ship MathPlayer but I'm not an expert on screen readers. 
+
+Since ChromeVox is mostly JavaScript (and open source), an obvious idea is to create a MathJax extension based on its technology.
+
+The thing is that accessibility is about more than aural rendering; in particular synchronized highlighting is extremely important for learning and other non-vision disabilities. That can't work with static strings.
+
+> I think nobody is suggesting to generate *only* SVG. 
+
+I'm glad I misunderstood you :)
+
+> I'm not sure about the need for reflow in Wikipedia, as the limits of texvc 
+> seem to have motivated authors to handle this manually in TeX.
+
+I seem to have a very different experience :( Anyway, right now PNGs are the only option on mobile (bug 45816).",task_subcomment,"['(In reply to comment #12)\n\nThanks, Gabriel!', ""That's very helpful."", ""QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's a good question."", 'Especially, if Content MathML from TeX  can be good enough (with ""random"" authoring instead of firm semantic guidelines).', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat would be awesome.', 'Subexpressions seems impossible right now -- but one day, with shadowdom and a lot of great heuristics it might just work...\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nA static speech string is never a bad idea for legacy screen readers.', 'There are only two math accessibility solutions, MathPlayer and ChromeVox.', ""AFAIK a number of screen readers ship MathPlayer but I'm not an expert on screen readers."", 'Since ChromeVox is mostly JavaScript (and open source), an obvious idea is to create a MathJax extension based on its technology.', 'The thing is that accessibility is about more than aural rendering; in particular synchronized highlighting is extremely important for learning and other non-vision disabilities.', ""That can't work with static strings."", ""QUOTE\n\nI'm glad I misunderstood you :)\n\nQUOTE\nQUOTE\n\nI seem to have a very different experience :( Anyway, right now PNGs are the only option on mobile (bug 45816).""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+238621,Parsoid: Output MathJax rendering for Math tags instead of images,"(In reply to comment #11)
+
+Peter, thanks for your input!
+
+> Are you just collecting thoughts on this? Are you thinking about long term or
+> short term? Is the topic now the back end or is it still the front end (as
+> the
+> issue title suggests)? 
+
+In the Parsoid project we are developing a long-term HTML storage format for Wikipedia content. The VisualEditor uses our HTML, but also has the freedom to cut some corners for display in the shorter term. However, our long-term goal is to use Parsoid HTML also for regular page views. This is why we are now thinking about issues like copy&paste from read-only pages into a VisualEditor instance while refining the DOM spec at http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec.
+
+Because of its rich metadata, Parsoid HTML is also useful for researchers and search engines. Ideally we'd also like to expose math in a way that works well for both content analysis / indexing *and* display.
+
+> I'm meeting Martin Schubotz (the author of the arXiv link)
+> over the next few days, so I hope to learn more about his projects (and he's
+> coming up to WMF after that I hear so that's awesome).
+
+I'm also looking forward to learning more about LaTeXML vs. MathJax options. No browser supports Content MathML currently. The question then is if it is still useful to produce it for search while always rendering via Presentation MathML and/or server-generated SVG.
+
+> From a search point of view there doesn't seem to be much difference (but of
+> course a specific search technology might prefer Content, Presentation, or
+> TeX).
+
+That might be, although Martin suggests that Content is better for search in his paper.
+
+> Copy&paste is tricky. Yes, it works in FF, but often OS clipboards do not
+> know
+> how to handle it, apps sanitize it away etc. MathJax offers a context menu to
+> access TeX & MathML source (and in our upcoming release any annotation-xml);
+> cumbersome but it works everywhere. We are considering web components /
+> shadow
+> dom, but given the state of support that's for the future (current
+> implementations have some funky copy&paste behavior).
+
+Copy&pasting entire formulas should be possible as long as our data-mw attribute on the outer wrapper node is preserved. That has the TeX source, which can be used to re-render the contents from scratch. This will enable copy&pasting of entire sections including formulas.
+
+I also get the impression that copy&pasting parts of a formula directly might not be feasible. It works with Presentation MathML in FF, but that would not be useful as we don't have a way to convert that back to TeX. It might make more sense to let users copy the TeX and insert that in a new formula using a widget.
+
+> * generating static speech strings is the lowest form of a11y, especially
+> when
+> you could use MathJax which math accessibility tools support.
+
+Are there popular screen readers that handle math? I agree that MathML is probably better in the longer term, but for current screen readers a speech string could still be a useful fall-back. At least if that would not prevent a plugin like math player from using the MathML instead.
+
+> * generating static images of any kind will remove all the advantages of
+> reflowable and accessible content.
+
+I think nobody is suggesting to generate *only* SVG. I'm not sure about the need for reflow in Wikipedia, as the limits of texvc seem to have motivated authors to handle this manually in TeX.",task_subcomment,"['(In reply to comment #11)\n\nPeter, thanks for your input!', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIn the Parsoid project we are developing a long-term HTML storage format for Wikipedia content.', 'The VisualEditor uses our HTML, but also has the freedom to cut some corners for display in the shorter term.', 'However, our long-term goal is to use Parsoid HTML also for regular page views.', 'This is why we are now thinking about issues like copy&paste from read-only pages into a VisualEditor instance while refining the DOM spec at URL\n\nBecause of its rich metadata, Parsoid HTML is also useful for researchers and search engines.', ""Ideally we'd also like to expose math in a way that works well for both content analysis / indexing *and* display."", ""QUOTE\nQUOTE\nQUOTE\n\nI'm also looking forward to learning more about LaTeXML vs. MathJax options."", 'No browser supports Content MathML currently.', 'The question then is if it is still useful to produce it for search while always rendering via Presentation MathML and/or server-generated SVG.', 'QUOTE\nQUOTE\nQUOTE\n\nThat might be, although Martin suggests that Content is better for search in his paper.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nCopy&pasting entire formulas should be possible as long as our data-mw attribute on the outer wrapper node is preserved.', 'That has the TeX source, which can be used to re-render the contents from scratch.', 'This will enable copy&pasting of entire sections including formulas.', 'I also get the impression that copy&pasting parts of a formula directly might not be feasible.', ""It works with Presentation MathML in FF, but that would not be useful as we don't have a way to convert that back to TeX."", 'It might make more sense to let users copy the TeX and insert that in a new formula using a widget.', 'QUOTE\nQUOTE\nQUOTE\n\nAre there popular screen readers that handle math?', 'I agree that MathML is probably better in the longer term, but for current screen readers a speech string could still be a useful fall-back.', 'At least if that would not prevent a plugin like math player from using the MathML instead.', 'QUOTE\nQUOTE\n\nI think nobody is suggesting to generate *only* SVG.', ""I'm not sure about the need for reflow in Wikipedia, as the limits of texvc seem to have motivated authors to handle this manually in TeX.""]","['ACTION ON ISSUE', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+238615,Parsoid: Output MathJax rendering for Math tags instead of images,"Arg -- I had responded twice, twice it was lost... Trying again.
+
+===
+
+On Sept 4 (after the IRC chat log) I tried to post:
+
+Obviously, I'd love to see MathML + MathJax on Wikipedia. That would be a huge step forward for math on the web, accessibility, and education. 
+
+But on the wikitech-I thread I started a while ago, there was a bit of uneasiness when it comes to MathJax performance, especially on mobile. I got the feeling that fallback images will be required for a while. Perhaps SVG might be better though and MathJax could help there, too. 
+
+MathJax is modular on input, internal and output which is sometimes confusing in discussions; so yes we have an HTML/CSS output and an SVG output. At the same time, the texlive+texvc backend is a bit horrible. Personally, I think LateXML is a great tool for converting full LaTeX documents but I worry that you'll need another texvc to limit it -- it's too powerful. MathJax might just fit better because of its restricted syntax (and is extensible through javascript). Obviously, I'm terribly biased. For the record, LaTeXML is miles better than texvc. I'm meeting Martin Schubotz (the author of the arXiv link) over the next few days, so I hope to learn more about his projects (and he's coming up to WMF after that I hear so that's awesome).
+
+Copy&paste is tricky. Yes, it works in FF, but often OS clipboards do not know how to handle it, apps sanitize it away etc. MathJax offers a context menu to access TeX & MathML source (and in our upcoming release any annotation-xml); cumbersome but it works everywhere. We are considering web components / shadow dom, but given the state of support that's for the future (current implementations have some funky copy&paste behavior).
+
+I did get the strong impression on wikitech-I that wiktext should keep TeX as its internal format, so I'm wondering what you have in mind for pasting MathML. MathML isn't semantically rich enough to produce human readable TeX.
+
+Regarding Content MathML, that's a topic of debate. I'm not an expert on Content MathML but I've heard relatively negative things about it from a semantic point of view. A case in point is that accessibility tools don't do better on Content MathML than on Presentation MathML -- they build their own semantic structures on top of it anyway. In any case, you don't see a lot ContentMathML in the wild since no one can render it.
+
+From a search point of view there doesn't seem to be much difference (but of course a specific search technology might prefer Content, Presentation, or TeX).
+
+It's more important to produce high quality Presentation MathML instead of low quality Content MathML. MathML today is a bit like HTML 1 -- we have the language, some basic rendering, that's it. MathML has missed out on 20 years of web development (although it's the de-facto standard in publishing and technical writing workflows). MathML on Wikipedia would be important to push things forward but small steps in what's currently possible would be better.
+
+
+====
+
+Yesterday I tried to post:
+
+cc'ing Fred and Moritz who have been actively working on the math extension recently.
+
+@Gabriel I'm a bit confused by your last two messages. [[well, less so after seeing that mine didn't get through]] 
+
+Are you just collecting thoughts on this? Are you thinking about long term or short term? Is the topic now the back end or is it still the front end (as the issue title suggests)? 
+
+Anyway, here a few more thoughts, trying to provide some outside input.
+
+* Content MathML won't help on the front end -- you need Presentation MathML on the front end and use polyfills where necessary. MathJax works on all current browsers and while older machines and older Android devices may still see performance issues, those will continue to improve. Replacing images (PNG or SVG) on the fly is a progressive enhancement on all systems.
+* the prototype that Gerardo mentioned combines MathJax and ChromeVox, so you'll run into the same problem for MathML support.
+* generating static speech strings is the lowest form of a11y, especially when you could use MathJax which math accessibility tools support.
+* generating static images of any kind will remove all the advantages of reflowable and accessible content.
+* the math extension does not yet use LaTeXML but Fred and Martin are working on that.
+
+I can't help but point out that there are also a number of serious issues with WIkipedia's math that are more important than ContentMathML. For example, there's no display math mode which is an incredible shortcoming. There's also poor unicode support and poor RTL support. None of this will improve by switching to Content MathML -- garbage in, garbage out would be the result.",task_subcomment,"['Arg -- I had responded twice, twice it was lost...', 'Trying again.', ""===\n\nOn Sept 4 (after the IRC chat log) I tried to post:\n\nObviously, I'd love to see MathML + MathJax on Wikipedia."", 'That would be a huge step forward for math on the web, accessibility, and education.', 'But on the wikitech-I thread I started a while ago, there was a bit of uneasiness when it comes to MathJax performance, especially on mobile.', 'I got the feeling that fallback images will be required for a while.', 'Perhaps SVG might be better though and MathJax could help there, too.', 'MathJax is modular on input, internal and output which is sometimes confusing in discussions; so yes we have an HTML/CSS output and an SVG output.', 'At the same time, the texlive+texvc backend is a bit horrible.', ""Personally, I think LateXML is a great tool for converting full LaTeX documents but I worry that you'll need another texvc to limit it -- it's too powerful."", 'MathJax might just fit better because of its restricted syntax (and is extensible through javascript).', ""Obviously, I'm terribly biased."", 'For the record, LaTeXML is miles better than texvc.', ""I'm meeting Martin Schubotz (the author of the arXiv link) over the next few days, so I hope to learn more about his projects (and he's coming up to WMF after that I hear so that's awesome)."", 'Copy&paste is tricky.', 'Yes, it works in FF, but often OS clipboards do not know how to handle it, apps sanitize it away etc.', 'MathJax offers a context menu to access TeX & MathML source (and in our upcoming release any annotation-xml); cumbersome but it works everywhere.', ""We are considering web components / shadow dom, but given the state of support that's for the future (current implementations have some funky copy&paste behavior)."", ""I did get the strong impression on wikitech-I that wiktext should keep TeX as its internal format, so I'm wondering what you have in mind for pasting MathML."", ""MathML isn't semantically rich enough to produce human readable TeX."", ""Regarding Content MathML, that's a topic of debate."", ""I'm not an expert on Content MathML but I've heard relatively negative things about it from a semantic point of view."", ""A case in point is that accessibility tools don't do better on Content MathML than on Presentation MathML -- they build their own semantic structures on top of it anyway."", ""In any case, you don't see a lot ContentMathML in the wild since no one can render it."", ""From a search point of view there doesn't seem to be much difference (but of course a specific search technology might prefer Content, Presentation, or TeX)."", ""It's more important to produce high quality Presentation MathML instead of low quality Content MathML."", ""MathML today is a bit like HTML 1 -- we have the language, some basic rendering, that's it."", ""MathML has missed out on 20 years of web development (although it's the de-facto standard in publishing and technical writing workflows)."", ""MathML on Wikipedia would be important to push things forward but small steps in what's currently possible would be better."", ""====\n\nYesterday I tried to post:\n\ncc'ing Fred and Moritz who have been actively working on the math extension recently."", ""SCREEN_NAME I'm a bit confused by your last two messages."", ""[[well, less so after seeing that mine didn't get through]] \n\nAre you just collecting thoughts on this?"", 'Are you thinking about long term or short term?', 'Is the topic now the back end or is it still the front end (as the issue title suggests)?', 'Anyway, here a few more thoughts, trying to provide some outside input.', ""* Content MathML won't help on the front end -- you need Presentation MathML on the front end and use polyfills where necessary."", 'MathJax works on all current browsers and while older machines and older Android devices may still see performance issues, those will continue to improve.', 'Replacing images (PNG or SVG) on the fly is a progressive enhancement on all systems.', ""* the prototype that Gerardo mentioned combines MathJax and ChromeVox, so you'll run into the same problem for MathML support."", '* generating static speech strings is the lowest form of a11y, especially when you could use MathJax which math accessibility tools support.', '* generating static images of any kind will remove all the advantages of reflowable and accessible content.', '* the math extension does not yet use LaTeXML but Fred and Martin are working on that.', ""I can't help but point out that there are also a number of serious issues with WIkipedia's math that are more important than ContentMathML."", ""For example, there's no display math mode which is an incredible shortcoming."", ""There's also poor unicode support and poor RTL support."", 'None of this will improve by switching to Content MathML -- garbage in, garbage out would be the result.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOCIAL CONVERSATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOCIAL CONVERSATION', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238609,Parsoid: Output MathJax rendering for Math tags instead of images,"MathJax only works with Presentation MathML: 
+http://www.mathjax.org/resources/faqs/#problem-content
+
+It also accepts only Presentation MathML as input. 
+
+We might actually be better off using LaTeXML (https://www.mediawiki.org/wiki/Extension:Math#LaTeXML) to generate Content MathML. LaTeXML provides a web service that we could probably use directly. SVG can be generated with dvisvg from the TeX source. Afaik this is already used in the math extension.",task_subcomment,"['MathJax only works with Presentation MathML: \nURL\n\nIt also accepts only Presentation MathML as input.', 'We might actually be better off using LaTeXML (URL to generate Content MathML.', 'LaTeXML provides a web service that we could probably use directly.', 'SVG can be generated with dvisvg from the TeX source.', 'Afaik this is already used in the math extension.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238603,Parsoid: Output MathJax rendering for Math tags instead of images,"Just had a meeting with Gerardo Capiel in which we also talked about math. He was involved in a node / MathJax prototype that renders to SVG plus a textual description of the formula suitable for screen readers. It might be possible to use that to avoid the need for client-side rendering altogether:
+
+* Content MathML as primary rendering for indexing and good rendering in Firefox
+* Server-generated SVG fallback for fast rendering on other browsers
+* Textual description for screen readers
+* tex in data-mw for editing
+
+The fall-back selection needs to be worked out, and might depend on JS. Compared to client-side rendering from TeX with MathJax this should be pretty fast. Ideally the DOM will not be modified, so that copy&pasting from a read-only page into an editor preserves all information.",task_subcomment,"['Just had a meeting with Gerardo Capiel in which we also talked about math.', 'He was involved in a node / MathJax prototype that renders to SVG plus a textual description of the formula suitable for screen readers.', 'It might be possible to use that to avoid the need for client-side rendering altogether:\n\n* Content MathML as primary rendering for indexing and good rendering in Firefox\n* Server-generated SVG fallback for fast rendering on other browsers\n* Textual description for screen readers\n* tex in data-mw for editing\n\nThe fall-back selection needs to be worked out, and might depend on JS.', 'Compared to client-side rendering from TeX with MathJax this should be pretty fast.', 'Ideally the DOM will not be modified, so that copy&pasting from a read-only page into an editor preserves all information.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR']"
+238594,Parsoid: Output MathJax rendering for Math tags instead of images,"Very relevant: http://arxiv.org/abs/1304.5475
+
+How does the MathML generated by MathJax compare to the 'content MathML' generated by LaTeXML? Is it purely presentational MathML?",task_subcomment,"[""Very relevant: URL\n\nHow does the MathML generated by MathJax compare to the 'content MathML' generated by LaTeXML?"", 'Is it purely presentational MathML?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+238588,Parsoid: Output MathJax rendering for Math tags instead of images,"We currently render as PNG with the tex available in an attribute. It would be nicer both for semantic information / indexing purposes and copy / pasting to render as MathML instead. MathJax could be used server-side to generate the MathML from tex, and client-side as a polyfill to provide HTML+CSS (or image?) rendering for browsers that don't support MathML well.
+
+Copy / pasting native MathML seemed to work quite well the last time I tried it in Firefox and vanilla contenteditable. MathJax-inserted HTML+CSS will likely not do so well unless we preserve the MathML and especially the tex in the data-mw attribute. At least entire formulas could be copy/pastable that way though.",task_subcomment,"['We currently render as PNG with the tex available in an attribute.', 'It would be nicer both for semantic information / indexing purposes and copy / pasting to render as MathML instead.', 'MathJax could be used server-side to generate the MathML from tex, and client-side as a polyfill to provide HTML+CSS (or image?)', ""rendering for browsers that don't support MathML well."", 'Copy / pasting native MathML seemed to work quite well the last time I tried it in Firefox and vanilla contenteditable.', 'MathJax-inserted HTML+CSS will likely not do so well unless we preserve the MathML and especially the tex in the data-mw attribute.', 'At least entire formulas could be copy/pastable that way though.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238581,Parsoid: Output MathJax rendering for Math tags instead of images,"Thanks for pointing me to this thread, Gabriel. 
+
+Let me add https://bugzilla.wikimedia.org/show_bug.cgi?id=48036. 
+
+If there's PNG+TeX in the page, then MathJax can replace the image on the fly. That will produce a nice user experience as the math will always be visible and only improve once MathJax is done (cf this Chrome extension https://chrome.google.com/webstore/detail/wikipedia-with-mathjax/fhomhkjcommffnlajeemenejemmegcmi).
+
+For the OP, I should point out that MathJax preprocessing will remove the spans and insert its script tags, so you might want to insere those directly see http://docs.mathjax.org/en/latest/model.html#how-mathematics-is-stored-in-the-page.",task_subcomment,"['Thanks for pointing me to this thread, Gabriel.', ""Let me add URL \n\nIf there's PNG+TeX in the page, then MathJax can replace the image on the fly."", 'That will produce a nice user experience as the math will always be visible and only improve once MathJax is done (cf this Chrome extension URL\n\nFor the OP, I should point out that MathJax preprocessing will remove the spans and insert its script tags, so you might want to insere those directly see URL']","['SOCIAL CONVERSATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+238576,Parsoid: Output MathJax rendering for Math tags instead of images,"From IRC discussion with pkrautzberger it seems that we could actually use MathJax directly to convert tex to MathML without calling the API at all. Some work is still needed though:
+
+[17:03]  do you have a node package?
+[17:03]  ah. no. The problem is that MathJax requires a dom  right now. But we plan to liberate parts.
+[17:03]  we have a dom
+[17:03]  (a lot functionality doesn't make sense outside the DOM).
+[17:04]  domino currently
+[17:04]  but TeX2MathML conversion could be isolated easily (MathML to SVG not as easily). BTW our internal format is MathML.
+[17:04]  it only implements DOM4 in case that makes a difference
+[17:04]  I'm not sure if dom4 would be a problem.
+[17:04]  but we've seen people use dom runners.
+[17:04]  we could also use JSDom for math if that helps
+[17:05]  supports the other levels
+[17:05]  and script tag execution
+[17:05]  well, ideally we could just isolate that from the dom.
+[17:05]  but yes, I know someone who got jsdom to work with MathJax.
+[17:06]  ah, that sounds promising",task_subcomment,"['From IRC discussion with pkrautzberger it seems that we could actually use MathJax directly to convert tex to MathML without calling the API at all.', 'Some work is still needed though:\n\n[17:03]  do you have a node package?', '[17:03]  ah.', 'no.', 'The problem is that MathJax requires a dom  right now.', 'But we plan to liberate parts.', ""[17:03]  we have a dom\n[17:03]  (a lot functionality doesn't make sense outside the DOM)."", '[17:04]  domino currently\n[17:04]  but TeX2MathML conversion could be isolated easily (MathML to SVG not as easily).', 'BTW our internal format is MathML.', ""[17:04]  it only implements DOM4 in case that makes a difference\n[17:04]  I'm not sure if dom4 would be a problem."", ""[17:04]  but we've seen people use dom runners."", '[17:04]  we could also use JSDom for math if that helps\n[17:05]  supports the other levels\n[17:05]  and script tag execution\n[17:05]  well, ideally we could just isolate that from the dom.', '[17:05]  but yes, I know someone who got jsdom to work with MathJax.', '[17:06]  ah, that sounds promising']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+238570,Parsoid: Output MathJax rendering for Math tags instead of images,See bug 52031.,task_subcomment,['See bug 52031.'],['OBSERVED BUG BEHAVIOR']
+238565,Parsoid: Output MathJax rendering for Math tags instead of images,Have we filed a bug against the mw api to support this?,task_subcomment,['Have we filed a bug against the mw api to support this?'],['SOLUTION DISCUSSION']
+238564,Parsoid: Output MathJax rendering for Math tags instead of images,"From IRC discussions:
+
+It appears that supporting this on the Parsoid end would definitely require an update to the mw api so we can pass in options to the extension (something like action=callextensiontag&attributes=...&options=...)
+
+In addition, if the math extension doesn't accept output rendering options (except via config settings), the extension itself will need an update to support this.
+
+Once both are present, Parsoid can emit mathml.",task_subcomment,"[""From IRC discussions:\n\nIt appears that supporting this on the Parsoid end would definitely require an update to the mw api so we can pass in options to the extension (something like action=callextensiontag&attributes=...&options=...)\n\nIn addition, if the math extension doesn't accept output rendering options (except via config settings), the extension itself will need an update to support this."", 'Once both are present, Parsoid can emit mathml.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+238563,Parsoid: Output MathJax rendering for Math tags instead of images,"With VE's JS requirements we can just force everyone to use the MathJax rendering when editing, makes things a lot simpler and both ends, and means we don't need to round-trip to re-render.",task_subcomment,"[""With VE's JS requirements we can just force everyone to use the MathJax rendering when editing, makes things a lot simpler and both ends, and means we don't need to round-trip to re-render.""]",['SOLUTION DISCUSSION']
+53680,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"http://it.wikipedia.org/wiki/Utente:Elitre_%28WMF%29/Sandbox?veaction=edit
+
+This was actually discussed on IRC by Inez, subbu, gwicke on July 3rd, I might provide that part of the log if useful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid.wmflabs.org/it/Utente:Elitre_(WMF)/Sandbox",task_description,"['Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki\n\nURL\n\nThis was actually discussed on IRC by Inez, subbu, gwicke on July 3rd, I might provide that part of the log if useful.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237641,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Change 87272 merged by jenkins-bot:
+Add 'MemoryAlpha' namespace for parser tests.
+
+https://gerrit.wikimedia.org/r/87272",task_subcomment,"[""Change 87272 merged by jenkins-bot:\nAdd 'MemoryAlpha' namespace for parser tests."", 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237636,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Change 87272 had a related patch set uploaded by Cscott:
+Add 'MemoryAlpha' namespace for parser tests.
+
+https://gerrit.wikimedia.org/r/87272",task_subcomment,"[""Change 87272 had a related patch set uploaded by Cscott:\nAdd 'MemoryAlpha' namespace for parser tests."", 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237630,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Change 87203 merged by jenkins-bot:
+ParserTests: allow test of precedence between interwiki links and namespaces
+
+https://gerrit.wikimedia.org/r/87203",task_subcomment,['Change 87203 merged by jenkins-bot:\nParserTests: allow test of precedence between interwiki links and namespaces\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237624,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Change 86872 merged by jenkins-bot:
+Bug 51680: Give preference to namespaces over interwiki prefixes
+
+https://gerrit.wikimedia.org/r/86872",task_subcomment,['Change 86872 merged by jenkins-bot:\nBug 51680: Give preference to namespaces over interwiki prefixes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237620,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Change 87203 had a related patch set uploaded by Cscott:
+ParserTests: allow test of precedence between interwiki links and namespaces
+
+https://gerrit.wikimedia.org/r/87203",task_subcomment,['Change 87203 had a related patch set uploaded by Cscott:\nParserTests: allow test of precedence between interwiki links and namespaces\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+237619,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Change 86872 had a related patch set uploaded by Marcoil:
+Bug 51680: Give preference to namespaces over interwiki prefixes
+
+https://gerrit.wikimedia.org/r/86872",task_subcomment,['Change 86872 had a related patch set uploaded by Marcoil:\nBug 51680: Give preference to namespaces over interwiki prefixes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237617,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"I have a patch for this one, taking it.",task_subcomment,"['I have a patch for this one, taking it.']",['SOLUTION DISCUSSION']
+237614,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Namespace prefixes need to take precedence over interwiki prefixes in Parsoid, as is the case in the PHP parser.",task_subcomment,"['Namespace prefixes need to take precedence over interwiki prefixes in Parsoid, as is the case in the PHP parser.']",['OBSERVED BUG BEHAVIOR']
+237609,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,Can't reproduce on enwp for obvious reasons.,task_subcomment,"[""Can't reproduce on enwp for obvious reasons.""]",['OBSERVED BUG BEHAVIOR']
+237604,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Created attachment 12996
+screenshot of adding a wikipedia: link
+
+**Attached**: {F11284}",task_subcomment,['Created attachment 12996\nscreenshot of adding a wikipedia: link\n\n**Attached**: {F11284}'],['ATTACHMENT']
+237599,Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"This is because Parsoid sees [[Wikipedia:VisualEditor/Cosa_cambia]] as a link to [[VisualEditor/Cosa_cambia]] on interwiki ""Wikipedia"" (i.e., the English Wikipedia). Whoops.",task_subcomment,"['This is because Parsoid sees [[Wikipedia:VisualEditor/Cosa_cambia]] as a link to [[VisualEditor/Cosa_cambia]] on interwiki ""Wikipedia"" (i.e., the English Wikipedia).', 'Whoops.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53677,VisualEditor: Rapidly multiplying pawns after editing near a link in MobileSafari on iPad,"An IP user on the English Wikipedia reports the following slightly alarming bug:
+
+""After I edited text near a link, ""♙♙♙♙♙♙♙"" characters started appearing around once a second, and I couldn't stop them or delete them.""
+
+Based on another bug report left a few minutes later by the same user they were using MobileSafari on iPad 2 with iOS 6.1.3
+
+I can't replicate this in Firefox on a Linux PC and don't have an iPad to test on.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: other
+**Platform**: Tablet PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50465",task_description,"['VisualEditor: Rapidly multiplying pawns after editing near a link in MobileSafari on iPad\n\nAn IP user on the English Wikipedia reports the following slightly alarming bug:\n\n""After I edited text near a link, ""♙♙♙♙♙♙♙"" characters started appearing around once a second, and I couldn\'t stop them or delete them.""', ""Based on another bug report left a few minutes later by the same user they were using MobileSafari on iPad 2 with iOS 6.1.3\n\nI can't replicate this in Firefox on a Linux PC and don't have an iPad to test on."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: other\n**Platform**: Tablet PC\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+475919,VisualEditor: Rapidly multiplying pawns after editing near a link in MobileSafari on iPad,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",task_subcomment,"['Seems to work for me now.', 'Tested on Beta Cluster using iOS Safari 8.0 on an iPad.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237371,VisualEditor: Rapidly multiplying pawns after editing near a link in MobileSafari on iPad,"(In reply to comment #0)
+> An IP user on the English Wikipedia reports the following slightly alarming
+> bug:
+> 
+> ""After I edited text near a link, ""♙♙♙♙♙♙♙"" characters started appearing
+> around
+> once a second, and I couldn't stop them or delete them.""
+> 
+> Based on another bug report left a few minutes later by the same user they
+> were
+> using MobileSafari on iPad 2 with iOS 6.1.3
+> 
+> I can't replicate this in Firefox on a Linux PC and don't have an iPad to
+> test
+> on.
+
+Since you asked,in VE test edit we had encountered it at mr wiki http://mr.wikipedia.org/w/index.php?title=तेकिर्दा_प्रांत&diff=prev&oldid=1189390 When I increased space.I suppose developers already may be taking care of this.
+
+I suppose en wiki maya be needs to track nowikis with better targeted edit filters for space and other mark up aspects.Thats my guess.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nSince you asked,in VE test edit we had encountered it at mr wiki URL When I increased space.I suppose developers already may be taking care of this.', 'I suppose en wiki maya be needs to track nowikis with better targeted edit filters for space and other mark up aspects.Thats my guess.']","['WORKAROUNDS', 'INVESTIGATION AND EXPLORATION']"
+53673,VisualEditor: Search of parameters in transclusion editor should be case insensitive,"The parameter search is case sensitive, requiring all lowercase input
+
+When searching for parameters in the transclusion/template editor the search returns ""Unknown parameter"" unless the search term is entirely lowercase.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11271}",task_description,"['VisualEditor: Search of parameters in transclusion editor should be case insensitive\n\nThe parameter search is case sensitive, requiring all lowercase input\n\nWhen searching for parameters in the transclusion/template editor the search returns ""Unknown parameter"" unless the search term is entirely lowercase.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11271}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237192,VisualEditor: Search of parameters in transclusion editor should be case insensitive,Done by gerrit 117305.,task_subcomment,['Done by gerrit 117305.'],['SOLUTION DISCUSSION']
+237188,VisualEditor: Search of parameters in transclusion editor should be case insensitive,*** Bug 52950 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52950 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237184,VisualEditor: Search of parameters in transclusion editor should be case insensitive,"After a moments though I wonder if this might be the same issue as bug 51670, with the search requiring input that matches the parameter as defined in the source (which the VE user has no way of knowing) rather than the title as displayed in the parameter list.",task_subcomment,"['After a moments though I wonder if this might be the same issue as bug 51670, with the search requiring input that matches the parameter as defined in the source (which the VE user has no way of knowing) rather than the title as displayed in the parameter list.']",['MOTIVATION']
+53672,VisualEditor: Move the remove template/parameter button to somewhere more prominent?,"Lack of ""remove template"" button in a 1366x480px Firefox 22 window on Xubuntu Linux
+
+In the Visual Editor template/transclusion editor the list of parameters obscures the ""remove template"" button so that it can only be clicked if you enter the name of a non-existant parameter into the search box. See attachment to bug 51671
+
+Even this does not help when the window is too small for it to be displayed (see attachment).
+
+Both problems could be solved by either: 
+*making the window scroll (separately from making the parameter list scroll); and/or
+*moving the ""Remove template"" button next to the ""save changes"" button (which would probably be more logical than placing it under ""options"" - see also bug 51135).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51739
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51135
+
+**Attached**: {F11269}",task_description,"['VisualEditor: Move the remove template/parameter button to somewhere more prominent?', 'Lack of ""remove template"" button in a 1366x480px Firefox 22 window on Xubuntu Linux\n\nIn the Visual Editor template/transclusion editor the list of parameters obscures the ""remove template"" button so that it can only be clicked if you enter the name of a non-existant parameter into the search box.', 'See attachment to bug 51671\n\nEven this does not help when the window is too small for it to be displayed (see attachment).', 'Both problems could be solved by either: \n*making the window scroll (separately from making the parameter list scroll); and/or\n*moving the ""Remove template"" button next to the ""save changes"" button (which would probably be more logical than placing it under ""options"" - see also bug 51135).', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL\n\n**Attached**: {F11269}']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+237132,VisualEditor: Move the remove template/parameter button to somewhere more prominent?,The button has now been moved to the right of the template or parameter's name.,task_subcomment,"[""The button has now been moved to the right of the template or parameter's name.""]",['SOLUTION USAGE']
+237124,VisualEditor: Move the remove template/parameter button to somewhere more prominent?,"(In reply to comment #2)
+> The problem is that button removes the single template that the pane is
+> about,
+> not the entire transclusion (which can cover from one template to thousands)
+> -
+> the dialog footer buttons are meant to apply to the entire dialog's subject,
+> not just the bit you're currently looking at.
+
+Ah rights, yes that does make sense
+
+> However, maybe it could be up in the top-right, alongside the name of the
+> template you've currently got selected?
+
+Right aligned on the same line as the template name / parameter name (for remove parameter) does seem like the best. Need to make sure that it doesn't collide with a long template/parameter name though.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAh rights, yes that does make sense\n\nQUOTE\nQUOTE\n\nRight aligned on the same line as the template name / parameter name (for remove parameter) does seem like the best.', ""Need to make sure that it doesn't collide with a long template/parameter name though.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237115,VisualEditor: Move the remove template/parameter button to somewhere more prominent?,"(In reply to comment #0)
+> *moving the ""Remove template"" button next to the ""save changes"" button (which
+> would probably be more logical than placing it under ""options"" - see also bug
+> 51135).
+
+The problem is that button removes the single template that the pane is about, not the entire transclusion (which can cover from one template to thousands) - the dialog footer buttons are meant to apply to the entire dialog's subject, not just the bit you're currently looking at.
+
+However, maybe it could be up in the top-right, alongside the name of the template you've currently got selected?",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nThe problem is that button removes the single template that the pane is about, not the entire transclusion (which can cover from one template to thousands) - the dialog footer buttons are meant to apply to the entire dialog's subject, not just the bit you're currently looking at."", ""However, maybe it could be up in the top-right, alongside the name of the template you've currently got selected?""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+237106,VisualEditor: Move the remove template/parameter button to somewhere more prominent?,"The fix to bug 51739 has made this less of an issue, in that the remove template button can be accessed by scrolling to the very bottom of the list. I still think the button would be better placed next to the ""save changes"" button though.
+
+Changing from a bug to an enhancement accordingly.",task_subcomment,"['The fix to bug 51739 has made this less of an issue, in that the remove template button can be accessed by scrolling to the very bottom of the list.', 'I still think the button would be better placed next to the ""save changes"" button though.', 'Changing from a bug to an enhancement accordingly.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+53665,VisualEditor: Drag-and-drop requires the item (image/reference/template) to be selected before it can be dragged,"A user on the English Wikipedia reports two problems when attempting to drag and drop an image.
+""Problem 1: Clicking on a media file and dragging the mouse causes the cursor to change to the ""I'm moving an image"" icon, but the image doesn't actually move. I can only move an image if I click it once to select it, then click and hold.
+
+Problem 2: If I move an image a small enough distance across the screen that it doesn't actually move, I can't move it again unless I deselect it and then reselect it.""
+
+They are using Firefox 21, I can confirm both problems in Firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54472",task_description,"['VisualEditor: Drag-and-drop requires the item (image/reference/template) to be selected before it can be dragged\n\nA user on the English Wikipedia reports two problems when attempting to drag and drop an image.', '""Problem 1: Clicking on a media file and dragging the mouse causes the cursor to change to the ""I\'m moving an image"" icon, but the image doesn\'t actually move.', 'I can only move an image if I click it once to select it, then click and hold.', 'Problem 2: If I move an image a small enough distance across the screen that it doesn\'t actually move, I can\'t move it again unless I deselect it and then reselect it.""', 'They are using Firefox 21, I can confirm both problems in Firefox 22.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']"
+236711,VisualEditor: Drag-and-drop requires the item (image/reference/template) to be selected before it can be dragged,"Specifically, this was fixed by Ed's changes to clickable nodes last week.",task_subcomment,"[""Specifically, this was fixed by Ed's changes to clickable nodes last week.""]",['BUG REPRODUCTION']
+236704,VisualEditor: Drag-and-drop requires the item (image/reference/template) to be selected before it can be dragged,This doesn't appear to be a problem in master.,task_subcomment,"[""This doesn't appear to be a problem in master.""]",['OBSERVED BUG BEHAVIOR']
+236699,VisualEditor: Drag-and-drop requires the item (image/reference/template) to be selected before it can be dragged,fwiw about Problem 1 the same happens with text based templates. Tested with the template {{languages}} at the top of the page at https://www.mediawiki.org/wiki/Groups,task_subcomment,"['fwiw about Problem 1 the same happens with text based templates.', 'Tested with the template {{languages}} at the top of the page at URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236694,VisualEditor: Drag-and-drop requires the item (image/reference/template) to be selected before it can be dragged,"Some suggestions about dragging from Adam C.:
+""If I might suggest, if dragging isn't possible, why not just make it that when you select an image, you have a few buttons. A left arrow to move it left, a right arrow to move it right, a menu button between them that'll give you the chance to edit image properties (and to set the rarely-used centre), ideally a way to directly edit the caption without entering a menu, and perhaps a little drag bar at the top for moving it vertically? (Having a standardised place to grab and drag would be an excellent idea, by the way.I'd suggest adding a little bar at the top of an element when it's clicked on.)"".",task_subcomment,"['Some suggestions about dragging from Adam C.:\n""If I might suggest, if dragging isn\'t possible, why not just make it that when you select an image, you have a few buttons.', ""A left arrow to move it left, a right arrow to move it right, a menu button between them that'll give you the chance to edit image properties (and to set the rarely-used centre), ideally a way to directly edit the caption without entering a menu, and perhaps a little drag bar at the top for moving it vertically?"", ""(Having a standardised place to grab and drag would be an excellent idea, by the way.I'd suggest adding a little bar at the top of an element when it's clicked on."", ')"".']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53650,VisualEditor: Remove (and stop adding) useless documentation,"/**
+ * Creates an ve.Element object.
+ *
+ * @class
+ * @abstract
+ *
+ * @constructor
+ */
+ve.Element = function VeElement
+
+These and everything like are useless (not really explaining anything) and annoying (gets you excited to see a line of text only to find out its nothing) and makes the jsduck --nodoc utility unusable since a lot of things without documentation aren't without documentation.
+
+So, henceforth, it is ""okay"" for a doc block to be just tags with no description on top (or even just /** */ with nothing, which is all jsduck needs to include a property in its index).
+
+I (or someone else) will be ridding these at some point, but lets try and not duplicate them more (I won't take ""consistency"" as an argument here when creating something that is like something else that has a useless description, fill it in or don't copy it, don't spread the virus).
+
+Thanks
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Remove (and stop adding) useless documentation\n\n/**\n * Creates an ve.Element object.', ""*\n *SCREEN_NAME\n *SCREEN_NAME\n *\n *SCREEN_NAME\n */\nve.Element = function VeElement\n\nThese and everything like are useless (not really explaining anything) and annoying (gets you excited to see a line of text only to find out its nothing) and makes the jsduck --nodoc utility unusable since a lot of things without documentation aren't without documentation."", 'So, henceforth, it is ""okay"" for a doc block to be just tags with no description on top (or even just /** */ with nothing, which is all jsduck needs to include a property in its index).', 'I (or someone else) will be ridding these at some point, but lets try and not duplicate them more (I won\'t take ""consistency"" as an argument here when creating something that is like something else that has a useless description, fill it in or don\'t copy it, don\'t spread the virus).', 'Thanks\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+235943,VisualEditor: Remove (and stop adding) useless documentation,"Change 146523 merged by jenkins-bot:
+Remove useless documentation, add more useful documentation
+
+https://gerrit.wikimedia.org/r/146523",task_subcomment,"['Change 146523 merged by jenkins-bot:\nRemove useless documentation, add more useful documentation\n\nGERRIT_URL']",['ACTION ON ISSUE']
+235938,VisualEditor: Remove (and stop adding) useless documentation,"Change 146523 had a related patch set uploaded by Krinkle:
+Remove useless documentation, add more useful documentation
+
+https://gerrit.wikimedia.org/r/146523",task_subcomment,"['Change 146523 had a related patch set uploaded by Krinkle:\nRemove useless documentation, add more useful documentation\n\nGERRIT_URL']",['INVESTIGATION AND EXPLORATION']
+235933,VisualEditor: Remove (and stop adding) useless documentation,"Change 125036 merged by jenkins-bot:
+Get rid of useless comments for classes
+
+https://gerrit.wikimedia.org/r/125036",task_subcomment,['Change 125036 merged by jenkins-bot:\nGet rid of useless comments for classes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+235928,VisualEditor: Remove (and stop adding) useless documentation,"Change 125036 had a related patch set uploaded by Krinkle:
+Get rid of useless comments for classes
+
+https://gerrit.wikimedia.org/r/125036",task_subcomment,['Change 125036 had a related patch set uploaded by Krinkle:\nGet rid of useless comments for classes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+235923,VisualEditor: Remove (and stop adding) useless documentation,Note that there is one (exactly one) piece of useful information in that comment: @abstract,task_subcomment,['Note that there is one (exactly one) piece of useful information in that comment:SCREEN_NAME'],['OBSERVED BUG BEHAVIOR']
+53634,Page actions are wrong for VisualEditor,"mw.gettingStarted.logging.getPageSchemaAction returns the wrong values for VE.  For instance, it returns page-impression when the VE edit screen is open.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Page actions are wrong for VisualEditor\n\nmw.gettingStarted.logging.getPageSchemaAction returns the wrong values for VE.', 'For instance, it returns page-impression when the VE edit screen is open.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+2251231,Page actions are wrong for VisualEditor,"#MediaWiki-extensions-GettingStarted has been removed from Wikimedia wikis and is getting archived per `T292654`. Thus declining this task to reflect reality.
+
+See e.g. #GrowthExperiments-NewcomerTasks or #GuidedTour instead nowadays for related use cases.",task_subcomment,"['#MediaWiki-extensions-GettingStarted has been removed from Wikimedia wikis and is getting archived per CODE.', 'Thus declining this task to reflect reality.', 'See e.g.', '#GrowthExperiments-NewcomerTasks or #GuidedTour instead nowadays for related use cases.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+402798,Page actions are wrong for VisualEditor,">>! In T53634#991958, @Halfak wrote:
+> @aklapper  Hmm..  This should not be assigned to me.  I'm not sure how that happen.  
+
+See https://old-bugzilla.wikimedia.org/show_bug.cgi?id=51634 - it was assigned to you in 02/2014.
+
+Unassigning (you can also do that) and lowering priority here.",task_subcomment,"['QUOTE\nQUOTE\n\nSee URL - it was assigned to you in 02/2014.', 'Unassigning (you can also do that) and lowering priority here.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+402703,Page actions are wrong for VisualEditor,@aklapper  Hmm..  This should not be assigned to me.  I'm not sure how that happen.  ,task_subcomment,"['SCREEN_NAME  Hmm..', 'This should not be assigned to me.', ""I'm not sure how that happen.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+401803,Page actions are wrong for VisualEditor,">>! In T53634#544033, @Mattflaschen wrote:
+> getPageSchemaAction has been removed entirely, so I'm tempted to close this.  However, we will need to revisit if we want to track something like ""edit impressions"" again.
+
+@Halfak: Still working on this? If yes what's the progress, if no should the assignee be reset and is ""high priority"" still correct here?",task_subcomment,"['QUOTE\nQUOTE\nSCREEN_NAME: Still working on this?', 'If yes what\'s the progress, if no should the assignee be reset and is ""high priority"" still correct here?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235026,Page actions are wrong for VisualEditor,As part of the new VE tests we will need to have reliable instrumentation (adding Nuria and James to make sure they are aware of this change).,task_subcomment,['As part of the new VE tests we will need to have reliable instrumentation (adding Nuria and James to make sure they are aware of this change).'],['FUTURE PLAN']
+235018,Page actions are wrong for VisualEditor,"getPageSchemaAction has been removed entirely, so I'm tempted to close this.  However, we will need to revisit if we want to track something like ""edit impressions"" again.",task_subcomment,"[""getPageSchemaAction has been removed entirely, so I'm tempted to close this."", 'However, we will need to revisit if we want to track something like ""edit impressions"" again.']","['ACTION ON ISSUE', 'FUTURE PLAN']"
+235011,Page actions are wrong for VisualEditor,"When this is fixed, we should also try to put back page-save-attempt and page-save-success for both (we might do it just for wikitext again in the meantime).",task_subcomment,"['When this is fixed, we should also try to put back page-save-attempt and page-save-success for both (we might do it just for wikitext again in the meantime).']",['SOLUTION DISCUSSION']
+235005,Page actions are wrong for VisualEditor,"Yes, good catch.  VE doesn't touch wgPostEdit, which we're using, at all.",task_subcomment,"['Yes, good catch.', ""VE doesn't touch wgPostEdit, which we're using, at all.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+234999,Page actions are wrong for VisualEditor,"**swalling** wrote:
+
+Would this impact page-save-success logging for VE?",task_subcomment,['**swalling** wrote:\n\nWould this impact page-save-success logging for VE?'],['OBSERVED BUG BEHAVIOR']
+53628,Images specified with size foopxpx render at native size,"If a stub template includes an image size declaration that includes ""px"" then that image is shown at native resolution in the editor.
+
+This was observed with [[Template:Cornwall-stub]] which originally had the code:
+{{asbox
+| image     = Flag of Cornwall.svg
+| pix       = 30px
+| subject   = [[Cornwall]]
+| category  = Cornwall stubs
+| name      = Template:Cornwall-stub
+}}
+
+When the ""pix"" parameter was changed to just ""30"" [https://en.wikipedia.org/w/index.php?title=Template:Cornwall-stub&diff=564819917&oldid=547286019] as was used by e.g. [[Template:Nigeria-stub]] the image size was displayed correctly. The icon has been rendering at correct size when rendered for reading, presumably since [https://en.wikipedia.org/w/index.php?title=Template:Cornwall-stub&diff=next&oldid=235904748 2009]. 
+
+Interestingly it renders as intended in VE when the template is initially placed, but does on every subsequent time it's opened in VE.
+
+Feel free to use [[User:Thryduulf/stubtemplate]] for testing (I'll leave it up at least until this bug is closed) as I have altered the actual Cornwall-stub template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51826",task_description,"['Images specified with size foopxpx render at native size\n\nIf a stub template includes an image size declaration that includes ""px"" then that image is shown at native resolution in the editor.', 'This was observed with [[Template:Cornwall-stub]] which originally had the code:\n{{asbox\n| image     = Flag of Cornwall.svg\n| pix       = 30px\n| subject   = [[Cornwall]]\n| category  = Cornwall stubs\n| name      = Template:Cornwall-stub\n}}\n\nWhen the ""pix"" parameter was changed to just ""30"" [URL as was used by e.g.', '[[Template:Nigeria-stub]] the image size was displayed correctly.', 'The icon has been rendering at correct size when rendered for reading, presumably since [URL 2009].', ""Interestingly it renders as intended in VE when the template is initially placed, but does on every subsequent time it's opened in VE."", ""Feel free to use [[User:Thryduulf/stubtemplate]] for testing (I'll leave it up at least until this bug is closed) as I have altered the actual Cornwall-stub template."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+2416201,Images specified with size foopxpx render at native size,"Uses of this ""trailing pxpx"" feature are now tracked, see T207032 and T15500, and this (kind of) feature will probably be removed in the future.",task_subcomment,"['Uses of this ""trailing pxpx"" feature are now tracked, see T207032 and T15500, and this (kind of) feature will probably be removed in the future.']",['FUTURE PLAN']
+2402140,Images specified with size foopxpx render at native size,"Uses of this ""leading pxpx"" feature are now tracked, see T207032 and T15500, and this (kind of) feature will probably be removed in the future.",task_subcomment,"['Uses of this ""leading pxpx"" feature are now tracked, see T207032 and T15500, and this (kind of) feature will probably be removed in the future.']",['FUTURE PLAN']
+234705,Images specified with size foopxpx render at native size,"Change 114345 merged by jenkins-bot:
+Support trailing 'pxpx' in image size options.
+
+https://gerrit.wikimedia.org/r/114345",task_subcomment,"[""Change 114345 merged by jenkins-bot:\nSupport trailing 'pxpx' in image size options."", 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+234698,Images specified with size foopxpx render at native size,"Change 114345 had a related patch set uploaded by Cscott:
+Support trailing 'pxpx' in image size options.
+
+https://gerrit.wikimedia.org/r/114345",task_subcomment,"[""Change 114345 had a related patch set uploaded by Cscott:\nSupport trailing 'pxpx' in image size options."", 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+234693,Images specified with size foopxpx render at native size,"(In reply to C. Scott Ananian from comment #8)
+> Yes, 'pxpx' is actually a ""feature"".  See bug 13500.
+
+groan!",task_subcomment,['(In reply to C. Scott Ananian from comment #8)\nQUOTE\n\ngroan!'],['SOCIAL CONVERSATION']
+234685,Images specified with size foopxpx render at native size,"Yes, 'pxpx' is actually a ""feature"".  See bug 13500.
+
+Working on a fix...",task_subcomment,"['Yes, \'pxpx\' is actually a ""feature"".', 'See bug 13500.', 'Working on a fix...']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+234680,Images specified with size foopxpx render at native size,"Another concrete example:
+http://parsoid.wmflabs.org/arwiki/%D9%85%D8%B7%D8%A7%D8%B1_%D8%B3%D9%8A%D8%B3%D9%8A%D9%85%D9%8A%D9%88%D8%AA?oldid=11661406
+
+This bug increases a little bit the size of the offline dumps. I have estimated for example that on arwiki, ~200 pictures (calls) are impacted.
+
+It seems that the PHP related code is the function parseWidthParam() in Parser.php (but this doesn't seems to support things lik ""$1px"".",task_subcomment,"['Another concrete example:\nURL\n\nThis bug increases a little bit the size of the offline dumps.', 'I have estimated for example that on arwiki, ~200 pictures (calls) are impacted.', 'It seems that the PHP related code is the function parseWidthParam() in Parser.php (but this doesn\'t seems to support things lik ""$1px"".']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234676,Images specified with size foopxpx render at native size,*** Bug 54371 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54371 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234672,Images specified with size foopxpx render at native size,"We are supporting localized option patterns. In this case we get something like $1px, which does not match 30pxpx. We need to investigate why this works in the PHP parser, but not in Parsoid.",task_subcomment,"['We are supporting localized option patterns.', 'In this case we get something like $1px, which does not match 30pxpx.', 'We need to investigate why this works in the PHP parser, but not in Parsoid.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234667,Images specified with size foopxpx render at native size,*** Bug 51826 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51826 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234663,Images specified with size foopxpx render at native size,"This happens on every infobox that uses
+https://de.wikipedia.org/wiki/Datei:Kazakhstan_location_map.svg
+e.g.
+https://de.wikipedia.org/wiki/Balqasch?veaction=edit
+
+Im seeing it on _some_ other SVG based location maps on German Wikipedia, but not many (1 in 15?)
+https://de.wikipedia.org/wiki/Almaty?veaction=edit
+https://de.wikipedia.org/wiki/Bosporus?veaction=edit
+
+Other similar issues
+https://de.wikipedia.org/wiki/Totes_Meer?veaction=edit
+https://de.wikipedia.org/wiki/Zittauer_Gebirge?veaction=edit",task_subcomment,"['This happens on every infobox that uses\nURL\ne.g.', 'URL\n\nIm seeing it on _some_ other SVG based location maps on German Wikipedia, but not many (1 in 15?)', 'URL\nURL\n\nOther similar issues\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+234656,Images specified with size foopxpx render at native size,*** Bug 51845 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51845 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234649,Images specified with size foopxpx render at native size,I've just been pointed to an older discussion about this issue at https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Problem_with_image_and_other_information_in_an_infobox,task_subcomment,"[""I've just been pointed to an older discussion about this issue at URL""]",['POTENTIAL NEW ISSUES AND REQUESTS']
+53624,VisualEditor: Delete immediately before (or backspace after) a table cell moves text out of/into cell,"User:NicoV at the English Wikipedia reports:
+*In [[The Drover's Boy]], if you put the cursor just before the table and hit Del, the first title (Song title) is put outside the table while Performes becomes the first title.
+*I saw this because I tried to insert a template just before the table, then deleted it => an empty line was visible before the table. When trying to delete this empty line, the first title was put outside the table.
+
+I did some more testing and can confirm that:
+*Pressing delete after the last character before a table deletes the first cell and moves the contents out of the table, and moves the second cell (including formatting) to the former position of the first cell. The position of the second cell is replaced with a blank cell.
+*The same happens when pressing backspace before the first character of the first cell
+*After repeating this sufficient times the contents of the last cell on the first line is moved out of the table and the line deleted.
+*Pressing delete after the last character in the last cell, or backspace before the first character after the last cell, moves the whole of the next line (or title) into the last cell of the table, preserving formatting and links, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50286",task_description,"[""VisualEditor: Delete immediately before (or backspace after) a table cell moves text out of/into cell\n\nUser:NicoV at the English Wikipedia reports:\n*In [[The Drover's Boy]], if you put the cursor just before the table and hit Del, the first title (Song title) is put outside the table while Performes becomes the first title."", '*I saw this because I tried to insert a template just before the table, then deleted it => an empty line was visible before the table.', 'When trying to delete this empty line, the first title was put outside the table.', 'I did some more testing and can confirm that:\n*Pressing delete after the last character before a table deletes the first cell and moves the contents out of the table, and moves the second cell (including formatting) to the former position of the first cell.', 'The position of the second cell is replaced with a blank cell.', '*The same happens when pressing backspace before the first character of the first cell\n*After repeating this sufficient times the contents of the last cell on the first line is moved out of the table and the line deleted.', '*Pressing delete after the last character in the last cell, or backspace before the first character after the last cell, moves the whole of the next line (or title) into the last cell of the table, preserving formatting and links, etc.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+445973,VisualEditor: Delete immediately before (or backspace after) a table cell moves text out of/into cell,"None of the reported issues happen any more. I think most of it was fixed a long time ago, I fixed the last stragglers with T92702.",task_subcomment,"['None of the reported issues happen any more.', 'I think most of it was fixed a long time ago, I fixed the last stragglers with T92702.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+234483,VisualEditor: Delete immediately before (or backspace after) a table cell moves text out of/into cell,"A user on Polish Wikipedia reports this is happening there, too. Please see Bug:61272.",task_subcomment,"['A user on Polish Wikipedia reports this is happening there, too.', 'Please see Bug:61272.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+234476,VisualEditor: Delete immediately before (or backspace after) a table cell moves text out of/into cell,"A user at en.wp has reported what appears to be the same bug also occurring with image captions:
+""Suppose an image lives between paragraphs 1 and 2. If I click before the first word of paragraph 2 and press ""backspace"", the rest of paragraph 2 gets moved into the caption of the image.
+
+Suppose an image lives between paragraphs 1 and 2. If I click after the last word of paragraph 1 and press ""delete"", the image disappears and the caption gets moved to the end paragraph 1.""",task_subcomment,"['A user at en.wp has reported what appears to be the same bug also occurring with image captions:\n""Suppose an image lives between paragraphs 1 and 2.', 'If I click before the first word of paragraph 2 and press ""backspace"", the rest of paragraph 2 gets moved into the caption of the image.', 'Suppose an image lives between paragraphs 1 and 2.', 'If I click after the last word of paragraph 1 and press ""delete"", the image disappears and the caption gets moved to the end paragraph 1.""']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53620,VisualEditor: Clarify beta explanation text,"User:Hhhippo notes that the language ""VisualEditor is in 'beta' and so many not let you edit everything yet"" is likely to be very confusing to those who are not techie or wiki insiders. New users may understand better if ""VisualEditor"" was explained or replaced with more general language such as ""This editing software"".
+
+While we're talking about clarifying language, I wonder if those same new editors would benefit from a note that they can use ""edit source"" if a feature they need does not work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Clarify beta explanation text\n\nUser:Hhhippo notes that the language ""VisualEditor is in \'beta\' and so many not let you edit everything yet"" is likely to be very confusing to those who are not techie or wiki insiders.', 'New users may understand better if ""VisualEditor"" was explained or replaced with more general language such as ""This editing software"".', 'While we\'re talking about clarifying language, I wonder if those same new editors would benefit from a note that they can use ""edit source"" if a feature they need does not work.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+234259,VisualEditor: Clarify beta explanation text,I think this is now better; closing.,task_subcomment,['I think this is now better; closing.'],['ACTION ON ISSUE']
+234256,VisualEditor: Clarify beta explanation text,"(In reply to comment #0)
+> User:Hhhippo notes that the language ""VisualEditor is in 'beta' and so many
+> not let you edit everything yet"" is likely to be very confusing to those who
+> are not techie or wiki insiders. New users may understand better if
+> ""VisualEditor"" was explained or replaced with more general language such as
+> ""This editing software"".
+> 
+> While we're talking about clarifying language, I wonder if those same new
+> editors would benefit from a note that they can use ""edit source"" if a
+> feature they need does not work.
+
+This language has already been changed (but not deployed yet - that will be this afternoon) to:
+
+| VisualEditor is in 'beta'. You may encounter software issues, and you may
+| not be able to edit parts of the page. Click ""Edit source"" to switch to
+| wikitext mode – unsaved changes will be lost.
+
+I think this makes this a bit clearer, though not perfect.",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis language has already been changed (but not deployed yet - that will be this afternoon) to:\n\n| VisualEditor is in 'beta'."", 'You may encounter software issues, and you may\n| not be able to edit parts of the page.', 'Click ""Edit source"" to switch to\n| wikitext mode – unsaved changes will be lost.', 'I think this makes this a bit clearer, though not perfect.']","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+53606,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently","Right now lots of users try VE with MW 1.21.x and are confused as to why they get nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"[""VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently\n\nRight now lots of users try VE with MW 1.21.x and are confused as to why they get nothing."", '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+233560,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently",This is now merged.,task_subcomment,['This is now merged.'],['SOLUTION USAGE']
+233552,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently","Change 76869 merged by jenkins-bot:
+Add dependency check for MW1.22/wmf11
+
+https://gerrit.wikimedia.org/r/76869",task_subcomment,['Change 76869 merged by jenkins-bot:\nAdd dependency check for MW1.22/wmf11\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233549,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently","Change 76869 had a related patch set uploaded by Jforrester:
+Add dependency check for MW1.22/wmf11
+
+https://gerrit.wikimedia.org/r/76869",task_subcomment,['Change 76869 had a related patch set uploaded by Jforrester:\nAdd dependency check for MW1.22/wmf11\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233543,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently","Change 76706 merged by jenkins-bot:
+Check MW version before loading VE
+
+https://gerrit.wikimedia.org/r/76706",task_subcomment,['Change 76706 merged by jenkins-bot:\nCheck MW version before loading VE\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233537,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently","Change 76706 had a related patch set uploaded by Esanders:
+Check MW version before loading VE
+
+https://gerrit.wikimedia.org/r/76706",task_subcomment,['Change 76706 had a related patch set uploaded by Esanders:\nCheck MW version before loading VE\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233530,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently",Digging around I assume wfUseMW( '1.22alpha' )?,task_subcomment,"[""Digging around I assume wfUseMW( '1.22alpha' )?""]",['OBSERVED BUG BEHAVIOR']
+233526,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently","http://www.mediawiki.org/wiki/Extension:VisualEditor says yes.
+
+I'm not familiar with how extensions usually check for MW version compatibility. Obviously we could do it in the client and throw a JS exception, but there may a preferred way in PHP?",task_subcomment,"['URL says yes.', ""I'm not familiar with how extensions usually check for MW version compatibility."", 'Obviously we could do it in the client and throw a JS exception, but there may a preferred way in PHP?']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+233522,"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently",Is MW >= 1.22 a requirement? If so we can check wgVersion and throw an exception,task_subcomment,"['Is MW >= 1.22 a requirement?', 'If so we can check wgVersion and throw an exception']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53592,VisualEditor: Remove formatting drop-down's horrendous use of strings as implicit message names,"'label': 'foo' should mean that the label is 'foo', not ve.msg( 'foo' );
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"[""VisualEditor: Remove formatting drop-down's horrendous use of strings as implicit message names\n\n'label': 'foo' should mean that the label is 'foo', not ve.msg( 'foo' );\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor""]",['OBSERVED BUG BEHAVIOR']
+232773,VisualEditor: Remove formatting drop-down's horrendous use of strings as implicit message names,This has been resolved in Ic97a636f9a193374728629931b6702bee1b3416a - now menu options are individual tools and they have static titleMessage properties.,task_subcomment,['This has been resolved in Ic97a636f9a193374728629931b6702bee1b3416a - now menu options are individual tools and they have static titleMessage properties.'],['SOLUTION USAGE']
+53590,VisualEditor: Support the  tag as a text annotation,"VisualEditor should support adding and editing the code tag ().
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Support the  tag as a text annotation\n\nVisualEditor should support adding and editing the code tag ().', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+232679,VisualEditor: Support the  tag as a text annotation,"This is now done, but marked as ""experimental"" (so it will show up on MediaWiki.org and the test wikis, but not on other production wikis like the Wikipedias). This is mostly because we don't yet have a proper design for how to have lots of different text annotations (currently we're tracking bugs to create an additional eight on top of the four that now exist including this one). Once we've got a design for that, we'll switch it out of experimental mode, but I'll mark this as fixed for now.",task_subcomment,"['This is now done, but marked as ""experimental"" (so it will show up on MediaWiki.org and the test wikis, but not on other production wikis like the Wikipedias).', ""This is mostly because we don't yet have a proper design for how to have lots of different text annotations (currently we're tracking bugs to create an additional eight on top of the four that now exist including this one)."", ""Once we've got a design for that, we'll switch it out of experimental mode, but I'll mark this as fixed for now.""]","['SOLUTION USAGE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232674,VisualEditor: Support the  tag as a text annotation,"Change 76077 merged by jenkins-bot:
+Code annotation button
+
+https://gerrit.wikimedia.org/r/76077",task_subcomment,['Change 76077 merged by jenkins-bot:\nCode annotation button\n\nGERRIT_URL'],['ACTION ON ISSUE']
+232669,VisualEditor: Support the  tag as a text annotation,"Change 76074 merged by jenkins-bot:
+'CodeScript' => 'Code'
+
+https://gerrit.wikimedia.org/r/76074",task_subcomment,"[""Change 76074 merged by jenkins-bot:\n'CodeScript' => 'Code'\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+232661,VisualEditor: Support the  tag as a text annotation,"Change 76077 had a related patch set uploaded by Esanders:
+Code annotation
+
+https://gerrit.wikimedia.org/r/76077",task_subcomment,['Change 76077 had a related patch set uploaded by Esanders:\nCode annotation\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+232652,VisualEditor: Support the  tag as a text annotation,"Change 76074 had a related patch set uploaded by Esanders:
+'CodeScript' => 'Code'
+
+https://gerrit.wikimedia.org/r/76074",task_subcomment,"[""Change 76074 had a related patch set uploaded by Esanders:\n'CodeScript' => 'Code'\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+232643,VisualEditor: Support the  tag as a text annotation,"With the latest master,  blocks are no longer alienated (so you can edit their contents and copy them), but we haven't added the user interaction tools to set or unset the styling.",task_subcomment,"[""With the latest master,  blocks are no longer alienated (so you can edit their contents and copy them), but we haven't added the user interaction tools to set or unset the styling.""]",['SOLUTION DISCUSSION']
+232638,VisualEditor: Support the  tag as a text annotation,"Change 74563 merged by jenkins-bot:
+De-alienate foo blocks (code element)
+
+https://gerrit.wikimedia.org/r/74563",task_subcomment,['Change 74563 merged by jenkins-bot:\nDe-alienate foo blocks (code element)\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+232632,VisualEditor: Support the  tag as a text annotation,"Change 74563 had a related patch set uploaded by Jforrester:
+De-alienate foo blocks (code element)
+
+https://gerrit.wikimedia.org/r/74563",task_subcomment,['Change 74563 had a related patch set uploaded by Jforrester:\nDe-alienate foo blocks (code element)\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53583,"Add more mw.hook events for wikipage: diff, categories etc.","T32713 added ""wikipage.content"" passing it #mw-content-text, and fired it on initial load and from live preview (and other code like VisualEditor and other extensions/gadgets should also fire it when they replace/update the content).
+
+A few others we should add for things outside the content:
+
+* [DONE in rMW125bfdfec63c3be1b7d94be2d03e21226fcf23f5] `wikipage.categories`
+  arguments: `.catlinks`
+
+  Fired initially and from live preview.
+  e.g. for things like HotCat to listen to
+
+* `wikipage.langlinks`
+  arguments: `#p-lang`
+
+  Fire initially if `#p-lang` exists/non-empty, and from live preview.
+
+* [DONE in rMW9cfb9cb9fba4dcfd25a0924237681b7cc86a20df] wikipage.diff
+  arguments: `#wikiDiff`
+
+  Fire initially if page has a diff on it, and from live preview if user
+  did ""show changes"".
+
+  e.g. for patrolling tools to hook into the diff and the [mark as patrolled] link.
+
+* [DONE in rMW8d0dcb863701e78cb4b066f176da89091bba67b3] `wikipage.editform`
+  arguments: (common parent of `.mw-summary-preview`, `.templatesUsed`, `.hiddencats`)
+
+  e.g. for vector.footerCleanup and other things that hook into this.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: normal",task_description,"['Add more mw.hook events for wikipage: diff, categories etc.', 'T32713 added ""wikipage.content"" passing it #mw-content-text, and fired it on initial load and from live preview (and other code like VisualEditor and other extensions/gadgets should also fire it when they replace/update the content).', 'A few others we should add for things outside the content:\n\n* [DONE in rMW125bfdfec63c3be1b7d94be2d03e21226fcf23f5] CODE\n  arguments: CODE\n\n  Fired initially and from live preview.', 'e.g.', 'for things like HotCat to listen to\n\n* CODE\n  arguments: CODE\n\n  Fire initially if CODE exists/non-empty, and from live preview.', '* [DONE in rMW9cfb9cb9fba4dcfd25a0924237681b7cc86a20df] wikipage.diff\n  arguments: CODE\n\n  Fire initially if page has a diff on it, and from live preview if user\n  did ""show changes"".', 'e.g.', 'for patrolling tools to hook into the diff and the [mark as patrolled] link.', '* [DONE in rMW8d0dcb863701e78cb4b066f176da89091bba67b3] CODE\n  arguments: (common parent of CODE, CODE, CODE)\n\n  e.g.', 'for vector.footerCleanup and other things that hook into this.', '--------------------------\n**Version**: 1.21.x\n**Severity**: normal']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+2062834,"Add more mw.hook events for wikipage: diff, categories etc.","Although this certainly has been discussed somewhere already, I'd suggest adding classes `.mw-diff` and `.mw-catlinks`, that would be used instead of `table.diff` and `.catlinks` respectively (of course, keeping these for BC).
+
+And we could still keep the `[data-mw=""interface""]` attributes, for cases we want to be really sure to avoid matching user-generated markup.
+
+Refs https://github.com/wikimedia/mediawiki/commit/b1e3f9e38d7c74e080e99e58dac55629b9f0b097",task_subcomment,"[""Although this certainly has been discussed somewhere already, I'd suggest adding classes CODE and CODE, that would be used instead of CODE and CODE respectively (of course, keeping these for BC)."", 'And we could still keep the CODE attributes, for cases we want to be really sure to avoid matching user-generated markup.', 'Refs URL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1151861,"Add more mw.hook events for wikipage: diff, categories etc.","Marking as done for now. We can consider the last point if/when we have a use case. When it comes up, I'd recommend we place the `mw.hook(..).fire()` code in `skins.vector.js` and same for other skins that want to support the hook.",task_subcomment,"['Marking as done for now.', 'We can consider the last point if/when we have a use case.', ""When it comes up, I'd recommend we place the CODE code in CODE and same for other skins that want to support the hook.""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1151860,"Add more mw.hook events for wikipage: diff, categories etc.","Hm.. might make sense to fire the Language portlet from individual skin scripts, rather than making core responsible. That also avoids shipping potentially dead code to all skins (e.g. Minerva where it wouldn't be used).",task_subcomment,"['Hm.. might make sense to fire the Language portlet from individual skin scripts, rather than making core responsible.', 'That also avoids shipping potentially dead code to all skins (e.g.', ""Minerva where it wouldn't be used).""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+587272,"Add more mw.hook events for wikipage: diff, categories etc.",">>! In T53583#1918917, @TheDJ wrote:
+> @Krinkle you do not think there is enough value if hotcat only hooks into this after VE saved the page ?
+
+That is valuable, but isn't compatible with using this hook. It would either need to hardcode VE, make exceptions for preview, or simply use the 'wikipage.content' or 'postEdit' hook instead. There doesn't seem to be an appropiate way for HotCat to use 'wikipage.categories' in that case.",task_subcomment,"[""QUOTE\nQUOTE\n\nThat is valuable, but isn't compatible with using this hook."", ""It would either need to hardcode VE, make exceptions for preview, or simply use the 'wikipage.content' or 'postEdit' hook instead."", ""There doesn't seem to be an appropiate way for HotCat to use 'wikipage.categories' in that case.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+587271,"Add more mw.hook events for wikipage: diff, categories etc.",@Krinkle you do not think there is enough value if hotcat only hooks into this after VE saved the page ?,task_subcomment,['SCREEN_NAME you do not think there is enough value if hotcat only hooks into this after VE saved the page ?'],['INVESTIGATION AND EXPLORATION']
+586994,"Add more mw.hook events for wikipage: diff, categories etc.",">>! In T53583#1885706, @TheDJ wrote:
+> @Krinkle, probably yes, but I think that is a concern for HotCat, and not for the hook I would assume.
+
+True, but if HotCat shouldn't use it, then that leaves the use-case question empty for this hook. Which means I may want to revert it. (It got merged meanwhile by @Jdlrobson)",task_subcomment,"[""QUOTE\nQUOTE\n\nTrue, but if HotCat shouldn't use it, then that leaves the use-case question empty for this hook."", 'Which means I may want to revert it.', '(It got merged meanwhile bySCREEN_NAME)']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+586910,"Add more mw.hook events for wikipage: diff, categories etc.","Change 219629 merged by jenkins-bot:
+Add wikipage.categories hook
+
+[[https://gerrit.wikimedia.org/r/219629]]",task_subcomment,['Change 219629 merged by jenkins-bot:\nAdd wikipage.categories hook\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+580098,"Add more mw.hook events for wikipage: diff, categories etc.","@Krinkle, probably yes, but I think that is a concern for HotCat, and not for the hook I would assume.",task_subcomment,"['SCREEN_NAME, probably yes, but I think that is a concern for HotCat, and not for the hook I would assume.']",['SOLUTION DISCUSSION']
+580086,"Add more mw.hook events for wikipage: diff, categories etc.",Triggering wikipage.categories post-save in VisualEditor will help HotCat. However triggering it in edit preview might be unexpected in the particular case of HotCat since it probably shouldn't be creating an edit interface for categories whilst on an edit page for wikitext already (since the two would conflict). Something to consider with regards to separation of concerns. ,task_subcomment,"['Triggering wikipage.categories post-save in VisualEditor will help HotCat.', ""However triggering it in edit preview might be unexpected in the particular case of HotCat since it probably shouldn't be creating an edit interface for categories whilst on an edit page for wikitext already (since the two would conflict)."", 'Something to consider with regards to separation of concerns.']","['SOLUTION DISCUSSION', 'MOTIVATION', 'SOLUTION DISCUSSION']"
+580047,"Add more mw.hook events for wikipage: diff, categories etc.",Rebased that patch to only cover the categories case (as it is analogous to diffs). langlinks first need templates per skin probably.,task_subcomment,"['Rebased that patch to only cover the categories case (as it is analogous to diffs).', 'langlinks first need templates per skin probably.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+579947,"Add more mw.hook events for wikipage: diff, categories etc.","Apologies and thanks for clarifying.
+
+Patch open is:
+https://gerrit.wikimedia.org/r/#/c/219629/",task_subcomment,"['Apologies and thanks for clarifying.', 'Patch open is:\nURL']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+579865,"Add more mw.hook events for wikipage: diff, categories etc.","Of the 4 items in the list of the description, one was marked as done. A second one is now also marked as done. There is also one patch still under review... and a 5 item was being discussed as possibly qualifying for addition to the list.
+",task_subcomment,"['Of the 4 items in the list of the description, one was marked as done.', 'A second one is now also marked as done.', 'There is also one patch still under review... and a 5 item was being discussed as possibly qualifying for addition to the list.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+579391,"Add more mw.hook events for wikipage: diff, categories etc.",Not sure what is left to do. Someone should re-open and clarify in the description (preferably via checkboxes if that's not true),task_subcomment,"['Not sure what is left to do.', ""Someone should re-open and clarify in the description (preferably via checkboxes if that's not true)""]","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+571997,"Add more mw.hook events for wikipage: diff, categories etc.",">>! In T53583#1844576, @Krinkle wrote:
+>>>! In T53583#1606076, @Schnark wrote:
+>> Not mentioned yet, but IMHO makes sense, too: `#firstHeading`
+> 
+> Why?
+
+There are tools that modify the first heading, for example append a link to edit the lead section only. or to change the heading via JS in cases where DISPLAYTITLE can't be used (e.g. [[https://fr.wikipedia.org/wiki/J_sharp|fr:J sharp]]), just to name two examples. These scripts should run again when the content was updated.",task_subcomment,"['QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThere are tools that modify the first heading, for example append a link to edit the lead section only.', ""or to change the heading via JS in cases where DISPLAYTITLE can't be used (e.g."", '[[URL sharp]]), just to name two examples.', 'These scripts should run again when the content was updated.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+571844,"Add more mw.hook events for wikipage: diff, categories etc.",Is this resolved? If not what's left to do?,task_subcomment,"['Is this resolved?', ""If not what's left to do?""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+571365,"Add more mw.hook events for wikipage: diff, categories etc.",">>! In T53583#1606076, @Schnark wrote:
+> Not mentioned yet, but IMHO makes sense, too: `#firstHeading`
+
+Why?",task_subcomment,['QUOTE\nQUOTE\n\nWhy?'],['OBSERVED BUG BEHAVIOR']
+570460,"Add more mw.hook events for wikipage: diff, categories etc.","Change 218275 merged by jenkins-bot:
+Add a wikipage.diff hook
+
+[[https://gerrit.wikimedia.org/r/218275]]",task_subcomment,['Change 218275 merged by jenkins-bot:\nAdd a wikipage.diff hook\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+520978,"Add more mw.hook events for wikipage: diff, categories etc.","Not mentioned yet, but IMHO makes sense, too: `#firstHeading`",task_subcomment,"['Not mentioned yet, but IMHO makes sense, too: CODE']",['SOLUTION DISCUSSION']
+478758,"Add more mw.hook events for wikipage: diff, categories etc.","Change 219629 had a related patch set uploaded (by TheDJ):
+Add wikipage.categories and wikipage.languages hooks
+
+[[https://gerrit.wikimedia.org/r/219629]]
+",task_subcomment,['Change 219629 had a related patch set uploaded (by TheDJ):\nAdd wikipage.categories and wikipage.languages hooks\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+474408,"Add more mw.hook events for wikipage: diff, categories etc.","Change 218275 had a related patch set uploaded (by TheDJ):
+Add a wikipage.diff hook
+
+[[https://gerrit.wikimedia.org/r/218275]]
+",task_subcomment,['Change 218275 had a related patch set uploaded (by TheDJ):\nAdd a wikipage.diff hook\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+434220,"Add more mw.hook events for wikipage: diff, categories etc.","So, now that I'm so much further along with LivePreview, I'm pondering taking on some of these elements next. I was thinking starting with templatesUsed, hiddencats and limit report (I've selected them because they are EditPage only elements, should be a safe start).
+
+Do we still agree that this is the right approach ? Or have ideas changed over the past 2 years ?",task_subcomment,"[""So, now that I'm so much further along with LivePreview, I'm pondering taking on some of these elements next."", ""I was thinking starting with templatesUsed, hiddencats and limit report (I've selected them because they are EditPage only elements, should be a safe start)."", 'Do we still agree that this is the right approach ?', 'Or have ideas changed over the past 2 years ?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232293,"Add more mw.hook events for wikipage: diff, categories etc.","Removing target milestone that was in the past.
+
+If you want this in a specific release, have a good reason AND you are willing to find resources to fix this bug, feel free to change it to something appropriate.",task_subcomment,"['Removing target milestone that was in the past.', 'If you want this in a specific release, have a good reason AND you are willing to find resources to fix this bug, feel free to change it to something appropriate.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+232286,"Add more mw.hook events for wikipage: diff, categories etc.",[Bumping TM as MediaWiki 1.22.0 tarball was released today.],task_subcomment,['[Bumping TM as MediaWiki 1.22.0 tarball was released today.]'],['POTENTIAL NEW ISSUES AND REQUESTS']
+232279,"Add more mw.hook events for wikipage: diff, categories etc.","As the Target Milestone on this ticket has been set to 1.22.0:
+
+According to http://lists.wikimedia.org/pipermail/wikitech-l/2013-September/072030.html ""MediaWiki 1.22 is slated for release on November 30th, at the very latest.""
+
+If this is still intended to get fixed for 1.22.0, a patch is needed soon.",task_subcomment,"['As the Target Milestone on this ticket has been set to 1.22.0:\n\nAccording to URL ""MediaWiki 1.22 is slated for release on November 30th, at the very latest.""', 'If this is still intended to get fixed for 1.22.0, a patch is needed soon.']","['FUTURE PLAN', 'BUG REPRODUCTION']"
+232269,"Add more mw.hook events for wikipage: diff, categories etc.","These are easy to add. Holding off until usage of ""wikipage.content"" is slightly more widespread and we have more use cases for these (e.g. will HotCat be able to use this? etc.)
+
+If you need one of these hooks, please let it know here including a brief description of how/where you'd like to use it. That'll help to shape the details of exactly where these hooks would go.",task_subcomment,"['These are easy to add.', 'Holding off until usage of ""wikipage.content"" is slightly more widespread and we have more use cases for these (e.g.', 'will HotCat be able to use this?', 'etc.)', ""If you need one of these hooks, please let it know here including a brief description of how/where you'd like to use it."", ""That'll help to shape the details of exactly where these hooks would go.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53565,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","At the moment, the VE's refresh after save isn't a full refresh - it refreshes ""in place"", using the parsoid DOM. This isn't something things like gadgets or site JS recognise, and so the reloaded page lacks power user functionality. Save should simply refresh the page cleanly to avoid this issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save\n\nAt the moment, the VE\'s refresh after save isn\'t a full refresh - it refreshes ""in place"", using the parsoid DOM.', ""This isn't something things like gadgets or site JS recognise, and so the reloaded page lacks power user functionality."", 'Save should simply refresh the page cleanly to avoid this issue.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+255890,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save",That's because the Math extension doesn't support this yet; see bug 36060.,task_subcomment,"[""That's because the Math extension doesn't support this yet; see bug 36060.""]",['OBSERVED BUG BEHAVIOR']
+255884,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","Hmm... Visual editor still doesn't call MathJax after saving the page (all I see is the source code of the formulas, e.g. $ \mathbb{N} $).",task_subcomment,"['Hmm...', ""Visual editor still doesn't call MathJax after saving the page (all I see is the source code of the formulas, e.g."", '$ \\mathbb{N} $).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+255878,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","The code of the gadget is not using the 'wikipage.content' hook introduced to fix bug 30713 (and added to VE on Gerrit Change 76751):
+https://en.wikipedia.org/wiki/MediaWiki:Gadget-popups.js
+
+I've made a request for this on its talk page:
+https://en.wikipedia.org/wiki/MediaWiki_talk:Gadget-popups.js#Use_the_.27wikipage.content.27_hook",task_subcomment,"[""The code of the gadget is not using the 'wikipage.content' hook introduced to fix bug 30713 (and added to VE on Gerrit Change 76751):\nURL\n\nI've made a request for this on its talk page:\nURL""]",['BUG REPRODUCTION']
+255870,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","Javascript (or at least navigation popups) are again not working after a page is saved but do work when the page is reloaded.
+
+To test:
+1. Enable the navigation popups gadget
+2. View any page editable in VE
+3. Hover over any link to see a popup
+4. Load the page in VE and save an edit (it doesn't mater what)
+5. Hover over any link and fail to see a popup.
+6. Reload the page, hover over the link and see a popup",task_subcomment,"['Javascript (or at least navigation popups) are again not working after a page is saved but do work when the page is reloaded.', 'To test:\n1.', 'Enable the navigation popups gadget\n2.', 'View any page editable in VE\n3.', 'Hover over any link to see a popup\n4.', ""Load the page in VE and save an edit (it doesn't mater what)\n5."", 'Hover over any link and fail to see a popup.', '6.', 'Reload the page, hover over the link and see a popup']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255864,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save",This is now merged and will be deployed later today.,task_subcomment,['This is now merged and will be deployed later today.'],['ACTION ON ISSUE']
+255861,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","Change 76751 merged by jenkins-bot:
+mw.ViewPageTarget: Fire 'wikipage.content' hook after saving
+
+https://gerrit.wikimedia.org/r/76751",task_subcomment,"[""Change 76751 merged by jenkins-bot:\nmw.ViewPageTarget: Fire 'wikipage.content' hook after saving\n\nGERRIT_URL""]",['SOLUTION USAGE']
+255857,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","Change 76751 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Fire 'wikipage.content' hook after saving
+
+https://gerrit.wikimedia.org/r/76751",task_subcomment,"[""Change 76751 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget: Fire 'wikipage.content' hook after saving\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+255852,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","This hook will not fire in VisualEditor's editing mode. Nodes are protected and don't allow interaction anyway.
+
+These hooks are for enhancements. Anything that's required for display should be handled by VisualEditor's ContentEditable node implementation (e.g. including Timeline, Math, etc.).",task_subcomment,"[""This hook will not fire in VisualEditor's editing mode."", ""Nodes are protected and don't allow interaction anyway."", 'These hooks are for enhancements.', ""Anything that's required for display should be handled by VisualEditor's ContentEditable node implementation (e.g."", 'including Timeline, Math, etc.', ').']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+255848,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","Change 74313 merged by jenkins-bot:
+mediawiki.page.ready: Use wikipage.content instead of domready
+
+https://gerrit.wikimedia.org/r/74313",task_subcomment,['Change 74313 merged by jenkins-bot:\nmediawiki.page.ready: Use wikipage.content instead of domready\n\nGERRIT_URL'],['ACTION ON ISSUE']
+255843,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save",It also affects the MathJax renderer see http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Minor_redisplay_glitch,task_subcomment,['It also affects the MathJax renderer see URL'],['OBSERVED BUG BEHAVIOR']
+255838,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","Some cases (e.g. navigation popups) may not want to fire in editing mode.  I'm not sure if that's best done with a separate hook, or just by making the listener check the mode.",task_subcomment,"['Some cases (e.g.', 'navigation popups) may not want to fire in editing mode.', ""I'm not sure if that's best done with a separate hook, or just by making the listener check the mode.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+255834,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","We may need this to fire when we re-render parts of the document in editing mode, e.g. you are using the Math extension with JS rendering (MathJax), or you re-render a template containing a makecollapsible.",task_subcomment,"['We may need this to fire when we re-render parts of the document in editing mode, e.g.', 'you are using the Math extension with JS rendering (MathJax), or you re-render a template containing a makecollapsible.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+255829,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","Change 74313 had a related patch set uploaded by Krinkle:
+mediawiki.page.ready: Use wikipage.content instead of domready
+
+https://gerrit.wikimedia.org/r/74313",task_subcomment,['Change 74313 had a related patch set uploaded by Krinkle:\nmediawiki.page.ready: Use wikipage.content instead of domready\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+255821,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save","No, we should not refresh because of this. This is not a new bug, this is a known issue in mediawiki core for years with ""live preview"".
+
+The difference being that in 2013 (unlike several years ago when live preview came along) we have solved this. Recently I developed mw.hook in core with an event ""wikipage.content"". Gadgets should listen to that instead of document-ready.
+
+Refreshing for every rendering is not a solution but a work around to have the native browser document trigger ""ready"" again. The solution is to have these wikipage (not html document) related actions be bound to its ready event and be able to fire that on-demand if the wiki page has changed (e.g. due to ajax navigation, live preview or page rendering like VisualEditor).
+
+This has been solved and it is up to gadgets to start using it.
+
+I'm rephrasing this bug to instead be a task for VisualEditor to start using this event (like LivePreview does in core).",task_subcomment,"['No, we should not refresh because of this.', 'This is not a new bug, this is a known issue in mediawiki core for years with ""live preview"".', 'The difference being that in 2013 (unlike several years ago when live preview came along) we have solved this.', 'Recently I developed mw.hook in core with an event ""wikipage.content"".', 'Gadgets should listen to that instead of document-ready.', 'Refreshing for every rendering is not a solution but a work around to have the native browser document trigger ""ready"" again.', 'The solution is to have these wikipage (not html document) related actions be bound to its ready event and be able to fire that on-demand if the wiki page has changed (e.g.', 'due to ajax navigation, live preview or page rendering like VisualEditor).', 'This has been solved and it is up to gadgets to start using it.', ""I'm rephrasing this bug to instead be a task for VisualEditor to start using this event (like LivePreview does in core).""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'WORKAROUNDS', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+255811,"VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save",*** Bug 51568 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51568 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53548,VisualEditor: Node action icon (e.g. for template) appearing in wrong location,"screenshot of the template edit icon in the wrong place
+
+I inserted an image into an article using the VE, then I selected the infobox on the article. Instead of appearing on the infobox like it usually would, the puzzle icon for editing the infobox template appeared on the newly-inserted image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52547
+
+**Attached**: {F11877}",task_description,"['VisualEditor: Node action icon (e.g.', 'for template) appearing in wrong location\n\nscreenshot of the template edit icon in the wrong place\n\nI inserted an image into an article using the VE, then I selected the infobox on the article.', 'Instead of appearing on the infobox like it usually would, the puzzle icon for editing the infobox template appeared on the newly-inserted image.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\n\n**Attached**: {F11877}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+411500,VisualEditor: Node action icon (e.g. for template) appearing in wrong location,">>! In T53548#1034742, @Elitre wrote:
+> I think this is still happening. See for example https://fr.wikipedia.org/w/index.php?title=Parox%C3%A9tine&veaction=edit&vesection=10 ; the list of ""Effets secondaires détaillés"" is actually a template. The blue area when you select it looks like a cross in Chrome and Opera, with the puzzle piece icon overlapping the picture at the right.
+
+That looks like it's {T52036} alone?",task_subcomment,"[""QUOTE\nQUOTE\n\nThat looks like it's {T52036} alone?""]",['SOLUTION DISCUSSION']
+410602,VisualEditor: Node action icon (e.g. for template) appearing in wrong location,"I think this is still happening. See for example https://fr.wikipedia.org/w/index.php?title=Parox%C3%A9tine&veaction=edit&vesection=10 ; the list of ""Effets secondaires détaillés"" is actually a template. The blue area when you select it looks like a cross in Chrome and Opera, with the puzzle piece icon overlapping the picture at the right.",task_subcomment,"['I think this is still happening.', 'See for example URL ; the list of ""Effets secondaires détaillés"" is actually a template.', 'The blue area when you select it looks like a cross in Chrome and Opera, with the puzzle piece icon overlapping the picture at the right.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254632,VisualEditor: Node action icon (e.g. for template) appearing in wrong location,All test cases provided appear to be working now.,task_subcomment,['All test cases provided appear to be working now.'],['BUG REPRODUCTION']
+254627,VisualEditor: Node action icon (e.g. for template) appearing in wrong location,*** Bug 60652 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 60652 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254624,VisualEditor: Node action icon (e.g. for template) appearing in wrong location,The new attachment refers to VEditing of https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61361267&oldid=61290806 .,task_subcomment,['The new attachment refers to VEditing of URL .'],['OBSERVED BUG BEHAVIOR']
+254619,VisualEditor: Node action icon (e.g. for template) appearing in wrong location,"Created attachment 13252
+An icon far, far away...
+
+**Attached**: {F11878}",task_subcomment,"['Created attachment 13252\nAn icon far, far away...\n\n**Attached**: {F11878}']",['ATTACHMENT']
+53546,VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog,"1. Click 'Edit'
+2. Click 'Edit source' quickly before VE has loaded
+3. You are show an API error in a confirm box 'Error loading data from server: error. Would you like to retry?', both OK & cancel let you navigate to edit source.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog\n\n1.', ""Click 'Edit'\n2."", ""Click 'Edit source' quickly before VE has loaded\n3."", ""You are show an API error in a confirm box 'Error loading data from server: error."", 'Would you like to retry?', ""', both OK & cancel let you navigate to edit source."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254544,VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog,*** Bug 57267 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 57267 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254538,VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog,"\o/
+
+Thanks, Alex and Roan!",task_subcomment,"['\\o/\n\nThanks, Alex and Roan!']",['ACTION ON ISSUE']
+254533,VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog,"Change 110108 merged by jenkins-bot:
+Stop API error dialog popping up if you navigate away from the page while Parsoid loads
+
+https://gerrit.wikimedia.org/r/110108",task_subcomment,['Change 110108 merged by jenkins-bot:\nStop API error dialog popping up if you navigate away from the page while Parsoid loads\n\nGERRIT_URL'],['ACTION ON ISSUE']
+254527,VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog,"Change 110108 had a related patch set uploaded by Alex Monk:
+Stop API error dialog popping up if you navigate away from the page while Parsoid loads
+
+https://gerrit.wikimedia.org/r/110108",task_subcomment,['Change 110108 had a related patch set uploaded by Alex Monk:\nStop API error dialog popping up if you navigate away from the page while Parsoid loads\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53527,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"Currently it is impossible to use Visual Editor in the pages of Portuguese Wikipedia which are on namespace 102 (""Anexo""), because the default value of $wgVisualEditorNamespaces is set to array( NS_MAIN ) instead of the $wgContentNamespaces (which usually, but not always is just array( NS_MAIN )). These pages are also articles, and as such should be editable by VisualEditor as any other article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52188",task_description,"['VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN )\n\nCurrently it is impossible to use Visual Editor in the pages of Portuguese Wikipedia which are on namespace 102 (""Anexo""), because the default value of $wgVisualEditorNamespaces is set to array( NS_MAIN ) instead of the $wgContentNamespaces (which usually, but not always is just array( NS_MAIN )).', 'These pages are also articles, and as such should be editable by VisualEditor as any other article.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+253556,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"Thanks! I've updated our docs :-)
+https://pt.wikipedia.org/w/index.php?diff=37359406",task_subcomment,"['Thanks!', ""I've updated our docs :-)\nURL""]","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+253551,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"(In reply to comment #6)
+> (In reply to comment #4)
+> > Why is this not working on Portuguese Wikipedia? Our ""Anexo"" namespace is a
+> > content namespace but this doesn't work:
+> > 
+> > https://pt.wikipedia.org/wiki/Anexo:Lista_de_listas?veaction=edit
+> 
+> This was because of how VE was configured to be used in WMF production; have
+> done a config patch (above) which fixes this - will get it pushed out on
+> Tuesday.
+
+Just to confirm, this is now done. Sorry!",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nJust to confirm, this is now done.', 'Sorry!']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+253547,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"Change 94420 merged by jenkins-bot:
+Make VisualEditor namespaces extend, not replace, default
+
+https://gerrit.wikimedia.org/r/94420",task_subcomment,"['Change 94420 merged by jenkins-bot:\nMake VisualEditor namespaces extend, not replace, default\n\nGERRIT_URL']",['ACTION ON ISSUE']
+253544,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"(In reply to comment #4)
+> Why is this not working on Portuguese Wikipedia? Our ""Anexo"" namespace is a
+> content namespace but this doesn't work:
+> 
+> https://pt.wikipedia.org/wiki/Anexo:Lista_de_listas?veaction=edit
+
+This was because of how VE was configured to be used in WMF production; have done a config patch (above) which fixes this - will get it pushed out on Tuesday.",task_subcomment,['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis was because of how VE was configured to be used in WMF production; have done a config patch (above) which fixes this - will get it pushed out on Tuesday.'],['SOLUTION DISCUSSION']
+253540,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"Change 94420 had a related patch set uploaded by Jforrester:
+Make VisualEditor namespaces extend, not replace, default
+
+https://gerrit.wikimedia.org/r/94420",task_subcomment,"['Change 94420 had a related patch set uploaded by Jforrester:\nMake VisualEditor namespaces extend, not replace, default\n\nGERRIT_URL']",['ACTION ON ISSUE']
+253536,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"Why is this not working on Portuguese Wikipedia? Our ""Anexo"" namespace is a content namespace but this doesn't work:
+
+https://pt.wikipedia.org/wiki/Anexo:Lista_de_listas?veaction=edit",task_subcomment,"['Why is this not working on Portuguese Wikipedia?', 'Our ""Anexo"" namespace is a content namespace but this doesn\'t work:\n\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253532,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"Change 74138 merged by jenkins-bot:
+Default $wgVisualEditorNamespaces to $wgContentNamespaces
+
+https://gerrit.wikimedia.org/r/74138",task_subcomment,['Change 74138 merged by jenkins-bot:\nDefault $wgVisualEditorNamespaces to $wgContentNamespaces\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+253525,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),Merged.,task_subcomment,['Merged.'],['SOLUTION DISCUSSION']
+253520,VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),"Change 74138 had a related patch set uploaded by Helder.wiki:
+Default $wgVisualEditorNamespaces to $wgContentNamespaces
+
+https://gerrit.wikimedia.org/r/74138",task_subcomment,['Change 74138 had a related patch set uploaded by Helder.wiki:\nDefault $wgVisualEditorNamespaces to $wgContentNamespaces\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53515,"VisualEditor: Unsetting ""minor edit"" for users with the ""mark all my edits as minor by default"" doesn't work","A community member marks his edits as ""minor edits"" (via preferences) by default. VE ignores un-marking it both in FF 20.0 and Chrome 27.0; see:
+
+FF:
+
+http://de.wikipedia.org/w/index.php?title=Benutzer:Thoken/test1&diff=prev&oldid=120588869
+
+Chrome:
+
+http://de.wikipedia.org/w/index.php?title=Benutzer:Thoken/test1&diff=prev&oldid=120590664
+
+discussion on De.WP:
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=120620759#Enthaken_von_.22Nur_Kleinigkeiten_wurden_ver.C3.A4ndert.22_ohne_Wirkung
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Unsetting ""minor edit"" for users with the ""mark all my edits as minor by default"" doesn\'t work\n\nA community member marks his edits as ""minor edits"" (via preferences) by default.', 'VE ignores un-marking it both in FF 20.0 and Chrome 27.0; see:\n\nFF:\n\nURL\n\nChrome:\n\nURL\n\ndiscussion on De.WP:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+252913,"VisualEditor: Unsetting ""minor edit"" for users with the ""mark all my edits as minor by default"" doesn't work",Fixed and will get deployed in a few minutes.,task_subcomment,['Fixed and will get deployed in a few minutes.'],['SOLUTION USAGE']
+252904,"VisualEditor: Unsetting ""minor edit"" for users with the ""mark all my edits as minor by default"" doesn't work","Change 75598 merged by jenkins-bot:
+Set 'notminor' if minor edit box not checked
+
+https://gerrit.wikimedia.org/r/75598",task_subcomment,"[""Change 75598 merged by jenkins-bot:\nSet 'notminor' if minor edit box not checked\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+252895,"VisualEditor: Unsetting ""minor edit"" for users with the ""mark all my edits as minor by default"" doesn't work","Change 75598 had a related patch set uploaded by Esanders:
+Set 'notminor' if minor edit box not checked
+
+https://gerrit.wikimedia.org/r/75598",task_subcomment,"[""Change 75598 had a related patch set uploaded by Esanders:\nSet 'notminor' if minor edit box not checked\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+252888,"VisualEditor: Unsetting ""minor edit"" for users with the ""mark all my edits as minor by default"" doesn't work",Confirmed in Firefox.  Note this preference is not available in English Wikipedia.,task_subcomment,"['Confirmed in Firefox.', 'Note this preference is not available in English Wikipedia.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53500,"VisualEditor: Beta notice incorrectly highlights ""Leave feedback"" link when hovering the notice","When hovering the notice (which users do by default as the cursor is there after clicking the ""Beta"" icon on the toolbar) we highlight the ""Leave feedback"" label.
+
+If the entire container was clickable and bound to opening the Feedback dialog that would be appropriate, however that isn't the case. On click we close the notice.
+
+.ve-init-mw-viewPageTarget-tool:hover .ve-init-mw-viewPageTarget-tool-label, .ve-init-mw-viewPageTarget-subtool-label:hover {
+text-decoration: underline;
+}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Beta notice incorrectly highlights ""Leave feedback"" link when hovering the notice\n\nWhen hovering the notice (which users do by default as the cursor is there after clicking the ""Beta"" icon on the toolbar) we highlight the ""Leave feedback"" label.', ""If the entire container was clickable and bound to opening the Feedback dialog that would be appropriate, however that isn't the case."", 'On click we close the notice.', '.ve-init-mw-viewPageTarget-tool:hover .ve-init-mw-viewPageTarget-tool-label, .ve-init-mw-viewPageTarget-subtool-label:hover {\ntext-decoration: underline;\n}\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252109,"VisualEditor: Beta notice incorrectly highlights ""Leave feedback"" link when hovering the notice",This was fixed in the toolbar re-write.,task_subcomment,['This was fixed in the toolbar re-write.'],['BUG REPRODUCTION']
+252102,"VisualEditor: Beta notice incorrectly highlights ""Leave feedback"" link when hovering the notice",This also happens when hovering over the beta label on the toolbar (both it and the leave feedback label are underlined).,task_subcomment,['This also happens when hovering over the beta label on the toolbar (both it and the leave feedback label are underlined).'],['OBSERVED BUG BEHAVIOR']
+53484,VisualEditor: Spaces at the ends of template parameter values are trimmed,"In both named and unnamed parameters.
+
+The unnamed one should be of course a bug.
+
+Should we manage to protect named ones from being trimmed in PHP parser?
+
+ie. generate ({{P1|1= hello }}) to protect the trailing space?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61049",task_description,"['VisualEditor: Spaces at the ends of template parameter values are trimmed\n\nIn both named and unnamed parameters.', 'The unnamed one should be of course a bug.', 'Should we manage to protect named ones from being trimmed in PHP parser?', 'ie.', 'generate ({{P1|1= hello }}) to protect the trailing space?', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+251026,VisualEditor: Spaces at the ends of template parameter values are trimmed,This was fixed some time ago in the clean-up re-write of the transclusion dialog; sorry for the slow triage.,task_subcomment,['This was fixed some time ago in the clean-up re-write of the transclusion dialog; sorry for the slow triage.'],['OBSERVED BUG BEHAVIOR']
+53483,Generic first edit tour,"Make a ""First Edit"" tour to help someone make their first edit, in general.  This should not have any connection to GettingStarted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Generic first edit tour\n\nMake a ""First Edit"" tour to help someone make their first edit, in general.', 'This should not have any connection to GettingStarted.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'POTENTIAL NEW ISSUES AND REQUESTS', 'OBSERVED BUG BEHAVIOR']"
+250985,Generic first edit tour,"**swalling** wrote:
+
+Tours for 'firstedit' and 'firsteditve' are out in the wild. :)",task_subcomment,"[""**swalling** wrote:\n\nTours for 'firstedit' and 'firsteditve' are out in the wild."", ':)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+250979,Generic first edit tour,This should also have browser tests.,task_subcomment,['This should also have browser tests.'],['SOLUTION DISCUSSION']
+250973,Generic first edit tour,"So far I've been using separate tours (one for VE, one for wikitext), so if we continue with that approach, we should make two tours.",task_subcomment,"[""So far I've been using separate tours (one for VE, one for wikitext), so if we continue with that approach, we should make two tours.""]",['SOLUTION DISCUSSION']
+250963,Generic first edit tour,"**swalling** wrote:
+
+(In reply to comment #0)
+> Make a ""First Edit"" tour to help someone make their first edit, in general. 
+> This should not have any connection to GettingStarted.
+
+Also should work with VisualEditor or wikitext editor.",task_subcomment,['**swalling** wrote:\n\n(In reply to comment #0)\nQUOTE\nQUOTE\n\nAlso should work with VisualEditor or wikitext editor.'],['INVESTIGATION AND EXPLORATION']
+250953,Generic first edit tour,"Change 64981 had a related patch set uploaded by Mattflaschen:
+Add tour to be used for first edit (other than GettingStarted).
+
+https://gerrit.wikimedia.org/r/64981",task_subcomment,"['Change 64981 had a related patch set uploaded by Mattflaschen:\nAdd tour to be used for first edit (other than GettingStarted).', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250942,Generic first edit tour,In progress at https://gerrit.wikimedia.org/r/#/c/64981/,task_subcomment,['In progress at URL'],['BUG REPRODUCTION']
+53454,VisualEditor: blocked-notice-logextract doesn't appear when editing user pages of blocked users with VE,"When editing the user page of a blocked user, some messages appear at the top of the page, for example blocked-notice-logextract.
+
+They don't appear when editing with the VisualEditor.
+
+Compare:
+
+Good: https://en.wikipedia.org/w/index.php?title=User:SEAROSE8&action=edit
+
+Bad: https://en.wikipedia.org/wiki/User:SEAROSE8?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52004",task_description,"[""VisualEditor: blocked-notice-logextract doesn't appear when editing user pages of blocked users with VE\n\nWhen editing the user page of a blocked user, some messages appear at the top of the page, for example blocked-notice-logextract."", ""They don't appear when editing with the VisualEditor."", 'Compare:\n\nGood: URL\n\nBad: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249218,VisualEditor: blocked-notice-logextract doesn't appear when editing user pages of blocked users with VE,"Change 121232 merged by jenkins-bot:
+Possibly show blocked-notice-logextract or userpage-userdoesnotexist when editing a user page
+
+https://gerrit.wikimedia.org/r/121232",task_subcomment,['Change 121232 merged by jenkins-bot:\nPossibly show blocked-notice-logextract or userpage-userdoesnotexist when editing a user page\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249213,VisualEditor: blocked-notice-logextract doesn't appear when editing user pages of blocked users with VE,"Change 121232 had a related patch set uploaded by Alex Monk:
+Possibly show blocked-notice-logextract or userpage-userdoesnotexist when editing a user page
+
+https://gerrit.wikimedia.org/r/121232",task_subcomment,['Change 121232 had a related patch set uploaded by Alex Monk:\nPossibly show blocked-notice-logextract or userpage-userdoesnotexist when editing a user page\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53450,VisualEditor: Page text sometimes pops up through the Media insertion dialog,"At unpredictable points, bits of the text from the underlying article sometimes show up on top of the Media search box. See attached video for an example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Linux
+**Platform**: PC",task_description,"['VisualEditor: Page text sometimes pops up through the Media insertion dialog\n\nAt unpredictable points, bits of the text from the underlying article sometimes show up on top of the Media search box.', 'See attached video for an example.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**OS**: Linux\n**Platform**: PC']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+496792,VisualEditor: Page text sometimes pops up through the Media insertion dialog,I'm guessing this is fixed by now. Reopen if you can still reproduce.,task_subcomment,"[""I'm guessing this is fixed by now."", 'Reopen if you can still reproduce.']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+249021,VisualEditor: Page text sometimes pops up through the Media insertion dialog,"Upload failed, so see the video here: https://commons.wikimedia.org/wiki/File:Screen_recording_of_text-over-Media_bug_in_VisualEditor.ogv",task_subcomment,"['Upload failed, so see the video here: URL']",['OBSERVED BUG BEHAVIOR']
+53436,Template search results list should contain each template's descripton,"**Author:** `turingt`
+
+**Description:**
+See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ]
+
+The search results for parameters include each parameter's description, making it easy to select the right one. 
+
+But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template).
+
+So, add the template description to the search results list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",task_description,"[""Template search results list should contain each template's descripton\n\n**Author:** CODE\n\n**Description:**\nSee this feedback trhead: [ URL ]\n\nThe search results for parameters include each parameter's description, making it easy to select the right one."", ""But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template)."", 'So, add the template description to the search results list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+446690,Template search results list should contain each template's descripton,Verified the fix in Betalabs,task_subcomment,['Verified the fix in Betalabs'],['BUG REPRODUCTION']
+445180,Template search results list should contain each template's descripton,"Change 203459 merged by jenkins-bot:
+Show template description in the template search
+
+[[https://gerrit.wikimedia.org/r/203459]]",task_subcomment,['Change 203459 merged by jenkins-bot:\nShow template description in the template search\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+442168,Template search results list should contain each template's descripton,"Change 203459 had a related patch set uploaded (by Mooeypoo):
+Show template description in the template search
+
+[[https://gerrit.wikimedia.org/r/203459]]
+",task_subcomment,['Change 203459 had a related patch set uploaded (by Mooeypoo):\nShow template description in the template search\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+248115,Template search results list should contain each template's descripton,"Thanks for the explanation, I've now reported it as bug 51822.",task_subcomment,"[""Thanks for the explanation, I've now reported it as bug 51822.""]",['ACTION ON ISSUE']
+248105,Template search results list should contain each template's descripton,"(In reply to comment #4)
+> (In reply to comment #3)
+> > > If I type ""book"", template ""Cite book"" is not shown, which limits the search
+> > > functionality to be useful only for people who already know template names
+> > > (i.e. those who don't need it).
+> > 
+> > That is a distinct enhancement request; please open a new bug for it.
+> 
+> Is it distinct or is it part of bug 51670?
+
+It's distinct. This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.",task_subcomment,"[""(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIt's distinct."", ""This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+248098,Template search results list should contain each template's descripton,"(In reply to comment #3)
+> > If I type ""book"", template ""Cite book"" is not shown, which limits the search
+> > functionality to be useful only for people who already know template names
+> > (i.e. those who don't need it).
+> 
+> That is a distinct enhancement request; please open a new bug for it.
+
+Is it distinct or is it part of bug 51670?",task_subcomment,['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIs it distinct or is it part of bug 51670?'],['MOTIVATION']
+248091,Template search results list should contain each template's descripton,"(In reply to comment #2)
+> Also typing a word only shows template names starting with that word, not
+> containing it, which is a weird search behavior.
+> 
+> If I type ""book"", template ""Cite book"" is not shown, which limits the search
+> functionality to be useful only for people who already know template names
+> (i.e. those who don't need it).
+
+That is a distinct enhancement request; please open a new bug for it.",task_subcomment,['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat is a distinct enhancement request; please open a new bug for it.'],['ACTION ON ISSUE']
+248087,Template search results list should contain each template's descripton,"**turingt** wrote:
+
+Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior.
+
+If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).",task_subcomment,"['**turingt** wrote:\n\nAlso typing a word only shows template names starting with that word, not containing it, which is a weird search behavior.', 'If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e.', ""those who don't need it).""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION']"
+248083,Template search results list should contain each template's descripton,"Also typing in 'new' into the New template box returns a list of 10 templates starting with 'new', with no way to scroll through the longer list of templates starting/containing with 'New'
+
+https://en.wikipedia.org/wiki/Special:PrefixIndex/Template:New
+
+More practical, 'New Zealand' or 'New York' only returns 10, and the user may not know the right keyword needed to return better results.",task_subcomment,"[""Also typing in 'new' into the New template box returns a list of 10 templates starting with 'new', with no way to scroll through the longer list of templates starting/containing with 'New'\n\nURL\n\nMore practical, 'New Zealand' or 'New York' only returns 10, and the user may not know the right keyword needed to return better results.""]",['BUG REPRODUCTION']
+53428,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified","In addition to the existing ""default"" attribute for each template parameter, that would be useful to have an ""autofill"" attribute for each template parameter:
+* ""default"" is the value that will be used by the template if the parameter is not specified
+* ""autofill"" could be used for indicating that when inserting a template in a article with VE (or other editor), some parameters should be created automatically with a given value.
+
+I think for example of some templates that have a date parameter to be filled with the date at which the template was inserted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified\n\nIn addition to the existing ""default"" attribute for each template parameter, that would be useful to have an ""autofill"" attribute for each template parameter:\n* ""default"" is the value that will be used by the template if the parameter is not specified\n* ""autofill"" could be used for indicating that when inserting a template in a article with VE (or other editor), some parameters should be created automatically with a given value.', 'I think for example of some templates that have a date parameter to be filled with the date at which the template was inserted.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+247675,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified","Change 157820 merged by jenkins-bot:
+Implement new 'autovalue' parameter property
+
+https://gerrit.wikimedia.org/r/157820",task_subcomment,"[""Change 157820 merged by jenkins-bot:\nImplement new 'autovalue' parameter property\n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+247672,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified","Change 157820 had a related patch set uploaded by Jforrester:
+Implement new 'autovalue' parameter property
+
+https://gerrit.wikimedia.org/r/157820",task_subcomment,"[""Change 157820 had a related patch set uploaded by Jforrester:\nImplement new 'autovalue' parameter property\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+247666,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified","This is generally worked around by wikis by providing another template that when substituted inserts the autofill parameters.
+
+e.g.
+
+{{subst:newdelete|reason=Foo}}
+-> 
+{{delete|reason=Foo|date=YYYY-MM-DD}}
+
+These templates need a ""must-subst"" property of sorts in template data first (bug 65550), but that would make this easier already.
+
+The subst-behaviour is a super set of the scope of this bug (autofill values), however it may be enough.
+
+The problem with a declarative autofill (as opposed to substituting a wrapper template) is that you'd need a fair amount of logic to express what you want to be filled in. Obviously you don't just want a literal string to be inserted, because then you'd just have users omit it and use that value as the default value.
+
+With autofill you most probably want a dynamic value (e.g. the result of invoking a template, or magic words like current date/times, current revision user, base page name etc. Some of these (like date) could be trivially done, but that still leaves a lot of questions (how to specify the date etc.) and compatibility.
+
+So I'd say let's solve bug 65550 first and see how that unfolds. If we still feel a need for this we can revisit it later.
+
+This should additionally be helpful since subst-ing is that wikis do now without VisualEditor so they likely have that in place already and will want to keep that for wikitext users.",task_subcomment,"['This is generally worked around by wikis by providing another template that when substituted inserts the autofill parameters.', 'e.g.', '{{subst:newdelete|reason=Foo}}\n-> \n{{delete|reason=Foo|date=YYYY-MM-DD}}\n\nThese templates need a ""must-subst"" property of sorts in template data first (bug 65550), but that would make this easier already.', 'The subst-behaviour is a super set of the scope of this bug (autofill values), however it may be enough.', ""The problem with a declarative autofill (as opposed to substituting a wrapper template) is that you'd need a fair amount of logic to express what you want to be filled in."", ""Obviously you don't just want a literal string to be inserted, because then you'd just have users omit it and use that value as the default value."", 'With autofill you most probably want a dynamic value (e.g.', 'the result of invoking a template, or magic words like current date/times, current revision user, base page name etc.', 'Some of these (like date) could be trivially done, but that still leaves a lot of questions (how to specify the date etc.)', 'and compatibility.', ""So I'd say let's solve bug 65550 first and see how that unfolds."", 'If we still feel a need for this we can revisit it later.', 'This should additionally be helpful since subst-ing is that wikis do now without VisualEditor so they likely have that in place already and will want to keep that for wikitext users.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+247661,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified","I almost submitted a new bug, but saw this one in the ""possible duplicates"" at the last second... Pasting the text I wrote, in case it helps:
+
+
+Most cleanup templates, banner and inline, have a ""|date={{CURRENTMONTHNAME}} {{CURRENTYEAR}}"" parameter.
+
+If we don't add them, then (on En.Wiki) AnomieBot adds them a few minutes later*, which clutters the history, and more importantly Buries the initial edit in watchlists, making it harder for us humans to check.
+
+*eg. https://en.wikipedia.org/w/index.php?title=Red_squirrel&curid=638291&diff=572563931&oldid=572553559
+
+
+Could we have an ""Add current month and year"" button, for parameters like this?
+
+Or, a tweak for TemplateData so that specific templates will add this parameter/value by default?",task_subcomment,"['I almost submitted a new bug, but saw this one in the ""possible duplicates"" at the last second... Pasting the text I wrote, in case it helps:\n\n\nMost cleanup templates, banner and inline, have a ""|date={{CURRENTMONTHNAME}} {{CURRENTYEAR}}"" parameter.', ""If we don't add them, then (on En.Wiki) AnomieBot adds them a few minutes later*, which clutters the history, and more importantly Buries the initial edit in watchlists, making it harder for us humans to check."", '*eg.', 'URL\n\n\nCould we have an ""Add current month and year"" button, for parameters like this?', 'Or, a tweak for TemplateData so that specific templates will add this parameter/value by default?']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247657,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified","From Bug 52028:
+TemplateData should allow some parameters to have default values which are
+prefilled when using the VisualEditor transclusion manager. 
+
+An example would be the current date for accessdate in citation templates.",task_subcomment,"['From Bug 52028:\nTemplateData should allow some parameters to have default values which are\nprefilled when using the VisualEditor transclusion manager.', 'An example would be the current date for accessdate in citation templates.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+247652,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified",*** Bug 52028 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52028 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247646,"TemplateData: Add an ""autofill"" attribute for parameters which clients would automatically insert if none specified","This seems like a nice improvement, though I worry that it sets up an expectation that a client may not honour.",task_subcomment,"['This seems like a nice improvement, though I worry that it sets up an expectation that a client may not honour.']",['SOLUTION DISCUSSION']
+53421,VisualEditor: Allow AbuseFilter rules to identify VE edits,"I would like to request that some flag or other indicator be added such that abuse filter rules can tell whether the edit is coming from VE or from the source editor.
+
+Because the abuse filter tends to encourage different sorts of editor errors, it would be useful to know which interface is being used when editing.  For example, a nowiki tag added by the source editor is almost certainly intentional, while a nowiki added by VE is probably an accident and should be tagged for inspection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T54281}",task_description,"['VisualEditor: Allow AbuseFilter rules to identify VE edits\n\nI would like to request that some flag or other indicator be added such that abuse filter rules can tell whether the edit is coming from VE or from the source editor.', 'Because the abuse filter tends to encourage different sorts of editor errors, it would be useful to know which interface is being used when editing.', 'For example, a nowiki tag added by the source editor is almost certainly intentional, while a nowiki added by VE is probably an accident and should be tagged for inspection.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T54281}']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+1607402,VisualEditor: Allow AbuseFilter rules to identify VE edits,"Change 456418 **abandoned** by Daimona Eaytoy:
+[mediawiki/extensions/VisualEditor@master] [WIP] Add user_visualeditor variable for AbuseFilter
+
+Reason:
+
+
+https://gerrit.wikimedia.org/r/456418",task_subcomment,['Change 456418 **abandoned** by Daimona Eaytoy:\n[mediawiki/extensions/VisualEditor@master] [WIP] Add user_visualeditor variable for AbuseFilter\n\nReason:\n\n\nGERRIT_URL'],['ACTION ON ISSUE']
+1133086,VisualEditor: Allow AbuseFilter rules to identify VE edits,"@matmarex That hurts :/ Adding a parameter would be surely working, but also highly specifical code which shouldn’t be the first choice; unless other parts of the code throughout MediaWiki will need to know if the current edit comes from VE. Before giving up, is there something else in the global scope which could help us?",task_subcomment,"['SCREEN_NAME That hurts :/ Adding a parameter would be surely working, but also highly specifical code which shouldn’t be the first choice; unless other parts of the code throughout MediaWiki will need to know if the current edit comes from VE.', 'Before giving up, is there something else in the global scope which could help us?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+1132919,VisualEditor: Allow AbuseFilter rules to identify VE edits,">>! In T53421#4546351, @Daimona wrote:
+> Is there something in the request which can uniquely identify VE edits? Sorry for asking, but I cannot set up Parsoid on my wiki and thus can't test VE.
+
+Not really. VE just calls the action=edit API internally (from PHP code), see ApiVisualEditorEdit::saveWikitext(). However, maybe you can add some magic parameter there and handle it on the other end in the AbuseFilter hook handler. I am not sure how it all works on the inside, you might need to experiment a bit :/",task_subcomment,"['QUOTE\nQUOTE\n\nNot really.', 'VE just calls the action=edit API internally (from PHP code), see ApiVisualEditorEdit::saveWikitext().', 'However, maybe you can add some magic parameter there and handle it on the other end in the AbuseFilter hook handler.', 'I am not sure how it all works on the inside, you might need to experiment a bit :/']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+1132795,VisualEditor: Allow AbuseFilter rules to identify VE edits,"To complete the patch, I need a way to determine whether the edit being saved comes from VE or not (yep, the main part). The main thing we have access to is the current WebRequest. Is there something in the request which can uniquely identify VE edits? Sorry for asking, but I cannot set up Parsoid on my wiki and thus can't test VE.",task_subcomment,"['To complete the patch, I need a way to determine whether the edit being saved comes from VE or not (yep, the main part).', 'The main thing we have access to is the current WebRequest.', 'Is there something in the request which can uniquely identify VE edits?', ""Sorry for asking, but I cannot set up Parsoid on my wiki and thus can't test VE.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+1132766,VisualEditor: Allow AbuseFilter rules to identify VE edits,"Change 456418 had a related patch set uploaded (by Daimona Eaytoy; owner: Daimona Eaytoy):
+[mediawiki/extensions/VisualEditor@master] [WIP] Add user_visualeditor variable for AbuseFilter
+
+[[https://gerrit.wikimedia.org/r/456418]]",task_subcomment,['Change 456418 had a related patch set uploaded (by Daimona Eaytoy; owner: Daimona Eaytoy):\n[mediawiki/extensions/VisualEditor@master] [WIP] Add user_visualeditor variable for AbuseFilter\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+1132618,VisualEditor: Allow AbuseFilter rules to identify VE edits,"I'm sorry, I may have missed something, but... wouldn't it be much easier to generate a dedicated AF variable inside VisualEditor using AF hooks? This would avoid messing up with change tags and request params, and it's also the way used to distinguish edits coming from e.g. mobile app or mobile version.",task_subcomment,"[""I'm sorry, I may have missed something, but... wouldn't it be much easier to generate a dedicated AF variable inside VisualEditor using AF hooks?"", ""This would avoid messing up with change tags and request params, and it's also the way used to distinguish edits coming from e.g."", 'mobile app or mobile version.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+788500,VisualEditor: Allow AbuseFilter rules to identify VE edits,">>! In T53421#2905524, @jhsoby wrote:
+> Now with the 2017 wikitext editor I think this should get a priority bump, seeing that it too uses ?veaction instead of ?action, which makes it impossible (AFAIK) to use edit filters to identify those edits.
+
+The action URL path is a poor guide to the source of edits (see the Special:Edit or whatever it's called tool, the mobile Web wikitext and visual editors, and other mechanisms). Anyone trying to capture edits by use of the URL path is going to fail pretty terribly.
+
+I also don't agree that this is a particular priority. People have been editing using different tools for years without the software allowing discriminatory edit validation.",task_subcomment,"[""QUOTE\nQUOTE\n\nThe action URL path is a poor guide to the source of edits (see the Special:Edit or whatever it's called tool, the mobile Web wikitext and visual editors, and other mechanisms)."", 'Anyone trying to capture edits by use of the URL path is going to fail pretty terribly.', ""I also don't agree that this is a particular priority."", 'People have been editing using different tools for years without the software allowing discriminatory edit validation.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+784647,VisualEditor: Allow AbuseFilter rules to identify VE edits,"Now with the 2017 wikitext editor I think this should get a priority bump, seeing that it too uses ?veaction instead of ?action, which makes it impossible (AFAIK) to use edit filters to identify those edits.",task_subcomment,"['Now with the 2017 wikitext editor I think this should get a priority bump, seeing that it too uses ?veaction instead of ?action, which makes it impossible (AFAIK) to use edit filters to identify those edits.']",['SOLUTION DISCUSSION']
+247245,VisualEditor: Allow AbuseFilter rules to identify VE edits,"(In reply to comment #10)
+> The original request was merely for the AbuseFilter to somehow be made aware
+> whether or not an edit had come from VE as opposed to source editing.  
+> 
+> For example, the Abuse Filter is aware of ""action="" but not ""veaction="".  At
+> present ""action=edit"" and ""veaction=edit"" look identical to the AbuseFilter.
+
+Adjusting comment accordingly.
+
+> I think the suggestion that AbuseFilter should somehow be allowed process
+> tags generated by other entities is actually an unnecessary (and more
+> complicated) diversion.
+
+Sure.",task_subcomment,"['(In reply to comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdjusting comment accordingly.', 'QUOTE\nQUOTE\nQUOTE\n\nSure.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247240,VisualEditor: Allow AbuseFilter rules to identify VE edits,"The original request was merely for the AbuseFilter to somehow be made aware whether or not an edit had come from VE as opposed to source editing.  
+
+For example, the Abuse Filter is aware of ""action="" but not ""veaction="".  At present ""action=edit"" and ""veaction=edit"" look identical to the AbuseFilter.
+
+I think the suggestion that AbuseFilter should somehow be allowed process tags generated by other entities is actually an unnecessary (and more complicated) diversion.",task_subcomment,"['The original request was merely for the AbuseFilter to somehow be made aware whether or not an edit had come from VE as opposed to source editing.', 'For example, the Abuse Filter is aware of ""action="" but not ""veaction="".', 'At present ""action=edit"" and ""veaction=edit"" look identical to the AbuseFilter.', 'I think the suggestion that AbuseFilter should somehow be allowed process tags generated by other entities is actually an unnecessary (and more complicated) diversion.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247235,VisualEditor: Allow AbuseFilter rules to identify VE edits,"s/invisible to VE/invisible to AF/. I swear, I did proofread that. :)",task_subcomment,"['s/invisible to VE/invisible to AF/.', 'I swear, I did proofread that.', ':)']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247230,VisualEditor: Allow AbuseFilter rules to identify VE edits,"s/attempts/happens/, of course.",task_subcomment,"['s/attempts/happens/, of course.']",['SOLUTION DISCUSSION']
+247225,VisualEditor: Allow AbuseFilter rules to identify VE edits,"AF's hook attempts *during* save, in EditPage#runPostMergeFilters and ApiEditPage#execute (the second one is only used to present nicer information about saving failure in the API and is what VE is actually hitting, but that doesn't matter here).
+
+VisualEditor's ApiVisualEditorEdit calls the edit API first (#saveWikitext) and only after it has succeeded calls ChangeTags::addTags to add the tags to the edit.
+
+So to make this work, we'd have to adjust code in core, in AbuseFilter and in VE to allow passing change tags with the edit API call or in some magical way before it. It'd make the logic really awkward (since tags could now be added before/during and after making the edit, and the second kind would be invisible to VE) and likely introduce back-compat issues (for the same reason).
+
+There are also requests to make the tags editable by users (bug 18670), which generally seems like a pretty good idea, but complicates the issue here even further.
+
+So to summarize, I don't see this happening, but feel free to prove me wrong if you think you can tackle this :)",task_subcomment,"[""AF's hook attempts *during* save, in EditPage#runPostMergeFilters and ApiEditPage#execute (the second one is only used to present nicer information about saving failure in the API and is what VE is actually hitting, but that doesn't matter here)."", ""VisualEditor's ApiVisualEditorEdit calls the edit API first (#saveWikitext) and only after it has succeeded calls ChangeTags::addTags to add the tags to the edit."", ""So to make this work, we'd have to adjust code in core, in AbuseFilter and in VE to allow passing change tags with the edit API call or in some magical way before it."", ""It'd make the logic really awkward (since tags could now be added before/during and after making the edit, and the second kind would be invisible to VE) and likely introduce back-compat issues (for the same reason)."", 'There are also requests to make the tags editable by users (bug 18670), which generally seems like a pretty good idea, but complicates the issue here even further.', ""So to summarize, I don't see this happening, but feel free to prove me wrong if you think you can tackle this :)""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247220,VisualEditor: Allow AbuseFilter rules to identify VE edits,"(In reply to comment #5)
+> I'm pretty sure it's impossible to do this since any kind of tags can be only
+> added after an edit is saved (ChangeTags::addTags() function requires the
+> edit to have a know rev_id which implies that it already exists in the
+> database).
+
+Does AF's hook happen after VE's save (which applies tags), at least?",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nDoes AF's hook happen after VE's save (which applies tags), at least?""]",['SOLUTION DISCUSSION']
+247218,VisualEditor: Allow AbuseFilter rules to identify VE edits,I'm pretty sure it's impossible to do this since any kind of tags can be only added after an edit is saved (ChangeTags::addTags() function requires the edit to have a know rev_id which implies that it already exists in the database).,task_subcomment,"[""I'm pretty sure it's impossible to do this since any kind of tags can be only added after an edit is saved (ChangeTags::addTags() function requires the edit to have a know rev_id which implies that it already exists in the database).""]",['OBSERVED BUG BEHAVIOR']
+247216,VisualEditor: Allow AbuseFilter rules to identify VE edits,"**nykevin.norris** wrote:
+
+Wait, if the AbuseFilter is going to understand tags, and already applies tags, what order will filters run in?  What if a later filter applies a tag that would have triggered an earlier filter?  Should MW just keep re-running the filters until everything's been triggered?",task_subcomment,"['**nykevin.norris** wrote:\n\nWait, if the AbuseFilter is going to understand tags, and already applies tags, what order will filters run in?', 'What if a later filter applies a tag that would have triggered an earlier filter?', ""Should MW just keep re-running the filters until everything's been triggered?""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247215,VisualEditor: Allow AbuseFilter rules to identify VE edits,"Can the abusefilter detect veaction=edit. Using that and we could block edits which insert nowikis from the VE when they are almost always in error and allow them from wikitext editor, when they are normally ment.",task_subcomment,"['Can the abusefilter detect veaction=edit.', 'Using that and we could block edits which insert nowikis from the VE when they are almost always in error and allow them from wikitext editor, when they are normally ment.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247209,VisualEditor: Allow AbuseFilter rules to identify VE edits,"This would need AbuseFilter to be extended to understand tags (or, to understand VisualEditor, which seems a less satisfying and extensible way of achieving this).",task_subcomment,"['This would need AbuseFilter to be extended to understand tags (or, to understand VisualEditor, which seems a less satisfying and extensible way of achieving this).']",['SOLUTION DISCUSSION']
+247203,VisualEditor: Allow AbuseFilter rules to identify VE edits,"Both AbuseFilter and VisualEditor use change tags.  It might be possible for AbuseFilter to use VisualEditor's tag if AbuseFilter runs after, though I don't see tags mentioned at https://www.mediawiki.org/wiki/Extension:AbuseFilter/Rules_format",task_subcomment,"['Both AbuseFilter and VisualEditor use change tags.', ""It might be possible for AbuseFilter to use VisualEditor's tag if AbuseFilter runs after, though I don't see tags mentioned at URL""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53401,VisualEditor: Page loading animated image is only LTR,"The file VisualEditor/modules/ve-mw/init/styles/images/loading.gif is a ""progress bar""-like loading indicator. It is moving only left to right. It would be more natural for RTL environments if it had an RTL version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Page loading animated image is only LTR\n\nThe file VisualEditor/modules/ve-mw/init/styles/images/loading.gif is a ""progress bar""-like loading indicator.', 'It is moving only left to right.', 'It would be more natural for RTL environments if it had an RTL version.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+245958,VisualEditor: Page loading animated image is only LTR,"Change 80490 merged by jenkins-bot:
+Reverse the progress image for RTL
+
+https://gerrit.wikimedia.org/r/80490",task_subcomment,['Change 80490 merged by jenkins-bot:\nReverse the progress image for RTL\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245948,VisualEditor: Page loading animated image is only LTR,Merged. Will go out with wmf15.,task_subcomment,"['Merged.', 'Will go out with wmf15.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+245941,VisualEditor: Page loading animated image is only LTR,"Change 80490 had a related patch set uploaded by Amire80:
+Reverse the progress image for RTL
+
+https://gerrit.wikimedia.org/r/80490",task_subcomment,['Change 80490 had a related patch set uploaded by Amire80:\nReverse the progress image for RTL\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53374,TemplateData: Add parameter type for wikitext,"I would want to propose to add a type to indicate the content is contained wikitext, instead of a arbitary string. This could help VE to display a visual editor for those fields instead of showing the wikicode directly. This can't be done on ""string"" types as it's not certain they contain real wikitext. If the parameter is only to contain a single template invocation of a specific type, then perhaps a type ""template"" and a pointer to which template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52652",task_description,"['TemplateData: Add parameter type for wikitext\n\nI would want to propose to add a type to indicate the content is contained wikitext, instead of a arbitary string.', 'This could help VE to display a visual editor for those fields instead of showing the wikicode directly.', 'This can\'t be done on ""string"" types as it\'s not certain they contain real wikitext.', 'If the parameter is only to contain a single template invocation of a specific type, then perhaps a type ""template"" and a pointer to which template.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+244368,TemplateData: Add parameter type for wikitext,"Change 91624 merged by jenkins-bot:
+Specify ""content"" and ""unbalanced-wikitext"" as a valid parameter types
+
+https://gerrit.wikimedia.org/r/91624",task_subcomment,"['Change 91624 merged by jenkins-bot:\nSpecify ""content"" and ""unbalanced-wikitext"" as a valid parameter types\n\nGERRIT_URL']",['ACTION ON ISSUE']
+244362,TemplateData: Add parameter type for wikitext,"Change 91624 had a related patch set uploaded by Krinkle:
+Specify ""wiki-markup"" as a valid parameter type
+
+https://gerrit.wikimedia.org/r/91624",task_subcomment,"['Change 91624 had a related patch set uploaded by Krinkle:\nSpecify ""wiki-markup"" as a valid parameter type\n\nGERRIT_URL']",['ACTION ON ISSUE']
+244357,TemplateData: Add parameter type for wikitext,"I was going to request this, because I've seen a similar case where the parameter is to be filled with just an internal link. VisualEditor should be able to hide the wikicode markup from new users as much as possible, and this seems to be a very common place where it still appears. See e.g. the values of the parameters ""imagem_legenda"" and ""cidade"" of the [[pt:Template:Info/Bairro do Brasil]]:
+http://toolserver.org/~kolossos/templatetiger/tt-table4.php?template=Info/Bairro%20do%20Brasil&lang=ptwiki&where=&is=
+
+We see things like ""A [[Praça Dom Sebastião]], com a [[Igreja da Conceição]] ao fundo (2007).""",task_subcomment,"[""I was going to request this, because I've seen a similar case where the parameter is to be filled with just an internal link."", 'VisualEditor should be able to hide the wikicode markup from new users as much as possible, and this seems to be a very common place where it still appears.', 'See e.g.', 'the values of the parameters ""imagem_legenda"" and ""cidade"" of the [[pt:Template:Info/Bairro do Brasil]]:\nURL\n\nWe see things like ""A [[Praça Dom Sebastião]], com a [[Igreja da Conceição]] ao fundo (2007).""']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+53372,"VisualEditor: Toolbar icons - ""reference"" (bookmark) alternatives or improvements","Original icon, and 2 suggested alternatives
+
+The ""Insert reference"" icon is not very intuitive. I've made a sketch of two alternatives.
+
+See attachment, or on-wiki at http://commons.wikimedia.org/wiki/File:VisualEditor_-_Toolbar_-_Reference-edit1.png
+
+That image includes the current icon, and two adaptations that consist of: a snippet of grey text, and a blue super-scripted number [1]. 
+
+The grey text could be made into abstract letterforms - squiggles - (rather than the letters REF) in order to make it usable by all languages. 
+
+Or we could use a grey ""+"" sign with the blue [number]. 
+
+(The only problem is RightToLeft languages. Not sure how to solve that.)
+
+The blue super-scripted [number] is universally recognizable and intuitively understandable as denoting references, both in Wikimedia projects and even beyond. I'd suggest this element, at the least, should form the basis for any replacement icon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53396
+
+**Attached**: {F11513}",task_description,"['VisualEditor: Toolbar icons - ""reference"" (bookmark) alternatives or improvements\n\nOriginal icon, and 2 suggested alternatives\n\nThe ""Insert reference"" icon is not very intuitive.', ""I've made a sketch of two alternatives."", 'See attachment, or on-wiki at URL\n\nThat image includes the current icon, and two adaptations that consist of: a snippet of grey text, and a blue super-scripted number [1].', 'The grey text could be made into abstract letterforms - squiggles - (rather than the letters REF) in order to make it usable by all languages.', 'Or we could use a grey ""+"" sign with the blue [number].', '(The only problem is RightToLeft languages.', 'Not sure how to solve that.)', 'The blue super-scripted [number] is universally recognizable and intuitively understandable as denoting references, both in Wikimedia projects and even beyond.', ""I'd suggest this element, at the least, should form the basis for any replacement icon."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\n\n**Attached**: {F11513}']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+244262,"VisualEditor: Toolbar icons - ""reference"" (bookmark) alternatives or improvements",I'm going to provisionally deem this solved with the new icon.,task_subcomment,"[""I'm going to provisionally deem this solved with the new icon.""]",['SOLUTION USAGE']
+244259,"VisualEditor: Toolbar icons - ""reference"" (bookmark) alternatives or improvements","**turingt** wrote:
+
+You should include a label besides each button whenever possible. When you have a clear label, it doesn't matter that the icon is hard to recognize. And no, hover text doesn't solve the problem.",task_subcomment,"['**turingt** wrote:\n\nYou should include a label besides each button whenever possible.', ""When you have a clear label, it doesn't matter that the icon is hard to recognize."", ""And no, hover text doesn't solve the problem.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+244257,"VisualEditor: Toolbar icons - ""reference"" (bookmark) alternatives or improvements","Notes: 
+
+The current icon is stored at http://commons.wikimedia.org/wiki/File:VisualEditor_-_Icon_-_Reference.svg
+
+Threads on en.wiki which discussed the confusing design of the current icon include these:
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Icons_are_incomprehensible
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Reference_Issues:_Omnibus_Edition
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Mystery_meat_navigation
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#References
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Attempting_to_add_a_reference
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#User_experience
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Refs_and_templates
+(And one thread that reminds us that cellphones/tablets don't get hover text)",task_subcomment,"[""Notes: \n\nThe current icon is stored at URL\n\nThreads on en.wiki which discussed the confusing design of the current icon include these:\nURL\nURL\nURL\nURL\nURL\nURL\nURL\n(And one thread that reminds us that cellphones/tablets don't get hover text)""]",['BUG REPRODUCTION']
+53337,VisualEditor: Improve how we suppress reference warnings in template rendering,"Currently it's a hack; it'd be nice to be a bit less of one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50423",task_description,"[""VisualEditor: Improve how we suppress reference warnings in template rendering\n\nCurrently it's a hack; it'd be nice to be a bit less of one."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+242265,VisualEditor: Improve how we suppress reference warnings in template rendering,"Done and merged, now that wmf12 is deployed everywhere.",task_subcomment,"['Done and merged, now that wmf12 is deployed everywhere.']",['SOLUTION USAGE']
+242259,VisualEditor: Improve how we suppress reference warnings in template rendering,"Change 73614 merged by jenkins-bot:
+Use new class to detect Cite errors inside templates
+
+https://gerrit.wikimedia.org/r/73614",task_subcomment,['Change 73614 merged by jenkins-bot:\nUse new class to detect Cite errors inside templates\n\nGERRIT_URL'],['ACTION ON ISSUE']
+242251,VisualEditor: Improve how we suppress reference warnings in template rendering,"Change 73096 merged by jenkins-bot:
+Add more specific class to cite errors
+
+https://gerrit.wikimedia.org/r/73096",task_subcomment,['Change 73096 merged by jenkins-bot:\nAdd more specific class to cite errors\n\nGERRIT_URL'],['ACTION ON ISSUE']
+242243,VisualEditor: Improve how we suppress reference warnings in template rendering,https://gerrit.wikimedia.org/r/#/c/73614/,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+242234,VisualEditor: Improve how we suppress reference warnings in template rendering,"Change 73096 had a related patch set uploaded by Jforrester:
+Add more specific class to cite errors
+
+https://gerrit.wikimedia.org/r/73096",task_subcomment,['Change 73096 had a related patch set uploaded by Jforrester:\nAdd more specific class to cite errors\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+53335,VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),"The Beta notice looks strange to me: 
+http://i.imgur.com/H5n3XdD.png
+ff23 linux
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52176",task_description,['VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems)\n\nThe Beta notice looks strange to me: \nURL\nff23 linux\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL'],['OBSERVED BUG BEHAVIOR']
+242153,VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),This flyout is now much wider.,task_subcomment,['This flyout is now much wider.'],['INVESTIGATION AND EXPLORATION']
+242151,VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),*** Bug 51618 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51618 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242149,VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),"(In reply to comment #3)
+> (In reply to comment #1)
+> > Which page / URL does this happen on? And what exactly is ""strange""? The line
+> > break between ""Leave"" and ""feedback"", or anything else? Feel free to edit the
+> > bug summary to be more specific. Thanks!
+> 
+> I suspect it is the font (DejaVu?) that is common on Linux systems. It has
+> wider characters than Arial (used on Windows).
+> 
+> The Beta popup should be made a little bit wider to accommodate this font.
+
+The width is defined in terms of the font used (ems). I'm not sure how this fails due to that font - unless its em width is wrong somehow?
+
+Note that we've just changed the language in the beta notices and expanded the width to compensate (deployment will be tomorrow afternoon PDT). Interested to know if this has an impact on this issue.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe width is defined in terms of the font used (ems).', ""I'm not sure how this fails due to that font - unless its em width is wrong somehow?"", ""Note that we've just changed the language in the beta notices and expanded the width to compensate (deployment will be tomorrow afternoon PDT)."", 'Interested to know if this has an impact on this issue.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+242146,VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),"(In reply to comment #1)
+> Which page / URL does this happen on? And what exactly is ""strange""? The line
+> break between ""Leave"" and ""feedback"", or anything else? Feel free to edit the
+> bug summary to be more specific. Thanks!
+
+I suspect it is the font (DejaVu?) that is common on Linux systems. It has wider characters than Arial (used on Windows).
+
+The Beta popup should be made a little bit wider to accommodate this font.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\n\nI suspect it is the font (DejaVu?)', 'that is common on Linux systems.', 'It has wider characters than Arial (used on Windows).', 'The Beta popup should be made a little bit wider to accommodate this font.']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+242143,VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),"Screenshot
+
+Adding a screenshot of how it looks for me (Firefox22, Windows 7).
+
+**Attached**: {F11423}",task_subcomment,"['Screenshot\n\nAdding a screenshot of how it looks for me (Firefox22, Windows 7).', '**Attached**: {F11423}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242140,VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),"Which page / URL does this happen on? And what exactly is ""strange""? The line break between ""Leave"" and ""feedback"", or anything else? Feel free to edit the bug summary to be more specific. Thanks!",task_subcomment,"['Which page / URL does this happen on?', 'And what exactly is ""strange""?', 'The line break between ""Leave"" and ""feedback"", or anything else?', 'Feel free to edit the bug summary to be more specific.', 'Thanks!']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+53314,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,"Since T40551 have been resolved, it is //possible// to have per-language bold/italic button variants. But the only two languages //using// this are currently English and German. Do we really need to ask language by language, when we've been through all this with the Vector edit toolbar (see e.g. {T25625}, {T25911}, {T26188} etc.).
+
+We already have https://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons#List_by_language -- cannot we use that?
+
+----
+
+See also: https://usability.wikimedia.org/wiki/Opinion_Icons",task_description,"['VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc.', 'for scripts/languages as appropriate\n\nSince T40551 have been resolved, it is //possible// to have per-language bold/italic button variants.', 'But the only two languages //using// this are currently English and German.', ""Do we really need to ask language by language, when we've been through all this with the Vector edit toolbar (see e.g."", '{T25625}, {T25911}, {T26188} etc.).', 'We already have URL -- cannot we use that?', '----\n\nSee also: URL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+513030,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],task_subcomment,['[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366]'],['INVESTIGATION AND EXPLORATION']
+240974,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,No outstanding requests for these; closing for now as complete.,task_subcomment,['No outstanding requests for these; closing for now as complete.'],['ACTION ON ISSUE']
+240972,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,"Change 74677 merged by jenkins-bot:
+Set Malayam to use B/I rather than A/A for toolbar icons
+
+https://gerrit.wikimedia.org/r/74677",task_subcomment,['Change 74677 merged by jenkins-bot:\nSet Malayam to use B/I rather than A/A for toolbar icons\n\nGERRIT_URL'],['ACTION ON ISSUE']
+240967,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,"Change 74677 had a related patch set uploaded by Jforrester:
+Set Malayam to use B/I rather than A/A for toolbar icons
+
+https://gerrit.wikimedia.org/r/74677",task_subcomment,['Change 74677 had a related patch set uploaded by Jforrester:\nSet Malayam to use B/I rather than A/A for toolbar icons\n\nGERRIT_URL'],['ACTION ON ISSUE']
+240963,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,"(In reply to comment #2)
+> That was exactly my point is that we do not want to do that, because we have
+> already went through this with Vector. But I guess I have not expressed
+> myself clearly: I do not care about the exact image files linked there. The
+> point is that _we already know_ that Czech, Hebrew, and Polish (in addition
+> to English) want to use B/I, and we already have these images, the only
+> problem is to modify the configuration. We already know that Danish,
+> Norwegian, and Swedish (in addition to German) want to use F/K, and we
+> already have these images, the only problem is to modify the configuration.
+
+Thank you! No, ""we"" do not know, as we are not experts - but you clearly do. :-) Have created this as bug 51330. Will do this tomorrow when I'm in the office.
+
+> We also already know what letters 13 other languages would want to use, even
+> though we do not have those images ready (I guess), but the best person to
+> create those missing images is the person who created the current A/A/B/I/F/K
+> ones, I would say.
+
+Our developer/designer time is limited; we did F/K as an example for others to follow, not as a commitment that we would do this for all scripts.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThank you!', 'No, ""we"" do not know, as we are not experts - but you clearly do.', ':-) Have created this as bug 51330.', ""Will do this tomorrow when I'm in the office."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOur developer/designer time is limited; we did F/K as an example for others to follow, not as a commitment that we would do this for all scripts.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'ACTION ON ISSUE', 'FUTURE PLAN']"
+240957,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,"(In reply to comment #1)
+> (In reply to comment #0)
+> > Since bug 38551 have been resolved, it is _possible_ to have per-language
+> > bold/italic button variants.
+> 
+> That's about Vector, which is entirely irrelevant here.
+
+Really? Bug 38551 ""VisualEditor: Bold and Italic UI buttons need to be internationalisable"" fixed by https://git.wikimedia.org/commit/mediawiki%2Fextensions%2FVisualEditor/f49d80d27a757d0500b542959284a6c6bc99aebe? Anyway, that's not important.
+
+> Yes (and the Latin-generic ones).
+
+Which are wrong, that's the point.
+
+> > We already have
+> > https://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons#List_by_language
+> > --
+> > cannot we use that?
+> 
+> No. Those are low-quality PNG-only icons and not in keeping with the existing
+> VisualEditor ones. VisualEditor's interface is in SVG. We look forward to the
+> creation of such icons and would gladly include them. Turning this into a
+> tracking bug so each language can be tracked against it.
+
+That was exactly my point is that we do not want to do that, because we have already went through this with Vector. But I guess I have not expressed myself clearly: I do not care about the exact image files linked there. The point is that _we already know_ that Czech, Hebrew, and Polish (in addition to English) want to use B/I, and we already have these images, the only problem is to modify the configuration. We already know that Danish, Norwegian, and Swedish (in addition to German) want to use F/K, and we already have these images, the only problem is to modify the configuration. We also already know what letters 13 other languages would want to use, even though we do not have those images ready (I guess), but the best person to create those missing images is the person who created the current A/A/B/I/F/K ones, I would say.
+
+So: I believe I do not need to manually create 6 new bugs to request Czech, Hebrew, and Polish to have ve.ui.BoldButtonTool.static.icon switched to 'bold-b' and ve.ui.ItalicButtonTool.static.icon switched to 'italic-i', and Danish, Norwegian, and Swedish to have ve.ui.BoldButtonTool.static.icon switched to 'bold-f' and ve.ui.ItalicButtonTool.static.icon switched to 'italic-k'.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nReally?', 'Bug 38551 ""VisualEditor: Bold and Italic UI buttons need to be internationalisable"" fixed by URL Anyway, that\'s not important.', ""QUOTE\n\nWhich are wrong, that's the point."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat was exactly my point is that we do not want to do that, because we have already went through this with Vector.', 'But I guess I have not expressed myself clearly: I do not care about the exact image files linked there.', 'The point is that _we already know_ that Czech, Hebrew, and Polish (in addition to English) want to use B/I, and we already have these images, the only problem is to modify the configuration.', 'We already know that Danish, Norwegian, and Swedish (in addition to German) want to use F/K, and we already have these images, the only problem is to modify the configuration.', 'We also already know what letters 13 other languages would want to use, even though we do not have those images ready (I guess), but the best person to create those missing images is the person who created the current A/A/B/I/F/K ones, I would say.', ""So: I believe I do not need to manually create 6 new bugs to request Czech, Hebrew, and Polish to have ve.ui.BoldButtonTool.static.icon switched to 'bold-b' and ve.ui.ItalicButtonTool.static.icon switched to 'italic-i', and Danish, Norwegian, and Swedish to have ve.ui.BoldButtonTool.static.icon switched to 'bold-f' and ve.ui.ItalicButtonTool.static.icon switched to 'italic-k'.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'SOLUTION DISCUSSION']"
+240950,VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate,"(In reply to comment #0)
+> Since bug 38551 have been resolved, it is _possible_ to have per-language
+> bold/italic button variants.
+
+That's about Vector, which is entirely irrelevant here.
+
+> But the only two languages _using_ this are currently English and German.
+
+Yes (and the Latin-generic ones).
+
+> Do we really need to ask language by language, when we've been through
+> all this with the Vector edit toolbar (see e.g. bug 23625, bug 23911,
+> bug 24188 etc.).
+
+See above.
+
+> We already have
+> https://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons#List_by_language
+> --
+> cannot we use that?
+
+No. Those are low-quality PNG-only icons and not in keeping with the existing VisualEditor ones. VisualEditor's interface is in SVG. We look forward to the creation of such icons and would gladly include them. Turning this into a tracking bug so each language can be tracked against it.",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\n\nThat's about Vector, which is entirely irrelevant here."", 'QUOTE\n\nYes (and the Latin-generic ones).', 'QUOTE\nQUOTE\nQUOTE\n\nSee above.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo.', 'Those are low-quality PNG-only icons and not in keeping with the existing VisualEditor ones.', ""VisualEditor's interface is in SVG."", 'We look forward to the creation of such icons and would gladly include them.', 'Turning this into a tracking bug so each language can be tracked against it.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+53306,VisualEditor: Templated calls to  (e.g. enwiki's {{reflist}}) don't get updated whilst the user is editing,"Twice I have added a bare URL as a reference to [[Paul Robert Magocsi]], which results in the [4] and [5] being added to the right spot in the text, 
+
+but ..
+
+The references section at the bottom did not display the reference.
+
+Steps to reproduce:
+1. Click add reference button
+2. Paste in URL
+3. Click 'Create new source'
+4. Click 'Insert reference'
+(Reference dialog appears)
+5. Click 'Apply changes'
+6. View the references list at bottom of article
+
+Expected results:
+the new reference is listed
+
+Actual results:
+The added reference was not visible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Templated calls to  (e.g.', ""enwiki's {{reflist}}) don't get updated whilst the user is editing\n\nTwice I have added a bare URL as a reference to [[Paul Robert Magocsi]], which results in the [4] and [5] being added to the right spot in the text, \n\nbut .."", 'The references section at the bottom did not display the reference.', 'Steps to reproduce:\n1.', 'Click add reference button\n2.', 'Paste in URL\n3.', ""Click 'Create new source'\n4."", ""Click 'Insert reference'\n(Reference dialog appears)\n5."", ""Click 'Apply changes'\n6."", 'View the references list at bottom of article\n\nExpected results:\nthe new reference is listed\n\nActual results:\nThe added reference was not visible.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+240460,VisualEditor: Templated calls to  (e.g. enwiki's {{reflist}}) don't get updated whilst the user is editing,"Re-titling; the problem is that VisualEditor has no idea that the block of content it's been handed by Parsoid happens to contain a  call, and neither does Parsoid unless it re-parses it.
+
+Consequently, we are expanding the syntax for  to make {{reflist}} unnecessary. WONTFIXing this bug.",task_subcomment,"[""Re-titling; the problem is that VisualEditor has no idea that the block of content it's been handed by Parsoid happens to contain a  call, and neither does Parsoid unless it re-parses it."", 'Consequently, we are expanding the syntax for  to make {{reflist}} unnecessary.', 'WONTFIXing this bug.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+53295,VisualEditor: Default insert type for RTL wikis should be thumb|left not thumb|right,"An Arabic editor has reported that he/she is having difficulty with getting images to display left-justified (as they should be in RTL wikis).  How does VE handle justification of elements in RTL?  Can images be defaulted to left justify?
+This issue might apply to other elements, such as infobox templates.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Default insert type for RTL wikis should be thumb|left not thumb|right\n\nAn Arabic editor has reported that he/she is having difficulty with getting images to display left-justified (as they should be in RTL wikis).', 'How does VE handle justification of elements in RTL?', 'Can images be defaulted to left justify?', 'This issue might apply to other elements, such as infobox templates.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+239913,VisualEditor: Default insert type for RTL wikis should be thumb|left not thumb|right,"Same thing as bug 51851, and that one has more discussion despite being reported later.
+
+*** This bug has been marked as a duplicate of bug 51851 ***",task_subcomment,"['Same thing as bug 51851, and that one has more discussion despite being reported later.', '*** This bug has been marked as a duplicate of bug 51851 ***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239908,VisualEditor: Default insert type for RTL wikis should be thumb|left not thumb|right,"(In reply to comment #1)
+> Please provide an exact testcase and/or link to reproduce, and browser
+> information. Might be a dup of bug 51293?
+
+Andre, here's a test case:
+
+*Go to ar.wikipedia, a RTL wiki
+
+*Enable VE in pref.
+
+*Go to your userpage or sandbox (Google Translate is calling these ""Stadiums""!)
+
+*Use media icon to bring up dialog, pick image.
+
+*Image defaults to the right.  Attempts to click'n'drag it to the left do not work.  
+
+*Curse the LTR imperialists.
+
+Duplicated on both latest Chrome and Firefox, OS 10.6.8.",task_subcomment,"[""(In reply to comment #1)\nQUOTE\nQUOTE\n\nAndre, here's a test case:\n\n*Go to ar.wikipedia, a RTL wiki\n\n*Enable VE in pref."", '*Go to your userpage or sandbox (Google Translate is calling these ""Stadiums""!)', '*Use media icon to bring up dialog, pick image.', '*Image defaults to the right.', ""Attempts to click'n'drag it to the left do not work."", '*Curse the LTR imperialists.', 'Duplicated on both latest Chrome and Firefox, OS 10.6.8.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239904,VisualEditor: Default insert type for RTL wikis should be thumb|left not thumb|right,"Please provide an exact testcase and/or link to reproduce, and browser information. Might be a dup of bug 51293?",task_subcomment,"['Please provide an exact testcase and/or link to reproduce, and browser information.', 'Might be a dup of bug 51293?']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+53289,References inside templates don't appear in the reference list in VisualEditor,"When viewed in edit mode, references included in an infobox are not included in the references list at the bottom of the article, and the first reference in the body of an article is numbered stating from 1, ignoring any in the infobox.
+
+Example articles: [[https://en.wikipedia.org/wiki/Popocatépetl|w:en:Popocatépetl]] and [[East Toowoomba, Queensland]].
+
+Possibly related to T52474 and/or T52479
+
+**See Also**:
+T54398
+T52474
+T52749
+T54427
+T55486
+T52896",task_description,"[""References inside templates don't appear in the reference list in VisualEditor\n\nWhen viewed in edit mode, references included in an infobox are not included in the references list at the bottom of the article, and the first reference in the body of an article is numbered stating from 1, ignoring any in the infobox."", 'Example articles: [[URL and [[East Toowoomba, Queensland]].', 'Possibly related to T52474 and/or T52479\n\n**See Also**:\nT54398\nT52474\nT52749\nT54427\nT55486\nT52896']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+475204,References inside templates don't appear in the reference list in VisualEditor,"This seems to be fixed, although T52474 (which is similar) remains open.",task_subcomment,"['This seems to be fixed, although T52474 (which is similar) remains open.']",['BUG REPRODUCTION']
+239579,References inside templates don't appear in the reference list in VisualEditor,*** Bug 69066 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 69066 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239571,References inside templates don't appear in the reference list in VisualEditor,"Also, as seen by editing https://en.wikipedia.org/w/index.php?oldid=596381198 you cannot re-use any references that are within an infobox.",task_subcomment,"['Also, as seen by editing URL you cannot re-use any references that are within an infobox.']",['OBSERVED BUG BEHAVIOR']
+239564,References inside templates don't appear in the reference list in VisualEditor,Gah.,task_subcomment,['Gah.'],['OBSERVED BUG BEHAVIOR']
+239558,References inside templates don't appear in the reference list in VisualEditor,This has started happening again. See [[OpenOffice.Org]] and [[Bristol]] for examples.,task_subcomment,"['This has started happening again.', 'See [[OpenOffice.Org]] and [[Bristol]] for examples.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+239550,References inside templates don't appear in the reference list in VisualEditor,"Ok thanks for the quick reply, now reported as bug 52427",task_subcomment,"['Ok thanks for the quick reply, now reported as bug 52427']",['BUG REPRODUCTION']
+239543,References inside templates don't appear in the reference list in VisualEditor,"(In reply to comment #3)
+> Mike Christie at en.wp has reported this happening with notes defined in
+> image captions. Will the fix for this bug solve that when it is deployed or
+> should I file a separate bug?
+
+This is now deployed; references in image captions sounds like a further bug, sadly.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nThis is now deployed; references in image captions sounds like a further bug, sadly.']",['SOLUTION USAGE']
+239537,References inside templates don't appear in the reference list in VisualEditor,Mike Christie at en.wp has reported this happening with notes defined in image captions. Will the fix for this bug solve that when it is deployed or should I file a separate bug?,task_subcomment,"['Mike Christie at en.wp has reported this happening with notes defined in image captions.', 'Will the fix for this bug solve that when it is deployed or should I file a separate bug?']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+239532,References inside templates don't appear in the reference list in VisualEditor,This is now fixed due to the same fixes as bug 51741 (and in Parsoid) - they're still numbered wrongly (which is bug 50474).,task_subcomment,"[""This is now fixed due to the same fixes as bug 51741 (and in Parsoid) - they're still numbered wrongly (which is bug 50474).""]",['BUG REPRODUCTION']
+239527,References inside templates don't appear in the reference list in VisualEditor,"Sorry, that second possibly related bug should be bug 50749",task_subcomment,"['Sorry, that second possibly related bug should be bug 50749']",['OBSERVED BUG BEHAVIOR']
+53287,VisualEditor: Stronger highlight of selected item in the media inserter dialog,"From English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):
+
+When selecting an image to be inserted, the selected thumbnail has a black box around it. The lines of the box are so fine as to make them almost invisible. A much better feedback would be if, when a thumbnail is selected, it turns blue in exactly the same way as when an image in an article is selected. (A blue coloring behavior - not the same as within an article, though - does happen for some images, though not most. For example, if one searches for ""Sandbox"", four of the first twelve thumbnails do add some blue if selected, though in one case just a sliver.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Stronger highlight of selected item in the media inserter dialog\n\nFrom English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):\n\nWhen selecting an image to be inserted, the selected thumbnail has a black box around it.', 'The lines of the box are so fine as to make them almost invisible.', 'A much better feedback would be if, when a thumbnail is selected, it turns blue in exactly the same way as when an image in an article is selected.', '(A blue coloring behavior - not the same as within an article, though - does happen for some images, though not most.', 'For example, if one searches for ""Sandbox"", four of the first twelve thumbnails do add some blue if selected, though in one case just a sliver.)', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+239446,VisualEditor: Stronger highlight of selected item in the media inserter dialog,This was done as part of the re-work of the media inserter in late July; marking as such.,task_subcomment,['This was done as part of the re-work of the media inserter in late July; marking as such.'],['INVESTIGATION AND EXPLORATION']
+53274,VisualEditor: Samsung browser fails the blacklist,"VisualEditor is disabled on the built-in & default browser, which has the user agent:
+>Mozilla/5.0 (Linux; U; Android 4.0.4; en-gb; GT-N7000 Build/IMM76D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30
+
+",task_description,"['VisualEditor: Samsung browser fails the blacklist\n\nVisualEditor is disabled on the built-in & default browser, which has the user agent:\nQUOTE']",['OBSERVED BUG BEHAVIOR']
+2358759,VisualEditor: Samsung browser fails the blacklist,See {T367735},task_subcomment,['See {T367735}'],['MOTIVATION']
+497001,VisualEditor: Samsung browser fails the blacklist,"@jayvdb, ah, so it was a [[http://www.gsmarena.com/samsung_galaxy_note_n7000-4135.php|Galaxy Note N-7000]]. Thanks!",task_subcomment,"['SCREEN_NAME, ah, so it was a [[URL Note N-7000]].', 'Thanks!']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+496920,VisualEditor: Samsung browser fails the blacklist,">>! In T53274#1481575, @Neil_P._Quinn_WMF wrote:
+> @jayvdb, which device did you notice this on, ...
+
+This is in the user-agent I posted with the bug.
+
+> and what was the browser named? Just ""internet""? (Sorry, I know this is two years old!)
+
+The app icon was 'Internet' (upper case I)
+
+My phone has since been bricked & replaced, so I cant retest this bug.",task_subcomment,"['QUOTE\nQUOTE\n\nThis is in the user-agent I posted with the bug.', ""QUOTE\n\nThe app icon was 'Internet' (upper case I)\n\nMy phone has since been bricked & replaced, so I cant retest this bug.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+496795,VisualEditor: Samsung browser fails the blacklist,"@jayvdb, which device did you notice this on, and what was the browser named? Just ""internet""? (Sorry, I know this is two years old!)",task_subcomment,"['SCREEN_NAME, which device did you notice this on, and what was the browser named?', 'Just ""internet""?', '(Sorry, I know this is two years old!)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+496794,VisualEditor: Samsung browser fails the blacklist,"@jayvdb, which device did you notice this on, and what is the browser named? Just ""internet""? (Sorry, I know this is two years old!)",task_subcomment,"['SCREEN_NAME, which device did you notice this on, and what is the browser named?', 'Just ""internet""?', '(Sorry, I know this is two years old!)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+238666,VisualEditor: Samsung browser fails the blacklist,Iv given the user-agent. It is the 'Internet' browser that ships with the device. It passes the vast majority on the compliance tests for content editable.,task_subcomment,"['Iv given the user-agent.', ""It is the 'Internet' browser that ships with the device."", 'It passes the vast majority on the compliance tests for content editable.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238662,VisualEditor: Samsung browser fails the blacklist,"Safari literally doesn't exist on Android phones; there is no such thing.
+
+Some mobile browsers report themselves as compatible with Mobile Safari, which appears to be what you're seeing.",task_subcomment,"[""Safari literally doesn't exist on Android phones; there is no such thing."", ""Some mobile browsers report themselves as compatible with Mobile Safari, which appears to be what you're seeing.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238657,VisualEditor: Samsung browser fails the blacklist,Mobile Safari isnt just iOS.  It is the *default* web browser on many Android phones.,task_subcomment,"['Mobile Safari isnt just iOS.', 'It is the *default* web browser on many Android phones.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53260,Support editing  tags to set multi-column display on/off,"For VisualEditor, we are continuously-bitten by  tags that are embedded within generated content like the English Wikipedia's {{reflist}} (T52769). 
+
+It would be much easier for everyone if we just moved the features provided by such templates into [[https://www.mediawiki.org/wiki/Extension:Cite|the Cite extension]] itself and allowed such templates to be replaced by the now more powerful  tag.
+
+Points of agreement include:
+* The main requirements are for  to support multiple columns and different list styles
+** T33597 discusses defaulting to multiple columns for all reference lists
+* Columns should be implemented using [[https://developer.mozilla.org/en-US/docs/Web/CSS/column-width|column widths]] rather than [[https://developer.mozilla.org/en-US/docs/Web/CSS/column-count|column counts]], to allow flexibility based on screen size.
+
+This task is currently blocked, on the following issues:
+* What the default settings/algorithms should be
+* Whether column widths and list styles should be customizable per-page, or only per-wiki 
+* If per-page customizations are allowed, whether they should be implemented by passing through CSS properties from the invocation of the  tag or by applying CSS classes, which are then given CSS properties on a per-wiki or global level.
+
+This would involve adding:
+
+* columns (default to 1; a number between 1 and … another number? - not allowing width, obviously)
+* list-style (default to decimal; just an escaped pass-through of the CSS list-style of the OL)
+
+Then we could just bot-substitute uses of the template, and everyone would be happy.
+
+**See Also**: T53145, T8019",task_description,"[""Support editing  tags to set multi-column display on/off\n\nFor VisualEditor, we are continuously-bitten by  tags that are embedded within generated content like the English Wikipedia's {{reflist}} (T52769)."", 'It would be much easier for everyone if we just moved the features provided by such templates into [[URL Cite extension]] itself and allowed such templates to be replaced by the now more powerful  tag.', 'Points of agreement include:\n* The main requirements are for  to support multiple columns and different list styles\n** T33597 discusses defaulting to multiple columns for all reference lists\n* Columns should be implemented using [[URL widths]] rather than [[URL counts]], to allow flexibility based on screen size.', 'This task is currently blocked, on the following issues:\n* What the default settings/algorithms should be\n* Whether column widths and list styles should be customizable per-page, or only per-wiki \n* If per-page customizations are allowed, whether they should be implemented by passing through CSS properties from the invocation of the  tag or by applying CSS classes, which are then given CSS properties on a per-wiki or global level.', 'This would involve adding:\n\n* columns (default to 1; a number between 1 and … another number?', '- not allowing width, obviously)\n* list-style (default to decimal; just an escaped pass-through of the CSS list-style of the OL)\n\nThen we could just bot-substitute uses of the template, and everyone would be happy.', '**See Also**: T53145, T8019']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+932969,Support editing  tags to set multi-column display on/off,"Change 378935 merged by jenkins-bot:
+[mediawiki/extensions/Cite@master] VE: Support 'responsive' attribute
+
+[[https://gerrit.wikimedia.org/r/378935]]
+",task_subcomment,"[""Change 378935 merged by jenkins-bot:\n[mediawiki/extensions/Cite@master] VE: Support 'responsive' attribute\n\n[[GERRIT_URL]]""]",['GERRIT_URL']
+932877,Support editing  tags to set multi-column display on/off,"Change 378935 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/Cite@master] VE: Support 'responsive' attribute
+
+[[https://gerrit.wikimedia.org/r/378935]]
+",task_subcomment,"[""Change 378935 had a related patch set uploaded (by Esanders; owner: Esanders):\n[mediawiki/extensions/Cite@master] VE: Support 'responsive' attribute\n\n[[GERRIT_URL]]""]",['GERRIT_URL']
+891461,Support editing  tags to set multi-column display on/off,"FYI, I've added some support to en.wp's {{reflist}} to explicitly enable and disable automatic columns.
+Next step for en.wp will be to enables responsive by default for a plain  element
+
+This leaves the following capabilities that are specific to Reflist, which currently cannot be fulfilled with a plain references element
+# Different list item counters
+# Differing column widths (this one is also not really compatible with automatic columns, which will create a bit of a disjunct in behaviour).
+
+This doesn't negate the fact that:
+* of course reflist is already universally used, and universally changing it will probably be seen as disruptive.
+* there is also a rather large documentation gap, atm. regarding new and old information.
+* ironically, it seems that the responsive attribute cannot be set/unset from VE
+
+An idea that played in my mind, which would be terribly WMF specific, but might make it easier to work with this problem, is if we should maybe change the VE editor of  and the Template:Reflist, to be aware of each other, and maybe offer the opportunity to switch between them (""more options"", vs ""convert to references element""). Just a thought.",task_subcomment,"[""FYI, I've added some support to en.wp's {{reflist}} to explicitly enable and disable automatic columns."", 'Next step for en.wp will be to enables responsive by default for a plain  element\n\nThis leaves the following capabilities that are specific to Reflist, which currently cannot be fulfilled with a plain references element\n# Different list item counters\n# Differing column widths (this one is also not really compatible with automatic columns, which will create a bit of a disjunct in behaviour).', ""This doesn't negate the fact that:\n* of course reflist is already universally used, and universally changing it will probably be seen as disruptive."", '* there is also a rather large documentation gap, atm.', 'regarding new and old information.', '* ironically, it seems that the responsive attribute cannot be set/unset from VE\n\nAn idea that played in my mind, which would be terribly WMF specific, but might make it easier to work with this problem, is if we should maybe change the VE editor of  and the Template:Reflist, to be aware of each other, and maybe offer the opportunity to switch between them (""more options"", vs ""convert to references element"").', 'Just a thought.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+559955,Support editing  tags to set multi-column display on/off,">For VisualEditor, we are continuously-bitten by  tags that are embedded within generated content like the English Wikipedia's {{reflist}} (T52769). It would be much easier for everyone if we just moved the features provided by such templates into the Cite extension itself and allowed such templates to be replaced by the now more powerful  tag.
+
+>Reference incidences (s) inside templates are an entirely distinct problem for VisualEditor to worry about, and this isn't about that. :-)
+
+You're contradicting yourself, chuckle. I agree with the second statement, fixing VisualEditor's difficulties with templates is bug T52769. This proposal of a more powerful more powerful  tag isn't going to help that bug because communities will still have various reasons for putting things inside various templates. If that's the purpose of this bug, it's a failure when it still gets templated.
+
+This bug really only makes sense in light of something like //T33597: Render references list in multiple columns based on the number of items// which aims to add useful new functionality regardless of whether it's put inside a template.",task_subcomment,"[""QUOTE\n\nQUOTE\n\nYou're contradicting yourself, chuckle."", ""I agree with the second statement, fixing VisualEditor's difficulties with templates is bug T52769."", ""This proposal of a more powerful more powerful  tag isn't going to help that bug because communities will still have various reasons for putting things inside various templates."", ""If that's the purpose of this bug, it's a failure when it still gets templated."", ""This bug really only makes sense in light of something like //T33597: Render references list in multiple columns based on the number of items// which aims to add useful new functionality regardless of whether it's put inside a template.""]","['SOCIAL CONVERSATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+484575,Support editing  tags to set multi-column display on/off,This was discussed at the weekly meeting on 2015-06-30. We decided that it wasn't a priority for this quarter.,task_subcomment,"['This was discussed at the weekly meeting on 2015-06-30.', ""We decided that it wasn't a priority for this quarter.""]","['MOTIVATION', 'FUTURE PLAN']"
+419186,Support editing  tags to set multi-column display on/off,It should be noted that mobilefrontend already does some CSS overrides here (setting a default column width).,task_subcomment,['It should be noted that mobilefrontend already does some CSS overrides here (setting a default column width).'],['SOLUTION DISCUSSION']
+332460,Support editing  tags to set multi-column display on/off,@thiemowmde mentions T33597,task_subcomment,['SCREEN_NAME mentions T33597'],['OBSERVED BUG BEHAVIOR']
+332889,Support editing  tags to set multi-column display on/off,Just to make this clear (since I was told to say this here rather than in Gerrit): 100% agree to what Krinkle and Gabriel said. See bug 31597 (T33597) for a much more elaborate proposal.,task_subcomment,"['Just to make this clear (since I was told to say this here rather than in Gerrit): 100% agree to what Krinkle and Gabriel said.', 'See bug 31597 (T33597) for a much more elaborate proposal.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+332886,Support editing  tags to set multi-column display on/off,Just to make this clear (since I was told to say this here rather than in Gerrit): 100% agree to what Krinkle and Gabriel said. See T31597 for a much more elaborate proposal.,task_subcomment,"['Just to make this clear (since I was told to say this here rather than in Gerrit): 100% agree to what Krinkle and Gabriel said.', 'See T31597 for a much more elaborate proposal.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237920,Support editing  tags to set multi-column display on/off,Just to make this clear (since I was told to say this here rather than in Gerrit): 100% agree to what Krinkle and Gabriel said. See bug 31597 for a much more elaborate proposal.,task_subcomment,"['Just to make this clear (since I was told to say this here rather than in Gerrit): 100% agree to what Krinkle and Gabriel said.', 'See bug 31597 for a much more elaborate proposal.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+334669,Support editing  tags to set multi-column display on/off,"I fail to see how it is in anyone's best interest to implement support for list-style and column sizes on an individual `` list.
+
+These are traditionally implemented in a `{{reflist}}` template on Wikipedia. That was by all accounts a compromise due to the limited capability they have inside a template. What people want is for stuff to just work. They don't actually want to specify it manually each time.
+
+Adding this to the extension will improve nothing other than move it from a template hack to something we now have to support and maintain forwards.
+
+There has yet to be given a valid reason for why anyone would explicitly, semantically, by intent, want one specific article to have its references in a certain number of columns or certain list item number style.
+
+The number of columns should be determined by width, not hardcoded count. And while the latest patch uses width, it is still imho fundamentally flawed. Users don't want to hardcode this everywhere (authors will not know this even exists, leading to generally no single user actually using this feature other than power users, whom then have to write bots that fix it everywhere; or more likely, they'll just use another template that specified the width and list-style they agree on for that wiki).
+
+If this were any other feature, it'd be obvious this is something for the software to provide as a convenience. Not a burden for the users. Based on design considerations, can make a reasonable choice for what the column width should be. And it can be improved as we collect more data and positively influence all readers.
+
+While there may not be a perfect value, I know for sure the factors that make it less perfect don't vary by article. They vary by device, browser, etc. It will traditionally and up with authors using their personal preference for what looks right on their device.
+
+The only thing that is probably in need of variation is list-style (based on content language), which, again, seems like something we can be much smarter about. If there isn't a way to get that already from the Language infrastructure, we can provide a config variable or mediawiki-message specifying the list-style for that wiki or language. One exception could be multi-lingual wikis, so maybe provide list-style as attribute indeed.
+
+
+Note: Gabriels proposal for css classes is imho better than providing a hardcoded column-width, but per the above, we don't need either.",task_subcomment,"[""I fail to see how it is in anyone's best interest to implement support for list-style and column sizes on an individual CODE list."", 'These are traditionally implemented in a CODE template on Wikipedia.', 'That was by all accounts a compromise due to the limited capability they have inside a template.', 'What people want is for stuff to just work.', ""They don't actually want to specify it manually each time."", 'Adding this to the extension will improve nothing other than move it from a template hack to something we now have to support and maintain forwards.', 'There has yet to be given a valid reason for why anyone would explicitly, semantically, by intent, want one specific article to have its references in a certain number of columns or certain list item number style.', 'The number of columns should be determined by width, not hardcoded count.', 'And while the latest patch uses width, it is still imho fundamentally flawed.', ""Users don't want to hardcode this everywhere (authors will not know this even exists, leading to generally no single user actually using this feature other than power users, whom then have to write bots that fix it everywhere; or more likely, they'll just use another template that specified the width and list-style they agree on for that wiki)."", ""If this were any other feature, it'd be obvious this is something for the software to provide as a convenience."", 'Not a burden for the users.', 'Based on design considerations, can make a reasonable choice for what the column width should be.', 'And it can be improved as we collect more data and positively influence all readers.', ""While there may not be a perfect value, I know for sure the factors that make it less perfect don't vary by article."", 'They vary by device, browser, etc.', 'It will traditionally and up with authors using their personal preference for what looks right on their device.', 'The only thing that is probably in need of variation is list-style (based on content language), which, again, seems like something we can be much smarter about.', ""If there isn't a way to get that already from the Language infrastructure, we can provide a config variable or mediawiki-message specifying the list-style for that wiki or language."", 'One exception could be multi-lingual wikis, so maybe provide list-style as attribute indeed.', ""Note: Gabriels proposal for css classes is imho better than providing a hardcoded column-width, but per the above, we don't need either.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+334668,Support editing  tags to set multi-column display on/off,"I fail to see how it is in anyone's best interest to implement support for list-style and column sizes on an individual `` list.
+
+These are traditionally implemented in a `{{reflist}}` template on Wikipedia. That was by all accounts a compromise due to the limited capability they have inside a template. What people want is for stuff to just work. They don't actually want to specify it manually each time.
+
+Adding this to the extension will improve nothing other than move it from a template hack to something we now have to support and maintain forwards.
+
+There has yet to be given a valid reason for why anyone would explicitly, semantically, by intent, want one specific article to have its references in a certain number of columns or certain list item number style.
+
+The number of columns should be determined by width, not hardcoded count. And while the latest patch uses width, it is still imho fundamentally flawed. Users don't want to hardcode this everywhere (authors will not know this even exists, leading to generally no single user actually using this feature other than power users, whom then have to write bots that fix it everywhere; or more likely, they'll just use another template that specified the width and list-style they agree on for that wiki).
+
+If this were any other feature, it'd be obvious this is something for the software to provide as a convenience. Not a burden for the users. Based on design considerations, can make a reasonable choice for what the column width should be. And it can be improved as we collect more data and positively influence all readers.
+
+While there may not be a perfect value, I know for sure the factors that make it less perfect don't vary by article. They vary by device, browser, etc. It will traditionally and up with authors using their personal preference for what looks right on their device.
+
+The only thing that is probably in need of variation is list-style (based on content language), which, again, seems like something we can be much smarter about. If there isn't a way to get that already from the Language infrastructure, we can provide a config variable or mediawiki-message specifying the list-style for that wiki or language. One exception could be multi-lingual wikis, so maybe provide list-style as attribute indeed.
+
+
+Note: Gabriels proposal for css classes is imho better than providing a hardcoded column-width, but per the above, we don't need neither.",task_subcomment,"[""I fail to see how it is in anyone's best interest to implement support for list-style and column sizes on an individual CODE list."", 'These are traditionally implemented in a CODE template on Wikipedia.', 'That was by all accounts a compromise due to the limited capability they have inside a template.', 'What people want is for stuff to just work.', ""They don't actually want to specify it manually each time."", 'Adding this to the extension will improve nothing other than move it from a template hack to something we now have to support and maintain forwards.', 'There has yet to be given a valid reason for why anyone would explicitly, semantically, by intent, want one specific article to have its references in a certain number of columns or certain list item number style.', 'The number of columns should be determined by width, not hardcoded count.', 'And while the latest patch uses width, it is still imho fundamentally flawed.', ""Users don't want to hardcode this everywhere (authors will not know this even exists, leading to generally no single user actually using this feature other than power users, whom then have to write bots that fix it everywhere; or more likely, they'll just use another template that specified the width and list-style they agree on for that wiki)."", ""If this were any other feature, it'd be obvious this is something for the software to provide as a convenience."", 'Not a burden for the users.', 'Based on design considerations, can make a reasonable choice for what the column width should be.', 'And it can be improved as we collect more data and positively influence all readers.', ""While there may not be a perfect value, I know for sure the factors that make it less perfect don't vary by article."", 'They vary by device, browser, etc.', 'It will traditionally and up with authors using their personal preference for what looks right on their device.', 'The only thing that is probably in need of variation is list-style (based on content language), which, again, seems like something we can be much smarter about.', ""If there isn't a way to get that already from the Language infrastructure, we can provide a config variable or mediawiki-message specifying the list-style for that wiki or language."", 'One exception could be multi-lingual wikis, so maybe provide list-style as attribute indeed.', ""Note: Gabriels proposal for css classes is imho better than providing a hardcoded column-width, but per the above, we don't need neither.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237914,Support editing  tags to set multi-column display on/off,"I fail to see how it is in anyone's best interest to implement support for list-style and column sizes on an individual  list.
+
+These are traditionally implemented in a {{reflist}} template on Wikipedia. That was by all accounts a compromise due to the limited capability they have inside a template. What people want is for stuff to just work. They don't actually want to specify it manually each time.
+
+Adding this to the extension will improve nothing other than move it from a template hack to something we now have to support and maintain forwards.
+
+There has yet to be given a valid reason for why anyone would explicitly, semantically, by intent, want one specific article to have its references in a certain number of columns or certain list item number style.
+
+The number of columns should be determined by width, not hardcoded count. And while the latest patch uses width, it is still imho fundamentally flawed. Users don't want to hardcode this everywhere (authors will not know this even exists, leading to generally no single user actually using this feature other than power users, whom then have to write bots that fix it everywhere; or more likely, they'll just use another template that specified the width and list-style they agree on for that wiki).
+
+If this were any other feature, it'd be obvious this is something for the software to provide as a convenience. Not a burden for the users. Based on design considerations, can make a reasonable choice for what the column width should be. And it can be improved as we collect more data and positively influence all readers.
+
+While there may not be a perfect value, I know for sure the factors that make it less perfect don't vary by article. They vary by device, browser, etc. It will traditionally and up with authors using their personal preference for what looks right on their device.
+
+The only thing that is probably in need of variation is list-style (based on content language), which, again, seems like something we can be much smarter about. If there isn't a way to get that already from the Language infrastructure, we can provide a config variable or mediawiki-message specifying the list-style for that wiki or language. One exception could be multi-lingual wikis, so maybe provide list-style as attribute indeed.
+
+--
+
+Gabriels proposal for css classes is imho better than providing a hardcoded column-width, but per the above, we don't need neither.",task_subcomment,"[""I fail to see how it is in anyone's best interest to implement support for list-style and column sizes on an individual  list."", 'These are traditionally implemented in a {{reflist}} template on Wikipedia.', 'That was by all accounts a compromise due to the limited capability they have inside a template.', 'What people want is for stuff to just work.', ""They don't actually want to specify it manually each time."", 'Adding this to the extension will improve nothing other than move it from a template hack to something we now have to support and maintain forwards.', 'There has yet to be given a valid reason for why anyone would explicitly, semantically, by intent, want one specific article to have its references in a certain number of columns or certain list item number style.', 'The number of columns should be determined by width, not hardcoded count.', 'And while the latest patch uses width, it is still imho fundamentally flawed.', ""Users don't want to hardcode this everywhere (authors will not know this even exists, leading to generally no single user actually using this feature other than power users, whom then have to write bots that fix it everywhere; or more likely, they'll just use another template that specified the width and list-style they agree on for that wiki)."", ""If this were any other feature, it'd be obvious this is something for the software to provide as a convenience."", 'Not a burden for the users.', 'Based on design considerations, can make a reasonable choice for what the column width should be.', 'And it can be improved as we collect more data and positively influence all readers.', ""While there may not be a perfect value, I know for sure the factors that make it less perfect don't vary by article."", 'They vary by device, browser, etc.', 'It will traditionally and up with authors using their personal preference for what looks right on their device.', 'The only thing that is probably in need of variation is list-style (based on content language), which, again, seems like something we can be much smarter about.', ""If there isn't a way to get that already from the Language infrastructure, we can provide a config variable or mediawiki-message specifying the list-style for that wiki or language."", 'One exception could be multi-lingual wikis, so maybe provide list-style as attribute indeed.', ""--\n\nGabriels proposal for css classes is imho better than providing a hardcoded column-width, but per the above, we don't need neither.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237909,Support editing  tags to set multi-column display on/off,"See also:
+Bug 31597 - generate class for references list according to the number of refs",task_subcomment,['See also:\nBug 31597 - generate class for references list according to the number of refs'],['BUG REPRODUCTION']
+237903,Support editing  tags to set multi-column display on/off,"Change 123105 abandoned by Alex Monk:
+Support new column-width and list-style attributes to Cite's 
+
+Reason:
+ok done
+
+https://gerrit.wikimedia.org/r/123105",task_subcomment,"[""Change 123105 abandoned by Alex Monk:\nSupport new column-width and list-style attributes to Cite's \n\nReason:\nok done\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+237897,Support editing  tags to set multi-column display on/off,I picked up the Cite & VE parts of this again.,task_subcomment,['I picked up the Cite & VE parts of this again.'],['INVESTIGATION AND EXPLORATION']
+237890,Support editing  tags to set multi-column display on/off,"Change 123105 restored by Alex Monk:
+Support new column-width and list-style attributes to Cite's 
+
+Reason:
+Restoring so I can do a rebase to get the VE patch working
+
+https://gerrit.wikimedia.org/r/123105",task_subcomment,"[""Change 123105 restored by Alex Monk:\nSupport new column-width and list-style attributes to Cite's \n\nReason:\nRestoring so I can do a rebase to get the VE patch working\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+237884,Support editing  tags to set multi-column display on/off,"Change 123093 restored by Alex Monk:
+WIP Support new column-width & list-style attributes to Cite's 
+
+https://gerrit.wikimedia.org/r/123093",task_subcomment,"[""Change 123093 restored by Alex Monk:\nWIP Support new column-width & list-style attributes to Cite's \n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+237876,Support editing  tags to set multi-column display on/off,"Change 120962 restored by Alex Monk:
+Support setting column-width and list-style in  tag
+
+Reason:
+Going to use classes.
+
+https://gerrit.wikimedia.org/r/120962",task_subcomment,"['Change 120962 restored by Alex Monk:\nSupport setting column-width and list-style in  tag\n\nReason:\nGoing to use classes.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237868,Support editing  tags to set multi-column display on/off,Bug 22265 - Allow references to be listed with letters,task_subcomment,['Bug 22265 - Allow references to be listed with letters'],['OBSERVED BUG BEHAVIOR']
+237862,Support editing  tags to set multi-column display on/off,"No. We /are/ going to do this. Gabriel is on the hook for suggesting how to do it in a way that makes him happy, given he vetoed the agreed way. It certainly isn't ""UNCONFIRMED"".",task_subcomment,"['No.', 'We /are/ going to do this.', 'Gabriel is on the hook for suggesting how to do it in a way that makes him happy, given he vetoed the agreed way.', 'It certainly isn\'t ""UNCONFIRMED"".']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+237858,Support editing  tags to set multi-column display on/off,"Change 123093 abandoned by Alex Monk:
+WIP Support new column-width & list-style attributes to Cite's 
+
+Reason:
+Abandoning all related patch sets
+
+https://gerrit.wikimedia.org/r/123093",task_subcomment,"[""Change 123093 abandoned by Alex Monk:\nWIP Support new column-width & list-style attributes to Cite's \n\nReason:\nAbandoning all related patch sets\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+237853,Support editing  tags to set multi-column display on/off,"Change 120962 abandoned by Alex Monk:
+Support setting column-width and list-style in  tag
+
+https://gerrit.wikimedia.org/r/120962",task_subcomment,['Change 120962 abandoned by Alex Monk:\nSupport setting column-width and list-style in  tag\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+237848,Support editing  tags to set multi-column display on/off,"Change 123105 abandoned by Alex Monk:
+Support new column-width and list-style attributes to Cite's 
+
+https://gerrit.wikimedia.org/r/123105",task_subcomment,"[""Change 123105 abandoned by Alex Monk:\nSupport new column-width and list-style attributes to Cite's \n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+237843,Support editing  tags to set multi-column display on/off,See https://gerrit.wikimedia.org/r/#/c/120962/ for more discussion on this.,task_subcomment,['See URL for more discussion on this.'],['SOLUTION DISCUSSION']
+237840,Support editing  tags to set multi-column display on/off,"(In reply to Gabriel Wicke from comment #24)
+> Is there a good reason to use magic attributes and inline styles here
+> instead of CSS classes? The latter is easier to customize for different
+> environments and creates less complexity in the parsers (PHP and Parsoid).
+> 
+> All VE needs is a list of classes to offer in a drop-down or the like.
+
+Your assertion that a restricted set of classes invented by the development team will be sufficient for the community's existing wishes to be fulfilled is not met by reality…",task_subcomment,"[""(In reply to Gabriel Wicke from comment #24)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYour assertion that a restricted set of classes invented by the development team will be sufficient for the community's existing wishes to be fulfilled is not met by reality…""]",['INVESTIGATION AND EXPLORATION']
+237834,Support editing  tags to set multi-column display on/off,"Is there a good reason to use magic attributes and inline styles here instead of CSS classes? The latter is easier to customize for different environments and creates less complexity in the parsers (PHP and Parsoid).
+
+All VE needs is a list of classes to offer in a drop-down or the like.",task_subcomment,"['Is there a good reason to use magic attributes and inline styles here instead of CSS classes?', 'The latter is easier to customize for different environments and creates less complexity in the parsers (PHP and Parsoid).', 'All VE needs is a list of classes to offer in a drop-down or the like.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237828,Support editing  tags to set multi-column display on/off,"Change 123105 had a related patch set uploaded by Alex Monk:
+Support new column-width and list-style attributes to Cite's 
+
+https://gerrit.wikimedia.org/r/123105",task_subcomment,"[""Change 123105 had a related patch set uploaded by Alex Monk:\nSupport new column-width and list-style attributes to Cite's \n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+237823,Support editing  tags to set multi-column display on/off,"Change 123093 had a related patch set uploaded by Alex Monk:
+Support new column-width and list-style attributes to Cite's 
+
+https://gerrit.wikimedia.org/r/123093",task_subcomment,"[""Change 123093 had a related patch set uploaded by Alex Monk:\nSupport new column-width and list-style attributes to Cite's \n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+237818,Support editing  tags to set multi-column display on/off,"What? We don't do LATER, and haven't for over a year.",task_subcomment,"['What?', ""We don't do LATER, and haven't for over a year.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+237813,Support editing  tags to set multi-column display on/off,"IMO this should be a WONTFIX or LATER, and instead bug 6019 should be fixed.",task_subcomment,"['IMO this should be a WONTFIX or LATER, and instead bug 6019 should be fixed.']",['BUG REPRODUCTION']
+237808,Support editing  tags to set multi-column display on/off,"Change 120962 had a related patch set uploaded by Alex Monk:
+Support setting column-width and list-style in  tag
+
+https://gerrit.wikimedia.org/r/120962",task_subcomment,['Change 120962 had a related patch set uploaded by Alex Monk:\nSupport setting column-width and list-style in  tag\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237804,Support editing  tags to set multi-column display on/off,"(In reply to Alex Monk from comment #17)
+> Can someone sum up exactly what has been agreed to do here?
+
+My understanding:
+
+Do: 
+
+* Add a ""column-width"" optional property to the  element, in ems, defaulting to unspecified => one column of 100% width.
+
+** Ensure the issues about RTL display being logical are fix (you need to make sure that the columns and their contents both flow RTL).
+
+** Make it look nice. :-)
+
+** Should this default be variable as a per-wiki option?
+
+
+* Add a ""list-style"" optional property to the  element, an escaped pass-through of the CSS list-style of the OL, defaulting to decimal.
+
+** Should this default be variable as a per-wiki/per-content-language option? I can imagine there might be better alternatives for some languages than ""Arabic"" Roman decimal.
+
+
+Do not:
+
+* Add a ""columns"" property (this breaks the concept of the Web's content being fit for any sized screen and shouldn't be encouraged).
+
+* Add a new class to the  OL – the ""references"" class can be over-ridden locally by wikis if they want to change it further.
+
+
+Is this what others think?",task_subcomment,"['(In reply to Alex Monk from comment #17)\nQUOTE\n\nMy understanding:\n\nDo: \n\n* Add a ""column-width"" optional property to the  element, in ems, defaulting to unspecified => one column of 100% width.', '** Ensure the issues about RTL display being logical are fix (you need to make sure that the columns and their contents both flow RTL).', '** Make it look nice.', ':-)\n\n** Should this default be variable as a per-wiki option?', '* Add a ""list-style"" optional property to the  element, an escaped pass-through of the CSS list-style of the OL, defaulting to decimal.', '** Should this default be variable as a per-wiki/per-content-language option?', 'I can imagine there might be better alternatives for some languages than ""Arabic"" Roman decimal.', 'Do not:\n\n* Add a ""columns"" property (this breaks the concept of the Web\'s content being fit for any sized screen and shouldn\'t be encouraged).', '* Add a new class to the  OL –\xa0the ""references"" class can be over-ridden locally by wikis if they want to change it further.', 'Is this what others think?']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237801,Support editing  tags to set multi-column display on/off,Can someone sum up exactly what has been agreed to do here?,task_subcomment,['Can someone sum up exactly what has been agreed to do here?'],['SOLUTION DISCUSSION']
+237796,Support editing  tags to set multi-column display on/off,"(In reply to comment #8)
+> The references tag should support html attributes, than you can write
+>  and the template can be replaced.
+
+This is bug 6019.
+ 
+> Needs a set up a class for list-styles.
+
+Has anyone done an analysis of list-style usage on the large wikis?  I am wondering whether Cite adding a class for the group name will suffice. (i.e. emitting class=""references references-$group $invocationClassesVal"") 
+
+I agree with others that Cite shouldn't add explicit support for columns, as this is very device-dependent; a class attribute indirectly provides this and more.",task_subcomment,"['(In reply to comment #8)\nQUOTE\nQUOTE\n\nThis is bug 6019.', 'QUOTE\n\nHas anyone done an analysis of list-style usage on the large wikis?', 'I am wondering whether Cite adding a class for the group name will suffice.', '(i.e.', 'emitting class=""references references-$group $invocationClassesVal"") \n\nI agree with others that Cite shouldn\'t add explicit support for columns, as this is very device-dependent; a class attribute indirectly provides this and more.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+237791,Support editing  tags to set multi-column display on/off,"Multiple columns for references causes two major usability issues:
+
+1. When there is only one reference and this reference is longer than the column width, it is split into several parts, causing gaps inside the reference. This gets even worse for bidi texts: If you have a reference in a right-to-left language inside a left-to-right context, and it is split into multiple columns, you have to start reading on the right end of the left column, read to the left, jump right to the next column, read to the left again, etc.
+
+2. When the list of references is longer than the screen and a reference breaks into two columns, you have to scroll to read it. This means:
+a) You click the superscript number, the browser sends you to the upper part of the reference.
+b) You have to scroll down to the beginning of the reference and start reading.
+c) You have to scroll up again to the second part and continue reading.
+d) If you don't know that you can use your browser's ""back"" function, you have to scroll down again to get to the back link.
+
+Both issues could be solved by using ""break-inside: avoid-column;"", but the browser support currently is very poor. So unless browser support for this improves in future or somebody writes a JS solution for it, multi-column reference lists are a bad idea for usability reasons.",task_subcomment,"['Multiple columns for references causes two major usability issues:\n\n1.', 'When there is only one reference and this reference is longer than the column width, it is split into several parts, causing gaps inside the reference.', 'This gets even worse for bidi texts: If you have a reference in a right-to-left language inside a left-to-right context, and it is split into multiple columns, you have to start reading on the right end of the left column, read to the left, jump right to the next column, read to the left again, etc.', '2.', 'When the list of references is longer than the screen and a reference breaks into two columns, you have to scroll to read it.', 'This means:\na) You click the superscript number, the browser sends you to the upper part of the reference.', 'b) You have to scroll down to the beginning of the reference and start reading.', 'c) You have to scroll up again to the second part and continue reading.', 'd) If you don\'t know that you can use your browser\'s ""back"" function, you have to scroll down again to get to the back link.', 'Both issues could be solved by using ""break-inside: avoid-column;"", but the browser support currently is very poor.', 'So unless browser support for this improves in future or somebody writes a JS solution for it, multi-column reference lists are a bad idea for usability reasons.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+237786,Support editing  tags to set multi-column display on/off,"For the record, both column-count and column-width are fully automated CSS properties in the browser. It's 1 line of code to tell the browser, and then browsers handle it natively for us. No development on our side to split the list or anything like that.",task_subcomment,"['For the record, both column-count and column-width are fully automated CSS properties in the browser.', ""It's 1 line of code to tell the browser, and then browsers handle it natively for us."", 'No development on our side to split the list or anything like that.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237781,Support editing  tags to set multi-column display on/off,"column-count is terrible indeed, especially for liquid layouts like in MediaWiki skins. When viewing it on a narrower window, it becomes unreadable.
+
+column-width is a much more sensible approach, though I find it hard to believe either makes sense to be specified on the individual reflist. What I've seen in practice (at least on nl.wikipedia) that there is authors who know about it and explicitly use reflist with 2 columns in all their articles, and others who don't know about it, and others who prefer 3 for whatever reason.
+
+The result is a chaos if different column counts per article.
+
+When incorporating this back into the Cite extension, we can also provide a better default based on whatever really makes sense to derive it from. Whatever the rational is for needing multiple columns (mostly for readability I presume as the lines become too wide, and the list too long), we can automate that trivially based on rational UX arguments (yes, there shall be a global wiki bikeshed about why 2 is better than 3). Probably deriving it from the number of references in the list.
+
+column-width will allow the list to fold back into 1 column on smaller devices and people who just like to narrow their window, and multiply out as the window gets wider. Of course this problem isn't entirely specific to references lists, it's also a long outstanding petpeeve of various designers about the article content itself, a fluid layout makes that content hard to read as well in some cases (though a fixed layout is probably better than multi-column in that case).
+
+",task_subcomment,"['column-count is terrible indeed, especially for liquid layouts like in MediaWiki skins.', 'When viewing it on a narrower window, it becomes unreadable.', 'column-width is a much more sensible approach, though I find it hard to believe either makes sense to be specified on the individual reflist.', ""What I've seen in practice (at least on nl.wikipedia) that there is authors who know about it and explicitly use reflist with 2 columns in all their articles, and others who don't know about it, and others who prefer 3 for whatever reason."", 'The result is a chaos if different column counts per article.', 'When incorporating this back into the Cite extension, we can also provide a better default based on whatever really makes sense to derive it from.', 'Whatever the rational is for needing multiple columns (mostly for readability I presume as the lines become too wide, and the list too long), we can automate that trivially based on rational UX arguments (yes, there shall be a global wiki bikeshed about why 2 is better than 3).', 'Probably deriving it from the number of references in the list.', 'column-width will allow the list to fold back into 1 column on smaller devices and people who just like to narrow their window, and multiply out as the window gets wider.', ""Of course this problem isn't entirely specific to references lists, it's also a long outstanding petpeeve of various designers about the article content itself, a fluid layout makes that content hard to read as well in some cases (though a fixed layout is probably better than multi-column in that case)."", '']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237775,Support editing  tags to set multi-column display on/off,What about the {{reflist}} variants on en.wiki such as {{notelist}}?,task_subcomment,['What about the {{reflist}} variants on en.wiki such as {{notelist}}?'],['SOLUTION DISCUSSION']
+237769,Support editing  tags to set multi-column display on/off,"The plwp infobox  is here:
+https://pl.wikipedia.org/wiki/Szablon:Infobox_uwagi_dodaj",task_subcomment,['The plwp infobox  is here:\nURL'],['OBSERVED BUG BEHAVIOR']
+237761,Support editing  tags to set multi-column display on/off,"(In reply to comment #7)
+> I don't understand what you're saying? This is an enhancement about users
+> frequently using a template to achieve a trivial software feature, and so 
+> building that into reference lists (s) rather than having them
+> need to invent and use the template.
+> 
+> Reference incidences (s) inside templates are an entirely distinct
+> problem
+> for VisualEditor to worry about, and this isn't about that. :-)
+
+This bug seems to be about enhancing  so people won't (often?) have to embed  in templates.  However, I think db's point is that there are other reasons (besides {{reflist}}) that  may be in a template.  The example Bartosz gave (Carles Puyol) boils down (after a few template layers) to [[pl:Szablon:Infobox_uwagi_dodaj]], which has its own references tag with a custom infobox group.  As shown at [[pl:Carles Puyol]], the effect is a small notes list just for the infobox.",task_subcomment,"[""(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis bug seems to be about enhancing  so people won't (often?)"", 'have to embed  in templates.', ""However, I think db's point is that there are other reasons (besides {{reflist}}) that  may be in a template."", 'The example Bartosz gave (Carles Puyol) boils down (after a few template layers) to [[pl:Szablon:Infobox_uwagi_dodaj]], which has its own references tag with a custom infobox group.', 'As shown at [[pl:Carles Puyol]], the effect is a small notes list just for the infobox.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237756,Support editing  tags to set multi-column display on/off,"(In reply to comment #3)
+> Also, some wikis include more stuff in their reflist-like templates; for
+> example [[pl:Template:Przypisy]] unconditionally includes the heading.
+
+Indeed. The equivalent template on Portuguese Wikipedia is also used to generate the header, and also has parameters to change the header text as well as its level (
    , 
    , ...):
+https://pt.wikipedia.org/wiki/Template:Referências",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\n\nIndeed.', 'The equivalent template on Portuguese Wikipedia is also used to generate the header, and also has parameters to change the header text as well as its level (
    , 
    , ...):\nURL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+237751,Support editing  tags to set multi-column display on/off,"The references tag should support html attributes, than you can write  and the template can be replaced.
+
+Needs a set up a class for list-styles.
+
+The extra class=""reflist"" is unneeded, because the references tag already adds class=""references"".
+
+Thats why you can already add
+
+.references { column-width: 35em; -moz-column-width: 35em; -webkit-column-width: 35em; }
+
+to your common.css/user.css and all references will have column width, no need to tag each references tag with its own class.
+
+
+But the template has the advanced, that syntax errors will not eat the rest of the page.",task_subcomment,"['The references tag should support html attributes, than you can write  and the template can be replaced.', 'Needs a set up a class for list-styles.', 'The extra class=""reflist"" is unneeded, because the references tag already adds class=""references"".', 'Thats why you can already add\n\n.references { column-width: 35em; -moz-column-width: 35em; -webkit-column-width: 35em; }\n\nto your common.css/user.css and all references will have column width, no need to tag each references tag with its own class.', 'But the template has the advanced, that syntax errors will not eat the rest of the page.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION']"
+237747,Support editing  tags to set multi-column display on/off,"(In reply to comment #5)
+> You will become also problems with  in infobox templates or so on, that
+> means you need another soluation than add a new tag or maintain a hardcoded
+> template list in VisualEditor.
+
+I don't understand what you're saying? This is an enhancement about users frequently using a template to achieve a trivial software feature, and so  building that into reference lists (s) rather than having them need to invent and use the template.
+
+Reference incidences (s) inside templates are an entirely distinct problem for VisualEditor to worry about, and this isn't about that. :-)",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\n\nI don't understand what you're saying?"", 'This is an enhancement about users frequently using a template to achieve a trivial software feature, and so  building that into reference lists (s) rather than having them need to invent and use the template.', ""Reference incidences (s) inside templates are an entirely distinct problem for VisualEditor to worry about, and this isn't about that."", ':-)']","['ACTION ON ISSUE', 'FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+237743,Support editing  tags to set multi-column display on/off,"(In reply to comment #5)
+> You will become also problems with  in infobox templates or so on, that
+> means you need another soluation than add a new tag or maintain a hardcoded
+> template list in VisualEditor.
+
+Hm, yeah, I didn't think about it, but some infoboxes include their own s *and* , for example pl.wp infoboxes for football players and some other sportsmen; an example can be seen on [[pl:Carles Puyol]].",task_subcomment,"[""(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\n\nHm, yeah, I didn't think about it, but some infoboxes include their own s *and* , for example pl.wp infoboxes for football players and some other sportsmen; an example can be seen on [[pl:Carles Puyol]].""]",['MOTIVATION']
+237738,Support editing  tags to set multi-column display on/off,"You will become also problems with  in infobox templates or so on, that means you need another soluation than add a new tag or maintain a hardcoded template list in VisualEditor.",task_subcomment,"['You will become also problems with  in infobox templates or so on, that means you need another soluation than add a new tag or maintain a hardcoded template list in VisualEditor.']",['SOLUTION DISCUSSION']
+237733,Support editing  tags to set multi-column display on/off,"(In reply to comment #3)
+> Also, some wikis include more stuff in their reflist-like templates; for
+> example [[pl:Template:Przypisy]] unconditionally includes the heading.
+> 
+> (In reply to comment #2)
+> > > ""Obviously""? In my opinion setting maximalcolumn width and letting the
+> > > browser figure out the layout makes more sense than hardcoded number
+> > > (although sadly it's not how it's done right now).
+> > 
+> > We should be reducing, not increasing, the use of hard-coded widths. HTML is
+> > not a graphical layout language, and should not be bastardised to serve as
+> > such.
+> 
+> Hardcoding the number of columns is the same, except worse, since it can't be
+> adjusted to the capabilities of the browser/device without violating CSS
+> spec.
+> 
+> CSS only allows specifying column width ""hints"", anyway, and they can be
+> measured in ems.
+> https://developer.mozilla.org/en-US/docs/Web/CSS/column-width
+
+OK, then I suppose we should maintain equivalence with {{reflist}} here.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOK, then I suppose we should maintain equivalence with {{reflist}} here.']",['SOLUTION DISCUSSION']
+237728,Support editing  tags to set multi-column display on/off,"Also, some wikis include more stuff in their reflist-like templates; for example [[pl:Template:Przypisy]] unconditionally includes the heading.
+
+(In reply to comment #2)
+> > ""Obviously""? In my opinion setting maximalcolumn width and letting the
+> > browser figure out the layout makes more sense than hardcoded number (although
+> > sadly it's not how it's done right now).
+> 
+> We should be reducing, not increasing, the use of hard-coded widths. HTML is
+> not a graphical layout language, and should not be bastardised to serve as
+> such.
+
+Hardcoding the number of columns is the same, except worse, since it can't be adjusted to the capabilities of the browser/device without violating CSS spec.
+
+CSS only allows specifying column width ""hints"", anyway, and they can be measured in ems. https://developer.mozilla.org/en-US/docs/Web/CSS/column-width",task_subcomment,"['Also, some wikis include more stuff in their reflist-like templates; for example [[pl:Template:Przypisy]] unconditionally includes the heading.', ""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nHardcoding the number of columns is the same, except worse, since it can't be adjusted to the capabilities of the browser/device without violating CSS spec."", 'CSS only allows specifying column width ""hints"", anyway, and they can be measured in ems.', 'URL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237721,Support editing  tags to set multi-column display on/off,"(In reply to comment #1)
+> (In reply to comment #0)
+> > * columns (default to 1; a number between 1 and … another number? - not
+> > allowing width, obviously)
+> 
+> ""Obviously""? In my opinion setting maximalcolumn width and letting the
+> browser figure out the layout makes more sense than hardcoded number (although
+> sadly it's not how it's done right now).
+
+We should be reducing, not increasing, the use of hard-coded widths. HTML is not a graphical layout language, and should not be bastardised to serve as such.
+
+> > * list-style (default to decimal; just an escaped pass-through of the CSS
+> > list-style of the OL)
+> 
+> That would be a bad way to do this; the list style should actually depends on
+> the group name used (since Cite has a way to provide custom markers instead
+> of [1] to reference citations, list-style is used to match them - see
+> [[Special:PrefixIndex/MediaWiki:Cite_link_label_group]] for ones defined on
+> en.wp).
+
+Sorry, yes, I meant ""default to what the group states; if no group, default to decimal; otherwise, let the user over-ride"".",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe should be reducing, not increasing, the use of hard-coded widths.', 'HTML is not a graphical layout language, and should not be bastardised to serve as such.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nSorry, yes, I meant ""default to what the group states; if no group, default to decimal; otherwise, let the user over-ride"".']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+237712,Support editing  tags to set multi-column display on/off,"(In reply to comment #0)
+> * columns (default to 1; a number between 1 and … another number? - not
+> allowing width, obviously)
+
+""Obviously""? In my opinion setting maximalcolumn width and letting the browser figure out the layout makes more sense than hardcoded number (although sadly it's not how it's done right now).
+
+
+> * list-style (default to decimal; just an escaped pass-through of the CSS
+> list-style of the OL)
+
+That would be a bad way to do this; the list style should actually depends on the group name used (since Cite has a way to provide custom markers instead of [1] to reference citations, list-style is used to match them - see [[Special:PrefixIndex/MediaWiki:Cite_link_label_group]] for ones defined on en.wp).",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\n\n""Obviously""?', ""In my opinion setting maximalcolumn width and letting the browser figure out the layout makes more sense than hardcoded number (although sadly it's not how it's done right now)."", 'QUOTE\nQUOTE\n\nThat would be a bad way to do this; the list style should actually depends on the group name used (since Cite has a way to provide custom markers instead of [1] to reference citations, list-style is used to match them - see [[Special:PrefixIndex/MediaWiki:Cite_link_label_group]] for ones defined on en.wp).']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53253,VisualEditor: Remove obsolete retry token logic in mw.Target,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,['VisualEditor: Remove obsolete retry token logic in mw.Target\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'],['OBSERVED BUG BEHAVIOR']
+237265,VisualEditor: Remove obsolete retry token logic in mw.Target,"Change 76860 merged by jenkins-bot:
+mw.Target: Removed unreachable badtoken recovery code
+
+https://gerrit.wikimedia.org/r/76860",task_subcomment,['Change 76860 merged by jenkins-bot:\nmw.Target: Removed unreachable badtoken recovery code\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+237256,VisualEditor: Remove obsolete retry token logic in mw.Target,"Change 76860 had a related patch set uploaded by Krinkle:
+Removed unreachable badtoken recovery code
+
+https://gerrit.wikimedia.org/r/76860",task_subcomment,['Change 76860 had a related patch set uploaded by Krinkle:\nRemoved unreachable badtoken recovery code\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+237246,VisualEditor: Remove obsolete retry token logic in mw.Target,"It also ignored the fact that the new token may be logged out or for a different user, though this was previous OK-ish because it was only to load the content which is a read action and not a write action (hence why we fixed that API recently to no longer require a token)",task_subcomment,"['It also ignored the fact that the new token may be logged out or for a different user, though this was previous OK-ish because it was only to load the content which is a read action and not a write action (hence why we fixed that API recently to no longer require a token)']",['INVESTIGATION AND EXPLORATION']
+237239,VisualEditor: Remove obsolete retry token logic in mw.Target,"onLoad no longer requires or even considers a token, so this is now obsolete.",task_subcomment,"['onLoad no longer requires or even considers a token, so this is now obsolete.']",['BUG REPRODUCTION']
+53251,Install Notifications (Echo) on the Polish Wikipedia,"Please install Notifications (Echo) on the Polish Wikipedia. I think the community supports this in general.
+
+Is it even possible? It seems some similar requests were rejected (bug 50064?).
+
+I'll start a straw poll to confirm this after it's made clear that the request will be fulfilled (I don't want to bother them otherwise).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52510",task_description,"['Install Notifications (Echo) on the Polish Wikipedia\n\nPlease install Notifications (Echo) on the Polish Wikipedia.', 'I think the community supports this in general.', 'Is it even possible?', 'It seems some similar requests were rejected (bug 50064?).', ""I'll start a straw poll to confirm this after it's made clear that the request will be fulfilled (I don't want to bother them otherwise)."", '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+237169,Install Notifications (Echo) on the Polish Wikipedia,"I'm pretty sure this can be closed now :) Thanks, Fabrice!",task_subcomment,"[""I'm pretty sure this can be closed now :) Thanks, Fabrice!""]",['ACTION ON ISSUE']
+237162,Install Notifications (Echo) on the Polish Wikipedia,"Sorry, I meant to say 'translate to Polish' (not 'Swedish'). My apologies, I am juggling a number of parallel releases and am using more copy-and-paste than I should. ;o)",task_subcomment,"[""Sorry, I meant to say 'translate to Polish' (not 'Swedish')."", 'My apologies, I am juggling a number of parallel releases and am using more copy-and-paste than I should.', ';o)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237158,Install Notifications (Echo) on the Polish Wikipedia,"Hello Bartosz,
+
+Thanks for bringing up the question about FlaggedRevs. At this point, we do not plan support these events, and will not be able to implement this request in the near-term, sadly.
+
+In the meantime, I would like to make sure that all is ready on your end for our August 20 release.
+
+If you haven't already, we recommend you do the following for this proposed release:
+
+* Confirm on Meta that the Notifications interface has been properly translated to Swedish -- update the translations if needed.
+
+* Translate and create a Polish version of this help page, which links from the tool's interface (question marks on flyout and archive):
+http://www.mediawiki.org/wiki/Help:Notifications
+
+* Go over the checklist in this Notifications release plan and determine if you need to make any special adjustments (e.g. default user settings):
+http://www.mediawiki.org/wiki/Echo/Release_Plan_2013
+
+Thanks so much for your interest in this tool. I look forward to working with you soon.",task_subcomment,"['Hello Bartosz,\n\nThanks for bringing up the question about FlaggedRevs.', 'At this point, we do not plan support these events, and will not be able to implement this request in the near-term, sadly.', 'In the meantime, I would like to make sure that all is ready on your end for our August 20 release.', ""If you haven't already, we recommend you do the following for this proposed release:\n\n* Confirm on Meta that the Notifications interface has been properly translated to Swedish -- update the translations if needed."", ""* Translate and create a Polish version of this help page, which links from the tool's interface (question marks on flyout and archive):\nURL\n\n* Go over the checklist in this Notifications release plan and determine if you need to make any special adjustments (e.g."", 'default user settings):\nURL\n\nThanks so much for your interest in this tool.', 'I look forward to working with you soon.']","['SOLUTION DISCUSSION', 'FUTURE PLAN', 'FUTURE PLAN', 'FUTURE PLAN', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237149,Install Notifications (Echo) on the Polish Wikipedia,"By the way, I just noticed that Echo doesn't provide notifications for events related to the FlaggedRevs extension pl.wp has installed, in particular the act of ""sighting"" a page (similar to how page patrolling in core works).
+
+I filed bug 52510 about this. It's not a deployment blocker, but it would be *really* nice to have it.",task_subcomment,"['By the way, I just noticed that Echo doesn\'t provide notifications for events related to the FlaggedRevs extension pl.wp has installed, in particular the act of ""sighting"" a page (similar to how page patrolling in core works).', 'I filed bug 52510 about this.', ""It's not a deployment blocker, but it would be *really* nice to have it.""]","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+237142,Install Notifications (Echo) on the Polish Wikipedia,"Wonderful, thank you!
+
+Let's reconnect after Wikimania, around Aug. 15, to see if there are any final questions before the scheduled Aug. 20 deployment, which should take place at about 21:00 CET.
+
+Cheers!",task_subcomment,"['Wonderful, thank you!', ""Let's reconnect after Wikimania, around Aug. 15, to see if there are any final questions before the scheduled Aug. 20 deployment, which should take place at about 21:00 CET."", 'Cheers!']","['SOLUTION USAGE', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+237134,Install Notifications (Echo) on the Polish Wikipedia,"I have copied relevant pages from the English Wikipedia to:
+* https://pl.wikipedia.org/wiki/Wikipedia:Powiadomienia
+* https://pl.wikipedia.org/wiki/Wikipedia:Powiadomienia/FAQ
+
+They should get translated and adjusted before the deployment.",task_subcomment,['I have copied relevant pages from the English Wikipedia to:\n* URL\n* URL\n\nThey should get translated and adjusted before the deployment.'],['INVESTIGATION AND EXPLORATION']
+237126,Install Notifications (Echo) on the Polish Wikipedia,And thanks for responding :) I'll forward this information to the community.,task_subcomment,"[""And thanks for responding :) I'll forward this information to the community.""]",['ACTION ON ISSUE']
+237117,Install Notifications (Echo) on the Polish Wikipedia,"(In reply to comment #3)
+> It would be great if someone could start translating this FAQ page to Polish,
+> and give us the URL, so we can link the help icons to that page when the tool
+> is released in late August:
+> http://en.wikipedia.org/wiki/Wikipedia:Notifications/FAQ
+
+Then this page should be copied somewhere that is not English Wikipedia and that has the Translate extension installed.
+
+VisualEditor's FAQ and help pages were being translated on mediawiki.org and copied to the wikis later, but Meta would do just as fine here.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThen this page should be copied somewhere that is not English Wikipedia and that has the Translate extension installed.', ""VisualEditor's FAQ and help pages were being translated on mediawiki.org and copied to the wikis later, but Meta would do just as fine here.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+237109,Install Notifications (Echo) on the Polish Wikipedia,"Hi Bartosz,
+
+Glad to hear that the Polish community has reached consensus for deployment of Notifications this summer. We are very happy to have you as one of our first pilot sites for this tool!
+
+Our current target date for this deployment is now set to Tuesday, August 20th at about 12pm PT (~21:00 Central European Time, if I am correct).
+
+It would be great if someone could start translating this FAQ page to Polish, and give us the URL, so we can link the help icons to that page when the tool is released in late August:
+http://en.wikipedia.org/wiki/Wikipedia:Notifications/FAQ
+
+We plan to deploy Notifications to MetaWiki tomorrow, which will give us a first preview of how the tool works in languages other than English. 
+
+Please let us know if you gave any questions, comments or suggestions.
+
+Look forward to working with you on this release!",task_subcomment,"['Hi Bartosz,\n\nGlad to hear that the Polish community has reached consensus for deployment of Notifications this summer.', 'We are very happy to have you as one of our first pilot sites for this tool!', 'Our current target date for this deployment is now set to Tuesday, August 20th at about 12pm PT (~21:00 Central European Time, if I am correct).', 'It would be great if someone could start translating this FAQ page to Polish, and give us the URL, so we can link the help icons to that page when the tool is released in late August:\nURL\n\nWe plan to deploy Notifications to MetaWiki tomorrow, which will give us a first preview of how the tool works in languages other than English.', 'Please let us know if you gave any questions, comments or suggestions.', 'Look forward to working with you on this release!']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'FUTURE PLAN', 'SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+237101,Install Notifications (Echo) on the Polish Wikipedia,"Straw poll: https://pl.wikipedia.org/wiki/Wikipedia:KT#Nowy_system_powiadomie.C5.84
+
+Overwhelming support, 21/2/2 right now :)
+
+Can we get a more precise estimate on ""later this summer""?",task_subcomment,"['Straw poll: URL\n\nOverwhelming support, 21/2/2 right now :)\n\nCan we get a more precise estimate on ""later this summer""?']",['ACTION ON ISSUE']
+237095,Install Notifications (Echo) on the Polish Wikipedia,"Hi Bartosz,
+
+Yes, we are now looking for a few wikis who want Notifications right away, so we can deploy it on their sites later this summer.
+
+Let us know what the Polish community thinks. If the straw poll is favorable, we can include you in our short list of summer deployments (which now includes Meta and the French Wikipedia).
+
+Thanks for taking the time to suggest this!",task_subcomment,"['Hi Bartosz,\n\nYes, we are now looking for a few wikis who want Notifications right away, so we can deploy it on their sites later this summer.', 'Let us know what the Polish community thinks.', 'If the straw poll is favorable, we can include you in our short list of summer deployments (which now includes Meta and the French Wikipedia).', 'Thanks for taking the time to suggest this!']","['FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+53237,VisualEditor: Add the capacity for help pages in dialogs,"So, for example, the template dialogue. Once you're in it, there's not really any guidance on what you should do: as intuitive as we can ultimately make it, there will always be some confusion. It would be good if the VisualEditor had space for some kind of help icon that would link, in a new tab/window, to a pertinent help page on the specific wiki: we could set up MediaWiki namespace pages that provide the wiki-specific link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51798",task_description,"['VisualEditor: Add the capacity for help pages in dialogs\n\nSo, for example, the template dialogue.', ""Once you're in it, there's not really any guidance on what you should do: as intuitive as we can ultimately make it, there will always be some confusion."", 'It would be good if the VisualEditor had space for some kind of help icon that would link, in a new tab/window, to a pertinent help page on the specific wiki: we could set up MediaWiki namespace pages that provide the wiki-specific link.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE']"
+236277,VisualEditor: Add the capacity for help pages in dialogs,"Instead of help /pages/ we've decided to go with help /popups/, per bug 51798.",task_subcomment,"[""Instead of help /pages/ we've decided to go with help /popups/, per bug 51798.""]",['INVESTIGATION AND EXPLORATION']
+53217,Implement way to round-trip tables with fosterable content that migrates out of the table,"Simple example:
+
+{|
+foo
+|}
+
+This doesn't RT correctly. 
+
+Real world test case: [[All-Ireland_Senior_Camogie_Championship_1992]]
+Related report: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#A_simple_table_gets_doubled_after_an_unrelated_edit_of_plain_text
+
+Interestingly enough, we have more robust handling for templated content.  The example below is handled properly and RTs correctly.
+
+{|
+{{echo|foo}}
+|}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53402",task_description,"[""Implement way to round-trip tables with fosterable content that migrates out of the table\n\nSimple example:\n\n{|\nfoo\n|}\n\nThis doesn't RT correctly."", 'Real world test case: [[All-Ireland_Senior_Camogie_Championship_1992]]\nRelated report: URL\n\nInterestingly enough, we have more robust handling for templated content.', 'The example below is handled properly and RTs correctly.', '{|\n{{echo|foo}}\n|}\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235289,Implement way to round-trip tables with fosterable content that migrates out of the table,"Fix deployed, but cache is not yet purged. The purge will happen tomorrow.",task_subcomment,"['Fix deployed, but cache is not yet purged.', 'The purge will happen tomorrow.']","['WORKAROUNDS', 'OBSERVED BUG BEHAVIOR']"
+235279,Implement way to round-trip tables with fosterable content that migrates out of the table,"Change 78242 merged by jenkins-bot:
+(Bug 52638) Fix selser regression introduced by fix for bug 51217
+
+https://gerrit.wikimedia.org/r/78242",task_subcomment,['Change 78242 merged by jenkins-bot:\n(Bug 52638) Fix selser regression introduced by fix for bug 51217\n\nGERRIT_URL'],['ACTION ON ISSUE']
+235271,Implement way to round-trip tables with fosterable content that migrates out of the table,"Change 78242 had a related patch set uploaded by Subramanya Sastry:
+(Bug 52638) Fix selser regression introduced by fix for bug 51217
+
+https://gerrit.wikimedia.org/r/78242",task_subcomment,['Change 78242 had a related patch set uploaded by Subramanya Sastry:\n(Bug 52638) Fix selser regression introduced by fix for bug 51217\n\nGERRIT_URL'],['BUG REPRODUCTION']
+235262,Implement way to round-trip tables with fosterable content that migrates out of the table,Now deployed in production.  I tested dummy test cases and it seems to work.  Would be good to keep an eye out for this in production.,task_subcomment,"['Now deployed in production.', 'I tested dummy test cases and it seems to work.', 'Would be good to keep an eye out for this in production.']","['SOLUTION USAGE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+235257,Implement way to round-trip tables with fosterable content that migrates out of the table,Another related patch: https://gerrit.wikimedia.org/r/#/c/76324/,task_subcomment,['Another related patch: URL'],['BUG REPRODUCTION']
+235254,Implement way to round-trip tables with fosterable content that migrates out of the table,Currently undergoing rt-testing and will be deployed Monday/Tuesday.,task_subcomment,['Currently undergoing rt-testing and will be deployed Monday/Tuesday.'],['WORKAROUNDS']
+235250,Implement way to round-trip tables with fosterable content that migrates out of the table,"Change 75253 merged by jenkins-bot:
+(Bug 51217) Detect fostered content and ignore in selser
+
+https://gerrit.wikimedia.org/r/75253",task_subcomment,['Change 75253 merged by jenkins-bot:\n(Bug 51217) Detect fostered content and ignore in selser\n\nGERRIT_URL'],['BUG REPRODUCTION']
+235246,Implement way to round-trip tables with fosterable content that migrates out of the table,*** Bug 51993 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51993 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235242,Implement way to round-trip tables with fosterable content that migrates out of the table,*** Bug 51964 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51964 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235237,Implement way to round-trip tables with fosterable content that migrates out of the table,"Change 75253 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 51217) Detect fostered content and ignore in selser
+
+https://gerrit.wikimedia.org/r/75253",task_subcomment,['Change 75253 had a related patch set uploaded by Subramanya Sastry:\nWIP: (Bug 51217) Detect fostered content and ignore in selser\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+235232,Implement way to round-trip tables with fosterable content that migrates out of the table,*** Bug 50754 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50754 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235226,Implement way to round-trip tables with fosterable content that migrates out of the table,This looks very similar to bug 50754.,task_subcomment,['This looks very similar to bug 50754.'],['MOTIVATION']
+235222,Implement way to round-trip tables with fosterable content that migrates out of the table,"From IRC:
+[14:44]  subbu, re https://bugzilla.wikimedia.org/show_bug.cgi?id=51217#c9: we should be able to detect when something was fostered out by our treebuilder, and should also be able to ensure that everything fosterable is dropped or fostered at the end of DOMPostProcessing
+[14:45]  yeah, I wonder what he is up to
+[14:45]  in that example, what do we do with the information at all .. itis not helpful since the output still looks corrupt.
+[14:45]  subbu: IMO it is fine to drop such content on edit, but if we can avoid dirty diffs with selser then that would be great
+[14:46]  we could strip the fostered content from the DOM
+[14:46]  is it the right thing to do in general?
+[14:46]  and rig selser so that it restores it unless the content is touched 
+[14:47]  or we can keep it in the DOM, but mark it so that selser does not serialize it
+[14:47]  ie, a zero-length dsr
+[14:48]  yes, the rig-selser bit is missing right now.
+[14:48]  subbu: detecting foster-parented content and then excluding it from dsr calculations might already be pretty effective
+[14:49]  I guess the gaps in dsr would be spanned by the dsr algorithm
+[14:49]  yes, that should work.
+[14:49]  (the holes where content disappeared)
+[14:50]  i was wondering if we should mark blocks of fostered content with a special div/marker so that VE can treat it specially if there is a use-case for it (not sure there is ..)
+[14:50]  subbu: I'd vote for data-parsoid
+[14:50]  data-parsoid is fine for internal use.
+[14:50]  if the user edits the fostered content, we serialize it
+[14:50]  i.e., do the dirty diff then
+[14:51]  but, i mean: if VE can do something special if it knew about it.  not sure what that would be .. i doubt this is a high priority thing in any case.
+[14:51]  when something adjacent to the former location is edited, we dirty-diff it there
+[14:51]  subbu: IMO we should abstract such issues
+[14:52]  bot authors would not want to deal with it either
+[14:52]  and the DOM should reflect the rendered semantics 
+[14:53]  dom should reflect rendered semantics for sure.",task_subcomment,"['From IRC:\n[14:44]  subbu, re URL we should be able to detect when something was fostered out by our treebuilder, and should also be able to ensure that everything fosterable is dropped or fostered at the end of DOMPostProcessing\n[14:45]  yeah, I wonder what he is up to\n[14:45]  in that example, what do we do with the information at all .. itis not helpful since the output still looks corrupt.', '[14:45]  subbu: IMO it is fine to drop such content on edit, but if we can avoid dirty diffs with selser then that would be great\n[14:46]  we could strip the fostered content from the DOM\n[14:46]  is it the right thing to do in general?', '[14:46]  and rig selser so that it restores it unless the content is touched \n[14:47]  or we can keep it in the DOM, but mark it so that selser does not serialize it\n[14:47]  ie, a zero-length dsr\n[14:48]  yes, the rig-selser bit is missing right now.', '[14:48]  subbu: detecting foster-parented content and then excluding it from dsr calculations might already be pretty effective\n[14:49]  I guess the gaps in dsr would be spanned by the dsr algorithm\n[14:49]  yes, that should work.', ""[14:49]  (the holes where content disappeared)\n[14:50]  i was wondering if we should mark blocks of fostered content with a special div/marker so that VE can treat it specially if there is a use-case for it (not sure there is ..)\n[14:50]  subbu: I'd vote for data-parsoid\n[14:50]  data-parsoid is fine for internal use."", '[14:50]  if the user edits the fostered content, we serialize it\n[14:50]  i.e., do the dirty diff then\n[14:51]  but, i mean: if VE can do something special if it knew about it.', 'not sure what that would be .. i doubt this is a high priority thing in any case.', '[14:51]  when something adjacent to the former location is edited, we dirty-diff it there\n[14:51]  subbu: IMO we should abstract such issues\n[14:52]  bot authors would not want to deal with it either\n[14:52]  and the DOM should reflect the rendered semantics \n[14:53]  dom should reflect rendered semantics for sure.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235215,Implement way to round-trip tables with fosterable content that migrates out of the table,"So, I investigated the bug with this page (https://en.wikipedia.org/w/index.php?title=List_of_Jessie_episodes&diff=564684769&oldid=564554799) (comment #3 above).  
+
+This is quite nasty and nothing to do with foster parenting as I mistakenly/hastily believed.  The page has since been edited to remove the problematic wikitext (https://en.wikipedia.org/w/index.php?title=List_of_Jessie_episodes&diff=564803163&oldid=564788048) so the problem will no longer manifest there.
+
+However, here is a snippet from 
+
+{{Episode list
+ |EpisodeNumber   = 1
+...
+...
+ |ProdCode        = 101
+ |Viewers         = ...
+...
+...
+|}
+
+Note the input to the 'ProdCode' param.  Here is a snippet for the template source of Episode list (https://en.wikipedia.org/w/index.php?title=Template:Episode_list&action=edit)
+
+... {{{ProdCode}}} ...
+
+See what that will do with the parameter passed in from the page.  Here is the expanded source that Parsoid sees:
+
+... "">101 ...
+
+So, that td-tag is totally broken and Parsoid renders that as literal text (rather than a html td tag) which then promptly gets fostered out (by Parsoid itself) which then adds noise to the HTML output which is what you see when you opened that page in VE (see video above added by AzaToth). 
+
+The editor Geraldo Perez has already fixed the page as I indicated earlier, so this is not a problem anymore.
+
+But, I dont think we should even bother trying to handle broken wikitext like this.  We do go to great lengths to fixup/handler broken wikitext while still preserving it as far as possible to not introduce dirty diffs, but dirty diffs are sometimes inevitable in situations like this.  So for now, I am going to classify this example as unfixable in Parsoid, unless someone has smart ideas.",task_subcomment,"['So, I investigated the bug with this page (URL (comment #3 above).', 'This is quite nasty and nothing to do with foster parenting as I mistakenly/hastily believed.', 'The page has since been edited to remove the problematic wikitext (URL so the problem will no longer manifest there.', 'However, here is a snippet from \n\n{{Episode list\n |EpisodeNumber   = 1\n...\n...\n |ProdCode        = 101\n |Viewers         = ...\n...\n...\n|}\n\nNote the input to the \'ProdCode\' param.', 'Here is a snippet for the template source of Episode list (URL\n\n... {{{ProdCode}}} ...\n\nSee what that will do with the parameter passed in from the page.', 'Here is the expanded source that Parsoid sees:\n\n... "">101 ...', 'So, that td-tag is totally broken and Parsoid renders that as literal text (rather than a html td tag) which then promptly gets fostered out (by Parsoid itself) which then adds noise to the HTML output which is what you see when you opened that page in VE (see video above added by AzaToth).', 'The editor Geraldo Perez has already fixed the page as I indicated earlier, so this is not a problem anymore.', 'But, I dont think we should even bother trying to handle broken wikitext like this.', 'We do go to great lengths to fixup/handler broken wikitext while still preserving it as far as possible to not introduce dirty diffs, but dirty diffs are sometimes inevitable in situations like this.', 'So for now, I am going to classify this example as unfixable in Parsoid, unless someone has smart ideas.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235209,Implement way to round-trip tables with fosterable content that migrates out of the table,"(In reply to comment #7)
+> The problem on the VE end is that foster-parenting happens already when the
+> browser parses the received HTML. Doing a simple string comparison with the
+> received HTML won't normally work because of quoting differences.
+This is right. We have no reasonable way to tell whether the browser's HTML parser introduced changes, because inferring anything about the HTML string requires using the browser's HTML parser which... well you get the idea.
+
+On the Parsoid end, this is easier to detect, because you have the original DOM. You could serialize that DOM to a string, then parse it into a DOM again, and compare that against the original DOM using .isEqualNode() (if that exists in your DOM library; alternatively, use your DOM differ).",task_subcomment,"['(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\nThis is right.', ""We have no reasonable way to tell whether the browser's HTML parser introduced changes, because inferring anything about the HTML string requires using the browser's HTML parser which... well you get the idea."", 'On the Parsoid end, this is easier to detect, because you have the original DOM.', 'You could serialize that DOM to a string, then parse it into a DOM again, and compare that against the original DOM using .isEqualNode() (if that exists in your DOM library; alternatively, use your DOM differ).']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+235203,Implement way to round-trip tables with fosterable content that migrates out of the table,The problem on the VE end is that foster-parenting happens already when the browser parses the received HTML. Doing a simple string comparison with the received HTML won't normally work because of quoting differences.,task_subcomment,"['The problem on the VE end is that foster-parenting happens already when the browser parses the received HTML.', ""Doing a simple string comparison with the received HTML won't normally work because of quoting differences.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235198,Implement way to round-trip tables with fosterable content that migrates out of the table,"On the Parsoid end, detecting that the page cannot be handle is equivalent to fixing it.  Same analysis work has to be done.  On the VE end, perhaps they could use the 've-needscheck' verification to detect something like this -- that is something that VE developers can respond to best.  Adding Roan to this ticket who might be better able to answer that part.",task_subcomment,"['On the Parsoid end, detecting that the page cannot be handle is equivalent to fixing it.', 'Same analysis work has to be done.', ""On the VE end, perhaps they could use the 've-needscheck' verification to detect something like this -- that is something that VE developers can respond to best."", 'Adding Roan to this ticket who might be better able to answer that part.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+235192,Implement way to round-trip tables with fosterable content that migrates out of the table,"Why not just disable VE on pages like these for now. Edit page, parsoid render, ""VisualEditor encountered a structure that it currently cannot handle. You will be redirected to the source editor.""
+
+Breaking pages == bad.",task_subcomment,"['Why not just disable VE on pages like these for now.', 'Edit page, parsoid render, ""VisualEditor encountered a structure that it currently cannot handle.', 'You will be redirected to the source editor.""', 'Breaking pages == bad.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+235185,Implement way to round-trip tables with fosterable content that migrates out of the table,See http://youtu.be/QYgkdnQ6Yng for realtime feeling about the issue,task_subcomment,['See URL for realtime feeling about the issue'],['OBSERVED BUG BEHAVIOR']
+235177,Implement way to round-trip tables with fosterable content that migrates out of the table,"Looks like this corruption is because content gets fostered out of the table on
+load in VE.  One more instance of fosterable content that needs to be handled.
+
+https://en.wikipedia.org/w/index.php?title=List_of_Jessie_episodes&diff=564684769&oldid=564554799",task_subcomment,"['Looks like this corruption is because content gets fostered out of the table on\nload in VE.', 'One more instance of fosterable content that needs to be handled.', 'URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+235171,Implement way to round-trip tables with fosterable content that migrates out of the table,"(In reply to comment #1)
+> Jotting down an idea:
+> 
+> https://gerrit.wikimedia.org/r/#/c/73369/ is going to add tag-ids to dom
+> elements.  Since they are added linearly, it will always be the case that
+> tag-id(node) < tag-id(node.nextSibling) and tag-id(node) < tag-id(node.child)
+> except when a child is fostered out. 
+
+http://www.mediawiki.org/w/index.php?title=Parsoid/Todo&oldid=554715#DOM_tree_builder is making a cameo appearance ;)
+
+After detection we'll have to figure out a way to make this work with selser though. Simply enlarging the start tag width to include the fostered content won't work. Fostered content can also come from several places in the table. The best is probably to prevent selser from serializing any of the fostered content, but serialize all of it when a part of it is edited.
+
+Generally we should not try to do more than avoiding dirty diffs. On edit to the fostered content (or even the table in general) we should take the liberty to fix the wikitext to more closely mirror the way that content actually renders.",task_subcomment,"[""(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nURL is making a cameo appearance ;)\n\nAfter detection we'll have to figure out a way to make this work with selser though."", ""Simply enlarging the start tag width to include the fostered content won't work."", 'Fostered content can also come from several places in the table.', 'The best is probably to prevent selser from serializing any of the fostered content, but serialize all of it when a part of it is edited.', 'Generally we should not try to do more than avoiding dirty diffs.', 'On edit to the fostered content (or even the table in general) we should take the liberty to fix the wikitext to more closely mirror the way that content actually renders.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235166,Implement way to round-trip tables with fosterable content that migrates out of the table,"Jotting down an idea:
+
+https://gerrit.wikimedia.org/r/#/c/73369/ is going to add tag-ids to dom elements.  Since they are added linearly, it will always be the case that tag-id(node) < tag-id(node.nextSibling) and tag-id(node) < tag-id(node.child) except when a child is fostered out. 
+
+So, we could actually use these tag ids to robustly detect fostered content and add some encapsulation typeof and about ids on the content and the table so that VE as well as Parsoid's serializer can deal with it.",task_subcomment,"['Jotting down an idea:\n\nURL is going to add tag-ids to dom elements.', 'Since they are added linearly, it will always be the case that tag-id(node) < tag-id(node.nextSibling) and tag-id(node) < tag-id(node.child) except when a child is fostered out.', ""So, we could actually use these tag ids to robustly detect fostered content and add some encapsulation typeof and about ids on the content and the table so that VE as well as Parsoid's serializer can deal with it.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+53202,Draw VisualEditor's non-CE block highlights using SVG polygons,"Shields/phantoms are currently recursively applying to protected elements and positioning additional elements inside them. This causes 2 major problems:
+
+1. Very slow, the CSS selectors use * and adding and controlling all these elements takes a lot of time as well.
+
+2. We are limited to a single rectangle per protected node, which for inline elements is especially problematic since they are meant to wrap.
+
+Using getClientRect and getClientRects (for inline stuff) can give us bounding box information that we can then cache, and render polygon click blocks for using an SVG layer. SVG's pointer-events: none works across browsers (unlike using this property in HTML) so we can control which elements in the SVG rendering block or pass through.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64709",task_description,"[""Draw VisualEditor's non-CE block highlights using SVG polygons\n\nShields/phantoms are currently recursively applying to protected elements and positioning additional elements inside them."", 'This causes 2 major problems:\n\n1.', 'Very slow, the CSS selectors use * and adding and controlling all these elements takes a lot of time as well.', '2.', 'We are limited to a single rectangle per protected node, which for inline elements is especially problematic since they are meant to wrap.', 'Using getClientRect and getClientRects (for inline stuff) can give us bounding box information that we can then cache, and render polygon click blocks for using an SVG layer.', ""SVG's pointer-events: none works across browsers (unlike using this property in HTML) so we can control which elements in the SVG rendering block or pass through."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE']"
+1901354,Draw VisualEditor's non-CE block highlights using SVG polygons,"Change 434103 **abandoned** by Bartosz Dziewoński:
+%%%[VisualEditor/VisualEditor@master] [WIP] FocusableNode: Allow the highlights to have holes (using SVG)%%%
+Reason:
+%%%%%%
+https://gerrit.wikimedia.org/r/434103",task_subcomment,['Change 434103 **abandoned** by Bartosz Dziewoński:\n%%%[VisualEditor/VisualEditor@master] [WIP] FocusableNode: Allow the highlights to have holes (using SVG)%%%\nReason:\n%%%%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1071105,Draw VisualEditor's non-CE block highlights using SVG polygons,">>! In T53202#542648, @Esanders wrote:
+> We are now using getBoundingClientRect and getClientRects. The only part missing from this bug is to use SVG. We should investigate the performance benefits/losses of doing so.
+
+This was implemented in {ee5b69772963c5d3f17b15742023cf33fc5dd48a} and I think that actually resolved all of the original performance concerns. I don't think switching the  `
    ` to  `` is likely to improve or worsen performance. I am only doing it because it gives us the flexibility to have non-rectangular highlights.
+
+----
+
+> Using getClientRect and getClientRects (for inline stuff) can give us bounding box information that we can then cache, and render polygon click blocks for using an SVG layer. SVG's pointer-events: none works across browsers (unlike using this property in HTML) so we can control which elements in the SVG rendering block or pass through.
+
+>>! In T53202#2280692, @Esanders wrote:
+> In order to prevent the SVG canvas (a bounding rectangle) from capturing click events we'd need to set pointer-events, which would mean this wouldn't work on IE<11
+
+This sounds like the idea was to use a single `` tag covering the whole page, but made unclickable with `pointer-events: none`, with `` or something for individual highlights.
+
+I think we should stick to smaller `` tags covering just the focusable node (like the current `
    ` tags). This seems like a potentially not very well-tested area in browsers, and it would be nice if any bugs affecting the new highlights (whether in our code or in browser code) were localised to just the highlight instead of breaking the entire page. For example, when I was playing with it yesterday, my first implementation had such large `` tags, and it caused the mouse cursor to rapidly flicker between regular pointer and text cursor while over it (I couldn't reproduce that again, but James saw it happen :) ).
+
+(These days we only support IE 11, so the only remaining browser that has no support for 'pointer-events' in HTML is Opera 12; it only supports the property in SVG.)",task_subcomment,"['QUOTE\nQUOTE\n\nThis was implemented in {ee5b69772963c5d3f17b15742023cf33fc5dd48a} and I think that actually resolved all of the original performance concerns.', ""I don't think switching the  CODE to  CODE is likely to improve or worsen performance."", 'I am only doing it because it gives us the flexibility to have non-rectangular highlights.', '----\n\nQUOTE\n\nQUOTE\nQUOTE\n\nThis sounds like the idea was to use a single CODE tag covering the whole page, but made unclickable with CODE, with CODE or something for individual highlights.', 'I think we should stick to smaller CODE tags covering just the focusable node (like the current CODE tags).', 'This seems like a potentially not very well-tested area in browsers, and it would be nice if any bugs affecting the new highlights (whether in our code or in browser code) were localised to just the highlight instead of breaking the entire page.', ""For example, when I was playing with it yesterday, my first implementation had such large CODE tags, and it caused the mouse cursor to rapidly flicker between regular pointer and text cursor while over it (I couldn't reproduce that again, but James saw it happen :) )."", ""(These days we only support IE 11, so the only remaining browser that has no support for 'pointer-events' in HTML is Opera 12; it only supports the property in SVG.)""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION']"
+1070925,Draw VisualEditor's non-CE block highlights using SVG polygons,"Change 434103 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[VisualEditor/VisualEditor@master] [WIP] FocusableNode: Allow the highlights to have holes (using SVG)
+
+[[https://gerrit.wikimedia.org/r/434103]]",task_subcomment,['Change 434103 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):\n[VisualEditor/VisualEditor@master] [WIP] FocusableNode: Allow the highlights to have holes (using SVG)\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+659399,Draw VisualEditor's non-CE block highlights using SVG polygons,"In order to prevent the SVG canvas (a bounding rectangle) from capturing click events we'd need to set pointer-events, which would mean this wouldn't work on IE<11",task_subcomment,"[""In order to prevent the SVG canvas (a bounding rectangle) from capturing click events we'd need to set pointer-events, which would mean this wouldn't work on IE<11""]",['OBSERVED BUG BEHAVIOR']
+332565,Draw VisualEditor's non-CE block highlights using SVG polygons,">>! In T53202#781046, @Esanders wrote:
+> This is not high priority
+
+Investigating performance options is generally always a priority. But you're probably right that it won't be hugely beneficial.",task_subcomment,"['QUOTE\nQUOTE\n\nInvestigating performance options is generally always a priority.', ""But you're probably right that it won't be hugely beneficial.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+332561,Draw VisualEditor's non-CE block highlights using SVG polygons,This is not high priority,task_subcomment,['This is not high priority'],['INVESTIGATION AND EXPLORATION']
+234397,Draw VisualEditor's non-CE block highlights using SVG polygons,We are now using getBoundingClientRect and getClientRects. The only part missing from this bug is to use SVG. We should investigate the performance benefits/losses of doing so.,task_subcomment,"['We are now using getBoundingClientRect and getClientRects.', 'The only part missing from this bug is to use SVG.', 'We should investigate the performance benefits/losses of doing so.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+234392,Draw VisualEditor's non-CE block highlights using SVG polygons,"@Trevor: Thanks for writing it down. I'm pretty excited about working on it. Btw. in the meantime, I'm working on shields/phantoms performance optimization here: https://gerrit.wikimedia.org/r/#/c/72113/",task_subcomment,"['SCREEN_NAME: Thanks for writing it down.', ""I'm pretty excited about working on it."", 'Btw.', ""in the meantime, I'm working on shields/phantoms performance optimization here: URL""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+53179,Re-enable user preference to disable VisualEditor,"The user preference for disabling VisualEditor has gone missing. It should be restored.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",task_description,"['Re-enable user preference to disable VisualEditor\n\nThe user preference for disabling VisualEditor has gone missing.', 'It should be restored.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233349,Re-enable user preference to disable VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 50929 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50929 ***'],['ISSUE CONTENT MANAGEMENT']
+233344,Re-enable user preference to disable VisualEditor,"The user preference should appear under the ""Editing"" tab at [[Special:Preferences]], where editors naturally expect to find it.",task_subcomment,"['The user preference should appear under the ""Editing"" tab at [[Special:Preferences]], where editors naturally expect to find it.']",['SOLUTION DISCUSSION']
+53151,Print helpful 'your API is not reachable' message instead of TypeError: Cannot set property '0' of null at Object.WikiConfig,"**Author:** `stephdechine`
+
+**Description:**
+I have just installed Parsoid for my private MediaWiki. However when I try to use VisualEditor, I got parsoidserver-http-bad-status: 500. Then I had checked localhost:8000, and that page displays correctly, but http://localhost:8000/en/Main_Page does not work as expected, and some error messages are thrown out.
+
+ TypeError: Cannot set property '0' of null
+    at Object.WikiConfig (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/lib/mediawiki.WikiConfig.js:52:29)
+    at Function.MWParserEnvironment.getParserEnv (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/lib/mediawiki.parser.environment.js:268:16)
+    at getParserServiceEnv (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/api/ParserService.js:365:22)
+    at app.post.oldid (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/api/ParserService.js:629:2)
+    at callbacks (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:272:11)
+    at param (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:246:11)
+    at pass (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:253:5)
+    at Router._dispatch (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:280:5)
+    at Object.Router.middleware [as handle] (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:45:10)
+    at next (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/node_modules/connect/lib/http.js:204:15)
+
+My OS is Gentoo Linux with everything up-to-date.
+
+I fetched the Parsoid extension by using git.
+
+I have once tried to install nodejs by compiling the source code, but failed due to ""Syntax error"" when running ./configure . Then I had checked my OS repo, and found out that there is only net-libs/nodejs with no npm. I installed that.
+
+net-libs/nodejs Installed versions:  0.10.8^t(19:04:51 07/10/13)
+(masked by default, I unmasked that.)
+
+And the remaining installation process are with no error.
+
+I copied the api/localsettings.js.example to api/localsettings.js and changed the localhost to the IP address. Debug options is uncommented. Others remain the same.
+
+That is all I have done to the whole Parsoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",task_description,"[""Print helpful 'your API is not reachable' message instead of TypeError: Cannot set property '0' of null at Object.WikiConfig\n\n**Author:** CODE\n\n**Description:**\nI have just installed Parsoid for my private MediaWiki."", 'However when I try to use VisualEditor, I got parsoidserver-http-bad-status: 500.', 'Then I had checked localhost:8000, and that page displays correctly, but URL does not work as expected, and some error messages are thrown out.', ""TypeError: Cannot set property '0' of null\n    at Object.WikiConfig (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/lib/mediawiki.WikiConfig.js:52:29)\n    at Function.MWParserEnvironment.getParserEnv (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/lib/mediawiki.parser.environment.js:268:16)\n    at getParserServiceEnv (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/api/ParserService.js:365:22)\n    at app.post.oldid (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/api/ParserService.js:629:2)\n    at callbacks (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:272:11)\n    at param (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:246:11)\n    at pass (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:253:5)\n    at Router._dispatch (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:280:5)\n    at Object.Router.middleware [as handle] (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/lib/router/index.js:45:10)\n    at next (/var/www/localhost/htdocs/wiki/extensions/Parsoid/js/node_modules/express/node_modules/connect/lib/http.js:204:15)\n\nMy OS is Gentoo Linux with everything up-to-date."", 'I fetched the Parsoid extension by using git.', 'I have once tried to install nodejs by compiling the source code, but failed due to ""Syntax error"" when running ./configure .', 'Then I had checked my OS repo, and found out that there is only net-libs/nodejs with no npm.', 'I installed that.', 'net-libs/nodejs Installed versions:  0.10.8^t(19:04:51 07/10/13)\n(masked by default, I unmasked that.)', 'And the remaining installation process are with no error.', 'I copied the api/localsettings.js.example to api/localsettings.js and changed the localhost to the IP address.', 'Debug options is uncommented.', 'Others remain the same.', 'That is all I have done to the whole Parsoid.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231553,Print helpful 'your API is not reachable' message instead of TypeError: Cannot set property '0' of null at Object.WikiConfig,"**stephdechine** wrote:
+
+(In reply to comment #2)
+> I also see that you are using Node 0.10.8.  Note that currently Parsoid only
+> supports node 0.8
+> (http://www.mediawiki.org/wiki/Parsoid#Use_node.js_0.8.2C_not_0.10)
+
+Thank you for pointing out that. After I downgrade node.js to 0.8.23 everything works correctly. My fault. That works for me.",task_subcomment,"['**stephdechine** wrote:\n\n(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nThank you for pointing out that.', 'After I downgrade node.js to 0.8.23 everything works correctly.', 'My fault.', 'That works for me.']","['ACTION ON ISSUE', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+231547,Print helpful 'your API is not reachable' message instead of TypeError: Cannot set property '0' of null at Object.WikiConfig,I also see that you are using Node 0.10.8.  Note that currently Parsoid only supports node 0.8 (http://www.mediawiki.org/wiki/Parsoid#Use_node.js_0.8.2C_not_0.10),task_subcomment,"['I also see that you are using Node 0.10.8.', 'Note that currently Parsoid only supports node 0.8 (URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+231541,Print helpful 'your API is not reachable' message instead of TypeError: Cannot set property '0' of null at Object.WikiConfig,"Your wiki API is not reachable from the Parsoid machine. Configure it correctly in localsettings.js and verify that it is indeed reachable using wget, curl, w3m or any other tool of your choice.
+
+Example commandline:
+
+curl 
+
+We should probably print this information when the config request fails. Repurposing this bug for that.",task_subcomment,"['Your wiki API is not reachable from the Parsoid machine.', 'Configure it correctly in localsettings.js and verify that it is indeed reachable using wget, curl, w3m or any other tool of your choice.', 'Example commandline:\n\ncurl \n\nWe should probably print this information when the config request fails.', 'Repurposing this bug for that.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+53148,VisualEditor: Newline migration issue,"As discovered in bug 50120, we need to find out what this is and fix it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Newline migration issue\n\nAs discovered in bug 50120, we need to find out what this is and fix it.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+512010,VisualEditor: Newline migration issue,"@Jdforrester-WMF, can we close this? T52120 has been resolved.",task_subcomment,"['SCREEN_NAME-WMF, can we close this?', 'T52120 has been resolved.']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+496798,VisualEditor: Newline migration issue,"@Jdforrester-WMF, can we close this? T52120 has been resolved.",task_subcomment,"['SCREEN_NAME-WMF, can we close this?', 'T52120 has been resolved.']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+53146,"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit","From English Wikipedia:
+
+I've not yet done a lot with refs and reflists (a lot of my work is stub-sorting where it rarely crops up) but.... 
+
+Editing Howard Wilson Elementary School I changed the number of columns of {{reflist}} from 2 to 1 (there's only one ref and it looks daft over 2 cols). The whole reflist disappeared, while I stayed in VE - see edit summary. On saving the page, it was there all present and correct.
+
+This is one of several instances where VE alarms the editor: if it's supposed to be a Visual Editor, it needs to reflect changes made and not give the impression that the template has been deleted. Worrying enough for an experienced editor - totally offputting for someone new.
+
+Apologies if this exact problem, or a more generalised case, is already tracked. PamD 16:38, 9 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit\n\nFrom English Wikipedia:\n\nI've not yet done a lot with refs and reflists (a lot of my work is stub-sorting where it rarely crops up) but...."", ""Editing Howard Wilson Elementary School I changed the number of columns of {{reflist}} from 2 to 1 (there's only one ref and it looks daft over 2 cols)."", 'The whole reflist disappeared, while I stayed in VE - see edit summary.', 'On saving the page, it was there all present and correct.', ""This is one of several instances where VE alarms the editor: if it's supposed to be a Visual Editor, it needs to reflect changes made and not give the impression that the template has been deleted."", 'Worrying enough for an experienced editor - totally offputting for someone new.', 'Apologies if this exact problem, or a more generalised case, is already tracked.', 'PamD 16:38, 9 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+489986,"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit",">>! In T53146#1442033, @Esanders wrote:
+> Where is the bug to move all the functionality over to the  tag making {{reflist}} redundant?
+
+https://phabricator.wikimedia.org/maniphest/query/7.xI5WLmYTc1/#R pffers some tasks about //specific// (not: //all//) functionality...",task_subcomment,['QUOTE\nQUOTE\n\nURL pffers some tasks about //specific// (not: //all//) functionality...'],['SOLUTION DISCUSSION']
+489448,"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit",Where is the bug to move all the functionality over to the  tag making {{reflist}} redundant?,task_subcomment,['Where is the bug to move all the functionality over to the  tag making {{reflist}} redundant?'],['BUG REPRODUCTION']
+231122,"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit","(In reply to James Forrester from comment #2)
+> This will be fixed when we switch over to Parsoid rendering the templates
+> mid-edit rather than rely on PHP parser.
+
+As follow-up, right now we don't have a way to give context to Parsoid, so when parsing a template that generates part of a wider structure – e.g. a cell, row or section of a table – we just give the template itself, contextless.
+
+This means that Parsoid (correctly) returns a fostered-out block, which we (correctly) splice into the location, meaning the document looks very odd. However, it saves fine.
+
+In the future we'd need a way to tell Parsoid that ""this is an update to transclusion id=1234 in structure id=4321"" or something so Parsoid has context; I assume this will need to wait until Parsoid puts GUIDs into the source for us.",task_subcomment,"[""(In reply to James Forrester from comment #2)\nQUOTE\nQUOTE\n\nAs follow-up, right now we don't have a way to give context to Parsoid, so when parsing a template that generates part of a wider structure – e.g."", 'a cell, row or section of a table – we just give the template itself, contextless.', 'This means that Parsoid (correctly) returns a fostered-out block, which we (correctly) splice into the location, meaning the document looks very odd.', 'However, it saves fine.', 'In the future we\'d need a way to tell Parsoid that ""this is an update to transclusion id=1234 in structure id=4321"" or something so Parsoid has context; I assume this will need to wait until Parsoid puts GUIDs into the source for us.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+231112,"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit",*** Bug 67856 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 67856 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231103,"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit",This will be fixed when we switch over to Parsoid rendering the templates mid-edit rather than rely on PHP parser.,task_subcomment,['This will be fixed when we switch over to Parsoid rendering the templates mid-edit rather than rely on PHP parser.'],['SOLUTION DISCUSSION']
+231094,"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit",Confirmed. This one's especially annoying given how common {{reflist}} is. See also bug 50075 (which I was no longer able to reproduce).,task_subcomment,"['Confirmed.', ""This one's especially annoying given how common {{reflist}} is."", 'See also bug 50075 (which I was no longer able to reproduce).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53141,VisualEditor: Nicer removal of Cite.php's class=error,"Currently this is really ugly; Trevor's better class will help, but in general we want to do this better.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: Nicer removal of Cite.php's class=error\n\nCurrently this is really ugly; Trevor's better class will help, but in general we want to do this better."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+1868378,VisualEditor: Nicer removal of Cite.php's class=error,"Change 763101 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Remove hack that hides ref errors unnecessarily%%%
+https://gerrit.wikimedia.org/r/763101",task_subcomment,['Change 763101 **merged** by jenkins-bot:\n%%%[mediawiki/extensions/Cite@master] Remove hack that hides ref errors unnecessarily%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1865304,VisualEditor: Nicer removal of Cite.php's class=error,"Change 763101 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/Cite@master] Remove hack that hides ref errors unnecessarily%%%
+https://gerrit.wikimedia.org/r/763101",task_subcomment,['Change 763101 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):\n%%%[mediawiki/extensions/Cite@master] Remove hack that hides ref errors unnecessarily%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+255328,VisualEditor: Nicer removal of Cite.php's class=error,"(In reply to James Forrester from comment #3)
+> Sorry!
+> 
+> This refers to the hacky fix for bug 50423 which added (eventually):
+> 
+>   /* HACK: Hide Ref errors in templates */
+>   .mw-ext-cite-error {
+> 	display: none;
+>   }
+> 
+> … to ve.ce.MWReferenceNode.css
+> 
+> This bug is asking for a way for these errors to not be shown that doesn't
+> just suppress the conent (they're caused by the templates rendering out of
+> context).
+
+I guess we could send some 'nocontext' parameter in the HTTP request which would suppress errors based on missing information... Sounds like it would be even worse than the current solution though.",task_subcomment,"[""(In reply to James Forrester from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI guess we could send some 'nocontext' parameter in the HTTP request which would suppress errors based on missing information..."", 'Sounds like it would be even worse than the current solution though.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+255318,VisualEditor: Nicer removal of Cite.php's class=error,"Sorry!
+
+This refers to the hacky fix for bug 50423 which added (eventually):
+
+  /* HACK: Hide Ref errors in templates */
+  .mw-ext-cite-error {
+	display: none;
+  }
+
+… to ve.ce.MWReferenceNode.css
+
+This bug is asking for a way for these errors to not be shown that doesn't just suppress the conent (they're caused by the templates rendering out of context).",task_subcomment,"['Sorry!', ""This refers to the hacky fix for bug 50423 which added (eventually):\n\n  /* HACK: Hide Ref errors in templates */\n  .mw-ext-cite-error {\n\tdisplay: none;\n  }\n\n… to ve.ce.MWReferenceNode.css\n\nThis bug is asking for a way for these errors to not be shown that doesn't just suppress the conent (they're caused by the templates rendering out of context).""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+255308,VisualEditor: Nicer removal of Cite.php's class=error,Hello?,task_subcomment,['Hello?'],['OBSERVED BUG BEHAVIOR']
+255299,VisualEditor: Nicer removal of Cite.php's class=error,So what is this about? There's a lot of missing context here.,task_subcomment,"['So what is this about?', ""There's a lot of missing context here.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+53133,"VisualEditor: Red ""remove xyz"" button may not be ideal styling in dialogs","An English Wikipedia user writes to note that since red is the color of a missing link, it may not be an ideal choice for ""remove template""
+
+I myself wonder if it might not show up as pale grey (hence suggesting it will not work) to the color blind.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Red ""remove xyz"" button may not be ideal styling in dialogs\n\nAn English Wikipedia user writes to note that since red is the color of a missing link, it may not be an ideal choice for ""remove template""\n\nI myself wonder if it might not show up as pale grey (hence suggesting it will not work) to the color blind.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['MOTIVATION', 'SOLUTION DISCUSSION']"
+254853,"VisualEditor: Red ""remove xyz"" button may not be ideal styling in dialogs","We now use a rubbish bin (""trash can"") icon which is a lot softer.",task_subcomment,"['We now use a rubbish bin (""trash can"") icon which is a lot softer.']",['SOLUTION DISCUSSION']
+254846,"VisualEditor: Red ""remove xyz"" button may not be ideal styling in dialogs","Note that this is in-line with the Design department's upcoming changes to the skins - it's a wider question. However, we should indeed flag this issue, I agree.",task_subcomment,"[""Note that this is in-line with the Design department's upcoming changes to the skins - it's a wider question."", 'However, we should indeed flag this issue, I agree.']","['FUTURE PLAN', 'SOLUTION DISCUSSION']"
+53116,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor","A user suggests that, in addition to the ""cancel"" option next to the ""save"" button, there should be an option to ""cancel"" from within the save box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor\n\nA user suggests that, in addition to the ""cancel"" option next to the ""save"" button, there should be an option to ""cancel"" from within the save box.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+254098,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor",I have.,task_subcomment,['I have.'],['OBSERVED BUG BEHAVIOR']
+254091,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor","Hmm... Yes, after thinking about this some more, I agree. Who wants to mark this wontfix?",task_subcomment,"['Hmm...', 'Yes, after thinking about this some more, I agree.', 'Who wants to mark this wontfix?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+254085,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor","Agree with Trevor, also on basic grounds of minimizing clutter; we should only add this if there's user testing that shows users don't know how to cancel their edits.",task_subcomment,"[""Agree with Trevor, also on basic grounds of minimizing clutter; we should only add this if there's user testing that shows users don't know how to cancel their edits.""]",['SOLUTION DISCUSSION']
+254078,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor","It's really cool that Alex has added a patch, but I feel pretty confident this is a mistake. If you open a dialog and then hit cancel, you are going to believe it will close the dialog without taking action. This is a reasonable sounding request, but we really need to say no to this.
+
+I'm not going to wontfix until other's chime in. Can anyone really make a case for why this is a good direction?",task_subcomment,"[""It's really cool that Alex has added a patch, but I feel pretty confident this is a mistake."", 'If you open a dialog and then hit cancel, you are going to believe it will close the dialog without taking action.', 'This is a reasonable sounding request, but we really need to say no to this.', ""I'm not going to wontfix until other's chime in."", 'Can anyone really make a case for why this is a good direction?']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+254071,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor","Change 127004 had a related patch set uploaded by Alex Monk:
+Add cancel & discard changes button to save dialog
+
+https://gerrit.wikimedia.org/r/127004",task_subcomment,['Change 127004 had a related patch set uploaded by Alex Monk:\nAdd cancel & discard changes button to save dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+254065,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor",The user is asking to escape VE entirely.,task_subcomment,['The user is asking to escape VE entirely.'],['INVESTIGATION AND EXPLORATION']
+254060,"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor","Would this be to escape from VisualEditor entirely (i.e., go back to view mode) or just to get out of the save dialog and back to the editor?",task_subcomment,"['Would this be to escape from VisualEditor entirely (i.e., go back to view mode) or just to get out of the save dialog and back to the editor?']",['INVESTIGATION AND EXPLORATION']
+53090,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"Links in the form [[./Bla]] are invalid markup, but are rendered as correct links in VisualEditor. There may be other types of invalid formats that are similarly accepted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33094",task_description,"[""[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one\n\nLinks in the form [[./Bla]] are invalid markup, but are rendered as correct links in VisualEditor."", 'There may be other types of invalid formats that are similarly accepted.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+252638,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"Change 124009 merged by jenkins-bot:
+(Bug 51090): Follow-up to 4dce7f620: handle transclusions + html2wt mode
+
+https://gerrit.wikimedia.org/r/124009",task_subcomment,['Change 124009 merged by jenkins-bot:\n(Bug 51090): Follow-up to 4dce7f620: handle transclusions + html2wt mode\n\nGERRIT_URL'],['BUG REPRODUCTION']
+252628,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"Change 121658 merged by jenkins-bot:
+Bug 51090: Render invalid wikilinks as plain text
+
+https://gerrit.wikimedia.org/r/121658",task_subcomment,['Change 121658 merged by jenkins-bot:\nBug 51090: Render invalid wikilinks as plain text\n\nGERRIT_URL'],['BUG REPRODUCTION']
+252620,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"Change 124009 had a related patch set uploaded by Subramanya Sastry:
+(Bug 51090): Follow-up to 4dce7f620: handles more scenarios
+
+https://gerrit.wikimedia.org/r/124009",task_subcomment,['Change 124009 had a related patch set uploaded by Subramanya Sastry:\n(Bug 51090): Follow-up to 4dce7f620: handles more scenarios\n\nGERRIT_URL'],['BUG REPRODUCTION']
+252613,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"This section details the invalid cases to handle:
+
+http://en.wikipedia.org/wiki/Wikipedia:Page_name#Technical_restrictions_and_limitations
+
+The best place to handle this is in onWikiLink in ext.core.LinkHandler.js.",task_subcomment,['This section details the invalid cases to handle:\n\nURL\n\nThe best place to handle this is in onWikiLink in ext.core.LinkHandler.js.'],['INVESTIGATION AND EXPLORATION']
+252607,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"This needs to be checked more carefully after template expansion. Test case this will need to handle as well:
+
+[[{{echo|./Bla}}]]",task_subcomment,"['This needs to be checked more carefully after template expansion.', 'Test case this will need to handle as well:\n\n[[{{echo|./Bla}}]]']","['OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR']"
+252599,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"Confirmed, see http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/Bug_51090 vs. http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/Bug_51090&veaction=edit",task_subcomment,"['Confirmed, see URL vs. URL']",['OBSERVED BUG BEHAVIOR']
+252593,[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one,"You can't now enter these links in VE (bug 33094) but when they appear in the page they are still rendered as valid links in VE. For example [[./Bla]] displays the same as [[Bla]] in the source would and when right clicked, it opens that page.",task_subcomment,"[""You can't now enter these links in VE (bug 33094) but when they appear in the page they are still rendered as valid links in VE."", 'For example [[./Bla]] displays the same as [[Bla]] in the source would and when right clicked, it opens that page.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+53065,VisualEditor: Link editor requires ENTER for input,"On any page, click Link icon
+
+Enter text in text field
+
+Click the ""<"" symbol
+
+Check the diff or save the page.  
+
+The link is created but the text entered is not preserved.  
+
+Suggest either preserving the contents of the text field upon the user clicking ""<"" or (less nice) disabling clicking ""<"" until the user has hit ENTER
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Link editor requires ENTER for input\n\nOn any page, click Link icon\n\nEnter text in text field\n\nClick the ""<"" symbol\n\nCheck the diff or save the page.', 'The link is created but the text entered is not preserved.', 'Suggest either preserving the contents of the text field upon the user clicking ""<"" or (less nice) disabling clicking ""<"" until the user has hit ENTER\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+251259,VisualEditor: Link editor requires ENTER for input,*** Bug 51177 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51177 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251254,VisualEditor: Link editor requires ENTER for input,This is now merged and will be deployed later.,task_subcomment,['This is now merged and will be deployed later.'],['ACTION ON ISSUE']
+251247,VisualEditor: Link editor requires ENTER for input,"Change 76839 merged by jenkins-bot:
+Link inspector bug fixes
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 merged by jenkins-bot:\nLink inspector bug fixes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+251241,VisualEditor: Link editor requires ENTER for input,"Change 76839 had a related patch set uploaded by Trevor Parscal:
+The greatest commit in the history of the world*
+
+https://gerrit.wikimedia.org/r/76839",task_subcomment,['Change 76839 had a related patch set uploaded by Trevor Parscal:\nThe greatest commit in the history of the world*\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+251236,VisualEditor: Link editor requires ENTER for input,"OK, my apologies.  I can reproduce with those steps.
+
+Bug 48789 looks more like a UI design 'enhancement', whereas this bug is a simple bugfix for the current design.",task_subcomment,"['OK, my apologies.', 'I can reproduce with those steps.', ""Bug 48789 looks more like a UI design 'enhancement', whereas this bug is a simple bugfix for the current design.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251230,VisualEditor: Link editor requires ENTER for input,Is this the same thing as bug 48789?,task_subcomment,['Is this the same thing as bug 48789?'],['MOTIVATION']
+251222,VisualEditor: Link editor requires ENTER for input,"
+It is reproducible, let me show an example: 
+
+Assume that the first word on a page to be edited is ""ThisIsALinkToGoogle"" (no quotes) 
+
+Open the page to be edited and without doing anything else to the page, click the Link icon.  The Link dialog shows ThisIsALinkToGoogle highlighted and entered automatically in the text field input. 
+
+In the input field, replace ThisIsALinkToGoogle by typing ""http://www.google.com""
+
+When you finish typing, just click the left-arrow icon to close the Link dialog and (ostensibly) save what you have typed into the text field. 
+
+Do the Save page/Review your changes dance. 
+
+In the diff and in the saved page you will see 	
+[[ThisIsALinkToGoogle]] which is not helpful.  
+
+What I would expect to see is your typing preserved in a link like [http://www.google.com ThisIsALinkToGoogle]",task_subcomment,"['\nIt is reproducible, let me show an example: \n\nAssume that the first word on a page to be edited is ""ThisIsALinkToGoogle"" (no quotes) \n\nOpen the page to be edited and without doing anything else to the page, click the Link icon.', 'The Link dialog shows ThisIsALinkToGoogle highlighted and entered automatically in the text field input.', 'In the input field, replace ThisIsALinkToGoogle by typing ""URL\n\nWhen you finish typing, just click the left-arrow icon to close the Link dialog and (ostensibly) save what you have typed into the text field.', 'Do the Save page/Review your changes dance.', 'In the diff and in the saved page you will see \t\n[[ThisIsALinkToGoogle]] which is not helpful.', 'What I would expect to see is your typing preserved in a link like [URL ThisIsALinkToGoogle]']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+251215,VisualEditor: Link editor requires ENTER for input,"Is this still reproducible?  I tried it, and the diff was empty, but maybe I'm not following the instructions correctly.",task_subcomment,"['Is this still reproducible?', ""I tried it, and the diff was empty, but maybe I'm not following the instructions correctly.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+53056,"VisualEditor: Don't let the user enter multiple consecutive spaces (except in preformatted blocks), because that's not how HTML works","Thread is at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563553593#Consecutive_spaces - I can't explain it any better than the user has :).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"[""VisualEditor: Don't let the user enter multiple consecutive spaces (except in preformatted blocks), because that's not how HTML works\n\nThread is at URL - I can't explain it any better than the user has :)."", '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+250484,"VisualEditor: Don't let the user enter multiple consecutive spaces (except in preformatted blocks), because that's not how HTML works",This is going to be a pain to get the user interaction pattern right.,task_subcomment,['This is going to be a pain to get the user interaction pattern right.'],['SOLUTION DISCUSSION']
+250476,"VisualEditor: Don't let the user enter multiple consecutive spaces (except in preformatted blocks), because that's not how HTML works","This was reported as an enhancement, but because it causes content (i.e. consecutive spaces) to display and behave differently in the edit window than in the view window, I think it is more appropriate to regard it as a bug.  Accordingly, I am upgrading this from ""enhancement"" to ""minor"".",task_subcomment,"['This was reported as an enhancement, but because it causes content (i.e.', 'consecutive spaces) to display and behave differently in the edit window than in the view window, I think it is more appropriate to regard it as a bug.', 'Accordingly, I am upgrading this from ""enhancement"" to ""minor"".']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'ACTION ON ISSUE']"
+53049,"TemplateData: Provide property ""example"" for template parameters","From
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/About_TemplateData
+
+'(...) would it be possible to add new parameter ""example"" (where is example text what should be added to the parameter) in addition ""label"", ""description"", ""type"" and ""required""?'
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['TemplateData: Provide property ""example"" for template parameters\n\nFrom\nURL\n\n\'(...) would it be possible to add new parameter ""example"" (where is example text what should be added to the parameter) in addition ""label"", ""description"", ""type"" and ""required""?\'', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+450809,"TemplateData: Provide property ""example"" for template parameters","Change 207123 merged by jenkins-bot:
+Add example property to HTML rendering
+
+[[https://gerrit.wikimedia.org/r/207123]]",task_subcomment,['Change 207123 merged by jenkins-bot:\nAdd example property to HTML rendering\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+450353,"TemplateData: Provide property ""example"" for template parameters","Change 207123 had a related patch set uploaded (by Krinkle):
+Add example property to HTML rendering
+
+[[https://gerrit.wikimedia.org/r/207123]]
+",task_subcomment,['Change 207123 had a related patch set uploaded (by Krinkle):\nAdd example property to HTML rendering\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+443724,"TemplateData: Provide property ""example"" for template parameters",Checked in betalabs - 'Example (en)' was added to Template documentation editor.,task_subcomment,"[""Checked in betalabs - 'Example (en)' was added to Template documentation editor.""]",['INVESTIGATION AND EXPLORATION']
+441962,"TemplateData: Provide property ""example"" for template parameters","Change 194386 merged by jenkins-bot:
+Add an example property to parameters
+
+[[https://gerrit.wikimedia.org/r/194386]]",task_subcomment,['Change 194386 merged by jenkins-bot:\nAdd an example property to parameters\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+428516,"TemplateData: Provide property ""example"" for template parameters","The feature support in MWParameterPage is a bit presumptuous as the exact definition and property name are still being reviewed upstream in TemplateData.
+
+Anyway, this feature seems useful, but I'd like to be more explicit about at least one use case before we land it. The talk thread that requests it didn't seem to note anything about the existing properties `description`, `default`  and `autofill` which currently cover the use case of showing what a field is for and what kind of value it should have.
+
+I take it it will be used as placeholder in a user interface. However in VisualEditor the `default` is currently also displayed in the `placeholder` attribute. And the (already merged) conditional implementation of that does indeed ignore the `example` value if there is a `default`. And it seems there is no difference communicated to the user visually to distinguish example from default.
+
+If the user won't be able to tell the difference, can authors?
+
+I feel like the feature would be useful, but it is imho not sufficiently clear in its specification, implementation and current use in VisualEditor to offset it from the other existing features. And I imagine this will lead to confusion or incorrect usage by authors and users.",task_subcomment,"['The feature support in MWParameterPage is a bit presumptuous as the exact definition and property name are still being reviewed upstream in TemplateData.', ""Anyway, this feature seems useful, but I'd like to be more explicit about at least one use case before we land it."", ""The talk thread that requests it didn't seem to note anything about the existing properties CODE, CODE  and CODE which currently cover the use case of showing what a field is for and what kind of value it should have."", 'I take it it will be used as placeholder in a user interface.', 'However in VisualEditor the CODE is currently also displayed in the CODE attribute.', 'And the (already merged) conditional implementation of that does indeed ignore the CODE value if there is a CODE.', 'And it seems there is no difference communicated to the user visually to distinguish example from default.', ""If the user won't be able to tell the difference, can authors?"", 'I feel like the feature would be useful, but it is imho not sufficiently clear in its specification, implementation and current use in VisualEditor to offset it from the other existing features.', 'And I imagine this will lead to confusion or incorrect usage by authors and users.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+423419,"TemplateData: Provide property ""example"" for template parameters","Change 194416 merged by jenkins-bot:
+MWParameterPage: Show the field's example if it exists
+
+[[https://gerrit.wikimedia.org/r/194416]]",task_subcomment,"[""Change 194416 merged by jenkins-bot:\nMWParameterPage: Show the field's example if it exists\n\n[[GERRIT_URL]]""]",['GERRIT_URL']
+421136,"TemplateData: Provide property ""example"" for template parameters","Change 194416 had a related patch set uploaded (by Mooeypoo):
+Show the field's example if it exists
+
+[[https://gerrit.wikimedia.org/r/194416]]
+",task_subcomment,"[""Change 194416 had a related patch set uploaded (by Mooeypoo):\nShow the field's example if it exists\n\n[[GERRIT_URL]]""]",['GERRIT_URL']
+420993,"TemplateData: Provide property ""example"" for template parameters","Change 194386 had a related patch set uploaded (by Mooeypoo):
+Add an example property to parameters
+
+[[https://gerrit.wikimedia.org/r/194386]]
+",task_subcomment,['Change 194386 had a related patch set uploaded (by Mooeypoo):\nAdd an example property to parameters\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+250162,"TemplateData: Provide property ""example"" for template parameters",Any progress?,task_subcomment,['Any progress?'],['ACTION ON ISSUE']
+53013,VisualEditor: OpenSearch results aren't perfect for checking for page existence,"Unpopular pages with short titles, e.g. [[Sop]], [[Topo]], do not appear in the top 10 opensearch suggestions, so VE thinks the pages don't exist. However, they definitely do exist.
+
+This, along with bug 50898, suggests that the VE team might need to implement its own wrapper web API for link suggestions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54361",task_description,"[""VisualEditor: OpenSearch results aren't perfect for checking for page existence\n\nUnpopular pages with short titles, e.g."", ""[[Sop]], [[Topo]], do not appear in the top 10 opensearch suggestions, so VE thinks the pages don't exist."", 'However, they definitely do exist.', 'This, along with bug 50898, suggests that the VE team might need to implement its own wrapper web API for link suggestions.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+248182,VisualEditor: OpenSearch results aren't perfect for checking for page existence,"FIXED by dint of bug 70958 being fixed. Thanks, Timo!",task_subcomment,"['FIXED by dint of bug 70958 being fixed.', 'Thanks, Timo!']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+248179,VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 54361 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54361 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248175,VisualEditor: OpenSearch results aren't perfect for checking for page existence,"Action item: When using search in a way that the user input should be used as first hit if it exists[1], our code should always do an additional query for the literal input against the pageinfo API. At least until the upstream bug in MediaWiki search is fixed (do we have a report for that?).
+
+
+[1] e.g. mediawiki link input widget, and transclusion dialog template name input, but not media dialog probably.",task_subcomment,"['Action item: When using search in a way that the user input should be used as first hit if it exists[1], our code should always do an additional query for the literal input against the pageinfo API.', 'At least until the upstream bug in MediaWiki search is fixed (do we have a report for that?).', '[1] e.g.', 'mediawiki link input widget, and transclusion dialog template name input, but not media dialog probably.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+248171,VisualEditor: OpenSearch results aren't perfect for checking for page existence,"Right now MediaWiki search has a bug where one searches ""Foo"" and a page by that name exists, it might not be included in the search results (or at least not in the first 10). Or sometimes it's in there but on #3.
+
+While fixing the order is harder, we can easily work around the case where it is absent by running an additional api query simply checking whether a page by the title of ""Foo"" exists.",task_subcomment,"['Right now MediaWiki search has a bug where one searches ""Foo"" and a page by that name exists, it might not be included in the search results (or at least not in the first 10).', ""Or sometimes it's in there but on #3."", 'While fixing the order is harder, we can easily work around the case where it is absent by running an additional api query simply checking whether a page by the title of ""Foo"" exists.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+248164,VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 65927 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 65927 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248158,VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 52596 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52596 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248152,VisualEditor: OpenSearch results aren't perfect for checking for page existence,This looks the same as bug 52596 which contains more details of which pages are believed to exist and which are not,task_subcomment,['This looks the same as bug 52596 which contains more details of which pages are believed to exist and which are not'],['OBSERVED BUG BEHAVIOR']
+53012,VisualEditor: Make defaultsort input field wider,"To fit long page titles. 
+
+There's plenty of empty space in the dialog box that could be put to use.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Make defaultsort input field wider\n\nTo fit long page titles.', ""There's plenty of empty space in the dialog box that could be put to use."", '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+248112,VisualEditor: Make defaultsort input field wider,Thanks!,task_subcomment,['Thanks!'],['SOLUTION DISCUSSION']
+248103,VisualEditor: Make defaultsort input field wider,"Change 119092 merged by jenkins-bot:
+Increases width of defaultsort and page redirect fields in options dialog
+
+https://gerrit.wikimedia.org/r/119092",task_subcomment,['Change 119092 merged by jenkins-bot:\nIncreases width of defaultsort and page redirect fields in options dialog\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+248096,VisualEditor: Make defaultsort input field wider,"Change 119092 had a related patch set uploaded by Mvolz:
+Increases width of defaultsort and page redirect fields in options dialog
+
+https://gerrit.wikimedia.org/r/119092",task_subcomment,['Change 119092 had a related patch set uploaded by Mvolz:\nIncreases width of defaultsort and page redirect fields in options dialog\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+248090,VisualEditor: Make defaultsort input field wider,"Created attachment 14834
+Other dialogs affected by change
+
+**Attached**: {F11659}",task_subcomment,['Created attachment 14834\nOther dialogs affected by change\n\n**Attached**: {F11659}'],['ATTACHMENT']
+248086,VisualEditor: Make defaultsort input field wider,"Created attachment 14833
+Screenshot of 100% width in default sort field
+
+**Attached**: {F11658}",task_subcomment,['Created attachment 14833\nScreenshot of 100% width in default sort field\n\n**Attached**: {F11658}'],['ATTACHMENT']
+248082,VisualEditor: Make defaultsort input field wider,"Created attachment 14832
+Screenshot of 30em width in default sort field
+
+So I've looked into this a bit and took some screenshots.
+
+Currently this is set in the class .oo-ui-textInputWidget and is set to 20em. The text input widget appears in Options -> Categories, Options -> Page Settings, and Insert -> Reference. 
+
+These 3 fields all look acceptable at a width of 30em. We could also go for 100% width of the div. I like the look of this in the two Options areas, although this looks a bit odd in the Reference dialog ""group by"" field. I think that even 20em was too wide for it to begin with- maybe we should add a special class here?
+
+Any opinions? I like both 30 em and 100%, and since reference dialog is likely to undergo radical UI changes the size of the group by field in the reference dialog could be ignored for the time being.
+
+**Attached**: {F11657}",task_subcomment,"[""Created attachment 14832\nScreenshot of 30em width in default sort field\n\nSo I've looked into this a bit and took some screenshots."", 'Currently this is set in the class .oo-ui-textInputWidget and is set to 20em.', 'The text input widget appears in Options -> Categories, Options -> Page Settings, and Insert -> Reference.', 'These 3 fields all look acceptable at a width of 30em.', 'We could also go for 100% width of the div.', 'I like the look of this in the two Options areas, although this looks a bit odd in the Reference dialog ""group by"" field.', 'I think that even 20em was too wide for it to begin with- maybe we should add a special class here?', 'Any opinions?', 'I like both 30 em and 100%, and since reference dialog is likely to undergo radical UI changes the size of the group by field in the reference dialog could be ignored for the time being.', '**Attached**: {F11657}']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+52998,"VisualEditor: ""Apply changes"" label should be replaced with ""Insert template/reflist"" when inserting template/reflist","When inserting a new template, the template dialog button label ""Apply changes"" doesn't make sense, since we're not changing an existing element. In that case, the button should be labeled ""Insert template"".
+
+Similarly, when inserting the list of references, the button should be labeled ""Insert references list"", not ""Apply changes"".
+
+In contrast, when inserting a footnote or media file, the button is correctly labeled ""Insert reference"" or ""Insert media"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: ""Apply changes"" label should be replaced with ""Insert template/reflist"" when inserting template/reflist\n\nWhen inserting a new template, the template dialog button label ""Apply changes"" doesn\'t make sense, since we\'re not changing an existing element.', 'In that case, the button should be labeled ""Insert template"".', 'Similarly, when inserting the list of references, the button should be labeled ""Insert references list"", not ""Apply changes"".', 'In contrast, when inserting a footnote or media file, the button is correctly labeled ""Insert reference"" or ""Insert media"".', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+247400,"VisualEditor: ""Apply changes"" label should be replaced with ""Insert template/reflist"" when inserting template/reflist",Verified the fix production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,task_subcomment,['Verified the fix production:URL'],['BUG REPRODUCTION']
+247394,"VisualEditor: ""Apply changes"" label should be replaced with ""Insert template/reflist"" when inserting template/reflist",Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&veaction=edit,task_subcomment,['Verified the fix in test2:URL'],['BUG REPRODUCTION']
+247388,"VisualEditor: ""Apply changes"" label should be replaced with ""Insert template/reflist"" when inserting template/reflist","Change 117342 merged by jenkins-bot:
+Keep label and disabled state of transclusion dialog apply button in sync
+
+https://gerrit.wikimedia.org/r/117342",task_subcomment,['Change 117342 merged by jenkins-bot:\nKeep label and disabled state of transclusion dialog apply button in sync\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247385,"VisualEditor: ""Apply changes"" label should be replaced with ""Insert template/reflist"" when inserting template/reflist","Change 117342 had a related patch set uploaded by Jforrester:
+Keep label and disabled state of transclusion dialog apply button in sync
+
+https://gerrit.wikimedia.org/r/117342",task_subcomment,['Change 117342 had a related patch set uploaded by Jforrester:\nKeep label and disabled state of transclusion dialog apply button in sync\n\nGERRIT_URL'],['ACTION ON ISSUE']
+52997,"VisualEditor: More gracefully handle situations where due to page length/slow client, slowness to load means browser kills VE","Splitting from bug 50475 comment 1.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: More gracefully handle situations where due to page length/slow client, slowness to load means browser kills VE\n\nSplitting from bug 50475 comment 1.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+52996,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,"Especially for templates, having a faster way to open the inspector would be very helpful. Right now in the case of a large template, you have to first select the template, then mouse over to the puzzle piece location and click it. Just double-clicking/tapping the template seems like a straightforward and discoverable gesture.
+
+For links and other nodes it may be less important, but what would be the disadvantages for just making open-on-double-click the default behavior for all nodes that have a primary inspector of some kind?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54827",task_description,"['VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog\n\nEspecially for templates, having a faster way to open the inspector would be very helpful.', 'Right now in the case of a large template, you have to first select the template, then mouse over to the puzzle piece location and click it.', 'Just double-clicking/tapping the template seems like a straightforward and discoverable gesture.', 'For links and other nodes it may be less important, but what would be the disadvantages for just making open-on-double-click the default behavior for all nodes that have a primary inspector of some kind?', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+247321,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,"Change 103062 merged by jenkins-bot:
+Create mixin that tries to execute primary node command
+
+https://gerrit.wikimedia.org/r/103062",task_subcomment,['Change 103062 merged by jenkins-bot:\nCreate mixin that tries to execute primary node command\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+247315,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,"Change 84461 abandoned by Robmoen:
+WIP: Create ve.ce.ClickableNode mixin
+
+Reason:
+old
+
+https://gerrit.wikimedia.org/r/84461",task_subcomment,['Change 84461 abandoned by Robmoen:\nWIP: Create ve.ce.ClickableNode mixin\n\nReason:\nold\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+247309,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,"Change 103062 had a related patch set uploaded by Robmoen:
+Create mixin for node that responds to node click events
+
+https://gerrit.wikimedia.org/r/103062",task_subcomment,['Change 103062 had a related patch set uploaded by Robmoen:\nCreate mixin for node that responds to node click events\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247300,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,"Change 84461 had a related patch set uploaded by Krinkle:
+WIP: Create ve.ce.ClickableNode mixin.
+
+https://gerrit.wikimedia.org/r/84461",task_subcomment,"['Change 84461 had a related patch set uploaded by Krinkle:\nWIP: Create ve.ce.ClickableNode mixin.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+247292,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,WIP: https://gerrit.wikimedia.org/r/#/c/84461/,task_subcomment,['WIP: URL'],['SOLUTION DISCUSSION']
+247288,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,"Sherry and I would really second Erik's suggestion.
+We just had feedback from a user who was clueless about what to do with ""a blue rectangle with a jigsaw icon"".",task_subcomment,"[""Sherry and I would really second Erik's suggestion."", 'We just had feedback from a user who was clueless about what to do with ""a blue rectangle with a jigsaw icon"".']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+247282,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,*** Bug 51176 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51176 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247275,VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,"I think this would work best for nodes (i.e., things that have a dialog) and not for annotations (i.e., things that are either toggled like bold or superscript, or have only an inspector link links or language).
+
+This would be a lot simpler from a UX perspective (consistency of action and explainability), and the change overall is a good quick affordance win.",task_subcomment,"['I think this would work best for nodes (i.e., things that have a dialog) and not for annotations (i.e., things that are either toggled like bold or superscript, or have only an inspector link links or language).', 'This would be a lot simpler from a UX perspective (consistency of action and explainability), and the change overall is a good quick affordance win.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52995,VisualEditor: Backspace from (or deleteing down) into a DL breaks badly,"If you backspace-delete the newline that appears immediately prior to the indented quote of this rev (the quote that begins with ""This was a kind of blank ..""), the entire quote is deleted. This may be related to the fact that the newline shouldn't be there in the first place; it does not exist in the wikitext version of the page, nor is the text indented by means of a template. 
+
+https://en.wikipedia.org/w/index.php?title=Ernestine_Eckstein&oldid=563439288&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50418",task_description,"['VisualEditor: Backspace from (or deleteing down) into a DL breaks badly\n\nIf you backspace-delete the newline that appears immediately prior to the indented quote of this rev (the quote that begins with ""This was a kind of blank ..""), the entire quote is deleted.', ""This may be related to the fact that the newline shouldn't be there in the first place; it does not exist in the wikitext version of the page, nor is the text indented by means of a template."", 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+445972,VisualEditor: Backspace from (or deleteing down) into a DL breaks badly,This seems fixed now. I was able to backspace or delete anything around the indentations on the test pages without the editor exploding in my face.,task_subcomment,"['This seems fixed now.', 'I was able to backspace or delete anything around the indentations on the test pages without the editor exploding in my face.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+247232,VisualEditor: Backspace from (or deleteing down) into a DL breaks badly,"Testing at https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=570858997 shows that attempting to backspace on one of the trailing new lines no longer deletes anything, it just moves the cursor to the end of the line above.",task_subcomment,"['Testing at URL shows that attempting to backspace on one of the trailing new lines no longer deletes anything, it just moves the cursor to the end of the line above.']",['OBSERVED BUG BEHAVIOR']
+247227,VisualEditor: Backspace from (or deleteing down) into a DL breaks badly,"I think this might be the same bug that I encountered last night. Details and a screenshot at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564667549#Indentation_with_colons_rendered_with_blank_lines._Attempting_to_delete_these_deletes_entire_section_and_cannot_be_undone
+
+Summary: Indentation with colons is rendered in VisualEditor with one blank line per level of indent before and after the indented section. Attempting to delete one of the blank lines before the indentation unindents by one level and removing a blank line before the indented text but not removing any after it. 
+
+Attempting to remove any of the blank lines after the indented text deletes the entire indentation section. This deletion cannot be undone.",task_subcomment,"['I think this might be the same bug that I encountered last night.', 'Details and a screenshot at URL\n\nSummary: Indentation with colons is rendered in VisualEditor with one blank line per level of indent before and after the indented section.', 'Attempting to delete one of the blank lines before the indentation unindents by one level and removing a blank line before the indented text but not removing any after it.', 'Attempting to remove any of the blank lines after the indented text deletes the entire indentation section.', 'This deletion cannot be undone.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247221,VisualEditor: Backspace from (or deleteing down) into a DL breaks badly,Also note that undo doesn't seem to work on this deletion event.,task_subcomment,"[""Also note that undo doesn't seem to work on this deletion event.""]",['OBSERVED BUG BEHAVIOR']
+52978,VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"Screenshot of odd rendering when using {{#tag:ref}}
+
+https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet?veaction=edit
+
+See attachment, [11] renders as span instead of as  (like [10]) and as such isn'y styled correctly (text is too big).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11600}",task_description,"[""VisualEditor: Display references rendered by {{#tag:ref}} in superscript\n\nScreenshot of odd rendering when using {{#tag:ref}}\n\nURL\n\nSee attachment, [11] renders as span instead of as  (like [10]) and as such isn'y styled correctly (text is too big)."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11600}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+246361,VisualEditor: Display references rendered by {{#tag:ref}} in superscript,Fixed and will go out later today.,task_subcomment,['Fixed and will go out later today.'],['SOLUTION USAGE']
+246353,VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"Change 73980 merged by jenkins-bot:
+Fake superscript style for references generated as spans
+
+https://gerrit.wikimedia.org/r/73980",task_subcomment,['Change 73980 merged by jenkins-bot:\nFake superscript style for references generated as spans\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+246347,VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"Change 73980 had a related patch set uploaded by Esanders:
+Fake superscript style for references generated as spans
+
+https://gerrit.wikimedia.org/r/73980",task_subcomment,['Change 73980 had a related patch set uploaded by Esanders:\nFake superscript style for references generated as spans\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+246339,VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"(In reply to comment #2)
+> Parsoid incorrectly renders references as s. The ones directly in the
+> main documented are rendered as s by VE, but we don't control the ones
+> in
+> templates and other generated content (and #tag is a ParserFunction).
+Ugh, didn't see James's summary edit. Moving back to VE.
+
+We could probably add CSS to make  render as a superscript, or munge it in some other way. Though ideally I'd like us to convince Parsoid to render references as s the way the PHP parser does.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nUgh, didn't see James's summary edit."", 'Moving back to VE.', 'We could probably add CSS to make  render as a superscript, or munge it in some other way.', ""Though ideally I'd like us to convince Parsoid to render references as s the way the PHP parser does.""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+246332,VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"Parsoid incorrectly renders references as s. The ones directly in the main documented are rendered as s by VE, but we don't control the ones in templates and other generated content (and #tag is a ParserFunction).",task_subcomment,"['Parsoid incorrectly renders references as s.', ""The ones directly in the main documented are rendered as s by VE, but we don't control the ones in templates and other generated content (and #tag is a ParserFunction).""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+246327,VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"This is confusing because the lack of superscript makes these refs look like an external link.
+
+This happens with all pages that use [[Template:Geographic reference]], which the English template page says is ""a very large number of Wikipedia articles"", and that template exists in 15 other Wikipedias including a few on the 'maybe' list for 22 July deployment.
+
+Example in the wild:
+
+https://en.wikipedia.org/wiki/Branford,_Florida?veaction=edit",task_subcomment,"['This is confusing because the lack of superscript makes these refs look like an external link.', 'This happens with all pages that use [[Template:Geographic reference]], which the English template page says is ""a very large number of Wikipedia articles"", and that template exists in 15 other Wikipedias including a few on the \'maybe\' list for 22 July deployment.', 'Example in the wild:\n\nURL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52966,VisualEditor: Provide some way of opening external links within templates,"From an editor on English Wikipedia:
+
+On the whole, I really like it. It's basically intuitive and seems to have massively improved since I first tested it out. The main problem I'm having involves the amount of effort now required to open external links in references (especially those using {{cite web}} etc). As far as I can tell, I have to click on the footnote, then the icon, then the text of the reference, then another icon, then the url parameter, and once I'm done copy and pasting I have to close two pop-ups. Is there any way around this that I've missed? It's not an error or a bug, but it's the main barrier to efficient editing that I've encountered so far. – Arms & Hearts (talk) 16:03, 7 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Provide some way of opening external links within templates\n\nFrom an editor on English Wikipedia:\n\nOn the whole, I really like it.', ""It's basically intuitive and seems to have massively improved since I first tested it out."", ""The main problem I'm having involves the amount of effort now required to open external links in references (especially those using {{cite web}} etc)."", ""As far as I can tell, I have to click on the footnote, then the icon, then the text of the reference, then another icon, then the url parameter, and once I'm done copy and pasting I have to close two pop-ups."", ""Is there any way around this that I've missed?"", ""It's not an error or a bug, but it's the main barrier to efficient editing that I've encountered so far."", '– Arms & Hearts (talk) 16:03, 7 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+496813,VisualEditor: Provide some way of opening external links within templates,"It's now possible to easily open links in citations and image captions using the link inspector. The same isn't true of gallery captions, but that's because we still need to make a visual editor for galleries (T45037).",task_subcomment,"[""It's now possible to easily open links in citations and image captions using the link inspector."", ""The same isn't true of gallery captions, but that's because we still need to make a visual editor for galleries (T45037).""]","['SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION']"
+245615,VisualEditor: Provide some way of opening external links within templates,*** Bug 66549 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 66549 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245610,VisualEditor: Provide some way of opening external links within templates,"This affects more than just templates.  You can't click to open any internal or external link that is located inside any ""node"" (galleries, image captions, ).",task_subcomment,"['This affects more than just templates.', 'You can\'t click to open any internal or external link that is located inside any ""node"" (galleries, image captions, ).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52955,VisualEditor: Clearer message when cancelling out of active edit,"An English Wikipedia user requests clarification of the ""cancel"" process, saying:
+
+""If you open a page in the VisualEditor, make a few changes, and then decide to hit the ""Cancel"" button, you get a message that says ""Are you sure you want to go back to view mode without saving first?"". The options are ""OK"" and ""Cancel"", which aren't really proper answers to this yes/no question. As such, I'd like to request that instead the buttons be replaced with ""Yes"" and ""No"", which are clear responses to the question. -Thunderforge (talk) 21:36, 6 July 2013 (UTC)""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Clearer message when cancelling out of active edit\n\nAn English Wikipedia user requests clarification of the ""cancel"" process, saying:\n\n""If you open a page in the VisualEditor, make a few changes, and then decide to hit the ""Cancel"" button, you get a message that says ""Are you sure you want to go back to view mode without saving first?"".', 'The options are ""OK"" and ""Cancel"", which aren\'t really proper answers to this yes/no question.', 'As such, I\'d like to request that instead the buttons be replaced with ""Yes"" and ""No"", which are clear responses to the question.', '-Thunderforge (talk) 21:36, 6 July 2013 (UTC)""\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+245010,VisualEditor: Clearer message when cancelling out of active edit,"Change 130394 merged by jenkins-bot:
+Swap from using native confirm() to using an OOUI dialog when cancelling
+
+https://gerrit.wikimedia.org/r/130394",task_subcomment,['Change 130394 merged by jenkins-bot:\nSwap from using native confirm() to using an OOUI dialog when cancelling\n\nGERRIT_URL'],['ACTION ON ISSUE']
+245004,VisualEditor: Clearer message when cancelling out of active edit,"Change 132316 merged by jenkins-bot:
+Update OOjs UI to v0.1.0-pre (80f1797a5c)
+
+https://gerrit.wikimedia.org/r/132316",task_subcomment,['Change 132316 merged by jenkins-bot:\nUpdate OOjs UI to v0.1.0-pre (80f1797a5c)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244998,VisualEditor: Clearer message when cancelling out of active edit,"Change 132318 merged by jenkins-bot:
+Update OOjs UI to v0.1.0-pre (80f1797a5c)
+
+https://gerrit.wikimedia.org/r/132318",task_subcomment,['Change 132318 merged by jenkins-bot:\nUpdate OOjs UI to v0.1.0-pre (80f1797a5c)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244991,VisualEditor: Clearer message when cancelling out of active edit,"Change 132113 merged by jenkins-bot:
+Add confirmation dialog
+
+https://gerrit.wikimedia.org/r/132113",task_subcomment,['Change 132113 merged by jenkins-bot:\nAdd confirmation dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244982,VisualEditor: Clearer message when cancelling out of active edit,"Change 132318 had a related patch set uploaded by Alex Monk:
+Register OOUI confirmation dialog with windowFactory
+
+https://gerrit.wikimedia.org/r/132318",task_subcomment,['Change 132318 had a related patch set uploaded by Alex Monk:\nRegister OOUI confirmation dialog with windowFactory\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244972,VisualEditor: Clearer message when cancelling out of active edit,"Change 132316 had a related patch set uploaded by Alex Monk:
+Add confirmation dialog messages to MW core
+
+https://gerrit.wikimedia.org/r/132316",task_subcomment,['Change 132316 had a related patch set uploaded by Alex Monk:\nAdd confirmation dialog messages to MW core\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+244963,VisualEditor: Clearer message when cancelling out of active edit,"Change 132113 had a related patch set uploaded by Alex Monk:
+Add confirmation dialog
+
+https://gerrit.wikimedia.org/r/132113",task_subcomment,['Change 132113 had a related patch set uploaded by Alex Monk:\nAdd confirmation dialog\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+244958,VisualEditor: Clearer message when cancelling out of active edit,"Change 130394 had a related patch set uploaded by Alex Monk:
+Swap from using native confirm() to using an OOUI dialog when cancelling
+
+https://gerrit.wikimedia.org/r/130394",task_subcomment,['Change 130394 had a related patch set uploaded by Alex Monk:\nSwap from using native confirm() to using an OOUI dialog when cancelling\n\nGERRIT_URL'],['ACTION ON ISSUE']
+244954,VisualEditor: Clearer message when cancelling out of active edit,"**ignatzmice.wiki** wrote:
+
+A user suggests [Return to editor] [Exit without saving]. https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=567692036",task_subcomment,"['**ignatzmice.wiki** wrote:\n\nA user suggests [Return to editor] [Exit without saving].', 'URL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+244951,VisualEditor: Clearer message when cancelling out of active edit,"From bug 51655 comment 1:
+
+| The confirmation dialog should have more descriptive buttons, such as
+|   [Discard edits] [Continue editing]
+| , or
+|   [Leave editing mode] [Return to editing]
+| , etc.
+| 
+| For this to happen, it needs to become a jQuery dialog.
+| 
+| In fact, VE shouldn't use native confirm() dialogs; the implementation in
+| most browsers is crappy.",task_subcomment,"['From bug 51655 comment 1:\n\n| The confirmation dialog should have more descriptive buttons, such as\n|   [Discard edits] [Continue editing]\n| , or\n|   [Leave editing mode] [Return to editing]\n| , etc.', '| \n| For this to happen, it needs to become a jQuery dialog.', ""| \n| In fact, VE shouldn't use native confirm() dialogs; the implementation in\n| most browsers is crappy.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+244946,VisualEditor: Clearer message when cancelling out of active edit,*** Bug 51655 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51655 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244942,VisualEditor: Clearer message when cancelling out of active edit,"**ignatzmice.wiki** wrote:
+
+See bug 51655, which should probably be closed as a duplicate. (On enwiki I'd say ""merge"".)",task_subcomment,"['**ignatzmice.wiki** wrote:\n\nSee bug 51655, which should probably be closed as a duplicate.', '(On enwiki I\'d say ""merge"".)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+244938,VisualEditor: Clearer message when cancelling out of active edit,"Unfortunately we can't actually replace the ""OK"" and ""Cancel"" buttons' text - that's supplied by the browser as is unchangeable.
+
+What we can do is tweak the message so it's clear what this does, perhaps. Any ideas what might work better?",task_subcomment,"['Unfortunately we can\'t actually replace the ""OK"" and ""Cancel"" buttons\' text - that\'s supplied by the browser as is unchangeable.', ""What we can do is tweak the message so it's clear what this does, perhaps."", 'Any ideas what might work better?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52951,VisualEditor: Handle transclusions within a table better,"**Author:** `adaml`
+
+**Description:**
+When editing a table which includes a transclusion as seen on http://test.wikipedia.org/wiki/TableRowTest it seems to copy the row and paste it before the start of the table. 
+
+In the example above, edit the page and select one of the rows for transclusion and change parameter 1 to a different value, all seems to be good until you save the page which screws it up
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50589
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50607",task_description,"['VisualEditor: Handle transclusions within a table better\n\n**Author:** CODE\n\n**Description:**\nWhen editing a table which includes a transclusion as seen on URL it seems to copy the row and paste it before the start of the table.', 'In the example above, edit the page and select one of the rows for transclusion and change parameter 1 to a different value, all seems to be good until you save the page which screws it up\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+244718,VisualEditor: Handle transclusions within a table better,The table will still be broken after an edit as Parsoid doesn't run with context yet.,task_subcomment,"[""The table will still be broken after an edit as Parsoid doesn't run with context yet.""]",['OBSERVED BUG BEHAVIOR']
+244715,VisualEditor: Handle transclusions within a table better,Fixed by gerrit 140439.,task_subcomment,['Fixed by gerrit 140439.'],['SOLUTION USAGE']
+244712,VisualEditor: Handle transclusions within a table better,This might be related to VisualEditor bug 50607 and foster-parenting.,task_subcomment,['This might be related to VisualEditor bug 50607 and foster-parenting.'],['OBSERVED BUG BEHAVIOR']
+244709,VisualEditor: Handle transclusions within a table better,"Confirmed.  This is probably the same problem as bug 50589, but this is a nice simple case and might be easier to solve.",task_subcomment,"['Confirmed.', 'This is probably the same problem as bug 50589, but this is a nice simple case and might be easier to solve.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+52943,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"An editor had an issue on English Wikipedia with the hyperlink tool when used within the reference editor.
+
+Specifically, he formatted a reference manually and then used the hyperlink tool within the reference editor to provide an external link to the work. He found that many options were offered, to the point that the reference box was obscured by the list of possible links and he had to just guess where to paste the actual url. 
+
+I reproduced this and took a screenshot. 
+
+http://en.wikipedia.org/wiki/File:VisualEditor_Reference_issue.jpg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?)', 'An editor had an issue on English Wikipedia with the hyperlink tool when used within the reference editor.', 'Specifically, he formatted a reference manually and then used the hyperlink tool within the reference editor to provide an external link to the work.', 'He found that many options were offered, to the point that the reference box was obscured by the list of possible links and he had to just guess where to paste the actual url.', 'I reproduced this and took a screenshot.', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+1240023,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),I can't reproduce this. This interface has changed many times since 2013 and presumably this was fixed.,task_subcomment,"[""I can't reproduce this."", 'This interface has changed many times since 2013 and presumably this was fixed.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244197,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"**adam.jenkins** wrote:
+
+Refreshing cache didn't help - I refreshed with VE open and again with the link dialog open. I noticed it didn't occur when adding a normal link in the body, only when adding a link in a reference.",task_subcomment,"[""**adam.jenkins** wrote:\n\nRefreshing cache didn't help - I refreshed with VE open and again with the link dialog open."", ""I noticed it didn't occur when adding a normal link in the body, only when adding a link in a reference.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244191,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"**adam.jenkins** wrote:
+
+Screenshot, Chrome, Mac running OSX 10.8.4
+
+Pop-up list sits above textbox, text box for group appears in pop-up list.
+
+**Attached**: {F11506}",task_subcomment,"['**adam.jenkins** wrote:\n\nScreenshot, Chrome, Mac running OSX 10.8.4\n\nPop-up list sits above textbox, text box for group appears in pop-up list.', '**Attached**: {F11506}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244183,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"(In reply to comment #3)
+> When adding a new reference:
+> 
+> * I typed in ""this is a lunk"" (I mistyped link) 
+> * Selected ""lunk"" and click on the link icon
+> 
+> This produces the pop-up list of suggested links, but it sits over the top of
+> the text box, preventing the user from seeing what is typed.
+
+OK, that's definitely broken behaviour - see the attachment I added just now for expected behaviour. Can you give a screenshot of what it looks like for you (is Maggie's link - http://en.wikipedia.org/wiki/File:VisualEditor_Reference_issue.jpg - accurate)? Does is still occur? In what skin? Do you have some gadgets installed, and does it occur if you disable them?
+
+> As a secondary problem, (which is why I used ""lunk"" as an example above), if
+> the pop-up list is long enough to extend over the ""Use this group"" textbox,
+> the textbox appears as an item in the pop-up list. You can see it a bit in
+> the attachment Maggie provided. If the pop-up list is longer, it is inserted
+> between elements.
+
+That won't happen if the link inspector's suggestion box appears in the correct mode.
+
+> This does not occur in Chrome under Windows 7, as pop-up list appears below
+> the text box, and doesn't have the issue with the ""Use this group"" textbox.
+
+This looks horribly like a caching bug - what happens if you hard-refresh (in Chrome on Mac, Command-Shift-R on any page whilst in VisualEditor mode)?",task_subcomment,"[""(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOK, that's definitely broken behaviour - see the attachment I added just now for expected behaviour."", ""Can you give a screenshot of what it looks like for you (is Maggie's link - URL - accurate)?"", 'Does is still occur?', 'In what skin?', 'Do you have some gadgets installed, and does it occur if you disable them?', ""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat won't happen if the link inspector's suggestion box appears in the correct mode."", 'QUOTE\nQUOTE\n\nThis looks horribly like a caching bug - what happens if you hard-refresh (in Chrome on Mac, Command-Shift-R on any page whilst in VisualEditor mode)?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION']"
+244176,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"Created attachment 12795
+Expected behaviour if adding a link in a DOM dialog like a reference
+
+**Attached**: {F11505}",task_subcomment,['Created attachment 12795\nExpected behaviour if adding a link in a DOM dialog like a reference\n\n**Attached**: {F11505}'],['INVESTIGATION AND EXPLORATION']
+244170,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"**adam.jenkins** wrote:
+
+I've been able to recreate the behaviour using Chrome on the iMac.",task_subcomment,"[""**adam.jenkins** wrote:\n\nI've been able to recreate the behaviour using Chrome on the iMac.""]",['OBSERVED BUG BEHAVIOR']
+244167,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"**adam.jenkins** wrote:
+
+Hi! I'm currently running Chrome 26 on a MacBook Pro retina running 10.8.4, but I think I also had it on an iMac, but I'll confirm. When adding a new reference:
+
+* I typed in ""this is a lunk"" (I mistyped link) 
+* Selected ""lunk"" and click on the link icon
+
+This produces the pop-up list of suggested links, but it sits over the top of the text box, preventing the user from seeing what is typed. A url can still be pasted in. If the user types a URL, the pop-up list will disappear, but reappear after any pause in typing, hiding the box again. (This reappearance would be desired behaviour normally).
+
+As a secondary problem, (which is why I used ""lunk"" as an example above), if the pop-up list is long enough to extend over the ""Use this group"" textbox, the textbox appears as an item in the pop-up list. You can see it a bit in the attachment Maggie provided. If the pop-up list is longer, it is inserted between elements.
+
+If a URL is entered the list reduces in size to two elements, the link in blue as an ""External link"", and the link in red as a ""New page"". However, the window still slightly overlaps the text box for entering the URL, and if accidently clicked when trying to select the textbox again, the link is changed to a wikilink and the options disappear. But there is no indication that this has occurred. This seems in part to be the ""new pages appear as blue links"" bug, so it might be fixed as part of that.
+
+This does not occur in Chrome under Windows 7, as pop-up list appears below the text box, and doesn't have the issue with the ""Use this group"" textbox.",task_subcomment,"['**adam.jenkins** wrote:\n\nHi!', ""I'm currently running Chrome 26 on a MacBook Pro retina running 10.8.4, but I think I also had it on an iMac, but I'll confirm."", 'When adding a new reference:\n\n* I typed in ""this is a lunk"" (I mistyped link) \n* Selected ""lunk"" and click on the link icon\n\nThis produces the pop-up list of suggested links, but it sits over the top of the text box, preventing the user from seeing what is typed.', 'A url can still be pasted in.', 'If the user types a URL, the pop-up list will disappear, but reappear after any pause in typing, hiding the box again.', '(This reappearance would be desired behaviour normally).', 'As a secondary problem, (which is why I used ""lunk"" as an example above), if the pop-up list is long enough to extend over the ""Use this group"" textbox, the textbox appears as an item in the pop-up list.', 'You can see it a bit in the attachment Maggie provided.', 'If the pop-up list is longer, it is inserted between elements.', 'If a URL is entered the list reduces in size to two elements, the link in blue as an ""External link"", and the link in red as a ""New page"".', 'However, the window still slightly overlaps the text box for entering the URL, and if accidently clicked when trying to select the textbox again, the link is changed to a wikilink and the options disappear.', 'But there is no indication that this has occurred.', 'This seems in part to be the ""new pages appear as blue links"" bug, so it might be fixed as part of that.', 'This does not occur in Chrome under Windows 7, as pop-up list appears below the text box, and doesn\'t have the issue with the ""Use this group"" textbox.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+244165,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"Maggie, I am not able to reproduce this behavior in Chrome or Firefox; the references dialog expands with a scrollbar if needed. Are you still getting this? If so could you provide more detailed steps to reproduce and browser info? Thanks!",task_subcomment,"['Maggie, I am not able to reproduce this behavior in Chrome or Firefox; the references dialog expands with a scrollbar if needed.', 'Are you still getting this?', 'If so could you provide more detailed steps to reproduce and browser info?', 'Thanks!']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+244162,VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?),"I should add his words (User:Bilby):
+
+""Short version - the pop-list of suggested wikilinks was malformed if it was long enough to cover the group name box, and prevents the user from seeing the text box when pasting a URL. When a URL is blindly pasted, it is easy to accidentally click on the wikilink option, but there is no indicator that this has occurred once the pop-up list disappears.""
+
+See http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563382661#Adding_references_with_links",task_subcomment,"['I should add his words (User:Bilby):\n\n""Short version - the pop-list of suggested wikilinks was malformed if it was long enough to cover the group name box, and prevents the user from seeing the text box when pasting a URL.', 'When a URL is blindly pasted, it is easy to accidentally click on the wikilink option, but there is no indicator that this has occurred once the pop-up list disappears.""', 'See URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52929,User preference to disable VisualEditor,"It's strange that I can't find a bug for this. Lots of user on en.wiki complained loudly about this [1], but nobody succeded to write a bug report for it? Well, here it is:
+
+Please provide an option in user preferences to turn VE off. Some users just don't like it and don't want to have an extra tab which they don't use anyway. The gadget isn't perfect, as the tab might appear for short time before it is removed again, and has to updated when VE integration changes. The only reason I found for why there is no such option is this:
+
+""It was planned, but the code turned out to be seriously buggy at the last minute. Getting it really, truly off (rather than just covered up) is more complicated than expected."" Whatamidoing (WMF) (talk) 06:32, 2 July 2013 (UTC)
+
+Now with the minimized amount of code that is loaded at startup, it is acceptable to load the code, but just not to execute it. Adding
+
+if ( !mw.user.options.get( 'visualeditor-enable' ) ) {
+ return;
+}
+
+near to the end of modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js should be all that's really needed.
+
+[1] https://en.wikipedia.org/wiki/Wikipedia:Vpt#.22Opt_out.22_of_VE_needed_under_preferences
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/Wikipedia:Vpt#.22Opt_out.22_of_VE_needed_under_preferences
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52086",task_description,"[""User preference to disable VisualEditor\n\nIt's strange that I can't find a bug for this."", 'Lots of user on en.wiki complained loudly about this [1], but nobody succeded to write a bug report for it?', 'Well, here it is:\n\nPlease provide an option in user preferences to turn VE off.', ""Some users just don't like it and don't want to have an extra tab which they don't use anyway."", ""The gadget isn't perfect, as the tab might appear for short time before it is removed again, and has to updated when VE integration changes."", 'The only reason I found for why there is no such option is this:\n\n""It was planned, but the code turned out to be seriously buggy at the last minute.', 'Getting it really, truly off (rather than just covered up) is more complicated than expected.""', 'Whatamidoing (WMF) (talk) 06:32, 2 July 2013 (UTC)\n\nNow with the minimized amount of code that is loaded at startup, it is acceptable to load the code, but just not to execute it.', ""Adding\n\nif ( !mw.user.options.get( 'visualeditor-enable' ) ) {\n return;\n}\n\nnear to the end of modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js should be all that's really needed."", '[1] URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement\n**URL**: URL\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'POTENTIAL NEW ISSUES AND REQUESTS', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+243412,User preference to disable VisualEditor,"[This comment is about the generalisation in the VE extension of the deployed patch, I open the bug 52086 for this specific generalisation inside the VE product.]
+
+I can see the logic behind the introduction of the new preference (use a negative preference instead of a positive to use it on wikis where the VE is the default editor), but for the sake of generality of the VE extension it would be better to name it as ""visualeditor-preference-disable: Disable VisualEditor"" (see bug 52086).
+
+And the temporary messages related to the deployment-test in the Wikimedia environment could be overriden in the WikimediaMessages extension. E.g. 
+  ""visualeditor-preference-enable: Enable VisualEditor (experimental, [[{{int:visualeditor-feedback-link}}|please help in reporting bugs]])""
+  ""visualeditor-preference-disable: Disable VisualEditor [during the beta phase] (but [[{{int:visualeditor-feedback-link}}|please help in reporting bugs]])""
+(I guess in this case the WikimediaMessages section in InitialiseSettings.php should be move below the VisualEditor section)",task_subcomment,"['[This comment is about the generalisation in the VE extension of the deployed patch, I open the bug 52086 for this specific generalisation inside the VE product.]', 'I can see the logic behind the introduction of the new preference (use a negative preference instead of a positive to use it on wikis where the VE is the default editor), but for the sake of generality of the VE extension it would be better to name it as ""visualeditor-preference-disable: Disable VisualEditor"" (see bug 52086).', 'And the temporary messages related to the deployment-test in the Wikimedia environment could be overriden in the WikimediaMessages extension.', 'E.g.', '""visualeditor-preference-enable: Enable VisualEditor (experimental, [[{{int:visualeditor-feedback-link}}|please help in reporting bugs]])""\n  ""visualeditor-preference-disable: Disable VisualEditor [during the beta phase] (but [[{{int:visualeditor-feedback-link}}|please help in reporting bugs]])""\n(I guess in this case the WikimediaMessages section in InitialiseSettings.php should be move below the VisualEditor section)']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+243408,User preference to disable VisualEditor,"I agree with hashar as well. And who knows, maybe hopefully by the time VE is out of beta this preference will not be really necessary (per comment 25). I'm pretty sure we're got at least a few months before we'll have to worry about that.",task_subcomment,"['I agree with hashar as well.', 'And who knows, maybe hopefully by the time VE is out of beta this preference will not be really necessary (per comment 25).', ""I'm pretty sure we're got at least a few months before we'll have to worry about that.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN']"
+243403,User preference to disable VisualEditor,So you will reopen this bug as soon as VE gets stable? Promised?,task_subcomment,"['So you will reopen this bug as soon as VE gets stable?', 'Promised?']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']"
+243399,User preference to disable VisualEditor,"For what it's worth, I agree with hashar. The bug as filed is resolved: there's now a user preference in the appropriate tab (""Editing"") that fully disables VisualEditor.
+
+I think we should deal with the future in the future. :-)",task_subcomment,"[""For what it's worth, I agree with hashar."", 'The bug as filed is resolved: there\'s now a user preference in the appropriate tab (""Editing"") that fully disables VisualEditor.', 'I think we should deal with the future in the future.', ':-)']","['SOLUTION DISCUSSION', 'SOLUTION USAGE', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+243396,User preference to disable VisualEditor,"Sorry, your perception of this bug is pretty messed up.
+
+Thhis bug is about ""disabling VE"", *not* about ""disabling VE during beta period"".
+
+The patch clearly doesn't solve this problem.",task_subcomment,"['Sorry, your perception of this bug is pretty messed up.', 'Thhis bug is about ""disabling VE"", *not* about ""disabling VE during beta period"".', ""The patch clearly doesn't solve this problem.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243393,User preference to disable VisualEditor,"This bug is about having a user preference to disable VisualEditor which is exactly what has been implemented by https://gerrit.wikimedia.org/r/#/c/75541/ . It is the proper way to handle this, not $wgHiddenPrefs :-D
+
+The fact that the preference might be gone after VE is out of beta is a different problem.  For now the request has been fulfilled as far as I understand it.  Just check the ""Temporarily disable VisualEditor while it is in beta"" in the user preference and VE is gone.",task_subcomment,"['This bug is about having a user preference to disable VisualEditor which is exactly what has been implemented by URL .', 'It is the proper way to handle this, not $wgHiddenPrefs :-D\n\nThe fact that the preference might be gone after VE is out of beta is a different problem.', 'For now the request has been fulfilled as far as I understand it.', 'Just check the ""Temporarily disable VisualEditor while it is in beta"" in the user preference and VE is gone.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'WORKAROUND']"
+243389,User preference to disable VisualEditor,"Sorry, but this is clearly *not* fixed!
+
+* The eye-wash preference in VE is nonsense and will be gone quickly when VE comes out of beta.
+* The core of the problem - disabling VE when one surely will never use it - will not be solved by this hack.
+* The failure by WMF (deploying a buggy beta software to everybody by default) is poorly concealed by this change but not solved either.
+
+In fact you're even working against your own goals with this change: In the beta phase where feedback by editors is needed most you're now offering a preference to disable VE. When VE becomes stable and feedback is not that necessary anymore the preference will be gone, and the same discussion you're trying to mute with this change will start again.
+
+Please reopen this bug, accept https://gerrit.wikimedia.org/r/73565, so we have a real fix in place!",task_subcomment,"['Sorry, but this is clearly *not* fixed!', '* The eye-wash preference in VE is nonsense and will be gone quickly when VE comes out of beta.', '* The core of the problem - disabling VE when one surely will never use it - will not be solved by this hack.', '* The failure by WMF (deploying a buggy beta software to everybody by default) is poorly concealed by this change but not solved either.', ""In fact you're even working against your own goals with this change: In the beta phase where feedback by editors is needed most you're now offering a preference to disable VE."", ""When VE becomes stable and feedback is not that necessary anymore the preference will be gone, and the same discussion you're trying to mute with this change will start again."", 'Please reopen this bug, accept GERRIT_URL, so we have a real fix in place!']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'ACTION ON ISSUE']"
+243385,User preference to disable VisualEditor,Fixed in VisualEditor extension itself with https://gerrit.wikimedia.org/r/#/c/75541/,task_subcomment,['Fixed in VisualEditor extension itself with URL'],['SOLUTION USAGE']
+243383,User preference to disable VisualEditor,"Change 73565 abandoned by Hashar:
+(bug 50929) Remove 'visualeditor-enable' from $wgHiddenPrefs
+
+Reason:
+A preference to temporarily disable VisualEditor has been introduced in the VisualEditor extension itself : https://gerrit.wikimedia.org/r/#/c/75541/
+
+This change is thus no more needed.
+
+https://gerrit.wikimedia.org/r/73565",task_subcomment,"[""Change 73565 abandoned by Hashar:\n(bug 50929) Remove 'visualeditor-enable' from $wgHiddenPrefs\n\nReason:\nA preference to temporarily disable VisualEditor has been introduced in the VisualEditor extension itself : URL\n\nThis change is thus no more needed."", 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+243380,User preference to disable VisualEditor,"Noting that the main issues causing people to disable VE are 
+1) bloat (this may be more perceived than real; the VE init.js isnt very large, and the scaffolding is used for other features besides VE) and 
+2) the UI for edit section links (which is bug 50688 and bug 50540).
+I am optimistic that both will be resolved before VisualEditor goes out of beta.",task_subcomment,"['Noting that the main issues causing people to disable VE are \n1) bloat (this may be more perceived than real; the VE init.js isnt very large, and the scaffolding is used for other features besides VE) and \n2) the UI for edit section links (which is bug 50688 and bug 50540).', 'I am optimistic that both will be resolved before VisualEditor goes out of beta.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+243376,User preference to disable VisualEditor,"https://gerrit.wikimedia.org/r/#/c/75542/ was merged today, but it is only a dirty workaround that doesn't fix the actual problem. 
+
+What happens when VisualEditor goes out of beta? Will editors that have turned it off be required to switch to it? What if they'd prefer to keep using source editing?",task_subcomment,"[""URL was merged today, but it is only a dirty workaround that doesn't fix the actual problem."", 'What happens when VisualEditor goes out of beta?', 'Will editors that have turned it off be required to switch to it?', ""What if they'd prefer to keep using source editing?""]","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243372,User preference to disable VisualEditor,"C. Scott Ananian: you're out of line.
+
+Bugzilla is regularly used for discussion (among devs and non-devs alike) and calling it abuse (comment 18) to use Bugzilla's comments field for discussion isn't appropriate at all.
+
+Richard Morris' comment (comment 20) correctly points to on-wiki discussion that's directly relevant to this bug. It's long-standing practice to cross-reference on-wiki consensus-gathering discussion with Bugzilla bugs.",task_subcomment,"[""C. Scott Ananian: you're out of line."", ""Bugzilla is regularly used for discussion (among devs and non-devs alike) and calling it abuse (comment 18) to use Bugzilla's comments field for discussion isn't appropriate at all."", ""Richard Morris' comment (comment 20) correctly points to on-wiki discussion that's directly relevant to this bug."", ""It's long-standing practice to cross-reference on-wiki consensus-gathering discussion with Bugzilla bugs.""]","['SOCIAL CONVERSATION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'FUTURE PLAN']"
+243366,User preference to disable VisualEditor,"Please do not discuss on this bug. The topic is on wikitech-l which has much more audience and is way easier to handle such long discussions :-]
+
+Thread starts at:
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070560.html",task_subcomment,"['Please do not discuss on this bug.', 'The topic is on wikitech-l which has much more audience and is way easier to handle such long discussions :-]\n\nThread starts at:\nURL']","['ISSUE CONTENT MANAGEMENT', 'ACTION ON ISSUE']"
+243360,User preference to disable VisualEditor,"@Richard Morris: Please, bugzilla is a tool for developers, not a discussion forum.   Please discuss this on the wikitech-l mailing list (url above, or subscribe at https://lists.wikimedia.org/mailman/listinfo/wikitech-l) or at the RFC you linked to, or on a Talk page.  Anywhere, really, except for bugzilla.
+
+Others: please do not respond here to Richard Morris or others.  Refrain from the temptation, whether you agree with him or not.  Make your point on one of the discussion sites (again: mailing list, talk page, RFC, IRC) not in bugzilla.
+
+Thanks.",task_subcomment,"['SCREEN_NAME Morris: Please, bugzilla is a tool for developers, not a discussion forum.', 'Please discuss this on the wikitech-l mailing list (url above, or subscribe at URL or at the RFC you linked to, or on a Talk page.', 'Anywhere, really, except for bugzilla.', 'Others: please do not respond here to Richard Morris or others.', 'Refrain from the temptation, whether you agree with him or not.', 'Make your point on one of the discussion sites (again: mailing list, talk page, RFC, IRC) not in bugzilla.', 'Thanks.']","['SOCIAL CONVERSATION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'ISSUE CONTENT MANAGEMENT', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+243353,User preference to disable VisualEditor,"Have you guys not read http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/RFC there is a clear consensus, 57 vrs 6, for ""VisualEditor should have a way to be turned off fully, easily, and without continuing to leech resources"". Many people don't want it the feedback page is constantly getting ""how do I switch this off?"" threads. Failure to implement this feature is causing more work for those on the wiki and a politically very bad decision.",task_subcomment,"['Have you guys not read URL there is a clear consensus, 57 vrs 6, for ""VisualEditor should have a way to be turned off fully, easily, and without continuing to leech resources"".', 'Many people don\'t want it the feedback page is constantly getting ""how do I switch this off?""', 'threads.', 'Failure to implement this feature is causing more work for those on the wiki and a politically very bad decision.']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+243347,User preference to disable VisualEditor,"(In reply to comment #18)
+> Tyler, please follow the entire link in comment 16.
+
+I did. It's only 3-4 people talking on a talk page. Kind of pales in comparison to the numerous people who supported this in the original link.
+
+> This discussion is occuring on wikitech-l as well:
+> http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070560.html
+> 
+> It's probably better to continue the discussion on the mailing list, rather
+> than to abuse bugzilla.
+> 
+> (Just trying to synchronize the conversation.)
+
+Agreed. I've continued the discussion there.",task_subcomment,"['(In reply to comment #18)\nQUOTE\n\nI did.', ""It's only 3-4 people talking on a talk page."", 'Kind of pales in comparison to the numerous people who supported this in the original link.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAgreed.', ""I've continued the discussion there.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+243341,User preference to disable VisualEditor,"Tyler, please follow the entire link in comment 16.
+
+This discussion is occuring on wikitech-l as well: http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070560.html
+
+It's probably better to continue the discussion on the mailing list, rather than to abuse bugzilla.
+
+(Just trying to synchronize the conversation.)",task_subcomment,"['Tyler, please follow the entire link in comment 16.', ""This discussion is occuring on wikitech-l as well: URL\n\nIt's probably better to continue the discussion on the mailing list, rather than to abuse bugzilla."", '(Just trying to synchronize the conversation.)']","['ACTION ON ISSUE', 'ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION']"
+243338,User preference to disable VisualEditor,"(In reply to comment #16)
+> Per
+> https://en.wikipedia.org/w/index.php?title=User_talk:
+> Eloquence&diff=564621335&oldid=564492863
+> and other lengthy discussion, this is and remains a WONTFIX.
+
+This is one user's talk page. What discussion are you referring to? Is the link at the top of the page no longer the consensus? Also I'd like to know exactly what reasoning there is for having this preference hidden.",task_subcomment,"[""(In reply to comment #16)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis is one user's talk page."", 'What discussion are you referring to?', 'Is the link at the top of the page no longer the consensus?', ""Also I'd like to know exactly what reasoning there is for having this preference hidden.""]","['ACTION ON ISSUE', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243334,User preference to disable VisualEditor,"Per https://en.wikipedia.org/w/index.php?title=User_talk:Eloquence&diff=564621335&oldid=564492863 and other lengthy discussion, this is and remains a WONTFIX.
+
+VisualEditor is switched on or off at the wiki-level, not on the per-user level. The fact that there is a temporary artefact of the alpha roll-out still around in the code that allows us to expose this option to users for the next few weeks (until it too goes away once the alpha roll-out is no longer needed) does not mean we should dishonestly mis-lead users into thinking that we are supporting this as a preference, which is what implementing this request would do.",task_subcomment,"['Per URL and other lengthy discussion, this is and remains a WONTFIX.', 'VisualEditor is switched on or off at the wiki-level, not on the per-user level.', 'The fact that there is a temporary artefact of the alpha roll-out still around in the code that allows us to expose this option to users for the next few weeks (until it too goes away once the alpha roll-out is no longer needed) does not mean we should dishonestly mis-lead users into thinking that we are supporting this as a preference, which is what implementing this request would do.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243328,User preference to disable VisualEditor,That would reopen bug 48666 Make VisualEditor a hidden preference.,task_subcomment,['That would reopen bug 48666 Make VisualEditor a hidden preference.'],['INVESTIGATION AND EXPLORATION']
+243325,User preference to disable VisualEditor,*** Bug 51389 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51389 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243322,User preference to disable VisualEditor,"Change 73565 had a related patch set uploaded by Odder:
+(bug 50929) Remove 'visualeditor-enable' from $wgHiddenPrefs
+
+https://gerrit.wikimedia.org/r/73565",task_subcomment,"[""Change 73565 had a related patch set uploaded by Odder:\n(bug 50929) Remove 'visualeditor-enable' from $wgHiddenPrefs\n\nGERRIT_URL""]",['BUG REPRODUCTION']
+243318,User preference to disable VisualEditor,"(In reply to comment #7)
+> This will not be a request only for English Wikipedia any longer, as soon as
+> the VE is activated by default on Wikipedias in other languages. Keep that in
+> mind!
+
+just in case what Bartos wrote is not 100% clear:
+
+The extension already implement a user-selectable enable/disable switch - nothing should be done there. 
+LocalSettings.php for enwiki specifically removes the choice, by setting the line
+
+""$wgHiddenPrefs[] = 'visualeditor-enable';""
+
+this bug is basically a request to delete this line from enwiki's LocalSettings.php, and thus allowing users to opt-out of VE.
+
+a derivative request would be such: once VE is enabled by default on other wikis, please do not to add such a line to their LocalSettings.php.
+the second part is a ""forward looking"" request, i.e. it's a request not to do something in the future, without actually knowing if there's any intention to do it...
+
+(as a side, it seems that the decision to remove user's switch was not a good one: the main result of this decision was that on enwiki, someone had to write a special gadget for disabling VE, instead of just using the built-in switch...)
+
+peace.",task_subcomment,"['(In reply to comment #7)\nQUOTE\nQUOTE\nQUOTE\n\njust in case what Bartos wrote is not 100% clear:\n\nThe extension already implement a user-selectable enable/disable switch - nothing should be done there.', 'LocalSettings.php for enwiki specifically removes the choice, by setting the line\n\n""$wgHiddenPrefs[] = \'visualeditor-enable\';""\n\nthis bug is basically a request to delete this line from enwiki\'s LocalSettings.php, and thus allowing users to opt-out of VE.', 'a derivative request would be such: once VE is enabled by default on other wikis, please do not to add such a line to their LocalSettings.php.', 'the second part is a ""forward looking"" request, i.e.', ""it's a request not to do something in the future, without actually knowing if there's any intention to do it...\n\n(as a side, it seems that the decision to remove user's switch was not a good one: the main result of this decision was that on enwiki, someone had to write a special gadget for disabling VE, instead of just using the built-in switch...)\n\npeace.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'FUTURE PLAN']"
+243314,User preference to disable VisualEditor,"Great, thank you.
+
+I'm marking this bug with the ""easy"" keyword accordingly.",task_subcomment,"['Great, thank you.', 'I\'m marking this bug with the ""easy"" keyword accordingly.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+243309,User preference to disable VisualEditor,"(In reply to comment #9)
+> Can you explain what the code in this area looks like? There _was_ a user
+> preference previously, it's just gone missing. Is this simply a matter of
+> setting a configuration variable?
+
+Yes, it's just a matter of removing ""$wgHiddenPrefs[] = 'visualeditor-enable';"" in CommonSettings.php.",task_subcomment,"['(In reply to comment #9)\nQUOTE\nQUOTE\nQUOTE\n\nYes, it\'s just a matter of removing ""$wgHiddenPrefs[] = \'visualeditor-enable\';"" in CommonSettings.php.']",['SOLUTION DISCUSSION']
+243304,User preference to disable VisualEditor,"(In reply to comment #6)
+> This is actually a site request for the English Wikipedia right now, as this
+> preference is enabled everywhere else right now. Changing Product/Component
+> accordingly.
+
+Can you explain what the code in this area looks like? There _was_ a user preference previously, it's just gone missing. Is this simply a matter of setting a configuration variable?",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nCan you explain what the code in this area looks like?', ""There _was_ a user preference previously, it's just gone missing."", 'Is this simply a matter of setting a configuration variable?']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+243300,User preference to disable VisualEditor,"(In reply to comment #3)
+> This should be in the obvious place, in the editing tab of user preferences,
+> not a gadget.
+
+Yep.",task_subcomment,['(In reply to comment #3)\nQUOTE\nQUOTE\n\nYep.'],['SOLUTION DISCUSSION']
+243292,User preference to disable VisualEditor,"This will not be a request only for English Wikipedia any longer, as soon as the VE is activated by default on Wikipedias in other languages. Keep that in mind!",task_subcomment,"['This will not be a request only for English Wikipedia any longer, as soon as the VE is activated by default on Wikipedias in other languages.', 'Keep that in mind!']","['FUTURE PLAN', 'SOLUTION DISCUSSION']"
+243284,User preference to disable VisualEditor,"This is actually a site request for the English Wikipedia right now, as this preference is enabled everywhere else right now. Changing Product/Component accordingly.",task_subcomment,"['This is actually a site request for the English Wikipedia right now, as this preference is enabled everywhere else right now.', 'Changing Product/Component accordingly.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+243275,User preference to disable VisualEditor,*** Bug 51179 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51179 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243263,User preference to disable VisualEditor,"Created attachment 12827
+en.wp temporary workaround
+
+Since I doubt this will get fixed any time soon, I have implemented a change to a label, to redirect users with words from on preferences tab to another.
+
+**Attached**: {F11458}",task_subcomment,"['Created attachment 12827\nen.wp temporary workaround\n\nSince I doubt this will get fixed any time soon, I have implemented a change to a label, to redirect users with words from on preferences tab to another.', '**Attached**: {F11458}']","['WORKAROUNDS', 'OBSERVED BUG BEHAVIOR']"
+243254,User preference to disable VisualEditor,"This should be in the obvious place, in the editing tab of user preferences, not a gadget.",task_subcomment,"['This should be in the obvious place, in the editing tab of user preferences, not a gadget.']",['SOLUTION DISCUSSION']
+243247,User preference to disable VisualEditor,"(Quote from comment #0)
+> The gadget isn't perfect, as the tab might appear for short time before it is
+> removed again, and has to updated when VE integration changes.",task_subcomment,['(Quote from comment #0)\nQUOTE\nQUOTE'],['SOLUTION DISCUSSION']
+243240,User preference to disable VisualEditor,"To disable: Preferences > Gadgets > Editing (section) > checkmark for ""Remove VisualEditor from the user interface"" > Save
+
+This is probably mentioned on http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback",task_subcomment,"['To disable: Preferences > Gadgets > Editing (section) > checkmark for ""Remove VisualEditor from the user interface"" > Save\n\nThis is probably mentioned on URL']",['INVESTIGATION AND EXPLORATION']
+52925,"VisualEditor: Edit section links below a diff should point to the rev shown, not the (older) rev the diff compares against","See: https://en.wikipedia.org/w/index.php?title=New%20Zealand%20English&diff=0&oldid=123
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=New%20Zealand%20English&diff=0&oldid=123",task_description,"['VisualEditor: Edit section links below a diff should point to the rev shown, not the (older) rev the diff compares against\n\nSee: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor\n**URL**: URL']",['BUG REPRODUCTION']
+243061,"VisualEditor: Edit section links below a diff should point to the rev shown, not the (older) rev the diff compares against","This is now deployed and appears to be working as expected in production, according to my testing. Marking as fixed. Please re-open if you find otherwise.",task_subcomment,"['This is now deployed and appears to be working as expected in production, according to my testing.', 'Marking as fixed.', 'Please re-open if you find otherwise.']","['SOLUTION USAGE', 'ACTION ON ISSUE', 'ACTION ON ISSUE']"
+243052,"VisualEditor: Edit section links below a diff should point to the rev shown, not the (older) rev the diff compares against","Change 72544 merged by jenkins-bot:
+mw.ViewPageTarget.init: Only bind edit section links on view page
+
+https://gerrit.wikimedia.org/r/72544",task_subcomment,['Change 72544 merged by jenkins-bot:\nmw.ViewPageTarget.init: Only bind edit section links on view page\n\nGERRIT_URL'],['SOLUTION USAGE']
+243045,"VisualEditor: Edit section links below a diff should point to the rev shown, not the (older) rev the diff compares against","Change 72544 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Don't bind edit section links on non-view page
+
+https://gerrit.wikimedia.org/r/72544",task_subcomment,"[""Change 72544 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget: Don't bind edit section links on non-view page\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+243037,"VisualEditor: Edit section links below a diff should point to the rev shown, not the (older) rev the diff compares against","(In reply to comment #0)
+> See:
+> https://en.wikipedia.org/w/index.
+> php?title=New%20Zealand%20English&diff=0&oldid=123
+
+I *think* this will get fixed by gerrit 72070 - Timo?",task_subcomment,['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nI *think* this will get fixed by gerrit 72070 - Timo?'],['SOLUTION DISCUSSION']
+52916,"VisualEditor: Preview the result of the transclusion dialog whilst it's be edited (before ""Apply changes"")","Taken from English Wikipedia
+
+***
+
+[[Template:Convert]] is actually a good example of where TemplateData falls over and hits the ground. The meaning of the numbered parameters changes depending on how many of them there are and whether the entry is text or a number. For example, each of the following are valid:
+{{convert|3.21|kg|lb}}
+3.21 kilograms (7.1 lb)
+{{convert|3.21|mi|3}}
+3.21 miles (5.166 km)
+{{convert|60|to|170|kg|lb}}
+60 to 170 kilograms (130 to 370 lb)
+{{convert|60|+/-|10|kg|lb}}
+60 ± 10 kilograms (130 ± 22 lb)
+{{convert|6|ft|5|in|m}}
+6 feet 5 inches (1.96 m)
+In those examples, parameter 3 is variously 1) The output unit, 2) The number of significant figures, 3) The upper limit of a range, 4) The measurement uncertainty, 5) The number of inches in foot-inches measurement. Now write a TemplateData description for parameter 3 (or 2 or 4 or 5)? Convert is used on 500,000+ pages, so it is not like it can simply be redesigned at this point. That said, if someone can see the values of each parameter in the transclusion window then it would still be pretty easy to figure out which one they need to edit. I would suggest that the transclusion editor needs a way to preview the parameter contents (even if just a snippet) without having to click on each parameter. Dragons flight (talk) 17:57, 5 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Preview the result of the transclusion dialog whilst it\'s be edited (before ""Apply changes"")\n\nTaken from English Wikipedia\n\n***\n\n[[Template:Convert]] is actually a good example of where TemplateData falls over and hits the ground.', 'The meaning of the numbered parameters changes depending on how many of them there are and whether the entry is text or a number.', 'For example, each of the following are valid:\n{{convert|3.21|kg|lb}}\n3.21 kilograms (7.1 lb)\n{{convert|3.21|mi|3}}\n3.21 miles (5.166 km)\n{{convert|60|to|170|kg|lb}}\n60 to 170 kilograms (130 to 370 lb)\n{{convert|60|+/-|10|kg|lb}}\n60 ± 10 kilograms (130 ± 22 lb)\n{{convert|6|ft|5|in|m}}\n6 feet 5 inches (1.96 m)\nIn those examples, parameter 3 is variously 1) The output unit, 2) The number of significant figures, 3) The upper limit of a range, 4) The measurement uncertainty, 5) The number of inches in foot-inches measurement.', 'Now write a TemplateData description for parameter 3 (or 2 or 4 or 5)?', 'Convert is used on 500,000+ pages, so it is not like it can simply be redesigned at this point.', 'That said, if someone can see the values of each parameter in the transclusion window then it would still be pretty easy to figure out which one they need to edit.', 'I would suggest that the transclusion editor needs a way to preview the parameter contents (even if just a snippet) without having to click on each parameter.', 'Dragons flight (talk) 17:57, 5 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+52910,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,"Reproduce:
+
+1. Go to this page: https://he.wikipedia.org/wiki/%D7%A9%D7%9C%D7%9E%D7%94_%D7%A4%D7%99%D7%9C%D7%91%D7%A8 (Image is floating on the left)
+
+2. Edit the page. The image is now stretched all across the content area, pushing the text down.
+
+This is a 'no picture existing' template. In the Hebrew wiki: https://he.wikipedia.org/wiki/%D7%AA%D7%91%D7%A0%D7%99%D7%AA:%D7%90%D7%99%D7%9F_%D7%AA%D7%9E%D7%95%D7%A0%D7%94
+
+It is probably an issue of the template code, but since it's used very often, it would be great if someone can help find the problem in this so we can fix the template itself.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50395",task_description,"['VisualEditor: CE CSS munging issue with specific (highly used) hewiki template\n\nReproduce:\n\n1.', 'Go to this page: URL (Image is floating on the left)\n\n2.', 'Edit the page.', 'The image is now stretched all across the content area, pushing the text down.', ""This is a 'no picture existing' template."", ""In the Hebrew wiki: URL\n\nIt is probably an issue of the template code, but since it's used very often, it would be great if someone can help find the problem in this so we can fix the template itself."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+242239,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,"Change 105639 merged by jenkins-bot:
+CSSJanus: Account for attribute selectors in brace lookahead
+
+https://gerrit.wikimedia.org/r/105639",task_subcomment,['Change 105639 merged by jenkins-bot:\nCSSJanus: Account for attribute selectors in brace lookahead\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+242229,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,"Change 105640 merged by jenkins-bot:
+Force CSSJanus to not flip image alignment classes
+
+https://gerrit.wikimedia.org/r/105640",task_subcomment,['Change 105640 merged by jenkins-bot:\nForce CSSJanus to not flip image alignment classes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+242225,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,"Change 105639 had a related patch set uploaded by Catrope:
+Support attribute selectors in CSSJanus
+
+https://gerrit.wikimedia.org/r/105639",task_subcomment,['Change 105639 had a related patch set uploaded by Catrope:\nSupport attribute selectors in CSSJanus\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+242222,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,"Change 105640 had a related patch set uploaded by Mooeypoo:
+Force CSSJanus to not flip image alignment classes
+
+https://gerrit.wikimedia.org/r/105640",task_subcomment,['Change 105640 had a related patch set uploaded by Mooeypoo:\nForce CSSJanus to not flip image alignment classes\n\nGERRIT_URL'],['ACTION ON ISSUE']
+242219,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,"I found the remaining issue - since the page (and transclusion div) is set to dir='rtl' the ""mw-halign-left"" class float:left turned to float:right. 
+
+This is quite odd, since these classes have /*@noflip*/ on them.",task_subcomment,"['I found the remaining issue - since the page (and transclusion div) is set to dir=\'rtl\' the ""mw-halign-left"" class float:left turned to float:right.', 'This is quite odd, since these classes have /*@noflip*/ on them.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242215,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,"Ah! Partially. The image is no longer spread wide, but it floats the wrong way - it should float to the left, but it floats to the right inside VE.",task_subcomment,"['Ah!', 'Partially.', 'The image is no longer spread wide, but it floats the wrong way - it should float to the left, but it floats to the right inside VE.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242211,VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,Was this fixed by the fix for bug 53436?,task_subcomment,['Was this fixed by the fix for bug 53436?'],['OBSERVED BUG BEHAVIOR']
+52900,VisualEditor: Label the edit summary box as such,"A user points out that much of our communication both external and internal of the wiki instruct people to leave an edit summary, but the save dialog doesn't name this field as such, which might make it difficult for people to make a match between the instructions and the actual save dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: Label the edit summary box as such\n\nA user points out that much of our communication both external and internal of the wiki instruct people to leave an edit summary, but the save dialog doesn't name this field as such, which might make it difficult for people to make a match between the instructions and the actual save dialog."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+241773,VisualEditor: Label the edit summary box as such,"This was done, ages ago.",task_subcomment,"['This was done, ages ago.']",['OBSERVED BUG BEHAVIOR']
+52898,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"If you have the [[Hands-on universe|Hands-On Universe]] link, it will report that Hands-On universe doesn't exist (which it does). This is probably because it matches on the different case: Hands-On Universe and then stops comparing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52596",task_description,"[""VisualEditor: Link dialog lies about existence of page due to case insensitive matching\n\nIf you have the [[Hands-on universe|Hands-On Universe]] link, it will report that Hands-On universe doesn't exist (which it does)."", 'This is probably because it matches on the different case: Hands-On Universe and then stops comparing.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241714,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,This was fixed as part of the tweaks to the link inspector earlier this month.,task_subcomment,['This was fixed as part of the tweaks to the link inspector earlier this month.'],['OBSERVED BUG BEHAVIOR']
+241709,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"Per discussion at Bug 52596 the presence of a redirect with a title of <=3 characters /may/ prevent an article with that title (but differently capitalised) appearing in the suggestions list.
+
+For example the existence of the [[Fra]] redirect may be what is preventing the [[FRA]] article appearing in the list (something is, and the redirect is one theory).",task_subcomment,"['Per discussion at Bug 52596 the presence of a redirect with a title of <=3 characters /may/ prevent an article with that title (but differently capitalised) appearing in the suggestions list.', 'For example the existence of the [[Fra]] redirect may be what is preventing the [[FRA]] article appearing in the list (something is, and the redirect is one theory).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241704,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"Forgot to add that redirects that differ other than by capitalisation are shown - e.g. [[Elizabeth II of the United Kingdom]], a redirect to [[Elizabeth II]], appears in the suggestions list.",task_subcomment,"['Forgot to add that redirects that differ other than by capitalisation are shown - e.g.', '[[Elizabeth II of the United Kingdom]], a redirect to [[Elizabeth II]], appears in the suggestions list.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+241700,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,*** Bug 52251 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52251 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241695,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"This also happens with redirects. 
+For example, [[Github]] is a redirect to [[GitHub]] but [[github]] is shown as not existing.
+
+See attachment 13013 to bug 52251",task_subcomment,"['This also happens with redirects.', 'For example, [[Github]] is a redirect to [[GitHub]] but [[github]] is shown as not existing.', 'See attachment 13013 to bug 52251']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+241689,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"(In reply to comment #1)
+> Other examples: [[A]], [[B]], [[To]], [[Hi]]
+
+I filed this as bug 51013.",task_subcomment,['(In reply to comment #1)\nQUOTE\n\nI filed this as bug 51013.'],['BUG REPRODUCTION']
+241683,VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"Other examples: [[A]], [[B]], [[To]], [[Hi]]",task_subcomment,"['Other examples: [[A]], [[B]], [[To]], [[Hi]]']",['OBSERVED BUG BEHAVIOR']
+52897,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","In the old editor, you could hit ctrl-alt-s to save the page. In the new editor the save action is not reachable using the keyboard.
+
+We could just add ctrl-s/cmd-s to the Save button ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=38042
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50047",task_description,"['VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog\n\nIn the old editor, you could hit ctrl-alt-s to save the page.', 'In the new editor the save action is not reachable using the keyboard.', 'We could just add ctrl-s/cmd-s to the Save button ?', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+241655,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","Change 110434 merged by jenkins-bot:
+Use accesskey=s on the save buttons
+
+https://gerrit.wikimedia.org/r/110434",task_subcomment,['Change 110434 merged by jenkins-bot:\nUse accesskey=s on the save buttons\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241650,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","Change 113319 abandoned by Esanders:
+Add save shortcut to dialog
+
+Reason:
+ALT+S is MediaWiki only, abandoning in favour of Idf4fa31b98d1fa9e
+
+https://gerrit.wikimedia.org/r/113319",task_subcomment,"['Change 113319 abandoned by Esanders:\nAdd save shortcut to dialog\n\nReason:\nALT+S is MediaWiki only, abandoning in favour of Idf4fa31b98d1fa9e\n\nGERRIT_URL']",['BUG REPRODUCTION']
+241645,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","Change 113319 had a related patch set uploaded by Alex Monk:
+Add save shortcut to dialog
+
+https://gerrit.wikimedia.org/r/113319",task_subcomment,['Change 113319 had a related patch set uploaded by Alex Monk:\nAdd save shortcut to dialog\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241642,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","Change 110434 had a related patch set uploaded by Alex Monk:
+Use accesskey=s on the save buttons
+
+https://gerrit.wikimedia.org/r/110434",task_subcomment,['Change 110434 had a related patch set uploaded by Alex Monk:\nUse accesskey=s on the save buttons\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+241639,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","Trying to use accesskey=s like action=edit will make this conflict with FlaggedRevs, which doesn't appear on action=edit but does on veaction=edit (with display:none).",task_subcomment,"[""Trying to use accesskey=s like action=edit will make this conflict with FlaggedRevs, which doesn't appear on action=edit but does on veaction=edit (with display:none).""]",['OBSERVED BUG BEHAVIOR']
+241637,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","I don't have any particularly strong views about the right way to do this, but I really want to be able to open the page in VisualEditor, make a small change to the text, and save the page, without ever taking my hands off the keyboard.",task_subcomment,"[""I don't have any particularly strong views about the right way to do this, but I really want to be able to open the page in VisualEditor, make a small change to the text, and save the page, without ever taking my hands off the keyboard.""]",['SOLUTION DISCUSSION']
+241635,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog",*** Bug 53693 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53693 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241630,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog",*** Bug 52745 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52745 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241626,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","Having shortcuts for Show preview/Review your changes, and for Save page (two different buttons, so if one shortcut is used for both, VE needs to check whether it is on the main page or in a dialog box), would certainly be helpful. To quote the WMF Deputy Director: ""It's worth noting that VisualEditor has its own set of keyboard shortcuts, which can help with common tasks such as linking (which I actually already find faster in VE) ...""
+
+And yes, there is also the accessibility issue - anything that can *only* be done by mouse is, by definition, an immovable problem to a physically disabled person who can only use a keyboard.",task_subcomment,"['Having shortcuts for Show preview/Review your changes, and for Save page (two different buttons, so if one shortcut is used for both, VE needs to check whether it is on the main page or in a dialog box), would certainly be helpful.', 'To quote the WMF Deputy Director: ""It\'s worth noting that VisualEditor has its own set of keyboard shortcuts, which can help with common tasks such as linking (which I actually already find faster in VE) ...""\n\nAnd yes, there is also the accessibility issue - anything that can *only* be done by mouse is, by definition, an immovable problem to a physically disabled person who can only use a keyboard.']","['SOLUTION DISCUSSION', 'MOTIVATION']"
+241622,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","(In reply to comment #2)
+> In the old editor, I would simply use TAB to reach the edit summary, type my
+> edit summary and press ENTER to activate the ""Save page"" button and save. If
+> I wanted to mark the edit minor, then I could type my edit summary, press TAB,
+> SPACE, and then ENTER to ""Save page"".
+
+Yeah... I split this out to bug 51918.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah...', 'I split this out to bug 51918.']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+241616,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog",This seems similar to bug 38042. They're not identical but definitely related and they could possibly be usefully fixed at the same time.,task_subcomment,"['This seems similar to bug 38042.', ""They're not identical but definitely related and they could possibly be usefully fixed at the same time.""]","['MOTIVATION', 'SOLUTION DISCUSSION']"
+241609,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog","**sk8er_97456** wrote:
+
+In the old editor, I would simply use TAB to reach the edit summary, type my edit summary and press ENTER to activate the ""Save page"" button and save. If I wanted to mark the edit minor, then I could type my edit summary, press TAB, SPACE, and then ENTER to ""Save page"".
+
+I can see that the new box for entering an edit summary allows newlines to be entered. I am not sure this is a good idea, because I just used a WSYIWYG editor and now ""What I see"" - well-formatted paragraphs describing my edit - is not going to be ""what I get"" - everything smashed on one line in the article history. But that is perhaps grist for another bug mill.
+
+It seems that the ""Save page"" button never receives caret focus if I use TAB to try to get there. This would seem to have accessibility ramifications.",task_subcomment,"['**sk8er_97456** wrote:\n\nIn the old editor, I would simply use TAB to reach the edit summary, type my edit summary and press ENTER to activate the ""Save page"" button and save.', 'If I wanted to mark the edit minor, then I could type my edit summary, press TAB, SPACE, and then ENTER to ""Save page"".', 'I can see that the new box for entering an edit summary allows newlines to be entered.', 'I am not sure this is a good idea, because I just used a WSYIWYG editor and now ""What I see"" - well-formatted paragraphs describing my edit - is not going to be ""what I get"" - everything smashed on one line in the article history.', 'But that is perhaps grist for another bug mill.', 'It seems that the ""Save page"" button never receives caret focus if I use TAB to try to get there.', 'This would seem to have accessibility ramifications.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241604,"VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog",I think taking over ctrl-s/⌘-s which is already used by every browser for a different task (local save of rendered HTML) is a bit rude; I'd suggest just implementing the same keyboard shortcut.,task_subcomment,"[""I think taking over ctrl-s/⌘-s which is already used by every browser for a different task (local save of rendered HTML) is a bit rude; I'd suggest just implementing the same keyboard shortcut.""]",['SOLUTION DISCUSSION']
+52896,VisualEditor: Support editing citations defined within a template,"For example, look at https://en.wikipedia.org/w/index.php?title=Peach_Springs_Trading_Post&oldid=563257259&veaction=edit.
+
+Citation [1] is defined inside the infobox template. It is then reused at the end of the first paragraph, but when you click the [1] there, you get an inspector with the message: ""This reference is defined in a template or generated block and for now can be only edited in source mode.""
+
+This also comes up when citations are defined within a template like `{{reflist}}`, as at https://en.wikipedia.org/w/index.php?title=Helminthopsis&oldid=592365854.
+
+**See Also**:
+T53289",task_description,"['VisualEditor: Support editing citations defined within a template\n\nFor example, look at URL\n\nCitation [1] is defined inside the infobox template.', 'It is then reused at the end of the first paragraph, but when you click the [1] there, you get an inspector with the message: ""This reference is defined in a template or generated block and for now can be only edited in source mode.""', 'This also comes up when citations are defined within a template like CODE, as at URL\n\n**See Also**:\nT53289']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+2250462,VisualEditor: Support editing citations defined within a template,"@Pginer-WMF That seems like a different problem. The bug here is that editing //references defined within a template// doesn't work, and VisualEditor recognizes this and mostly prevents them from being messed up. The other bug is confusing, but it seems that ContentTranslation has some issues with //templates used inside references//, and it //doesn't// recognize this situation and messes up the markup as a result.",task_subcomment,"['SCREEN_NAME-WMF That seems like a different problem.', ""The bug here is that editing //references defined within a template// doesn't work, and VisualEditor recognizes this and mostly prevents them from being messed up."", ""The other bug is confusing, but it seems that ContentTranslation has some issues with //templates used inside references//, and it //doesn't// recognize this situation and messes up the markup as a result.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+2247817,VisualEditor: Support editing citations defined within a template,I also received complaints from editors at Russian Wikipedia that this behavior greatly interferes with their work.,task_subcomment,['I also received complaints from editors at Russian Wikipedia that this behavior greatly interferes with their work.'],['OBSERVED BUG BEHAVIOR']
+2246875,VisualEditor: Support editing citations defined within a template,"Sharing a recent comment from a user on a ticket where this issue manifests in Content Translation since it uses the Visual Editor editing surface:
+
+>>! In T213277#9403536, @Framawiki wrote:
+> This bug is really the worst of the ones opened on #contenttranslation in my opinion, given the time spent by all the volunteer contributors who have to go back behind a translation to try and reformat the translations that have been substituted. It literally freezes the citation in a version that can't be edited later, except if somebody spend some time to fill a template. Not good to have such non-editable stuff in our wikis !
+> 
+> It still happens regularly in 2023, I have a script that at least removes unnecessary categories added when substituting citation templates. Check out ""untranslated category"" (""catégorie non traduite"") in my bot's list of [[ https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Contributions&end=&namespace=0&start=&tagfilter=&target=Framabot&offset=&limit=100 | recent contributions ]], ie [[ https://fr.wikipedia.org/w/index.php?title=Rowland_Prothero&diff=prev&oldid=210406768 ]]. I can just remove the category shown in red in the article, there is no automatic way to reverse the template substitution (except spend some days with regexes for low success..)
+",task_subcomment,['Sharing a recent comment from a user on a ticket where this issue manifests in Content Translation since it uses the Visual Editor editing surface:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE'],['INVESTIGATION AND EXPLORATION']
+1715428,VisualEditor: Support editing citations defined within a template,"This is discussed in hewiki village pump: https://he.wikipedia.org/w/index.php?title=%D7%95%D7%99%D7%A7%D7%99%D7%A4%D7%93%D7%99%D7%94:%D7%9E%D7%96%D7%A0%D7%95%D7%9F&oldid=31292360#%D7%94%D7%A2%D7%95%D7%A8%D7%9A_%D7%94%D7%97%D7%96%D7%95%D7%AA%D7%99_%D7%9C%D7%90_%D7%A2%D7%95%D7%91%D7%93_%D7%A2%D7%9D_{{%D7%94%D7%A2%D7%A8%D7%94%7C...}}
+
+To summarize the discussion there:
+* (background) hewiki is written in Hebrew, and Hebrew is right to left language. Using tags such as  is not behaving nicely to the source editor as ""ref"" is all latin characters that force LTR, and there is no support translated tags ( T30980 ) 
+* Editors who use source editor commonly replace  to template {{הערה}} which is basically {{#tag:ref}}. Editors who use VisualEditor complain this breaks reference editing, because VE lacks proper support for references defined in templates",task_subcomment,"['This is discussed in hewiki village pump: URL\n\nTo summarize the discussion there:\n* (background) hewiki is written in Hebrew, and Hebrew is right to left language.', 'Using tags such as  is not behaving nicely to the source editor as ""ref"" is all latin characters that force LTR, and there is no support translated tags ( T30980 ) \n* Editors who use source editor commonly replace  to template {{הערה}} which is basically {{#tag:ref}}.', 'Editors who use VisualEditor complain this breaks reference editing, because VE lacks proper support for references defined in templates']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+1379439,VisualEditor: Support editing citations defined within a template,"Based on [[ https://www.mediawiki.org/w/index.php?title=Topic:V8rwlqoii9ylxtl2&topic_showPostId=v9x2up7pdri3gj9e&fromnotif=1#flow-post-v9x2up7pdri3gj9e | this conversation ]] with a Content translation user, [[ https://en.wikipedia.org/wiki/Outreachy | Outreachy ]] is another good example article for this kind of issue, where most references are defined inside a ""reflist"" template.",task_subcomment,"['Based on [[ URL | this conversation ]] with a Content translation user, [[ URL | Outreachy ]] is another good example article for this kind of issue, where most references are defined inside a ""reflist"" template.']",['SOLUTION DISCUSSION']
+1291088,VisualEditor: Support editing citations defined within a template,"To slightly restate the suggestion, a good starting goal would be for the content of a reference to be editable in cases where VE is able to identify the reference and open the Reference dialog. This essentially requires being able to figure out how to edit the element that now ""only can be editing in source mode"". ",task_subcomment,"['To slightly restate the suggestion, a good starting goal would be for the content of a reference to be editable in cases where VE is able to identify the reference and open the Reference dialog.', 'This essentially requires being able to figure out how to edit the element that now ""only can be editing in source mode"".']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+1290928,VisualEditor: Support editing citations defined within a template,"This ticket focuses on improving the support for references defined inside any template.
+References defined inside the [[ https://en.wikipedia.org/wiki/Template:Reflist | Reflist template ]] seems one of the most prominent instances of the problem. So maybe it is worth focusing on fixing this particular case if that is simpler than finding a generic solution that works for all kinds of templates.
+
+Based on [[ https://ca.wikipedia.org/w/index.php?title=Tema:Uwf7s3n1s8391x6a&topic_showPostId=v0movrdn2phc2ww8#flow-post-v0movrdn2phc2ww8 | reports from en editor ]] about a problematic translation I found [[ https://en.wikipedia.org/wiki/The_Deer%27s_Cry_(P%C3%A4rt) | The Deer's Cry (Pärt) ]] a good example article where most references cannot be edited with Visual Editor because the are defined inside the list of references:
+
+{F29284489, size=full}",task_subcomment,"['This ticket focuses on improving the support for references defined inside any template.', 'References defined inside the [[ URL | Reflist template ]] seems one of the most prominent instances of the problem.', 'So maybe it is worth focusing on fixing this particular case if that is simpler than finding a generic solution that works for all kinds of templates.', ""Based on [[ URL | reports from en editor ]] about a problematic translation I found [[ URL | The Deer's Cry (Pärt) ]] a good example article where most references cannot be edited with Visual Editor because the are defined inside the list of references:\n\n{F29284489, size=full}""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+1184469,VisualEditor: Support editing citations defined within a template,"This limitation has been reported several times in the context of [[ https://www.mediawiki.org/wiki/Content_translation | Content translation ]]. In this case, the main limitation is that Content Translation cannot transfer those references from the source article into the translation, when adding a paragraph with references to translate. So more than being able to edit existing references (which would be great, but may be less common) here the issue is that these references are gone.
+
+In addition, Content translation only supports the visual mode, users cannot switch to wikitext mode as a workaround there. The specific Content translation issue is captured in {T209266} for more details. ",task_subcomment,"['This limitation has been reported several times in the context of [[ URL | Content translation ]].', 'In this case, the main limitation is that Content Translation cannot transfer those references from the source article into the translation, when adding a paragraph with references to translate.', 'So more than being able to edit existing references (which would be great, but may be less common) here the issue is that these references are gone.', 'In addition, Content translation only supports the visual mode, users cannot switch to wikitext mode as a workaround there.', 'The specific Content translation issue is captured in {T209266} for more details.']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+577376,VisualEditor: Support editing citations defined within a template,"Why isn't this given a higher priority, and/or assigned to someone? This issue affects every article that has an infobox with one or more citations, and that's a VERY large number, and continually increasing - and a high percentage of the most viewed articles DO have infoboxes.
+
+More importantly, this isn't just an issue of problems with reuse: having a citation/footnote in a template such as an infobox also disrupts the numbering system for footnotes - the numbering that what appears in the body of an article, when in VE editing mode, //doesn't match //the list of footnotes shown in VE editing mode. That's obviously a source of confusion to those doing editing; again, this certainly affects thousands of articles, and quite probably tens of thousands. 
+
+We //want// as much information as possible in Wikipedia articles to have inline supporting sources, and infoboxes are extremely popular (and helpful to readers). But the combination - citations inside templates such as infoboxes - is currently disruptive when editing using VE. That should be fixed.",task_subcomment,"[""Why isn't this given a higher priority, and/or assigned to someone?"", ""This issue affects every article that has an infobox with one or more citations, and that's a VERY large number, and continually increasing - and a high percentage of the most viewed articles DO have infoboxes."", ""More importantly, this isn't just an issue of problems with reuse: having a citation/footnote in a template such as an infobox also disrupts the numbering system for footnotes - the numbering that what appears in the body of an article, when in VE editing mode, //doesn't match //the list of footnotes shown in VE editing mode."", ""That's obviously a source of confusion to those doing editing; again, this certainly affects thousands of articles, and quite probably tens of thousands."", 'We //want// as much information as possible in Wikipedia articles to have inline supporting sources, and infoboxes are extremely popular (and helpful to readers).', 'But the combination - citations inside templates such as infoboxes - is currently disruptive when editing using VE.', 'That should be fixed.']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+241578,VisualEditor: Support editing citations defined within a template,"(In reply to John Broughton from comment #1)
+> This should NOT be a low priority. It's quite common for an article to have
+> ALL references inside a template - see, for example,
+> https://en.wikipedia.org/wiki/Helminthopsis . 
+> 
+> At the moment, VE is able to figure out that the citation information is
+> elsewhere - a tooltip appears that says ""This reference is defined in a
+> template or other generated block, and for now can be only edited in source
+> mode."" If VE can figure that out
+
+We figure that out because we can tell that there's no actual reference on the page, so presumably it was made with a hack.
+
+>, then it should be able to perform the following three additional steps:
+
+This doesn't actually follow.
+
+
+> * Check if the information is in the {{reflist}} template (match the ""ref
+> name="" parameter in the body of the text to a ref name parameter within the
+> reflist template)
+
+No. That would require making up a list of hack templates that each wiki uses, which is a WONTFIX if ever there was one. See instead bug 51260 which will mean we can get rid of this class of template hacks once and for all.
+ 
+> * If a match is found, pull the relevant citation information from the
+> reflist template, allowing the user to edit it
+
+Again, this would require a list of hack extraction approaches for each of the hack templates. WONTFIX. Sorry, but these templates are ghastly abominations and should have been strangled at birth.
+
+> * After the edit is finished, put the (modified) citation information back
+> into the reflist template
+
+That requires magic psychic modification of wikitext. Yet again, WONTFIX. Sorry.
+
+
+> (Side note: for edit conflict purposes, this is an edit of the section where
+> the reflist template is located, not where the footnote label exists within
+> the body of the text).
+
+You are mistaken about how edit conflict detection works. Sections don't come into it. See endless suggestions and bugs passim where this myth has been disproven.
+
+> If VE is NOT modified to allow users to edit such references/citations,
+> users are going to be (randomly) frustrated because they can't edit any
+> footnotes in some articles using VE (see above) and because in some articles
+> (https://en.wikipedia.org/wiki/Pope_Francis , for example), there are
+> occasional footnotes that aren't editable in VE.
+
+Or, alternatively, we could dump the stupid templates that make it harder for users even using wikitext to know what on Earth is happening, and instead use the wikitext the way it was designed, without resorting to hacks of doom?",task_subcomment,"[""(In reply to John Broughton from comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe figure that out because we can tell that there's no actual reference on the page, so presumably it was made with a hack."", ""QUOTE\n\nThis doesn't actually follow."", 'QUOTE\nQUOTE\nQUOTE\n\nNo.', 'That would require making up a list of hack templates that each wiki uses, which is a WONTFIX if ever there was one.', 'See instead bug 51260 which will mean we can get rid of this class of template hacks once and for all.', 'QUOTE\nQUOTE\n\nAgain, this would require a list of hack extraction approaches for each of the hack templates.', 'WONTFIX.', 'Sorry, but these templates are ghastly abominations and should have been strangled at birth.', 'QUOTE\nQUOTE\n\nThat requires magic psychic modification of wikitext.', 'Yet again, WONTFIX.', 'Sorry.', 'QUOTE\nQUOTE\nQUOTE\n\nYou are mistaken about how edit conflict detection works.', ""Sections don't come into it."", 'See endless suggestions and bugs passim where this myth has been disproven.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOr, alternatively, we could dump the stupid templates that make it harder for users even using wikitext to know what on Earth is happening, and instead use the wikitext the way it was designed, without resorting to hacks of doom?']","['MOTIVATION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'MOTIVATION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+241573,VisualEditor: Support editing citations defined within a template,"This should NOT be a low priority. It's quite common for an article to have ALL references inside a template - see, for example, https://en.wikipedia.org/wiki/Helminthopsis . 
+
+At the moment, VE is able to figure out that the citation information is elsewhere - a tooltip appears that says ""This reference is defined in a template or other generated block, and for now can be only edited in source mode."" If VE can figure that out, then it should be able to perform the following three additional steps:
+
+* Check if the information is in the {{reflist}} template (match the ""ref name="" parameter in the body of the text to a ref name parameter within the reflist template)
+
+* If a match is found, pull the relevant citation information from the reflist template, allowing the user to edit it
+
+* After the edit is finished, put the (modified) citation information back into the reflist template
+
+(Side note: for edit conflict purposes, this is an edit of the section where the reflist template is located, not where the footnote label exists within the body of the text).
+
+If VE is NOT modified to allow users to edit such references/citations, users are going to be (randomly) frustrated because they can't edit any footnotes in some articles using VE (see above) and because in some articles (https://en.wikipedia.org/wiki/Pope_Francis , for example), there are occasional footnotes that aren't editable in VE.",task_subcomment,"['This should NOT be a low priority.', ""It's quite common for an article to have ALL references inside a template - see, for example, URL ."", 'At the moment, VE is able to figure out that the citation information is elsewhere - a tooltip appears that says ""This reference is defined in a template or other generated block, and for now can be only edited in source mode.""', 'If VE can figure that out, then it should be able to perform the following three additional steps:\n\n* Check if the information is in the {{reflist}} template (match the ""ref name="" parameter in the body of the text to a ref name parameter within the reflist template)\n\n* If a match is found, pull the relevant citation information from the reflist template, allowing the user to edit it\n\n* After the edit is finished, put the (modified) citation information back into the reflist template\n\n(Side note: for edit conflict purposes, this is an edit of the section where the reflist template is located, not where the footnote label exists within the body of the text).', ""If VE is NOT modified to allow users to edit such references/citations, users are going to be (randomly) frustrated because they can't edit any footnotes in some articles using VE (see above) and because in some articles (URL , for example), there are occasional footnotes that aren't editable in VE.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+52895,VisualEditor: Inspector widget should not stay open when moving the cursor to similar annotation,"This happens with the Link annotation, but also happened to me with my Language annotation prototype when I play with it.
+
+Steps to view the problem:
+1. Go to some link in the text, put the cursor on it.
+2. The 'link' button pops up, recognizing the annotation, and if you click it, the full annotation fragment is selected (expected behavior) and the input widget appears.
+3. Without closing the input widget, click on another link in the text. The widget moves to the new location with the proper data, but the text of that fragment isn't selected, and it's a bit odd to edit. 
+
+I think a better behavior may be to close the widget and have the icon pop up on the new location, as if I clicked an unrelated non-link text and then again selected a link.
+
+(I hope this makes sense, I can post some screenshots if needed)
+
+I use Firefox 22.0 under Ubuntu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Inspector widget should not stay open when moving the cursor to similar annotation\n\nThis happens with the Link annotation, but also happened to me with my Language annotation prototype when I play with it.', 'Steps to view the problem:\n1.', 'Go to some link in the text, put the cursor on it.', '2.', ""The 'link' button pops up, recognizing the annotation, and if you click it, the full annotation fragment is selected (expected behavior) and the input widget appears."", '3.', 'Without closing the input widget, click on another link in the text.', ""The widget moves to the new location with the proper data, but the text of that fragment isn't selected, and it's a bit odd to edit."", 'I think a better behavior may be to close the widget and have the icon pop up on the new location, as if I clicked an unrelated non-link text and then again selected a link.', '(I hope this makes sense, I can post some screenshots if needed)\n\nI use Firefox 22.0 under Ubuntu.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+241526,VisualEditor: Inspector widget should not stay open when moving the cursor to similar annotation,Looks like the fix works. Can't reproduce this anymore on latest master.,task_subcomment,"['Looks like the fix works.', ""Can't reproduce this anymore on latest master.""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+241518,VisualEditor: Inspector widget should not stay open when moving the cursor to similar annotation,"Change 72865 merged by jenkins-bot:
+Reset context menu on selection change while inspector is open
+
+https://gerrit.wikimedia.org/r/72865",task_subcomment,['Change 72865 merged by jenkins-bot:\nReset context menu on selection change while inspector is open\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241509,VisualEditor: Inspector widget should not stay open when moving the cursor to similar annotation,"Change 72865 had a related patch set uploaded by Jforrester:
+[WIP] Reset context menu on selection change while inspector is open
+
+https://gerrit.wikimedia.org/r/72865",task_subcomment,['Change 72865 had a related patch set uploaded by Jforrester:\n[WIP] Reset context menu on selection change while inspector is open\n\nGERRIT_URL'],['WORKAROUNDS']
+52885,VisualEditor: Long editnotices are truncated with no way to scroll,"[[Jyllands-Posten Muhammad cartoons controversy]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52667",task_description,"['VisualEditor: Long editnotices are truncated with no way to scroll\n\n[[Jyllands-Posten Muhammad cartoons controversy]].', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240894,VisualEditor: Long editnotices are truncated with no way to scroll,This was fixed last week.,task_subcomment,['This was fixed last week.'],['BUG REPRODUCTION']
+240889,VisualEditor: Long editnotices are truncated with no way to scroll,*** Bug 62408 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 62408 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240882,VisualEditor: Long editnotices are truncated with no way to scroll,"In terms of combinations, I think we need to plan to support the display of at least three edit notices.  It is not at all unusual for articles at the English Wikipedia to display both the standard BLP notice (https://en.wikipedia.org/wiki/Template:BLP_editintro) and a semi-protection notice, and being able to view three means that only one more item could be included.
+
+https://en.wikipedia.org/w/index.php?title=Barack_Obama&action=edit&editintro=Template:BLP_editintro shows three items.  Some of them have much longer notices.  https://en.wikipedia.org/w/index.php?title=Cat&action=edit shows only two, but one has some fairly long collapsed text (which VisualEditor does not collapse).",task_subcomment,"['In terms of combinations, I think we need to plan to support the display of at least three edit notices.', 'It is not at all unusual for articles at the English Wikipedia to display both the standard BLP notice (URL and a semi-protection notice, and being able to view three means that only one more item could be included.', 'URL shows three items.', 'Some of them have much longer notices.', 'URL shows only two, but one has some fairly long collapsed text (which VisualEditor does not collapse).']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240876,VisualEditor: Long editnotices are truncated with no way to scroll,"It's not just single long edit notices, combinations of messages can also exceed screen height, e.g. at [[Caucasian Albania]]. The ArbCom sanctions notice is only about 5 lines in the source view, which has vastly greater horizontal space, likewise the semi-protection notice is designed for a horizontal layout.
+
+Is there a reason why the VE notices must be vertical? Could they not horizontally expand to fit the messages? Doing so would reduce (but not remove) the need for bug 52471",task_subcomment,"[""It's not just single long edit notices, combinations of messages can also exceed screen height, e.g."", 'at [[Caucasian Albania]].', 'The ArbCom sanctions notice is only about 5 lines in the source view, which has vastly greater horizontal space, likewise the semi-protection notice is designed for a horizontal layout.', 'Is there a reason why the VE notices must be vertical?', 'Could they not horizontally expand to fit the messages?', 'Doing so would reduce (but not remove) the need for bug 52471']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+240871,VisualEditor: Long editnotices are truncated with no way to scroll,"In general, long edit notices misunderstand the concept of a brief message for users - but yes, we should fix this.",task_subcomment,"['In general, long edit notices misunderstand the concept of a brief message for users - but yes, we should fix this.']",['SOLUTION DISCUSSION']
+240866,VisualEditor: Long editnotices are truncated with no way to scroll,"Comments from bug 52602
+
+""Edit notices should scroll when they are larger than the height of the window.
+Presently the bottom of the message is unreadable. The screenshot attached
+shows en.wp's ""Today's featured article"" edit notice displayed in a 581px high
+window (which is what I normally use for browsing).""
+
+The screenshot is attachment 13067
+
+""A couple of users have reported this also happening with ""the notice
+specifically for VE"", which I presume is the beta welcome dialog. They are
+unable to scroll through and read it all.""",task_subcomment,"['Comments from bug 52602\n\n""Edit notices should scroll when they are larger than the height of the window.', 'Presently the bottom of the message is unreadable.', 'The screenshot attached\nshows en.wp\'s ""Today\'s featured article"" edit notice displayed in a 581px high\nwindow (which is what I normally use for browsing).""', 'The screenshot is attachment 13067\n\n""A couple of users have reported this also happening with ""the notice\nspecifically for VE"", which I presume is the beta welcome dialog.', 'They are\nunable to scroll through and read it all.""']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240860,VisualEditor: Long editnotices are truncated with no way to scroll,*** Bug 52602 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52602 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52878,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"If you click in the link
+https://en.wikipedia.org/wiki/Math?veaction=edit
+you will be redirected to [[Mathematics]] and the VisualEditor will load on that page instead of in the redirect page [[Math]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/Math?veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54921
+https://bugzilla.wikimedia.org/show_bug.cgi?id=25470",task_description,"['VisualEditor: Remove the disablement of VisualEditor for redirect pages\n\nIf you click in the link\nURL\nyou will be redirected to [[Mathematics]] and the VisualEditor will load on that page instead of in the redirect page [[Math]].', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**URL**: URL\n**See Also**:\nURL\nURL']","['SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION']"
+240401,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"Change 95213 merged by jenkins-bot:
+Let users set #REDIRECT and __STATICREDIRECT__ status
+
+https://gerrit.wikimedia.org/r/95213",task_subcomment,['Change 95213 merged by jenkins-bot:\nLet users set #REDIRECT and __STATICREDIRECT__ status\n\nGERRIT_URL'],['ACTION ON ISSUE']
+240397,VisualEditor: Remove the disablement of VisualEditor for redirect pages,*** Bug 60425 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 60425 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240394,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"Change 95213 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT
+
+https://gerrit.wikimedia.org/r/95213",task_subcomment,['Change 95213 had a related patch set uploaded by Jforrester:\n[WIP] Let users set #REDIRECT\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+240391,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"Change 95103 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__
+
+https://gerrit.wikimedia.org/r/95103",task_subcomment,"['Change 95103 had a related patch set uploaded by Jforrester:\n[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__\n\nGERRIT_URL']",['INVESTIGATION AND EXPLORATION']
+240386,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"(In reply to comment #3)
+Indeed, I first noticed this bug in a user page which was a redirect.",task_subcomment,"['(In reply to comment #3)\nIndeed, I first noticed this bug in a user page which was a redirect.']",['OBSERVED BUG BEHAVIOR']
+240379,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"I figured out that the redirect was the reason why I could not see VE tab on my userpage at vec.wiki, but I also suggest that this should probably be more visible. Redirects are also widely used on user pages, and I assume that there will be people who might consider writing a proper user page with VE at some point and will be puzzled that they can't find its tab there. Just my 2c :)",task_subcomment,"['I figured out that the redirect was the reason why I could not see VE tab on my userpage at vec.wiki, but I also suggest that this should probably be more visible.', ""Redirects are also widely used on user pages, and I assume that there will be people who might consider writing a proper user page with VE at some point and will be puzzled that they can't find its tab there."", 'Just my 2c :)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+240374,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"Not a duplicate of bug 50877; this is about being able to edit page redirects, which is an enhancement we want to do shortly, blocked by bug 47328.",task_subcomment,"['Not a duplicate of bug 50877; this is about being able to edit page redirects, which is an enhancement we want to do shortly, blocked by bug 47328.']",['FUTURE PLAN']
+240370,VisualEditor: Remove the disablement of VisualEditor for redirect pages,"I assume this bug is a duplicate. I believe an initial compromise was to remove the ""edit"" tab (leaving only ""edit source"") on redirects. But the behavior here still is pretty wonky and will likely remain wonky until someone writes a redirect VisualEditor module/plugin, I think?",task_subcomment,"['I assume this bug is a duplicate.', 'I believe an initial compromise was to remove the ""edit"" tab (leaving only ""edit source"") on redirects.', 'But the behavior here still is pretty wonky and will likely remain wonky until someone writes a redirect VisualEditor module/plugin, I think?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52877,VisualEditor: Editor not triggered on system redirects,"If you click in the link
+https://en.wikipedia.org/wiki/Special:MyPage?veaction=edit
+you will be redirected to your user page in ""view"" mode instead of ""vedit"" mode
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/wiki/Special:MyPage?veaction=edit",task_description,"['VisualEditor: Editor not triggered on system redirects\n\nIf you click in the link\nURL\nyou will be redirected to your user page in ""view"" mode instead of ""vedit"" mode\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor\n**URL**: URL']",['OBSERVED BUG BEHAVIOR']
+240339,VisualEditor: Editor not triggered on system redirects,"Change 134788 merged by jenkins-bot:
+Preserve veaction, vesection on special redirects to wiki pages
+
+https://gerrit.wikimedia.org/r/134788",task_subcomment,"['Change 134788 merged by jenkins-bot:\nPreserve veaction, vesection on special redirects to wiki pages\n\nGERRIT_URL']",['OBSERVED BUG BEHAVIOR']
+240334,VisualEditor: Editor not triggered on system redirects,"Change 134788 had a related patch set uploaded by Mattflaschen:
+Preserve veaction, vesection on special redirects to wiki pages
+
+https://gerrit.wikimedia.org/r/134788",task_subcomment,"['Change 134788 had a related patch set uploaded by Mattflaschen:\nPreserve veaction, vesection on special redirects to wiki pages\n\nGERRIT_URL']",['ACTION ON ISSUE']
+240327,VisualEditor: Editor not triggered on system redirects,"From bug 51178 comment 0:
+
+| The veaction parameter is not passed by Special:MyPage, so links like this do
+| not work: http://en.wikipedia.org/wiki/Special:MyPage/sandbox?veaction=edit
+|
+| See the patch for bug 45219 for the way a similar issue was solved for the
+| Guided Tours extension.",task_subcomment,"['From bug 51178 comment 0:\n\n| The veaction parameter is not passed by Special:MyPage, so links like this do\n| not work: URL\n|\n| See the patch for bug 45219 for the way a similar issue was solved for the\n| Guided Tours extension.']",['OBSERVED BUG BEHAVIOR']
+240323,VisualEditor: Editor not triggered on system redirects,*** Bug 51178 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51178 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52874,"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist","Lots of testing involved here; currently assigning to myself.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist\n\nLots of testing involved here; currently assigning to myself.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+476932,"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist","This is not the right task for ""add something to the whitelist"".",task_subcomment,"['This is not the right task for ""add something to the whitelist"".']",['OBSERVED BUG BEHAVIOR']
+473383,"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist",re-opening since I think it works pretty well.,task_subcomment,['re-opening since I think it works pretty well.'],['SOLUTION DISCUSSION']
+240226,"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist","INVALID-ing this given that the answer on testing is 'no'. Will need to take forward as real bugs, sadly.",task_subcomment,"[""INVALID-ing this given that the answer on testing is 'no'."", 'Will need to take forward as real bugs, sadly.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+240221,"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist","(In reply to comment #1)
+> Currently the answer appears to be ""no we don't work very well"". :) Selection
+> is broken, and typing seems to eat the entire document.
+
+Darn. :-(
+
+> James, do you have a copy of Windows 8.1 Preview to test with? I can provide
+> an installer ISO and a couple of product keys if you need them. Runs fine in
+> Parallels.
+
+Thanks for the offer, though Microsoft reached out to us and gave me the same; I've just not had a chance to do anything with it yet.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\n\nDarn.', "":-(\n\nQUOTE\nQUOTE\nQUOTE\n\nThanks for the offer, though Microsoft reached out to us and gave me the same; I've just not had a chance to do anything with it yet.""]","['ACTION ON ISSUE', 'CONTRIBUTION AND COMMITMENT']"
+240217,"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist","Currently the answer appears to be ""no we don't work very well"". :) Selection is broken, and typing seems to eat the entire document.
+
+James, do you have a copy of Windows 8.1 Preview to test with? I can provide an installer ISO and a couple of product keys if you need them. Runs fine in Parallels.",task_subcomment,"['Currently the answer appears to be ""no we don\'t work very well"".', ':) Selection is broken, and typing seems to eat the entire document.', 'James, do you have a copy of Windows 8.1 Preview to test with?', 'I can provide an installer ISO and a couple of product keys if you need them.', 'Runs fine in Parallels.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+52872,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,"Even though section editing in VE is a long way off, it would be really helpful if the title of the section you click edit on was automatically included in the edit summary in the same way that the source editor does. For example, when making [https://en.wikipedia.org/w/index.php?title=Viareggio_train_derailment&diff=next&oldid=563164136 this edit] I launched the VE by clicking on the edit link for the ""See also"" section, so I was expecting the edit summary to begin with the usual ""-> See also"". This provides context for the edit summary and so helps give context at recent changes and on watchlists.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56891
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51903",task_description,"['VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link\n\nEven though section editing in VE is a long way off, it would be really helpful if the title of the section you click edit on was automatically included in the edit summary in the same way that the source editor does.', 'For example, when making [URL this edit] I launched the VE by clicking on the edit link for the ""See also"" section, so I was expecting the edit summary to begin with the usual ""-> See also"".', 'This provides context for the edit summary and so helps give context at recent changes and on watchlists.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+240148,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,Done and will be deployed tomorrow.,task_subcomment,['Done and will be deployed tomorrow.'],['ACTION ON ISSUE']
+240140,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,"Change 74545 merged by jenkins-bot:
+Prepend section title to edit summary
+
+https://gerrit.wikimedia.org/r/74545",task_subcomment,['Change 74545 merged by jenkins-bot:\nPrepend section title to edit summary\n\nGERRIT_URL'],['ACTION ON ISSUE']
+240132,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,"(In reply to comment #7)
+> *** Bug 51903 has been marked as a duplicate of this bug. ***
+
+not exactly: this bug is about ""when launched from section edit link"".
+
+IMO, this will be wrong: VE does not support section edit, and a user can launch VE from a section edit link, and then do whatever anywhere on the page. 
+
+bug 51903 asked VE to analyze the page when the user press ""save"", find out whether or not the changes are confined to a specific section, and if so (regardless of how VE was launched), add the section name to the summary.
+
+so i do not think these two are truly ""duplicates"". 
+if anything, this bug should be marked ""invalid"" and bug 51903 should be resurrected (51903 was opened as ""enhancement request"").
+
+peace.",task_subcomment,"['(In reply to comment #7)\nQUOTE\n\nnot exactly: this bug is about ""when launched from section edit link"".', 'IMO, this will be wrong: VE does not support section edit, and a user can launch VE from a section edit link, and then do whatever anywhere on the page.', 'bug 51903 asked VE to analyze the page when the user press ""save"", find out whether or not the changes are confined to a specific section, and if so (regardless of how VE was launched), add the section name to the summary.', 'so i do not think these two are truly ""duplicates"".', 'if anything, this bug should be marked ""invalid"" and bug 51903 should be resurrected (51903 was opened as ""enhancement request"").', 'peace.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+240128,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,*** Bug 51903 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51903 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240124,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,"Change 74545 had a related patch set uploaded by Esanders:
+Prepend section title to edit summary
+
+https://gerrit.wikimedia.org/r/74545",task_subcomment,['Change 74545 had a related patch set uploaded by Esanders:\nPrepend section title to edit summary\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+240119,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,*** Bug 51343 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51343 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240113,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,"Well, having a misleading ""edit section"" link isn't considered a problem.",task_subcomment,"['Well, having a misleading ""edit section"" link isn\'t considered a problem.']",['SOLUTION DISCUSSION']
+240108,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,"Absolutely it can (and probably should) be removable.
+
+As for editing other sections, hmm. My initial thought is to wonder whether it could be detectable from the diff generator which section(s) have been edited?",task_subcomment,"['Absolutely it can (and probably should) be removable.', 'As for editing other sections, hmm.', 'My initial thought is to wonder whether it could be detectable from the diff generator which section(s) have been edited?']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+240102,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,*** Bug 50535 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50535 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240096,VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,"(In reply to comment #0)
+> Even though section editing in VE is a long way off, it would be really
+> helpful if the title of the section you click edit on was automatically
+> included in the edit summary in the same way that the source editor does.
+> For example, when making https://en.wikipedia.org/w/?diff=next&oldid=563164136
+> this edit I launched the VE by clicking on the edit link for the ""See also""
+> section, so I was expecting the edit summary to begin with the usual ""-> See
+> also"". This provides context for the edit summary and so helps give context
+> at recent changes and on watchlists.
+
+Won't this be rather mis-leading? Normally reviewers will expect the changes to be limited to that section, whereas editors are unlikely to keep their changes restricted in that way. Potentially we could add it into the edit summary box before the user adds anything, so they can remove it if they want?",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWon't this be rather mis-leading?"", 'Normally reviewers will expect the changes to be limited to that section, whereas editors are unlikely to keep their changes restricted in that way.', 'Potentially we could add it into the edit summary box before the user adds anything, so they can remove it if they want?']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+52870,mediawiki.notification: Notification area should remain visible when scrolled down,"Original bug title:
+mediawiki.notification should show the notification bubble relative to the screen, not to the document
+
+Current behaviour:
+Calling mw.notify(""abc"") in JavaScript creates a message-bubble somewhere below the first 
     heading (the title) and the bubble disappears after about 5s.
+
+Why this is an issue:
+But if you have scrolled-down the page, the notification disappears without being read.
+
+Where is this an issue:
+For example, when marking large new pages as patrolled, the patrol link is at the bottom of the page and the message whether patrolling succeeded is not visible to the user. Or at custom gadgets/user scripts.
+
+Expected behaviour:
+Bubble shown, no matter of the current scroll position.
+
+Possible implementation:
+Fixed position.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",task_description,"['mediawiki.notification: Notification area should remain visible when scrolled down\n\nOriginal bug title:\nmediawiki.notification should show the notification bubble relative to the screen, not to the document\n\nCurrent behaviour:\nCalling mw.notify(""abc"") in JavaScript creates a message-bubble somewhere below the first 
     heading (the title) and the bubble disappears after about 5s.', 'Why this is an issue:\nBut if you have scrolled-down the page, the notification disappears without being read.', 'Where is this an issue:\nFor example, when marking large new pages as patrolled, the patrol link is at the bottom of the page and the message whether patrolling succeeded is not visible to the user.', 'Or at custom gadgets/user scripts.', 'Expected behaviour:\nBubble shown, no matter of the current scroll position.', 'Possible implementation:\nFixed position.', '--------------------------\n**Version**: 1.22.0\n**Severity**: enhancement']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+240004,mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 48689 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 48689 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239997,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 75662 had a related patch set uploaded by Matmarex:
+mw.notification: Fix incorrect initial offset
+
+https://gerrit.wikimedia.org/r/75662",task_subcomment,['Change 75662 had a related patch set uploaded by Matmarex:\nmw.notification: Fix incorrect initial offset\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+239990,mediawiki.notification: Notification area should remain visible when scrolled down,"@se4598, thanks for the report, I7444bf55 should fix this. Sorry!",task_subcomment,"['SCREEN_NAME, thanks for the report, I7444bf55 should fix this.', 'Sorry!']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+239982,mediawiki.notification: Notification area should remain visible when scrolled down,"above change deployed recently doesn't work for me; breaks UI:
+* notification doesn't scroll with
+* blocks user bar and other tabs in the top right corner
+* css style changed
+
+experienced in firefox 22 as well in chrome",task_subcomment,"[""above change deployed recently doesn't work for me; breaks UI:\n* notification doesn't scroll with\n* blocks user bar and other tabs in the top right corner\n* css style changed\n\nexperienced in firefox 22 as well in chrome""]",['OBSERVED BUG BEHAVIOR']
+239976,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 75614 merged by Catrope:
+mediawiki.notification: Make notification area sticky to window
+
+https://gerrit.wikimedia.org/r/75614",task_subcomment,['Change 75614 merged by Catrope:\nmediawiki.notification: Make notification area sticky to window\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+239974,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 75611 merged by Catrope:
+mediawiki.notification: Make notification area sticky to window
+
+https://gerrit.wikimedia.org/r/75611",task_subcomment,['Change 75611 merged by Catrope:\nmediawiki.notification: Make notification area sticky to window\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+239971,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 75614 had a related patch set uploaded by Catrope:
+mediawiki.notification: Make notification area sticky to window
+
+https://gerrit.wikimedia.org/r/75614",task_subcomment,['Change 75614 had a related patch set uploaded by Catrope:\nmediawiki.notification: Make notification area sticky to window\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239968,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 75611 had a related patch set uploaded by Catrope:
+mediawiki.notification: Make notification area sticky to window
+
+https://gerrit.wikimedia.org/r/75611",task_subcomment,['Change 75611 had a related patch set uploaded by Catrope:\nmediawiki.notification: Make notification area sticky to window\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239963,mediawiki.notification: Notification area should remain visible when scrolled down,"Fixed in the above patch, which we will deploy tomorrow as a cherry-pick given the need to fix this urgently for VisualEditor.",task_subcomment,"['Fixed in the above patch, which we will deploy tomorrow as a cherry-pick given the need to fix this urgently for VisualEditor.']",['ACTION ON ISSUE']
+239958,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 72322 merged by jenkins-bot:
+mediawiki.notification: Make notification area sticky to window
+
+https://gerrit.wikimedia.org/r/72322",task_subcomment,['Change 72322 merged by jenkins-bot:\nmediawiki.notification: Make notification area sticky to window\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239955,mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 51785 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51785 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239950,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 73948 abandoned by Krinkle:
+Use fixed position for notifications
+
+Reason:
+Dupe of Icb7cd68f484 (which has existed longer)
+
+https://gerrit.wikimedia.org/r/73948",task_subcomment,['Change 73948 abandoned by Krinkle:\nUse fixed position for notifications\n\nReason:\nDupe of Icb7cd68f484 (which has existed longer)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239943,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 73948 had a related patch set uploaded by Helder.wiki:
+Use fixed position for notifications
+
+https://gerrit.wikimedia.org/r/73948",task_subcomment,['Change 73948 had a related patch set uploaded by Helder.wiki:\nUse fixed position for notifications\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239934,mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 51432 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51432 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239924,mediawiki.notification: Notification area should remain visible when scrolled down,">Argh, I forgot that position:fixed is always relative to the entire document, >not to any positioned ancestor.
+This is only true if you set top,left,right or bottom, AFAIK. Look at [[:commons:Special:Permalink/99667607]] (the grey DIV 2 inner is fixed)
+
+See also http://stackoverflow.com/questions/8712047/positionfixed-when-left-top-right-bottom-arent-specified-desired-results-in
+
+If one still wants to use something fancier (and one will have to for safari, unfortunately), one may use jQuery:
+offset ( http://api.jquery.com/offset/ ) -- ""Get the current coordinates of the first element in the set of matched elements, relative to the document.""
+This way one can get the position of mw.util.$content and add 1em. Here is an example implementation (one has to execute the positioning code every time the message is shown or one has to catch window.resize events).
+
+var $content = mw.util.$content,
+    $container = $('
    ').appendTo($content)
+    $n = $('
    ').text('Message here').css({
+     'float': 'right', // Set this in CSS so Janus can flip!
+     'margin':  '1em'
+    }).appendTo($container),
+    o = $content.offset();
+    
+$container.css({
+    position: 'fixed',
+    width: $content.width()
+}).offset(o);
+
+Feel free to improve (padding of mw.util.$content is not respected) and note that styles are also touched in skin files like skins/vector/screen.css ( https://git.wikimedia.org/blob/mediawiki%2Fcore.git/9cbd77868a92022170348504fb5444e4e1f302fa/skins%2Fvector%2Fscreen.css#L807 )",task_subcomment,"['QUOTE\nThis is only true if you set top,left,right or bottom, AFAIK.', 'Look at [[:commons:Special:Permalink/99667607]] (the grey DIV 2 inner is fixed)\n\nSee also URL\n\nIf one still wants to use something fancier (and one will have to for safari, unfortunately), one may use jQuery:\noffset ( URL ) -- ""Get the current coordinates of the first element in the set of matched elements, relative to the document.""', 'This way one can get the position of mw.util.$content and add 1em.', 'Here is an example implementation (one has to execute the positioning code every time the message is shown or one has to catch window.resize events).', ""var $content = mw.util.$content,\n    $container = $('
    ').appendTo($content)\n    $n = $('
    ').text('Message here').css({\n     'float': 'right', // Set this in CSS so Janus can flip!"", ""'margin':  '1em'\n    }).appendTo($container),\n    o = $content.offset();\n    \n$container.css({\n    position: 'fixed',\n    width: $content.width()\n}).offset(o);\n\nFeel free to improve (padding of mw.util.$content is not respected) and note that styles are also touched in skin files like skins/vector/screen.css ( URL )""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239918,mediawiki.notification: Notification area should remain visible when scrolled down,"Heh, I though they behave in this way. Seems like an obvious enhancement.",task_subcomment,"['Heh, I though they behave in this way.', 'Seems like an obvious enhancement.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+239914,mediawiki.notification: Notification area should remain visible when scrolled down,"Change 72322 had a related patch set uploaded by Matmarex:
+mediawiki.notification: Show the notifications relative to the screen
+
+https://gerrit.wikimedia.org/r/72322",task_subcomment,['Change 72322 had a related patch set uploaded by Matmarex:\nmediawiki.notification: Show the notifications relative to the screen\n\nGERRIT_URL'],['ACTION ON ISSUE']
+52847,"Allow launching once per-user, per-situation","Allow launching a tour while limiting it to once per-user.  The idea is that GuidedTour handles this, so the calling code (GettingStarted, VisualEditor, etc.) doesn't need to think about hidden user preferences, etc.  I'll call it launchOnceForUser as illustration; better name suggestions welcome
+
+Example use case: The VisualEditor edit screen calls launchOncePerUser, then GuidedTour decides internally whether to launch it based on whether the user has already seen it.
+
+Ideally, it will allow launching immediately, and pre-launching by setting a cookie (we did this once with GettingStarted).
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",task_description,"['Allow launching once per-user, per-situation\n\nAllow launching a tour while limiting it to once per-user.', 'The idea is that GuidedTour handles this, so the calling code (GettingStarted, VisualEditor, etc.)', ""doesn't need to think about hidden user preferences, etc."", ""I'll call it launchOnceForUser as illustration; better name suggestions welcome\n\nExample use case: The VisualEditor edit screen calls launchOncePerUser, then GuidedTour decides internally whether to launch it based on whether the user has already seen it."", 'Ideally, it will allow launching immediately, and pre-launching by setting a cookie (we did this once with GettingStarted).', '--------------------------\n**Version**: master\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION']"
+238673,"Allow launching once per-user, per-situation","I need to think about whether this should go in the tour specification (defineTour), the launch site, or both.",task_subcomment,"['I need to think about whether this should go in the tour specification (defineTour), the launch site, or both.']",['FUTURE PLAN']
+52840,VisualEditor: Clean up 'cache': 'false',"We have lots of occurrences of 'cache': 'false' in $.ajax invocations in our code, and only one occurrence of 'cache': true. Based on the documentation, it seems to me that 'cache' should pretty much never be set to false. But then again, we set it to the string 'false', not the boolean false.
+
+This seems bad and in need of cleanup. Assigning to Timo.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: Clean up 'cache': 'false'\n\nWe have lots of occurrences of 'cache': 'false' in $.ajax invocations in our code, and only one occurrence of 'cache': true."", ""Based on the documentation, it seems to me that 'cache' should pretty much never be set to false."", ""But then again, we set it to the string 'false', not the boolean false."", 'This seems bad and in need of cleanup.', 'Assigning to Timo.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+238136,VisualEditor: Clean up 'cache': 'false',Done in Roan's clean-up of API usage.,task_subcomment,"[""Done in Roan's clean-up of API usage.""]",['SOLUTION DISCUSSION']
+52791,"VisualEditor: For alienated block nodes in inline positions, alienation area is a single line, not the whole block","Take for example this: 
+https://en.wikipedia.org/wiki/AMS-LaTeX?veaction=edit
+
+The green alienation is only covering one line of the Math block after the sentence: ""causes the equals signs in the two lines to be aligned with one another, like this:""
+
+{F11183}
+
+**See Also**: {T66625}",task_description,"['VisualEditor: For alienated block nodes in inline positions, alienation area is a single line, not the whole block\n\nTake for example this: \nURL\n\nThe green alienation is only covering one line of the Math block after the sentence: ""causes the equals signs in the two lines to be aligned with one another, like this:""\n\n{F11183}\n\n**See Also**: {T66625}']",['MOTIVATION']
+1845917,"VisualEditor: For alienated block nodes in inline positions, alienation area is a single line, not the whole block","This doesn't seem to be a problem any more, even if I make the visual editor forget what math nodes are:
+```lang=js
+ve.dm.converter.modelRegistry.unregister(ve.dm.MWMathNode);
+ve.dm.converter.modelRegistry.unregister(ve.dm.MWAlienBlockExtensionNode);
+ve.dm.converter.modelRegistry.unregister(ve.dm.MWAlienInlineExtensionNode);
+```
+{F34920206}
+
+This might have been fixed by the same patch as T66625, years ago.",task_subcomment,"[""This doesn't seem to be a problem any more, even if I make the visual editor forget what math nodes are:\n``CODE``\n{F34920206}\n\nThis might have been fixed by the same patch as T66625, years ago.""]",['OBSERVED BUG BEHAVIOR']
+52788,VisualEditor: We need a representation of red-linked images,"Quote: ""I was editing this revision https://en.wikipedia.org/w/index.php?title=Chubby_bunny&oldid=562098358 of [[Chubby bunny]] to try to remove a thumbnail of a deleted image, the following wikitext:
+[[Image:Sara_Jay_Chubby_Bunny_Challenge.png|thumbnail|Sara Jay playing Chubby Bunny]]
+
+The red image link and/or its caption shown in the normal article view do not appear in the Visual Editor view and as far as I tell removing it in that view is impossible.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: We need a representation of red-linked images\n\nQuote: ""I was editing this revision URL of [[Chubby bunny]] to try to remove a thumbnail of a deleted image, the following wikitext:\n[[Image:Sara_Jay_Chubby_Bunny_Challenge.png|thumbnail|Sara Jay playing Chubby Bunny]]\n\nThe red image link and/or its caption shown in the normal article view do not appear in the Visual Editor view and as far as I tell removing it in that view is impossible.""', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+459833,VisualEditor: We need a representation of red-linked images,"Change 210625 merged by jenkins-bot:
+Representation of red-linked images in VE
+
+[[https://gerrit.wikimedia.org/r/210625]]",task_subcomment,['Change 210625 merged by jenkins-bot:\nRepresentation of red-linked images in VE\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+459083,VisualEditor: We need a representation of red-linked images,"Change 210625 had a related patch set uploaded (by SuchetaG):
+[WIP] Representation of red-linked images in VE
+
+[[https://gerrit.wikimedia.org/r/210625]]
+",task_subcomment,['Change 210625 had a related patch set uploaded (by SuchetaG):\n[WIP] Representation of red-linked images in VE\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+444194,VisualEditor: We need a representation of red-linked images,"The current handling of red-linked images in wmf1.25/1.26
+
+-  the non-existing images can be inserted only in 'Edit source'
+-  in Read they are represented as {F113350}
+-  switching to VE {F113352}
+
+- hovering over the image gives: 'Sorry, this element can only be edited in source mode for now.'
+- the image can be deleted in VE ",task_subcomment,"[""The current handling of red-linked images in wmf1.25/1.26\n\n-  the non-existing images can be inserted only in 'Edit source'\n-  in Read they are represented as {F113350}\n-  switching to VE {F113352}\n\n- hovering over the image gives: 'Sorry, this element can only be edited in source mode for now.'"", '- the image can be deleted in VE']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+444172,VisualEditor: We need a representation of red-linked images,">>! In T52788#1210051, @cscott wrote:
+> We are emitting the mw:Error markup in Parsoid, I believe, and that hasn't changed.  What @mooeypoo reports is a regression in VE?
+
+Probably.",task_subcomment,['QUOTE\nQUOTE\n\nProbably.'],['SOLUTION DISCUSSION']
+444159,VisualEditor: We need a representation of red-linked images,"We are emitting the mw:Error markup in Parsoid, I believe, and that hasn't changed.  What @mooeypoo reports is a regression in VE?",task_subcomment,"[""We are emitting the mw:Error markup in Parsoid, I believe, and that hasn't changed."", 'WhatSCREEN_NAME reports is a regression in VE?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+420373,VisualEditor: We need a representation of red-linked images,"This is no longer the case. Red link images (or images that aren't loading, in the case of bad internet, etc) are disappearing from CE completely.",task_subcomment,"['This is no longer the case.', ""Red link images (or images that aren't loading, in the case of bad internet, etc) are disappearing from CE completely.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+401915,VisualEditor: We need a representation of red-linked images,Marking as Resolved.,task_subcomment,['Marking as Resolved.'],['ACTION ON ISSUE']
+401910,VisualEditor: We need a representation of red-linked images,"This task is open but has two ""verified-in-phaseX"" projects associated. Could someone clarify?",task_subcomment,"['This task is open but has two ""verified-in-phaseX"" projects associated.', 'Could someone clarify?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+392323,VisualEditor: We need a representation of red-linked images,"Visual editor displays a placeholder for non-existent images, so red-linked images can be deleted from VE.
+Checked in production/betalabs/test2.",task_subcomment,"['Visual editor displays a placeholder for non-existent images, so red-linked images can be deleted from VE.', 'Checked in production/betalabs/test2.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235088,VisualEditor: We need a representation of red-linked images,"[15:09]  RoanKattouw, re https://bugzilla.wikimedia.org/show_bug.cgi?id=50788: the idea is to have a generic way to represent errored content
+[15:09]  while still matching CSS etc so that it renders as expected
+[15:09]  Right
+[15:09]  I guess I could hack tolerance for that into VE's type system
+[15:10]  I think it's kind of an abuse of a type but I see why you'd do it
+[15:10]  You want to have a single unified thing to easily identify error nodes
+[15:11]  yeah; there is a chance that querySelectorAll also supports typeof
+[15:12]  [typeof~=mw:Error]
+[15:12]  Exactl
+[15:12]  y
+[15:12]  which is more efficient than [data-mw] and then decoding each & look for errors
+[15:14]  RoanKattouw, I think you are already giving mw:Placeholder a high precedence
+[15:14]  could mw:Error have a similarly high precedence?
+[15:15]  gwicke: No, mw:Placeholder is unrecognized
+[15:15]  Any unrecognized type matching /^mw:/ triggers immediate alienation
+[15:15]  For mw:Error we'd need the reverse
+[15:15]  yeah, but aren't you handling typeof=""mw:Placeholder mw:Image"" already?
+[15:15]  Which is ignore mw:Error as a type completely, otherwise either everything with mw:Error would be alienated, or everything would have to specify mw:Error
+[15:16]  (by letting the placeholder win)
+[15:16]  No, the placeholder doesn't win
+[15:16]  ah, I see
+[15:16]  The rules for ""special"" type prefixes (for ve-mw, that's only /^mw:/ ) are as follows:
+[15:16]  that's a problem
+[15:16]  A class matches if:
+[15:16]  * It specifies some type that's present on the element
+[15:17]  * It specifies ALL mw: types that are present on the element
+[15:17]  (i.e. both of those have to be true)
+[15:17]  Additionally, we don't currently have a facility for saying ""I recognize either mw:Foo or mw:Foo+mw:Error""
+[15:17]  You can only do AND, not OR
+[15:17]  RoanKattouw: I see, that makes mw:Error harder to handle for you
+[15:18]  I mean, I can do it
+[15:18]  By introducing the concept of ignored types or whatever I want to call it
+[15:18]  I could even make mw:Placeholder one
+[15:18]  Then placeholderized images could be handled
+[15:18]  Handlers for node types still have the option to trigger alienation by returning null
+[15:18]  we already have mw:Image and mw:ExpandedAttrs
+[15:19]  and all permutations of images of course
+[15:19]  So if mw:Image+mw:Placeholder meant ""alienate except in certain cases"", then we could send it to the image handler and do if ( conditions ) { return null; // Alienate
+[15:19]  Right, mw:ExpandedAttrs is another good candidate for an ignored typer
+[15:19]  It can apply to anything
+[15:19]  And sometimes we need to alienate and sometimes we don't
+[15:19]  Hmm, maybe the jargon should be ""universal type""
+[15:19]  yup, so the general ability to match that kind of thing is needed in any case
+[15:20]  Yeah
+[15:20]  I will file a bug about this",task_subcomment,"[""[15:09]  RoanKattouw, re URL the idea is to have a generic way to represent errored content\n[15:09]  while still matching CSS etc so that it renders as expected\n[15:09]  Right\n[15:09]  I guess I could hack tolerance for that into VE's type system\n[15:10]  I think it's kind of an abuse of a type but I see why you'd do it\n[15:10]  You want to have a single unified thing to easily identify error nodes\n[15:11]  yeah; there is a chance that querySelectorAll also supports typeof\n[15:12]  [typeof~=mw:Error]\n[15:12]  Exactl\n[15:12]  y\n[15:12]  which is more efficient than [data-mw] and then decoding each & look for errors\n[15:14]  RoanKattouw, I think you are already giving mw:Placeholder a high precedence\n[15:14]  could mw:Error have a similarly high precedence?"", '[15:15]  gwicke: No, mw:Placeholder is unrecognized\n[15:15]  Any unrecognized type matching /^mw:/ triggers immediate alienation\n[15:15]  For mw:Error we\'d need the reverse\n[15:15]  yeah, but aren\'t you handling typeof=""mw:Placeholder mw:Image"" already?', '[15:15]  Which is ignore mw:Error as a type completely, otherwise either everything with mw:Error would be alienated, or everything would have to specify mw:Error\n[15:16]  (by letting the placeholder win)\n[15:16]  No, the placeholder doesn\'t win\n[15:16]  ah, I see\n[15:16]  The rules for ""special"" type prefixes (for ve-mw, that\'s only /^mw:/ ) are as follows:\n[15:16]  that\'s a problem\n[15:16]  A class matches if:\n[15:16]  * It specifies some type that\'s present on the element\n[15:17]  * It specifies ALL mw: types that are present on the element\n[15:17]  (i.e.', 'both of those have to be true)\n[15:17]  Additionally, we don\'t currently have a facility for saying ""I recognize either mw:Foo or mw:Foo+mw:Error""\n[15:17]  You can only do AND, not OR\n[15:17]  RoanKattouw: I see, that makes mw:Error harder to handle for you\n[15:18]  I mean, I can do it\n[15:18]  By introducing the concept of ignored types or whatever I want to call it\n[15:18]  I could even make mw:Placeholder one\n[15:18]  Then placeholderized images could be handled\n[15:18]  Handlers for node types still have the option to trigger alienation by returning null\n[15:18]  we already have mw:Image and mw:ExpandedAttrs\n[15:19]  and all permutations of images of course\n[15:19]  So if mw:Image+mw:Placeholder meant ""alienate except in certain cases"", then we could send it to the image handler and do if ( conditions ) { return null; // Alienate\n[15:19]  Right, mw:ExpandedAttrs is another good candidate for an ignored typer\n[15:19]  It can apply to anything\n[15:19]  And sometimes we need to alienate and sometimes we don\'t\n[15:19]  Hmm, maybe the jargon should be ""universal type""\n[15:19]  yup, so the general ability to match that kind of thing is needed in any case\n[15:20]  Yeah\n[15:20]  I will file a bug about this']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235082,VisualEditor: We need a representation of red-linked images,"(In reply to C. Scott Ananian from comment #5)
+> There's a draft spec at
+> https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Error_handling --
+> would that work for VE?
+It would be reasonable-ish. Having a separate mw:Error type would be quite inconvenient though, we'd have to add it to (almost) all of our node definitions. Would it be OK to drop the mw:Error type and just have the data-mw thing there?",task_subcomment,"['(In reply to C. Scott Ananian from comment #5)\nQUOTE\nQUOTE\nQUOTE\nIt would be reasonable-ish.', ""Having a separate mw:Error type would be quite inconvenient though, we'd have to add it to (almost) all of our node definitions."", 'Would it be OK to drop the mw:Error type and just have the data-mw thing there?']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235078,VisualEditor: We need a representation of red-linked images,There's a draft spec at https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Error_handling -- would that work for VE?,task_subcomment,"[""There's a draft spec at URL -- would that work for VE?""]",['SOLUTION DISCUSSION']
+235074,VisualEditor: We need a representation of red-linked images,*** Bug 52186 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52186 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235071,VisualEditor: We need a representation of red-linked images,"So currently redlink images are returned as . I see a couple of ways to solve this:
+
+1. Parsoid gives us back normal image tags, and we make sure our handling of images can deal with 404 src's. This way when we support changing image src's these will be editable in a useful way.
+
+2. We treat mw:Placeholder as real data, and come up with a rendering for it (maybe using parsewikitextfragment, like templates). We'd need to know what else converts to a mw:Placeholder as this may be undesirable in other situations.
+
+Pinging gwicke as this requires some Parsoid input.",task_subcomment,"['So currently redlink images are returned as .', 'I see a couple of ways to solve this:\n\n1.', ""Parsoid gives us back normal image tags, and we make sure our handling of images can deal with 404 src's."", ""This way when we support changing image src's these will be editable in a useful way."", '2.', 'We treat mw:Placeholder as real data, and come up with a rendering for it (maybe using parsewikitextfragment, like templates).', ""We'd need to know what else converts to a mw:Placeholder as this may be undesirable in other situations."", 'Pinging gwicke as this requires some Parsoid input.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+235066,VisualEditor: We need a representation of red-linked images,*** Bug 51968 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51968 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235063,VisualEditor: We need a representation of red-linked images,"Yes, this is a bit of a mess.",task_subcomment,"['Yes, this is a bit of a mess.']",['OBSERVED BUG BEHAVIOR']
+52781,VisualEditor: Browser blacklist issues (tracking),"Tracking bug for:
+
+- Browsers that shouldn't be blacklisted but are;
+
+- Browsers that should be blacklisted but aren't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Browser blacklist issues (tracking)\n\nTracking bug for:\n\n- Browsers that shouldn't be blacklisted but are;\n\n- Browsers that should be blacklisted but aren't."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+403776,VisualEditor: Browser blacklist issues (tracking),Replaced by #VisualEditor-Initialisation.,task_subcomment,['Replaced by #VisualEditor-Initialisation.'],['OBSERVED BUG BEHAVIOR']
+234651,VisualEditor: Browser blacklist issues (tracking),"There's no real point adding Bugzilla aliases, as Phabricator doesn't support them so they're going to get dropped in a matter of weeks.",task_subcomment,"[""There's no real point adding Bugzilla aliases, as Phabricator doesn't support them so they're going to get dropped in a matter of weeks.""]",['WORKAROUNDS']
+234644,VisualEditor: Browser blacklist issues (tracking),"I'm going to add MSIE to the list, given that we really should get it working again.",task_subcomment,"[""I'm going to add MSIE to the list, given that we really should get it working again.""]",['SOLUTION DISCUSSION']
+52780,VisualEditor: Firefox 11 and 12 also need to be blacklisted,"Following up to T52534, at least currently, Firefox 11 and 12 are broken as well. The first version of Firefox that at least loads the editor is Firefox 13.
+
+Reported by user for Firefox 12, and confirmed in crossbrowsertesting.com.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Firefox 11 and 12 also need to be blacklisted\n\nFollowing up to T52534, at least currently, Firefox 11 and 12 are broken as well.', 'The first version of Firefox that at least loads the editor is Firefox 13.', 'Reported by user for Firefox 12, and confirmed in crossbrowsertesting.com.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+234597,VisualEditor: Firefox 11 and 12 also need to be blacklisted,This is now merged.,task_subcomment,['This is now merged.'],['SOLUTION USAGE']
+234591,VisualEditor: Firefox 11 and 12 also need to be blacklisted,"Change 72119 abandoned by Jforrester:
+Blacklist Firefox 11 and 12
+
+https://gerrit.wikimedia.org/r/72119",task_subcomment,['Change 72119 abandoned by Jforrester:\nBlacklist Firefox 11 and 12\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+234587,VisualEditor: Firefox 11 and 12 also need to be blacklisted,"Change 72119 had a related patch set uploaded by Jforrester:
+Blacklist Firefox 11 and 12
+
+https://gerrit.wikimedia.org/r/72119",task_subcomment,['Change 72119 had a related patch set uploaded by Jforrester:\nBlacklist Firefox 11 and 12\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+234581,VisualEditor: Firefox 11 and 12 also need to be blacklisted,"Change 72118 abandoned by Jforrester:
+Blacklist Firefox 11 and 12
+
+https://gerrit.wikimedia.org/r/72118",task_subcomment,['Change 72118 abandoned by Jforrester:\nBlacklist Firefox 11 and 12\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+234576,VisualEditor: Firefox 11 and 12 also need to be blacklisted,"Change 72118 had a related patch set uploaded by Jforrester:
+Blacklist Firefox 11 and 12
+
+https://gerrit.wikimedia.org/r/72118",task_subcomment,['Change 72118 had a related patch set uploaded by Jforrester:\nBlacklist Firefox 11 and 12\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+234572,VisualEditor: Firefox 11 and 12 also need to be blacklisted,"Change 72107 had a related patch set uploaded by Jforrester:
+Blacklist Firefox 11 and 12
+
+https://gerrit.wikimedia.org/r/72107",task_subcomment,['Change 72107 had a related patch set uploaded by Jforrester:\nBlacklist Firefox 11 and 12\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+52779,"VisualEditor: Deleting a sole LI in front of a GC block doesn't, but selects the GC block","May be dup of 50213? 
+
+User:Joe Decker reports:
+
+The revision of an article here (http://en.wikipedia.org/w/index.php?title=David_Busic&oldid=562867623) has an interesting thing, a completely empty bulleted list item, which does not normally display when the article is read. It is just below the reflist, you can both confirm this in the old-style editor, and see it visually in VisualEditor. However, I have found myself unable to delete that from within Visual Editor without also deleting the preceding reference list, which is a little wacky from a UI point of view. E.g., I attempt to backspace over the bullet and I lose a reference list. Reproduced on Chrome and Safari. --j⚛e deckertalk 18:48, 4 July 2013 (UTC)
+
+Replicated by me.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Deleting a sole LI in front of a GC block doesn't, but selects the GC block\n\nMay be dup of 50213?"", 'User:Joe Decker reports:\n\nThe revision of an article here (URL has an interesting thing, a completely empty bulleted list item, which does not normally display when the article is read.', 'It is just below the reflist, you can both confirm this in the old-style editor, and see it visually in VisualEditor.', 'However, I have found myself unable to delete that from within Visual Editor without also deleting the preceding reference list, which is a little wacky from a UI point of view.', 'E.g., I attempt to backspace over the bullet and I lose a reference list.', 'Reproduced on Chrome and Safari.', '--j⚛e deckertalk 18:48, 4 July 2013 (UTC)\n\nReplicated by me.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234541,"VisualEditor: Deleting a sole LI in front of a GC block doesn't, but selects the GC block","This now works, probably caused by Ed's re-working of GCNs.",task_subcomment,"[""This now works, probably caused by Ed's re-working of GCNs.""]",['SOLUTION DISCUSSION']
+234533,"VisualEditor: Deleting a sole LI in front of a GC block doesn't, but selects the GC block","Had the same experience in http://en.wikipedia.org/w/index.php?title=The_Mortal_Instruments%3A_City_of_Bones_%28soundtrack%29&diff=566255621&oldid=566255504 . The empty bulleted list here was something in a sort of template used by the initial creator of the article, to vertically separate two comments. The bulleted list is not visible in the article when read, but is visible in VE: so the careful editor goes to delete this rubbish, and deletes the item above (not the hidden comment, but the reflist, in this case). I'm in Firefox 22 on Vista.",task_subcomment,"['Had the same experience in URL .', 'The empty bulleted list here was something in a sort of template used by the initial creator of the article, to vertically separate two comments.', 'The bulleted list is not visible in the article when read, but is visible in VE: so the careful editor goes to delete this rubbish, and deletes the item above (not the hidden comment, but the reflist, in this case).', ""I'm in Firefox 22 on Vista.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52777,VisualEditor: Add Amazon Silk browser to blacklist,"Copied from English Wikipedia:
+
+When I try to use VisualEditor on my Kindle Fire, the article goes into edit mode, but clicking in the article doesn't bring up the keyboard like it does on an iPad. I'm presuming that aading support for the Kindle Fire's Amazon Silk browser isn't on your to do list now. Could you please add this browser to the blacklist? I would like to keep VE on in my preferences so it works when I'm on my PC but not have VE get in the way while on the Kindle. Thanks! GoingBatty (talk) 02:59, 4 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"[""VisualEditor: Add Amazon Silk browser to blacklist\n\nCopied from English Wikipedia:\n\nWhen I try to use VisualEditor on my Kindle Fire, the article goes into edit mode, but clicking in the article doesn't bring up the keyboard like it does on an iPad."", ""I'm presuming that aading support for the Kindle Fire's Amazon Silk browser isn't on your to do list now."", 'Could you please add this browser to the blacklist?', ""I would like to keep VE on in my preferences so it works when I'm on my PC but not have VE get in the way while on the Kindle."", 'Thanks!', 'GoingBatty (talk) 02:59, 4 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'CONTRIBUTION AND COMMITMENT', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+234470,VisualEditor: Add Amazon Silk browser to blacklist,"Change 72108 merged by jenkins-bot:
+Blacklist Amazon Silk
+
+https://gerrit.wikimedia.org/r/72108",task_subcomment,['Change 72108 merged by jenkins-bot:\nBlacklist Amazon Silk\n\nGERRIT_URL'],['ACTION ON ISSUE']
+234465,VisualEditor: Add Amazon Silk browser to blacklist,"Change 110989 merged by jenkins-bot:
+jquery.client: Recognise Amazon Silk browser
+
+https://gerrit.wikimedia.org/r/110989",task_subcomment,['Change 110989 merged by jenkins-bot:\njquery.client: Recognise Amazon Silk browser\n\nGERRIT_URL'],['ACTION ON ISSUE']
+234462,VisualEditor: Add Amazon Silk browser to blacklist,"Change 110989 had a related patch set uploaded by Alex Monk:
+jquery.client: Recognise Amazon Silk
+
+https://gerrit.wikimedia.org/r/110989",task_subcomment,['Change 110989 had a related patch set uploaded by Alex Monk:\njquery.client: Recognise Amazon Silk\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+234459,VisualEditor: Add Amazon Silk browser to blacklist,"(In reply to comment #6)
+> (In reply to comment #4)
+> > Well, here's the sample UA strings, plop those in your tests. :)
+> > 
+> > https://developer.amazon.com/sdk/fire/specifications.html#UserAgentStrings
+> 
+> That redirects me to another page without a user agent section...
+
+Now apparently moved to:
+
+http://docs.aws.amazon.com/silk/latest/developerguide/user-agent.html",task_subcomment,['(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNow apparently moved to:\n\nURL'],['ACTION ON ISSUE']
+234456,VisualEditor: Add Amazon Silk browser to blacklist,"(In reply to comment #4)
+> Well, here's the sample UA strings, plop those in your tests. :)
+> 
+> https://developer.amazon.com/sdk/fire/specifications.html#UserAgentStrings
+
+That redirects me to another page without a user agent section...",task_subcomment,['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\n\nThat redirects me to another page without a user agent section...'],['INVESTIGATION AND EXPLORATION']
+234453,VisualEditor: Add Amazon Silk browser to blacklist,"Change 72108 had a related patch set uploaded by Jforrester:
+[WIP] Blacklist Amazon Silk
+
+https://gerrit.wikimedia.org/r/72108",task_subcomment,['Change 72108 had a related patch set uploaded by Jforrester:\n[WIP] Blacklist Amazon Silk\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+234449,VisualEditor: Add Amazon Silk browser to blacklist,"Well, here's the sample UA strings, plop those in your tests. :)
+
+https://developer.amazon.com/sdk/fire/specifications.html#UserAgentStrings",task_subcomment,"[""Well, here's the sample UA strings, plop those in your tests."", ':)\n\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234441,VisualEditor: Add Amazon Silk browser to blacklist,"(In reply to comment #2)
+> I found emulator images for the 2nd-gen Kindle Fires and HDs, but they don't
+> include the browser.
+> 
+> *headdesk*
+
+Mostly we just want to verify that any blacklisting we put in jquery.client based on UA string actually works. :-)",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nMostly we just want to verify that any blacklisting we put in jquery.client based on UA string actually works.', ':-)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+234433,VisualEditor: Add Amazon Silk browser to blacklist,"I found emulator images for the 2nd-gen Kindle Fires and HDs, but they don't include the browser.
+
+*headdesk*",task_subcomment,"[""I found emulator images for the 2nd-gen Kindle Fires and HDs, but they don't include the browser."", '*headdesk*']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234426,VisualEditor: Add Amazon Silk browser to blacklist,"Note that I've got a first-gen Kindle Fire in my collection at the office, if it needs testing. I don't have the newer generations (Android 4-based) though.",task_subcomment,"[""Note that I've got a first-gen Kindle Fire in my collection at the office, if it needs testing."", ""I don't have the newer generations (Android 4-based) though.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+52776,VisualEditor: Alien shield is mis-sized for inline content (assumes it's just one line of text high),"Copied from English Wikipedia:
+
+Hovering over a displayed math formula in  tags is supposed to get a tooltip that explains that the formula can't be edited in the VisualEditor. It sort of works; but it has trouble with tall formulas. The tooltip doesn't show up unless the cursor is moved to the middle of the formula. For some formulas this is OK, as users can be reasonably expected to put their cursor in the middle. For other formulas it's not. [See the link for] the opening of [[Companion matrix]], which has both a formula that works and one that doesn't:
+
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562893799#Math_tags
+
+
+It would be more helpful if the tooltip appeared whenever the cursor was over any pixel of the formula, not just a middle pixel. Ozob (talk) 01:21, 4 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"[""VisualEditor: Alien shield is mis-sized for inline content (assumes it's just one line of text high)\n\nCopied from English Wikipedia:\n\nHovering over a displayed math formula in  tags is supposed to get a tooltip that explains that the formula can't be edited in the VisualEditor."", 'It sort of works; but it has trouble with tall formulas.', ""The tooltip doesn't show up unless the cursor is moved to the middle of the formula."", 'For some formulas this is OK, as users can be reasonably expected to put their cursor in the middle.', ""For other formulas it's not."", ""[See the link for] the opening of [[Companion matrix]], which has both a formula that works and one that doesn't:\n\nURL\n\n\nIt would be more helpful if the tooltip appeared whenever the cursor was over any pixel of the formula, not just a middle pixel."", 'Ozob (talk) 01:21, 4 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR']"
+234386,VisualEditor: Alien shield is mis-sized for inline content (assumes it's just one line of text high),"This was actually a different issue (slightly), so separating it. Still FIXED, though. :-)",task_subcomment,"['This was actually a different issue (slightly), so separating it.', 'Still FIXED, though.', ':-)']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+234379,VisualEditor: Alien shield is mis-sized for inline content (assumes it's just one line of text high),"
+
+*** This bug has been marked as a duplicate of bug 64625 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 64625 ***'],['ISSUE CONTENT MANAGEMENT']
+52726,VisualEditor: Moving cursor up or down before a reference behaves as page up/down in Firefox,"Use Firefox 20 or 21.
+
+Place the cursor in front of a [1] ref. Note how the cursor doesn't seem to jump to another line, but instead go to end of page or toolbar.
+
+I don't see this on Safari 6.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53750",task_description,"['VisualEditor: Moving cursor up or down before a reference behaves as page up/down in Firefox\n\nUse Firefox 20 or 21.', 'Place the cursor in front of a [1] ref.', ""Note how the cursor doesn't seem to jump to another line, but instead go to end of page or toolbar."", ""I don't see this on Safari 6."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231402,VisualEditor: Moving cursor up or down before a reference behaves as page up/down in Firefox,"(In reply to James Forrester from comment #3)
+> I believe that it's now fixed, yes. The cursor getting stuck on down is odd
+> and I'll make a new bug for that.
+
+Now in bug 64983.",task_subcomment,['(In reply to James Forrester from comment #3)\nQUOTE\nQUOTE\n\nNow in bug 64983.'],['ACTION ON ISSUE']
+231395,VisualEditor: Moving cursor up or down before a reference behaves as page up/down in Firefox,"I believe that it's now fixed, yes. The cursor getting stuck on down is odd and I'll make a new bug for that.",task_subcomment,"[""I believe that it's now fixed, yes."", ""The cursor getting stuck on down is odd and I'll make a new bug for that.""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+231388,VisualEditor: Moving cursor up or down before a reference behaves as page up/down in Firefox,"I've tested a few times, and I am not seeing a 'page down' effect now.
+
+However using the arrow keys anywhere near references in VE cause the arrow keys to start misbehaving.
+
+Steps to reproduce:
+1. Load https://en.wikipedia.org/wiki/Jos%C3%A9_Cl%C3%A1udio_Ribeiro_da_Silva?veaction=edit which will place cursor at the beginning of the first line of text.
+2. Press the right arrow until it moves past the reference at the end of the first paragraph, into the second paragraph.
+3. Press up arrow
+
+Result: The cursor disappears
+
+Steps to reproduce:
+1. Load https://en.wikipedia.org/wiki/Jos%C3%A9_Cl%C3%A1udio_Ribeiro_da_Silva?veaction=edit which will place cursor at the beginning of the first line of text.
+2. Press right arrow (or use mouse) to place cursor further right on the first paragraph relative to the position of the first reference in the first paragraph.
+4. Press down. (the cursor should now be directly right of of the first reference)
+5. Press down.
+
+Result: The cursor is stuck on the first reference.
+
+(The same result can be achieved by placing the cursor in the second paragraph and pressing up)",task_subcomment,"[""I've tested a few times, and I am not seeing a 'page down' effect now."", 'However using the arrow keys anywhere near references in VE cause the arrow keys to start misbehaving.', 'Steps to reproduce:\n1.', 'Load URL which will place cursor at the beginning of the first line of text.', '2.', 'Press the right arrow until it moves past the reference at the end of the first paragraph, into the second paragraph.', '3.', 'Press up arrow\n\nResult: The cursor disappears\n\nSteps to reproduce:\n1.', 'Load URL which will place cursor at the beginning of the first line of text.', '2.', 'Press right arrow (or use mouse) to place cursor further right on the first paragraph relative to the position of the first reference in the first paragraph.', '4.', 'Press down.', '(the cursor should now be directly right of of the first reference)\n5.', 'Press down.', 'Result: The cursor is stuck on the first reference.', '(The same result can be achieved by placing the cursor in the second paragraph and pressing up)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+231380,VisualEditor: Moving cursor up or down before a reference behaves as page up/down in Firefox,"Also occurs on Firefox 22, Windows & Linux & OSX.
+
+Cant reproduce on Chrome.",task_subcomment,"['Also occurs on Firefox 22, Windows & Linux & OSX.', 'Cant reproduce on Chrome.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52723,VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin,"It seems that the visual editor can glitch a bit when it initially renders a template. Yet when the template is altered without changes this is corrected. (Firefox 22, Mono skin)
+
+'''Steps to reproduce:'''
+* Navigate to https://en.wikipedia.org/w/index.php?title=User:Excirial/Playground/Content&oldid=562754871 (Historical revision of my sandbox)
+* Edit the page in the Visual Editor. You will immediately notice that the template isn't correctly displayed.
+* Enter the template setting screen and just select ""Apply Settings"".
+
+Once that is done, the template is rendered correctly. Note that the same template was initially added trough the visual editor itself and displayed just fine. Only when you open an already saved page it seems to glitch a bit (Until the settings are applied without change - somehow that corrects it). The page reports no changes after applying, so it seems this is just a rendering issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin\n\nIt seems that the visual editor can glitch a bit when it initially renders a template."", 'Yet when the template is altered without changes this is corrected.', ""(Firefox 22, Mono skin)\n\n'''Steps to reproduce:'''\n* Navigate to URL (Historical revision of my sandbox)\n* Edit the page in the Visual Editor."", ""You will immediately notice that the template isn't correctly displayed."", '* Enter the template setting screen and just select ""Apply Settings"".', 'Once that is done, the template is rendered correctly.', 'Note that the same template was initially added trough the visual editor itself and displayed just fine.', 'Only when you open an already saved page it seems to glitch a bit (Until the settings are applied without change - somehow that corrects it).', 'The page reports no changes after applying, so it seems this is just a rendering issue.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+1970716,VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin,"I believe that this is now long-fixed, yes.",task_subcomment,"['I believe that this is now long-fixed, yes.']",['SOLUTION DISCUSSION']
+1970657,VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin,"The test page has been deleted, and this task doesn't have any details about what it contained. Is this still an issue?",task_subcomment,"[""The test page has been deleted, and this task doesn't have any details about what it contained."", 'Is this still an issue?']","['OBSERVED BUG BEHAVIOR', 'ISSUE CONTENT MANAGEMENT']"
+231212,VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin,"This is an artefact of VisualEditor using Parsoid to render HTML originally, but the MediaWiki PHP parser for updates. The HTML outputted by the two are normally very similar, except for images - which, until we switch the PHP parser our for Parsoid for rendering read HTML, which will involve re-writing the entire skins system, amongst other minor issues. (See http://parsoid.wmflabs.org/en/User:Excirial/Playground/Content?oldid=562754871 for the HTML returned to VisualEditor - note the use of 
     rather than 
     etc.)
+
+This is an image that's created by a template, so we're not re-drawing it; clearly in this case we should. Is this a special case for items that are 'typeof=""mw:Transclusion mw:Image/Frame""', or should we be traversing the template tree for all images inside generated blocks?",task_subcomment,"['This is an artefact of VisualEditor using Parsoid to render HTML originally, but the MediaWiki PHP parser for updates.', 'The HTML outputted by the two are normally very similar, except for images - which, until we switch the PHP parser our for Parsoid for rendering read HTML, which will involve re-writing the entire skins system, amongst other minor issues.', '(See URL for the HTML returned to VisualEditor - note the use of 
     rather than 
     etc.)', ""This is an image that's created by a template, so we're not re-drawing it; clearly in this case we should."", 'Is this a special case for items that are \'typeof=""mw:Transclusion mw:Image/Frame""\', or should we be traversing the template tree for all images inside generated blocks?']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+52707,Separate ve.init and ve.platform,"Our ""init"" hasn't been init for a long time. We load a lot of classes (ext.visualEditor.base and ext.visualEditor.mediawiki) for the ViewPageTarget.
+
+### Goal
+
+Integration layers in MediaWiki and elsewhere would only need the `visualeditor.init` module at first. This should provide them with tools to determine whether the current environment supports VE (feature test / browser sniffing), and the ability to then (on demand) proceed and actually load the editor, with an edit surface.
+
+The init module would provide only a lightweight `ve` and `ve.init` object with little to no dependencies. Only jquery and oojs as dependency. Not oojs-ui or anything else.
+
+For MediaWiki this means the mw.ve.init module would also take care of checking user preferences and wiki configuration with regards to skin/namespace/contentmodel etc. And mw.ve.init would also continue to handle the various skin transformations and loading bars (which would be readily available). 
+
+### Thoughts
+
+Do we need Platform to bootstrap Target? Right now in standalone we do, but in MediaWiki we don't. It's up to the Target implementation to decide this. So let's keep Platform shipped in init.
+
+Class structure:
+ * ve.init.Platform
+ * ve.init.Target.
+ * ve.init.sa.Platform becomes ve.sa.init.Platform. `ve/sa` becomes a showcase for how to bootstrap VE. Assuming we keep this generic, we can keep it under `ve.*` and ship it by default. If it becomes a demo instead that people should not extend but instead copy from, we should move it to a global VEDemo javascript namespace or something like that.
+ * ve.init.sa.Target becomes ve.sa.init.Target.
+ * ve.init.mw.Target becomes mw.ve.init.Platform.
+
+Also relevant are the feature tests. Currently only our MediaWiki platform has these feature tests, we should move these into the base  hardcoded in the MediaWiki platform. These should be moved to `ve.support` and become part of the lightweight init module.
+* Feature detection (ve.support)
+ * `support.es5`
+ * `support.contentEditable`
+ * (maybe)  `support.svg`, since we're currently repeating` ( document.createElementNS && document.createElementNS( 'http://www.w3.org/2000/svg', 'svg' ).createSVGRect` in five places.
+* Browser sniffing (ve.support.browsers.{whitelist,blacklist})
+
+
+
+See also:
+{T52612}
+{T75593} (and its dependencies)",task_description,"['Separate ve.init and ve.platform\n\nOur ""init"" hasn\'t been init for a long time.', 'We load a lot of classes (ext.visualEditor.base and ext.visualEditor.mediawiki) for the ViewPageTarget.', '### Goal\n\nIntegration layers in MediaWiki and elsewhere would only need the CODE module at first.', 'This should provide them with tools to determine whether the current environment supports VE (feature test / browser sniffing), and the ability to then (on demand) proceed and actually load the editor, with an edit surface.', 'The init module would provide only a lightweight CODE and CODE object with little to no dependencies.', 'Only jquery and oojs as dependency.', 'Not oojs-ui or anything else.', 'For MediaWiki this means the mw.ve.init module would also take care of checking user preferences and wiki configuration with regards to skin/namespace/contentmodel etc.', 'And mw.ve.init would also continue to handle the various skin transformations and loading bars (which would be readily available).', '### Thoughts\n\nDo we need Platform to bootstrap Target?', ""Right now in standalone we do, but in MediaWiki we don't."", ""It's up to the Target implementation to decide this."", ""So let's keep Platform shipped in init."", 'Class structure:\n * ve.init.Platform\n * ve.init.Target.', '* ve.init.sa.Platform becomes ve.sa.init.Platform.', 'CODE becomes a showcase for how to bootstrap VE.', 'Assuming we keep this generic, we can keep it under CODE and ship it by default.', 'If it becomes a demo instead that people should not extend but instead copy from, we should move it to a global VEDemo javascript namespace or something like that.', '* ve.init.sa.Target becomes ve.sa.init.Target.', '* ve.init.mw.Target becomes mw.ve.init.Platform.', 'Also relevant are the feature tests.', 'Currently only our MediaWiki platform has these feature tests, we should move these into the base  hardcoded in the MediaWiki platform.', 'These should be moved to CODE and become part of the lightweight init module.', ""* Feature detection (ve.support)\n * CODE\n * CODE\n * (maybe)  CODE, since we're currently repeatingCODE in five places."", '* Browser sniffing (ve.support.browsers.', '{whitelist,blacklist})\n\n\n\nSee also:\n{T52612}\n{T75593} (and its dependencies)']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+451277,Separate ve.init and ve.platform,"In the public weekly triage on 2015-04-29, we discussed this task. We decided that this task, though important, does not block further progress against current goals around better stability and performance for users, or an improved mobile editing experience, so we rejected it for the quarter's blocking list.",task_subcomment,"['In the public weekly triage on 2015-04-29, we discussed this task.', ""We decided that this task, though important, does not block further progress against current goals around better stability and performance for users, or an improved mobile editing experience, so we rejected it for the quarter's blocking list.""]","['FUTURE PLAN', 'FUTURE PLAN']"
+449793,Separate ve.init and ve.platform,I think @Krinkle should rewrite it.,task_subcomment,['I thinkSCREEN_NAME should rewrite it.'],['OBSERVED BUG BEHAVIOR']
+449788,Separate ve.init and ve.platform,"@Krinkle & @Krenair: This task was skipped during the last two #editing_department_2014_15_q4_blockers triage meetings because it's tagged ""[REWRITE ME]"". Who would be the best person to rewrite it? It would be ideal if it could be rewritten before the next triage meeting so it's not skipped again.",task_subcomment,"['SCREEN_NAME &SCREEN_NAME: This task was skipped during the last two #editing_department_2014_15_q4_blockers triage meetings because it\'s tagged ""[REWRITE\xa0ME]"".', 'Who would be the best person to rewrite it?', ""It would be ideal if it could be rewritten before the next triage meeting so it's not skipped again.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52693,"VisualEditor: Setting a link on an image causes the caption's content to be be linked (fine), but the link inspector follows the cursor around (bad)","I apologize for the lousy name this is starting off with - I have no idea what toc all this.
+
+Taken from English Wikipedia:
+
+Time for another ""Why did you even try this""? kind of bug. (Tested on Firefox 22, Mono)
+
+'''Steps to Reproduct'''
+* Edit the [[bugonia]] article using the visual editor.
+* Click the ""Aristeas and bugonia. Virgil's Georgics. Lyon. 1517"" image, which is about halfway down the article.
+* There is an uneditable section a bit higher. It starts with the text ""If any further evidence is necessary"". Click that one.
+* Now click the hyperlink button. A slight white block will appear on the image.
+* Select any other word in the image and click the hyperlink button.
+
+For some reason the hyperlink dialog box will now show up on the image, no matter what word you select. After trying a few times it seems to tire of that and starts jumping over the screen at random when a word is selected. The added screenshot is an example of this - it tried to hide behind the search box. Excirial (Contact me,Contribs) 19:37, 3 July 2013 (UTC)
+
+Link to screenshot:
+http://en.wikipedia.org/wiki/File:VisualEditor_-_Hyperlink_Dialog_glitch.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Setting a link on an image causes the caption's content to be be linked (fine), but the link inspector follows the cursor around (bad)\n\nI apologize for the lousy name this is starting off with - I have no idea what toc all this."", 'Taken from English Wikipedia:\n\nTime for another ""Why did you even try this""?', 'kind of bug.', ""(Tested on Firefox 22, Mono)\n\n'''Steps to Reproduct'''\n* Edit the [[bugonia]] article using the visual editor."", '* Click the ""Aristeas and bugonia.', ""Virgil's Georgics."", 'Lyon.', '1517"" image, which is about halfway down the article.', '* There is an uneditable section a bit higher.', 'It starts with the text ""If any further evidence is necessary"".', 'Click that one.', '* Now click the hyperlink button.', 'A slight white block will appear on the image.', '* Select any other word in the image and click the hyperlink button.', 'For some reason the hyperlink dialog box will now show up on the image, no matter what word you select.', 'After trying a few times it seems to tire of that and starts jumping over the screen at random when a word is selected.', 'The added screenshot is an example of this - it tried to hide behind the search box.', 'Excirial (Contact me,Contribs) 19:37, 3 July 2013 (UTC)\n\nLink to screenshot:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['MOTIVATION', 'SOCIAL CONVERSATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254414,"VisualEditor: Setting a link on an image causes the caption's content to be be linked (fine), but the link inspector follows the cursor around (bad)","I believe that this is now fixed, but I'm not quite sure. Please re-open if you can give a current example.",task_subcomment,"[""I believe that this is now fixed, but I'm not quite sure."", 'Please re-open if you can give a current example.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+52677,VisualEditor: Init loads oo.js on every page view (before browser blacklist) which throws an error in IE10 + compatibility mode,"On every page I load on IE10, when switched into compatibility mode, I currently get the following error.
+
+oo.js, line 97 character 2
+Object doesn't support property or method 'create'
+
+Also, if VE is not enabled on IE10, then why is this code being loaded ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50612",task_description,"['VisualEditor: Init loads oo.js on every page view (before browser blacklist) which throws an error in IE10 + compatibility mode\n\nOn every page I load on IE10, when switched into compatibility mode, I currently get the following error.', ""oo.js, line 97 character 2\nObject doesn't support property or method 'create'\n\nAlso, if VE is not enabled on IE10, then why is this code being loaded ?"", '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+253514,VisualEditor: Init loads oo.js on every page view (before browser blacklist) which throws an error in IE10 + compatibility mode,But now fixed in production anyway. :-),task_subcomment,"['But now fixed in production anyway.', ':-)']","['SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+253511,VisualEditor: Init loads oo.js on every page view (before browser blacklist) which throws an error in IE10 + compatibility mode,Reclassifying as not serious after feedback confirming this only happens in developer mode.,task_subcomment,['Reclassifying as not serious after feedback confirming this only happens in developer mode.'],['BUG REPRODUCTION']
+253507,VisualEditor: Init loads oo.js on every page view (before browser blacklist) which throws an error in IE10 + compatibility mode,"This code shouldn't be running before the browser blacklists, you're right. We need to fix this urgently to avoid so many errors for users on every page load.
+
+To avoid confusion, note that this code works fine in ""real"" IE10, just not in compatibility mode; this isn't a blocker for VE working in IE.",task_subcomment,"[""This code shouldn't be running before the browser blacklists, you're right."", 'We need to fix this urgently to avoid so many errors for users on every page load.', 'To avoid confusion, note that this code works fine in ""real"" IE10, just not in compatibility mode; this isn\'t a blocker for VE working in IE.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+253503,VisualEditor: Init loads oo.js on every page view (before browser blacklist) which throws an error in IE10 + compatibility mode,"(In reply to comment #0)
+> On every page I load on IE10, when switched into compatibility mode, I
+> currently get the following error.
+> 
+> oo.js, line 97 character 2
+> Object doesn't support property or method 'create'
+> 
+Object.create and other ES5 features are only supported in IE10 and up, so IE10 in compat mode does not support them.
+
+> Also, if VE is not enabled on IE10, then why is this code being loaded ?
+Unfortunately, the blacklisting code is in a class, and that class extends another class, and oo.extendClass() uses Object.create() :(
+
+We're working on fixing this by moving the blacklisting up, see bug 50612",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nObject.create and other ES5 features are only supported in IE10 and up, so IE10 in compat mode does not support them.', ""QUOTE\nUnfortunately, the blacklisting code is in a class, and that class extends another class, and oo.extendClass() uses Object.create() :(\n\nWe're working on fixing this by moving the blacklisting up, see bug 50612""]","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+52656,TemplateData: Parse wikicode and/or HTML in interface text,"Parse wikicode and/or HTML in interface text. This is useful to make longer descriptions, i.e. with some lists, more readable, see URL for a trial.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://de.wikipedia.org/w/index.php?title=Vorlage:Normdaten/Doku&diff=120168256&oldid=120165159
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49772
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48451",task_description,"['TemplateData: Parse wikicode and/or HTML in interface text\n\nParse wikicode and/or HTML in interface text.', 'This is useful to make longer descriptions, i.e.', 'with some lists, more readable, see URL for a trial.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**URL**: URL\n**See Also**:\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+1605011,TemplateData: Parse wikicode and/or HTML in interface text,"Here's an inelegant proof-of-concept https://gitlab.com/wmde/mediawiki-extensions-VisualEditor/-/commit/3d06cd4e37e7356bd4b9f5235c9145fcc538cf0e
+
+Probably better to parse on the backend as part of the TemplateData API request, as discussed in {T241586}.",task_subcomment,"[""Here's an inelegant proof-of-concept URL\n\nProbably better to parse on the backend as part of the TemplateData API request, as discussed in {T241586}.""]",['SOLUTION DISCUSSION']
+600567,TemplateData: Parse wikicode and/or HTML in interface text,">>! In T52656#1937666, @Krenair wrote:
+> Well we definitely can't allow all HTML, and we probably don't want to put everything through the full MW parser...
+
+Even if we don't want to put everything through the full MW parser having the possibility to use internal links inside the description to link for example with help pages or external pages where the information to add in the parameter is provided.",task_subcomment,"[""QUOTE\nQUOTE\n\nEven if we don't want to put everything through the full MW parser having the possibility to use internal links inside the description to link for example with help pages or external pages where the information to add in the parameter is provided.""]",['SOLUTION DISCUSSION']
+597930,TemplateData: Parse wikicode and/or HTML in interface text,Providing a link to the template documentation page would be useful for some complex templates like https://en.wikipedia.org/wiki/Template:Coord which is almost impossible to describe using TemplateData. This is bug T51772.,task_subcomment,"['Providing a link to the template documentation page would be useful for some complex templates like URL which is almost impossible to describe using TemplateData.', 'This is bug T51772.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+597871,TemplateData: Parse wikicode and/or HTML in interface text,"For elaborate documentation and examples, one should use the Template documentation page instead. Remember this all has to fit within the VE interface when inserting a Template. This isn't the place for elaborate instructions.
+
+Contextual information per-parameter tends to be more appropiate. The interface currently provides a link back to the Template documentation page only if the template has no TemplateData yet:
+{F3284165}
+
+Perhaps we should provide this link always? Instead of only when data is absent.",task_subcomment,"['For elaborate documentation and examples, one should use the Template documentation page instead.', 'Remember this all has to fit within the VE interface when inserting a Template.', ""This isn't the place for elaborate instructions."", 'Contextual information per-parameter tends to be more appropiate.', 'The interface currently provides a link back to the Template documentation page only if the template has no TemplateData yet:\n{F3284165}\n\nPerhaps we should provide this link always?', 'Instead of only when data is absent.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+590914,TemplateData: Parse wikicode and/or HTML in interface text,"Well we definitely can't allow all HTML, and we probably don't want to put everything through the full MW parser...",task_subcomment,"[""Well we definitely can't allow all HTML, and we probably don't want to put everything through the full MW parser...""]",['SOLUTION DISCUSSION']
+252310,TemplateData: Parse wikicode and/or HTML in interface text,*** Bug 51311 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51311 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252306,TemplateData: Parse wikicode and/or HTML in interface text,Please don't mark older bugs as duplicates of newer ones.,task_subcomment,"[""Please don't mark older bugs as duplicates of newer ones.""]",['CONTRIBUTION AND COMMITMENT']
+252300,TemplateData: Parse wikicode and/or HTML in interface text,"(In reply to comment #1)
+> Is this the same as Bug 51311?
+
+I think so.
+
+*** This bug has been marked as a duplicate of bug 51311 ***",task_subcomment,"['(In reply to comment #1)\nQUOTE\n\nI think so.', '*** This bug has been marked as a duplicate of bug 51311 ***']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+252293,TemplateData: Parse wikicode and/or HTML in interface text,Is this the same as Bug 51311?,task_subcomment,['Is this the same as Bug 51311?'],['MOTIVATION']
+52643,VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that,"What it says on the tin; if you do nothing but rearrange text, the VE does not recognise it as an alteration and refuses to let you save.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49981
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50721",task_description,"['VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that\n\nWhat it says on the tin; if you do nothing but rearrange text, the VE does not recognise it as an alteration and refuses to let you save.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+251616,VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that,"The drag-and-drop operation previously had the appearance of being successful, in that the text would change to the dropped position.  After the text was moved, the save button wasnt enabled.
+
+Now the text can only be picked up and dragged around, but the text move operation is cancelled when the text is dropped.
+
+The bug has been fixed, and I am closing as such.  Probably as part of another piece of related work.
+
+For bonus points, VE shouldnt allow the text to be picked up and dragged.  I've opened that as an enhancement bug 54757.",task_subcomment,"['The drag-and-drop operation previously had the appearance of being successful, in that the text would change to the dropped position.', 'After the text was moved, the save button wasnt enabled.', 'Now the text can only be picked up and dragged around, but the text move operation is cancelled when the text is dropped.', 'The bug has been fixed, and I am closing as such.', 'Probably as part of another piece of related work.', 'For bonus points, VE shouldnt allow the text to be picked up and dragged.', ""I've opened that as an enhancement bug 54757.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'ACTION ON ISSUE', 'POTENTIAL NEW ISSUES AND REQUESTS', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+251611,VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that,fwiw I'm using Firefox and... it seems to work? The first post is not very descriptive so I don't know what to test. Happy to help.,task_subcomment,"[""fwiw I'm using Firefox and... it seems to work?"", ""The first post is not very descriptive so I don't know what to test."", 'Happy to help.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+251605,VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that,*** Bug 50977 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50977 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251599,VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that,*** Bug 50721 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50721 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251593,VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that,"Bug 49981 is about actually supporting this; until we do, we should disable it appearing to try to work in Firefox, only to not do so (because it's disabled).",task_subcomment,"[""Bug 49981 is about actually supporting this; until we do, we should disable it appearing to try to work in Firefox, only to not do so (because it's disabled).""]",['BUG REPRODUCTION']
+251587,VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that,"**JohnCD67** wrote:
+
+This only happens with drag-and-drop. VE will let you save a text rearrangement done with Ctrl-X, Ctrl-V, or Right-click/Cut, Right-click/Paste.",task_subcomment,"['**JohnCD67** wrote:\n\nThis only happens with drag-and-drop.', 'VE will let you save a text rearrangement done with Ctrl-X, Ctrl-V, or Right-click/Cut, Right-click/Paste.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52633,"VisualEditor: Display and let users edit arbitrary HTML anchors, e.g. in section headings","Some pages use anchors in the headings - useful for redirected articles.  Can VE display these and make them editable?
+
+Original request:
+
+I noticed that when editing (e.g.) [[ https://en.wikipedia.org/wiki/TRS-80#Compatible_successors | TRS-80 ]] that anchor templates, such as the ones I'd included within the section titles (e.g. [13])- for links that don't break when section titles change- don't show up in the visual editor... but they're still easily (inadvertantly) deletable, simply by backspacing over the hidden markup.
+
+You couldn't blame a newbie- or even nontechnical editor- for deleting something that wasn't even shown to them(!), but this is the sort of thing that could be a major pain in the neck.
+
+While I'm in favour of the visual editor in principle (the ability to contribute content shouldn't be reliant upon geekish markup skills), this *was* an issue that concerned me when I heard about the idea- namely that the large amounts of complicated templates and markup (which IMHO will never be entirely representable in the visual editor) would be inadvertantly messed up, either by users or by oversights within the design of a ""helpful"" visual editor itself.
+
+Ubcule (talk) 22:28, 2 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Display and let users edit arbitrary HTML anchors, e.g.', 'in section headings\n\nSome pages use anchors in the headings - useful for redirected articles.', 'Can VE display these and make them editable?', 'Original request:\n\nI noticed that when editing (e.g.)', ""[[ URL | TRS-80 ]] that anchor templates, such as the ones I'd included within the section titles (e.g."", ""[13])- for links that don't break when section titles change- don't show up in the visual editor... but they're still easily (inadvertantly) deletable, simply by backspacing over the hidden markup."", ""You couldn't blame a newbie- or even nontechnical editor- for deleting something that wasn't even shown to them(!"", '), but this is the sort of thing that could be a major pain in the neck.', 'While I\'m in favour of the visual editor in principle (the ability to contribute content shouldn\'t be reliant upon geekish markup skills), this *was* an issue that concerned me when I heard about the idea- namely that the large amounts of complicated templates and markup (which IMHO will never be entirely representable in the visual editor) would be inadvertantly messed up, either by users or by oversights within the design of a ""helpful"" visual editor itself.', 'Ubcule (talk) 22:28, 2 July 2013 (UTC)\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+52631,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**Author:** `ryuch`
+
+**Description:**
+Korean input is not complete. 
+
+I tried to input ""한글 시험 합니다."". 
+But it eats up some letters and produce ""글 험 다."".
+
+I tested with Chrome and Safari on Mac OSX. And it is all the same with Chrome on Windows XP.
+
+**See Also**: {T52105} {T72353}",task_description,"['VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME\n\n**Author:** CODE\n\n**Description:**\nKorean input is not complete.', 'I tried to input ""한글 시험 합니다."".', 'But it eats up some letters and produce ""글 험 다."".', 'I tested with Chrome and Safari on Mac OSX.', 'And it is all the same with Chrome on Windows XP.', '**See Also**: {T52105} {T72353}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+534068,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Seem to be resolved (idk which patch solved it).
+
+It's good to see that the #1 reason I hate/blame VE is finally resolved.",task_subcomment,"['Seem to be resolved (idk which patch solved it).', ""It's good to see that the #1 reason I hate/blame VE is finally resolved.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+533542,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Hi, typing seems to work for me in on en.wikipedia.org and on VE-standalone master, using:
+
+- Windows 8, MS or Nalgaeset IME, Firefox 40.0.3 or Chrome 45.0.2454.99 m
+- Ubuntu 15.04, Anthy IME, Firefox 40.0.3 or Chromium 44.0.2403.89 Ubuntu 15.04 (64-bit)
+
+In particular, I'm not seeing the ""first word disappears"" behaviour. Can we close this bug, or is anyone still seeing corruption?",task_subcomment,"['Hi, typing seems to work for me in on en.wikipedia.org and on VE-standalone master, using:\n\n- Windows 8, MS or Nalgaeset IME, Firefox 40.0.3 or Chrome 45.0.2454.99 m\n- Ubuntu 15.04, Anthy IME, Firefox 40.0.3 or Chromium 44.0.2403.89 Ubuntu 15.04 (64-bit)\n\nIn particular, I\'m not seeing the ""first word disappears"" behaviour.', 'Can we close this bug, or is anyone still seeing corruption?']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+517124,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"|browser|version|input|output|diff|
+|----|----|----|----|----|
+|IE|11.0.9600.17959|인터넷 익스플로러 테스트|인터넷 익스플로러 테스트|14721416|
+|Firefox|40.0.3|파이어폭스 테스트|파이어폭스 테스트|14721436|
+|Chrome|44.0.2403.157|구글 크롬 테스트|구글 크롬 테스트|14721446|
+
+OS: Win7, 32bit. IME: MS default one.
+
+For diff, use [[https://ko.wikipedia.org/wiki/Special:Diff|Special:Diff]].",task_subcomment,"['|browser|version|input|output|diff|\n|----|----|----|----|----|\n|IE|11.0.9600.17959|인터넷 익스플로러 테스트|인터넷 익스플로러 테스트|14721416|\n|Firefox|40.0.3|파이어폭스 테스트|파이어폭스 테스트|14721436|\n|Chrome|44.0.2403.157|구글 크롬 테스트|구글 크롬 테스트|14721446|\n\nOS: Win7, 32bit.', 'IME: MS default one.', 'For diff, use [[URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+341600,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Same here.
+```
+구글 크롬 윈도 7 39.0.2171.71 m
+```
+resulted
+```
+크롬 윈도 7 39.0.2171.71 m
+```
+It omits first word (구글).
+Tested on Win7 32bit Chrome version 39.0.2171.71 m.",task_subcomment,"['Same here.', '``CODE`CODE`CODE``\nIt omits first word (구글).', 'Tested on Win7 32bit Chrome version 39.0.2171.71 m.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+341599,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Same here.
+```
+구글 크롬 윈도 7 39.0.2171.71 m
+```
+resulted
+```
+크롬 윈도 7 39.0.2171.71 m
+```
+It omits first sentense.
+Tested on Win7 32bit Chrome version 39.0.2171.71 m.",task_subcomment,"['Same here.', '``CODE`CODE`CODE``\nIt omits first sentense.', 'Tested on Win7 32bit Chrome version 39.0.2171.71 m.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+341568,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Helo. It seems that finally most of Korean problems are solved.
+But one more problem is seen in VE.
+
+In the Windows 7 Chrome 64bit, when Hanguls first inputed and then spaced, the first word disappears.
+And this seems not results from IME.
+
+I input it Korean nalgaeset IME:
+Input : 날개셋 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다
+Output : 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다
+
+Anyway, thank you for your continuous effort.",task_subcomment,"['Helo.', 'It seems that finally most of Korean problems are solved.', 'But one more problem is seen in VE.', 'In the Windows 7 Chrome 64bit, when Hanguls first inputed and then spaced, the first word disappears.', 'And this seems not results from IME.', 'I input it Korean nalgaeset IME:\nInput : 날개셋 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다\nOutput : 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다\n\nAnyway, thank you for your continuous effort.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']"
+341567,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Helo. It seems that finally most of Korean problems are solved.
+But one more problem is seen in VE.
+
+In the Windows 7 Chrome 64bit, when Hanguls first inputed and then spaced, the first word disappears.
+And this seems not results from IME.
+
+I input it Korean senaru IME:
+Input : 세나루 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다
+Output : 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다
+
+Anyway, thank you for your continuous effort.",task_subcomment,"['Helo.', 'It seems that finally most of Korean problems are solved.', 'But one more problem is seen in VE.', 'In the Windows 7 Chrome 64bit, when Hanguls first inputed and then spaced, the first word disappears.', 'And this seems not results from IME.', 'I input it Korean senaru IME:\nInput : 세나루 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다\nOutput : 입력기로도 비슷한 결과가 나오는걸 보니 IME 문제는 애시당초 아니었겠습네다\n\nAnyway, thank you for your continuous effort.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']"
+340260,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,">>! In T52631#836024, @Revi wrote:
+> Hmm, while reviewing [[ https://ko.wikipedia.org/w/index.php?title=특수:최근바뀜&tagfilter=visualeditor | kowiki VE tag ]] , I find most edits have no problem.
+
+Yes, it's unclear right now which IMEs people are using and what their different impacts in VisualEditor are. It's possible that by now Korean works pretty well for the majority of users. We should follow-up with detailed automatic tests of each specific IME's functionalities so we can assess whether or not it works.",task_subcomment,"[""QUOTE\nQUOTE\n\nYes, it's unclear right now which IMEs people are using and what their different impacts in VisualEditor are."", ""It's possible that by now Korean works pretty well for the majority of users."", ""We should follow-up with detailed automatic tests of each specific IME's functionalities so we can assess whether or not it works.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+340259,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Hmm, while reviewing [[ https://ko.wikipedia.org/w/index.php?title=특수:최근바뀜&tagfilter=visualeditor | kowiki VE tag ]] , I find most edits have no problem.",task_subcomment,"['Hmm, while reviewing [[ URL | kowiki VE tag ]] , I find most edits have no problem.']",['OBSERVED BUG BEHAVIOR']
+250886,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"I tried VE in [[en:User:Hym411/VETest]] with VE betafeatures enabled;
+
+Input: ""구글 크롬 안드로이드용 최신 버전""
+
+Output: See the page above. - ""국글 클롬 안들롱읻등용 쵯신 벚전""
+
+I used latest release of Google Chrome for Android.
+
+Also, comment 25 's 'backspace does not work' still happens to me.",task_subcomment,"['I tried VE in [[en:User:Hym411/VETest]] with VE betafeatures enabled;\n\nInput: ""구글 크롬 안드로이드용 최신 버전""\n\nOutput: See the page above.', '- ""국글 클롬 안들롱읻등용 쵯신 벚전""\n\nI used latest release of Google Chrome for Android.', ""Also, comment 25 's 'backspace does not work' still happens to me.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250877,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Thanks very much for the video -- that's a great help!
+
+I agree about the events. Actually I think it's every browser/OS/IME combination, so it's really troublesome.
+
+As far as I can tell, there are actually two issues at the moment:
+
+(1) Entering Korean text into an empty paragraph, and
+(2) Entering Korean text into a non-empty paragraph.
+
+Your video shows that case (1) is still broken. In order to test (2), would it be possible to try typing ""hello"", and then start typing Korean immediately after the ""o"" (i.e. without starting a new line/paragraph)?
+
+I have done these sorts of tests, but I can't reproduce the behaviour you show in the video, presumably because of some slight difference between our test platforms.
+
+Thanks again!",task_subcomment,"[""Thanks very much for the video -- that's a great help!"", 'I agree about the events.', ""Actually I think it's every browser/OS/IME combination, so it's really troublesome."", 'As far as I can tell, there are actually two issues at the moment:\n\n(1) Entering Korean text into an empty paragraph, and\n(2) Entering Korean text into a non-empty paragraph.', 'Your video shows that case (1) is still broken.', 'In order to test (2), would it be possible to try typing ""hello"", and then start typing Korean immediately after the ""o"" (i.e.', 'without starting a new line/paragraph)?', ""I have done these sorts of tests, but I can't reproduce the behaviour you show in the video, presumably because of some slight difference between our test platforms."", 'Thanks again!']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250867,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**heesub** wrote:
+
+(In reply to comment #34)
+> Would it be possible to test against current master? We believe that we have
+> fixed this (or, at least, change the behaviour) since you tested it with
+> cba2935 (thank you!).
+
+I've tested the latest version and uploaded a video clip which shows what is happening on VisualEditor with Korean characters. You can find the video on this link: http://youtu.be/-Q8n4vNONm0
+
+I am not a JavaScript or web programming expert, it seems that every browser out there has different behaviors on firing and processing compositionStart/End and keyDown events. Take a look at this document: http://joone4u.blogspot.kr/2010/07/composition-events-are-handled_27.html
+
+After digging this issue, I found some combinations which avoid this issue:
+ - Safari, Google Chrome (maybe every other browsers, but not tested) on Mac OS X. and change preference settings of Korean IME: set 'Input by' to 'Word' not 'Syllable' which is default.
+ - Firefox on Ubuntu
+
+Hope this helps!",task_subcomment,"[""**heesub** wrote:\n\n(In reply to comment #34)\nQUOTE\nQUOTE\nQUOTE\n\nI've tested the latest version and uploaded a video clip which shows what is happening on VisualEditor with Korean characters."", 'You can find the video on this link: URL\n\nI am not a JavaScript or web programming expert, it seems that every browser out there has different behaviors on firing and processing compositionStart/End and keyDown events.', ""Take a look at this document: URL\n\nAfter digging this issue, I found some combinations which avoid this issue:\n - Safari, Google Chrome (maybe every other browsers, but not tested) on Mac OS X. and change preference settings of Korean IME: set 'Input by' to 'Word' not 'Syllable' which is default."", '- Firefox on Ubuntu\n\nHope this helps!']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+250860,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Would it be possible to test against current master? We believe that we have fixed this (or, at least, change the behaviour) since you tested it with cba2935 (thank you!).",task_subcomment,"['Would it be possible to test against current master?', 'We believe that we have fixed this (or, at least, change the behaviour) since you tested it with cba2935 (thank you!', ').']","['TESTING', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250854,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**heesub** wrote:
+
+(In reply to comment #32)
+> I am suffering from this issue, tested on the latest version from mediawiki's
+> core.git: 217fd43. The odd thing is that it seems to work properly on Firefox
+> which comes with Ubuntu 13.04 LTS distribution(, but not perfectly).
+
+I'd tested on VisualEditor.git: cba2935 and also with patchset v16 by David Chan. Not fixed.",task_subcomment,"[""**heesub** wrote:\n\n(In reply to comment #32)\nQUOTE\nQUOTE\nQUOTE\n\nI'd tested on VisualEditor.git: cba2935 and also with patchset v16 by David Chan."", 'Not fixed.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250849,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**heesub** wrote:
+
+I am suffering from this issue, tested on the latest version from mediawiki's core.git: 217fd43. The odd thing is that it seems to work properly on Firefox which comes with Ubuntu 13.04 LTS distribution(, but not perfectly).
+
+I've tried:
+* IE on Windows 7 : not working
+* Google Chrome on Windows 7 : not working
+* Google Chrome on Ubuntu 13.04 : not working
+* Safari on Mac OSX 10.8.5: not working
+* Google Chrome on Mac OSX 10.8.5: not working
+* Firefox on Ubuntu 13.04 : WORKING
+
+I hope this information help you guys so that it gets fixed.",task_subcomment,"[""**heesub** wrote:\n\nI am suffering from this issue, tested on the latest version from mediawiki's core.git: 217fd43."", 'The odd thing is that it seems to work properly on Firefox which comes with Ubuntu 13.04 LTS distribution(, but not perfectly).', ""I've tried:\n* IE on Windows 7 : not working\n* Google Chrome on Windows 7 : not working\n* Google Chrome on Ubuntu 13.04 : not working\n* Safari on Mac OSX 10.8.5: not working\n* Google Chrome on Mac OSX 10.8.5: not working\n* Firefox on Ubuntu 13.04 : WORKING\n\nI hope this information help you guys so that it gets fixed.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+250843,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"(In reply to comment #30)
+> (In reply to comment #29)
+> > Marking this as ""FIXED"" on the expectation that it's fixed - please re-open
+> > if
+> > you find that it is still occurring.
+> 
+> I am sorry. It is not fixed.  I tested on mediawiki.org.
+
+:-(
+
+> I open it again.
+
+OK, we'll look at it urgently. Sorry for this.",task_subcomment,"[""(In reply to comment #30)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n:-(\n\nQUOTE\n\nOK, we'll look at it urgently."", 'Sorry for this.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+250837,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+(In reply to comment #29)
+> Marking this as ""FIXED"" on the expectation that it's fixed - please re-open
+> if
+> you find that it is still occurring.
+
+I am sorry. It is not fixed.  I tested on mediawiki.org.
+
+I open it again.",task_subcomment,"['**ryuch** wrote:\n\n(In reply to comment #29)\nQUOTE\nQUOTE\nQUOTE\n\nI am sorry.', 'It is not fixed.', 'I tested on mediawiki.org.', 'I open it again.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250830,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",task_subcomment,"['Marking this as ""FIXED"" on the expectation that it\'s fixed - please re-open if you find that it is still occurring.']",['ACTION ON ISSUE']
+250820,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:
+
+https://gerrit.wikimedia.org/r/#/c/82858/
+
+Please let us know whether it fixes the bug!",task_subcomment,"[""There's code to address this bug in the following patch, which is due to go live by mediawiki.org on 13 September 2013:\n\nURL\n\nPlease let us know whether it fixes the bug!""]",['BUG REPRODUCTION']
+250809,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+(In reply to comment #26)
+> (In reply to comment #25)
+> > https://gerrit.wikimedia.org/r/#/c/79451 did not fix the problem
+> 
+> Just to avoid misunderstandings: How did you test this? Do you run a private
+> wiki with recent VisualEditor from git master?
+
+Not on a private one, I ran on  MediaWiki.Org, specifically on  [[mw:VisualEditor:Test]].
+
+
+
+> 
+> > I found another thing, when the cursor is after Korean letters backspace does
+> > not work.
+> 
+> Please file separate bug reports for separate issues. Thanks! :)
+
+I think the space problem is caused by this bug. I suppose we need to fix error  of synchronization between DM and CE.
+
+Thank you, too.",task_subcomment,"['**ryuch** wrote:\n\n(In reply to comment #26)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNot on a private one, I ran on  MediaWiki.Org, specifically on  [[mw:VisualEditor:Test]].', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI think the space problem is caused by this bug.', 'I suppose we need to fix error  of synchronization between DM and CE.', 'Thank you, too.']","['OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250797,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"(In reply to comment #25)
+> https://gerrit.wikimedia.org/r/#/c/79451 did not fix the problem
+
+Just to avoid misunderstandings: How did you test this? Do you run a private wiki with recent VisualEditor from git master?
+
+> I found another thing, when the cursor is after Korean letters backspace does
+> not work.
+
+Please file separate bug reports for separate issues. Thanks! :)",task_subcomment,"['(In reply to comment #25)\nQUOTE\n\nJust to avoid misunderstandings: How did you test this?', 'Do you run a private wiki with recent VisualEditor from git master?', 'QUOTE\nQUOTE\n\nPlease file separate bug reports for separate issues.', 'Thanks!', ':)']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250787,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+(In reply to comment #16)
+> I believe the following patch resolves the problem on those platforms where
+> there still was one: https://gerrit.wikimedia.org/r/#/c/79451 . At least, the
+> patch seems to fix the Korean ibus method on Ubuntu+Chromium. However it's
+> hard
+> to be sure because of the problems reproducing the bug.
+
+David,
+
+https://gerrit.wikimedia.org/r/#/c/79451 did not fix the problem even Chrome on Ubuntu, if the code is applied to MediaWiki.org as James said.
+
+I found another thing, when the cursor is after Korean letters backspace does not work.",task_subcomment,"['**ryuch** wrote:\n\n(In reply to comment #16)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nDavid,\n\nURL did not fix the problem even Chrome on Ubuntu, if the code is applied to MediaWiki.org as James said.', 'I found another thing, when the cursor is after Korean letters backspace does not work.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250778,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"(In reply to comment #22)
+> We can check on en.wikipedia or ko.wikipedia, only,
+> if the problem fixed.
+> 
+> So can you apply it on there?
+
+The code will be applied as part of the normal MediaWiki release cycle, which you can see here: [[mw:MediaWiki_1.22/Roadmap#Schedule_for_the_deployments]].
+
+This code is tagged against the release that happened this morning (""wmf14"") - this means that the code is available now on MediaWiki.org, and will be available on all Wikipedias (including the English and Korean Wikipedias) next Thursday, 29 August, at approximately 18:00 UTC.
+
+If you want to test and confirm the code, you can edit pages on MediaWiki.org like [[mw:VisualEditor:Test]]. Also, all code is immediately available on the ""Beta labs"" testing site, which can also be edited (note that it uses a different account system to production ""real"" Wikipedias): http://en.wikipedia.beta.wmflabs.org/wiki/VisualEditor 
+
+Hope this helps!",task_subcomment,"['(In reply to comment #22)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe code will be applied as part of the normal MediaWiki release cycle, which you can see here: [[mw:MediaWiki_1.22/Roadmap#Schedule_for_the_deployments]].', 'This code is tagged against the release that happened this morning (""wmf14"") - this means that the code is available now on MediaWiki.org, and will be available on all Wikipedias (including the English and Korean Wikipedias) next Thursday, 29 August, at approximately 18:00 UTC.', 'If you want to test and confirm the code, you can edit pages on MediaWiki.org like [[mw:VisualEditor:Test]].', 'Also, all code is immediately available on the ""Beta labs"" testing site, which can also be edited (note that it uses a different account system to production ""real"" Wikipedias): URL \n\nHope this helps!']","['SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE']"
+250770,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,Yes. All code in master is eventually deployed during our scheduled deployments. If you want to test the code ahead of the deployment you will have to check it out locally.,task_subcomment,"['Yes.', 'All code in master is eventually deployed during our scheduled deployments.', 'If you want to test the code ahead of the deployment you will have to check it out locally.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'WORKAROUNDS']"
+250764,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"We can check on en.wikipedia or ko.wikipedia, only,
+if the problem fixed.
+
+So can you apply it on there?",task_subcomment,"['We can check on en.wikipedia or ko.wikipedia, only,\nif the problem fixed.', 'So can you apply it on there?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250759,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"No, it hasn't been deployed to en.wiki yet.",task_subcomment,"[""No, it hasn't been deployed to en.wiki yet.""]",['OBSERVED BUG BEHAVIOR']
+250753,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Sorry, but If you applied it on en.wikipedia. it yet not fixed.",task_subcomment,"['Sorry, but If you applied it on en.wikipedia.', 'it yet not fixed.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+250748,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Given that this is now merged, I'm going to mark this as fixed. However, this is provisional - please re-open if you think that this has not worked!",task_subcomment,"[""Given that this is now merged, I'm going to mark this as fixed."", 'However, this is provisional - please re-open if you think that this has not worked!']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+250744,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Change 80080 merged by jenkins-bot:
+Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",task_subcomment,"[""Change 80080 merged by jenkins-bot:\nDon't emit Surface changes back to the Surface\n\nGERRIT_URL""]",['OBSERVED BUG BEHAVIOR']
+250738,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Change 80080 had a related patch set uploaded by Jforrester:
+WIP:Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",task_subcomment,"[""Change 80080 had a related patch set uploaded by Jforrester:\nWIP:Don't emit Surface changes back to the Surface\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+250732,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"I believe the following patch resolves the problem on those platforms where there still was one: https://gerrit.wikimedia.org/r/#/c/79451 . At least, the patch seems to fix the Korean ibus method on Ubuntu+Chromium. However it's hard to be sure because of the problems reproducing the bug.",task_subcomment,"['I believe the following patch resolves the problem on those platforms where there still was one: URL .', 'At least, the patch seems to fix the Korean ibus method on Ubuntu+Chromium.', ""However it's hard to be sure because of the problems reproducing the bug.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250726,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+==Test Cases==
+
+글험 합니다. 다닏ㄴ합하험허시ㅅ (2013.8.14, Chrome of Windows XP)
+
+글 험 다. (2013.8.14, Chrome of Mac OS X)
+
+한글 시험 합니다. (2013.8.14, Chrome of Ubuntu, iBus 1.4.1)",task_subcomment,"['**ryuch** wrote:\n\n==Test Cases==\n\n글험 합니다.', '다닏ㄴ합하험허시ㅅ (2013.8.14, Chrome of Windows XP)\n\n글 험 다.', '(2013.8.14, Chrome of Mac OS X)\n\n한글 시험 합니다.', '(2013.8.14, Chrome of Ubuntu, iBus 1.4.1)']","['OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+250719,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+awesome. anyway.
+Please make it opt-in on KOWP.
+
+I will catch you guys at the lounge.",task_subcomment,"['**ryuch** wrote:\n\nawesome.', 'anyway.', 'Please make it opt-in on KOWP.', 'I will catch you guys at the lounge.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+250714,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,@Ryu not deliberately! Come to the VE lounge tomorrow (hackathon room) and speak to me and David.,task_subcomment,"['SCREEN_NAME not deliberately!', 'Come to the VE lounge tomorrow (hackathon room) and speak to me and David.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+250708,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,It also works on Chrome for WinXP/Win7/Android(though it is not supported).,task_subcomment,['It also works on Chrome for WinXP/Win7/Android(though it is not supported).'],['INVESTIGATION AND EXPLORATION']
+250704,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+You fixed this? It works.
+
+http://en.wikipedia.org/w/index.php?title=User%3ARyuch&diff=567832037&oldid=567831839
+
+I tested with Chrome on Ubuntu at this moment.",task_subcomment,"['**ryuch** wrote:\n\nYou fixed this?', 'It works.', 'URL\n\nI tested with Chrome on Ubuntu at this moment.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+250700,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Now the problem seems something changed, but It is yet hard.
+
+I input '한글 결과는 언제 나오나요'
+
+but in the en wikipedia's visual editor @ chrome ,
+it have 'ㄱㅡㄹ ㅏㄴㄴ 제 오요나나제언ㅇㅏ결겨ㄱㅡ'.
+
+See http://en.wikipedia.org/w/index.php?title=User:Galadrien/sandbox&diff=564998163&oldid=549762292 .",task_subcomment,"['Now the problem seems something changed, but It is yet hard.', ""I input '한글 결과는 언제 나오나요'\n\nbut in the en wikipedia's visual editor @ chrome ,\nit have 'ㄱㅡㄹ ㅏㄴㄴ 제 오요나나제언ㅇㅏ결겨ㄱㅡ'."", 'See URL .']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+250696,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+
+I think VE team is working on this issue. Did you change the code related this?
+I think so.
+DangSunM's report is not what I got when I made the first report.
+
+Now I tested on Chome of iPad. It is different also.
+I input '한글 시험 합니다.', same as previous.
+And now I have '한글 싷험 합닏다.', like the think 
+http://en.wikipedia.org/w/index.php?title=User:Ryuch&curid=284811&diff=564158229&oldid=554104287
+.
+
+It duplicates the begining consonant of a syllable to the place of ending consonant of a syllable just before it in a word when the ending consonant is null.",task_subcomment,"['**ryuch** wrote:\n\n\nI think VE team is working on this issue.', 'Did you change the code related this?', 'I think so.', ""DangSunM's report is not what I got when I made the first report."", 'Now I tested on Chome of iPad.', 'It is different also.', ""I input '한글 시험 합니다."", ""', same as previous."", ""And now I have '한글 싷험 합닏다."", ""', like the think \nURL\n."", 'It duplicates the begining consonant of a syllable to the place of ending consonant of a syllable just before it in a word when the ending consonant is null.']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250688,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"I also tried to write some Korean words using visual editor
+"" 시 각 편 집 기 테 스 트 근데 잘 안되""
+but it types 
+"" 시 각 편 집 기 테 스 트 근데 잘 안되 되도안아잘자ㅈ데근ㄱ트스ㅋ크스ㅅ테ㅌㅍ페기집지편펴가"" see http://ko.wikipedia.org/w/index.php?title=%EC%82%AC%EC%9A%A9%EC%9E%90%3A%EB%B6%84%EB%8B%B9%EC%84%A0M&diff=11132326&oldid=11087937 for details",task_subcomment,"['I also tried to write some Korean words using visual editor\n"" 시 각 편 집 기 테 스 트 근데 잘 안되""\nbut it types \n"" 시 각 편 집 기 테 스 트 근데 잘 안되 되도안아잘자ㅈ데근ㄱ트스ㅋ크스ㅅ테ㅌㅍ페기집지편펴가"" see URL for details']",['BUG REPRODUCTION']
+250682,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Yes, lack of reliable IME support would be a show-stopper.",task_subcomment,"['Yes, lack of reliable IME support would be a show-stopper.']",['INVESTIGATION AND EXPLORATION']
+250675,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"**ryuch** wrote:
+
+This was feed backed to 
+http://www.mediawiki.org/w/index.php?title=Thread:VisualEditor/Feedback/i_can%27t_type_a_east_asian_character
+
+If you cannot resolve the problem in time, we'd better postpone the deployment on Korean Wikipedia or other Korean projects.",task_subcomment,"[""**ryuch** wrote:\n\nThis was feed backed to \nURL\n\nIf you cannot resolve the problem in time, we'd better postpone the deployment on Korean Wikipedia or other Korean projects.""]",['WORKAROUNDS']
+250668,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"(In reply to comment #4)
+> The latin text in iBus Korean is:
+> 
+> gks rmf [SPACE] tl gja [SPACE] gkq sl ek
+> 
+> Typing just ""gksr"" the following events are fired:
+> 
+> compositionstart
+> g,k,s
+> compositionend
+> compositionstart
+> r
+> compositionend
+
+
+I'm seeing slightly different behaviour on Chromium 25.0.1364.160-0ubuntu0.12.04.1 using ibus 1.4.1-3ubuntu1 and ibus-hangul 1.3.1-3build1.
+
+If I start with an almost blank document (just the letter ""A"" with the cursor immediately after), then I can type ""gksrmf tlgja gkqslek"" and get exactly the expected characters """"한글 시험 합니다"". The event sequence is as it should be (with the second compositionend only happening when I hit space).
+
+However, if I then type the full stop, it goes *after* the cursor.",task_subcomment,"[""(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n\nI'm seeing slightly different behaviour on Chromium 25.0.1364.160-0ubuntu0.12.04.1 using ibus 1.4.1-3ubuntu1 and ibus-hangul 1.3.1-3build1."", 'If I start with an almost blank document (just the letter ""A"" with the cursor immediately after), then I can type ""gksrmf tlgja gkqslek"" and get exactly the expected characters """"한글 시험 합니다"".', 'The event sequence is as it should be (with the second compositionend only happening when I hit space).', 'However, if I then type the full stop, it goes *after* the cursor.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250662,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,"Trying to type into an empty/slug paragraph causes all sorts of whacky behaviour and should probably be filed as a separate bug
+
+The latin text in iBus Korean is:
+
+gks rmf [SPACE] tl gja [SPACE] gkq sl ek
+
+Typing just ""gksr"" the following events are fired:
+
+compositionstart
+g,k,s
+compositionend
+compositionstart
+r
+compositionend
+
+with the final compositionend causing the second Hangul character to end prematurely.
+
+Need to investigate if this a browser bug related to IME's which allow continuous typing across graphemes.",task_subcomment,"['Trying to type into an empty/slug paragraph causes all sorts of whacky behaviour and should probably be filed as a separate bug\n\nThe latin text in iBus Korean is:\n\ngks rmf [SPACE] tl gja [SPACE] gkq sl ek\n\nTyping just ""gksr"" the following events are fired:\n\ncompositionstart\ng,k,s\ncompositionend\ncompositionstart\nr\ncompositionend\n\nwith the final compositionend causing the second Hangul character to end prematurely.', ""Need to investigate if this a browser bug related to IME's which allow continuous typing across graphemes.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250656,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,This looks quite a lot like an IME issue (at least with iBus Korean).,task_subcomment,['This looks quite a lot like an IME issue (at least with iBus Korean).'],['OBSERVED BUG BEHAVIOR']
+250651,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,David and I may take a look at this over a cocktail.,task_subcomment,['David and I may take a look at this over a cocktail.'],['SOLUTION DISCUSSION']
+250647,VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,It also comes to Chrome on Win7.,task_subcomment,['It also comes to Chrome on Win7.'],['OBSERVED BUG BEHAVIOR']
+52615,"VisualEditor: ""Error contacting the Parsoid server"" while editing a section in a diff","From En:Wikipedia
+
+""Interesting one that i just wandered across while looking at an old Articles for creation backlog drive, that causes a very interesting error popup to appear (Tested in Firefox 22)
+
+Navigate to http://en.wikipedia.org/w/index.php?title=Baylor_University_Institute_for_Oral_History&diff=555106174&oldid=prev
+Try to edit the ""Mission"" section in the VE.
+Result: An error popup stating Error loading data from server: parsoidserver: Error contacting the Parsoid server. Would you like to retry?
+This seems to be caused by the ""oldid=prev"" part. Normally this loads the revision prior to the Diff part of the URL, but it seems the VE cannot handle that correctly. Excirial (Contact me,Contribs) 21:25, 2 July 2013 (UTC)""
+
+
+I tried this and had the same experience on Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: ""Error contacting the Parsoid server"" while editing a section in a diff\n\nFrom En:Wikipedia\n\n""Interesting one that i just wandered across while looking at an old Articles for creation backlog drive, that causes a very interesting error popup to appear (Tested in Firefox 22)\n\nNavigate to URL\nTry to edit the ""Mission"" section in the VE.', 'Result: An error popup stating Error loading data from server: parsoidserver: Error contacting the Parsoid server.', 'Would you like to retry?', 'This seems to be caused by the ""oldid=prev"" part.', 'Normally this loads the revision prior to the Diff part of the URL, but it seems the VE cannot handle that correctly.', 'Excirial (Contact me,Contribs) 21:25, 2 July 2013 (UTC)""\n\n\nI tried this and had the same experience on Chrome.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52609,VisualEditor: Cancelling out of adding a reference adds an empty reference,"From David Gerard on the en.wp feedback page: if you go to add a reference and then choose not to continue and exit out of the template and save the page instead of going back, VisualEditor creates an empty closed reference tab .  See here:
+https://en.wikipedia.org/w/index.php?title=User:David_Gerard&diff=562600190&oldid=545746964
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52182",task_description,"['VisualEditor: Cancelling out of adding a reference adds an empty reference\n\nFrom David Gerard on the en.wp feedback page: if you go to add a reference and then choose not to continue and exit out of the template and save the page instead of going back, VisualEditor creates an empty closed reference tab .', 'See here:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249527,VisualEditor: Cancelling out of adding a reference adds an empty reference,This was fixed in (I think) August; sorry for not noting it until now.,task_subcomment,['This was fixed in (I think) August; sorry for not noting it until now.'],['SOLUTION USAGE']
+249515,VisualEditor: Cancelling out of adding a reference adds an empty reference,"This is because we currently have the logic for a creating refernece (and potentially re-using an existing reference) and actually interacting with the content of a reference in a separate dialog. As soon as you go into the editor it inserts an empty reference and lets you edit that.
+
+This sounds like another reason to keep those two things in the same dialog (instead of making it look like one, actually have it be one). A dialog is perfectly capable of having multiple ""pages"" or ""states"". This would save a small amount of duplication and gain a fix for this bug and the bug of the animation between the two dialogs.",task_subcomment,"['This is because we currently have the logic for a creating refernece (and potentially re-using an existing reference) and actually interacting with the content of a reference in a separate dialog.', 'As soon as you go into the editor it inserts an empty reference and lets you edit that.', 'This sounds like another reason to keep those two things in the same dialog (instead of making it look like one, actually have it be one).', 'A dialog is perfectly capable of having multiple ""pages"" or ""states"".', 'This would save a small amount of duplication and gain a fix for this bug and the bug of the animation between the two dialogs.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+249506,VisualEditor: Cancelling out of adding a reference adds an empty reference,"(In reply to comment #1)
+> Note that this doesn't happen until you hit ""Create reference"" inside the
+> first dialogue box, so you have arguably told it to create a reference ...
+> but this will confuse people, because modal dialogue boxes in applications
+> usually cancel out your actions if you just keep hitting the X.
+
+Agreed. We'll get this fixed.
+
+> Arguably, it shouldn't create a reference if it's got nothing to put into
+> the reference.
+
+Are you telling users they're not allowed to do what they want?! ;-) I think that the number of users irritated by just silently munching references created as blank (""so I can come back to it later!"") would be non-zero.",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAgreed.', ""We'll get this fixed."", ""QUOTE\nQUOTE\n\nAre you telling users they're not allowed to do what they want?!"", ';-) I think that the number of users irritated by just silently munching references created as blank (""so I can come back to it later!"")', 'would be non-zero.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+249497,VisualEditor: Cancelling out of adding a reference adds an empty reference,"Note that this doesn't happen until you hit ""Create reference"" inside the first dialogue box, so you have arguably told it to create a reference ... but this will confuse people, because modal dialogue boxes in applications usually cancel out your actions if you just keep hitting the X. Arguably, it shouldn't create a reference if it's got nothing to put into the reference.",task_subcomment,"['Note that this doesn\'t happen until you hit ""Create reference"" inside the first dialogue box, so you have arguably told it to create a reference ... but this will confuse people, because modal dialogue boxes in applications usually cancel out your actions if you just keep hitting the X. Arguably, it shouldn\'t create a reference if it\'s got nothing to put into the reference.']",['BUG REPRODUCTION']
+52607,"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output","Compare the charts table in 
+
+* http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?oldid=561481881
+* http://parsoid.wmflabs.org/en/2012_%28It_Ain%27t_the_End%29?oldid=561481881
+* http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?veaction=edit&oldid=561481881
+
+In VE, the table cells seem to be squashed into one. The DOM looks like nested divs there, which would explain the different rendering.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50951",task_description,"['VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output\n\nCompare the charts table in \n\n* URL\n* URL\n* URL\n\nIn VE, the table cells seem to be squashed into one.', 'The DOM looks like nested divs there, which would explain the different rendering.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249425,"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output",Fixed by gerrit 140439.,task_subcomment,['Fixed by gerrit 140439.'],['SOLUTION USAGE']
+249418,"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output",*** Bug 52485 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52485 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249411,"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output","**Wikifram** wrote:
+
+Note that this bug affects all 5,000 pages that use Template:Episode list on enwiki.",task_subcomment,"['**Wikifram** wrote:\n\nNote that this bug affects all 5,000 pages that use Template:Episode list on enwiki.']",['OBSERVED BUG BEHAVIOR']
+249407,"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output","{{yes}}. For comparison, the Parsoid output at http://parsoid.wmflabs.org/en/Comparison_of_open-source_software_hosting_facilities looks fine.",task_subcomment,"['{{yes}}.', 'For comparison, the Parsoid output at URL looks fine.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+249405,"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output",Is this bug responsible for the {{yes}} and {{no}} templated cells not rendering as separate cells at https://en.wikipedia.org/w/index.php?title=Comparison_of_open-source_software_hosting_facilities&veaction=edit§ion=1 ?,task_subcomment,['Is this bug responsible for the {{yes}} and {{no}} templated cells not rendering as separate cells at URL ?'],['OBSERVED BUG BEHAVIOR']
+249402,"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output","This is because the HTML looks like ...... and so the group of table cells is considered a template, and so the CE rendering is wrapped in a 
    . I'd like to be able to render templates (and aliens) without wrapper divs in CE, but I'm not sure how realistic that is.",task_subcomment,"['This is because the HTML looks like ...... and so the group of table cells is considered a template, and so the CE rendering is wrapped in a 
    .', ""I'd like to be able to render templates (and aliens) without wrapper divs in CE, but I'm not sure how realistic that is.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52589,Templates that create multiple table cells don't work,"**Author:** `kwwilliams`
+
+**Description:**
+VE can't properly display any table using {{singlechart}} on English Wikipedia, which makes any editing of the fields pretty dicey.
+
+Taking http://en.wikipedia.org/wiki/5_O%27Clock_%28T-Pain_song%29 as an example (it's actually one of thousands), http://en.wikipedia.org/wiki/File:Singlechart-Articleview.PNG shows what the table looks like when being displayed. http://en.wikipedia.org/wiki/File:Visual-editor-singlechart.png shows what it looks like after Visual editor has been engaged. Note that South Korea (GAON) rows and Romanian Top 100 rows are generated by manual table markup and the remainder are template calls.
+
+This probably comes about from two factors:
+
+1) Singlechart generates a ""|"" or ""!"" internally to start a table row, based on whether it has been called with the rowheader parameter.
+2) Singlechart generates another | between the two data items it outputs to separate the fields in the table row.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50366
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44498
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50951
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52296",task_description,"[""Templates that create multiple table cells don't work\n\n**Author:** CODE\n\n**Description:**\nVE can't properly display any table using {{singlechart}} on English Wikipedia, which makes any editing of the fields pretty dicey."", ""Taking URL as an example (it's actually one of thousands), URL shows what the table looks like when being displayed."", 'URL shows what it looks like after Visual editor has been engaged.', 'Note that South Korea (GAON) rows and Romanian Top 100 rows are generated by manual table markup and the remainder are template calls.', 'This probably comes about from two factors:\n\n1) Singlechart generates a ""|"" or ""!""', 'internally to start a table row, based on whether it has been called with the rowheader parameter.', '2) Singlechart generates another | between the two data items it outputs to separate the fields in the table row.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\nURL\nURL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248266,Templates that create multiple table cells don't work,"Fixed by https://gerrit.wikimedia.org/r/#/c/79430/, which is now deployed. Chart tables such as the one on http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?veaction=edit now render and round-trip as expected.
+
+The unrelated table rendering issue in http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?veaction=edit is VisualEditor bug 50607.",task_subcomment,"['Fixed by URL which is now deployed.', 'Chart tables such as the one on URL now render and round-trip as expected.', 'The unrelated table rendering issue in URL is VisualEditor bug 50607.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+248260,Templates that create multiple table cells don't work,This seems to be related to bug 44498.,task_subcomment,['This seems to be related to bug 44498.'],['MOTIVATION']
+248255,Templates that create multiple table cells don't work,"Not sure if I should open a new or make a comment here... But is this wrong rendering (too much td nodes) the result of this bug?
+http://parsoid.wmflabs.org/sr/%D0%93%D0%BB%D0%B0%D0%B2%D0%BD%D0%B0_%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B0",task_subcomment,"['Not sure if I should open a new or make a comment here...', 'But is this wrong rendering (too much td nodes) the result of this bug?', 'URL']","['CONTRIBUTION AND COMMITMENT', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+248251,Templates that create multiple table cells don't work,"(In reply to comment #10)
+> Oh wow, on some more investigation it looks like we are actually rendering
+> the table just fine:
+> 
+> http://parsoid.wmflabs.org/en/2012_%28It_Ain%27t_the_End%29
+> 
+> So the odd rendering seems to be a VE issue.
+
+Should this bug be recategorized then?",task_subcomment,['(In reply to comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nShould this bug be recategorized then?'],['SOLUTION DISCUSSION']
+248246,Templates that create multiple table cells don't work,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+248240,Templates that create multiple table cells don't work,"Oh wow, on some more investigation it looks like we are actually rendering the table just fine:
+
+http://parsoid.wmflabs.org/en/2012_%28It_Ain%27t_the_End%29
+
+So the odd rendering seems to be a VE issue.",task_subcomment,"['Oh wow, on some more investigation it looks like we are actually rendering the table just fine:\n\nURL\n\nSo the odd rendering seems to be a VE issue.']",['OBSERVED BUG BEHAVIOR']
+248234,Templates that create multiple table cells don't work,"> You really need to be parsing *after* template expansion and tracking all the
+> text that the templates generate.
+
+We are tokenizing templates and content separately so that we can cut template vs. non-template content on a token level. Attribute keys and values can also be templated, but we don't support templates producing several attributes and parts of a token.
+
+This and the need to infer resulting DOM structures affected by template-produced tokens already adds a lot of complexity, but at least the results can somewhat sanely be represented in DOM. Having 1/3 of a DOM element's start tag be generated by page source and 2/3 templated on some arbitrary boundary would be a nightmare to represent in DOM and even worse in a UI.
+
+You are right though that we *could* in theory represent something like |{{singlechart|..}} as a special case of a multi-part templated construct. This would run counter to our desire to move towards self-contained templates though that are easier to edit both in wikitext and the VE. Removing the pipes in the page and returning the full table row from singlechart would be better in that regard.
+
+> Removing the pipe doesn't quite work, though: take a peek at
+> http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?veaction=edit vs.
+> http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29 and notice how the
+> manual entries and the templated entries align in the normal view but
+> scramble
+> in the edit view.
+
+Indeed, it seems that we don't recognize single-line rows that don't start with ||. As a workaround, it should be possible to emit '||' from the template instead. I'll file a bug for our table row tokenization bug.",task_subcomment,"['QUOTE\nQUOTE\n\nWe are tokenizing templates and content separately so that we can cut template vs. non-template content on a token level.', ""Attribute keys and values can also be templated, but we don't support templates producing several attributes and parts of a token."", 'This and the need to infer resulting DOM structures affected by template-produced tokens already adds a lot of complexity, but at least the results can somewhat sanely be represented in DOM.', ""Having 1/3 of a DOM element's start tag be generated by page source and 2/3 templated on some arbitrary boundary would be a nightmare to represent in DOM and even worse in a UI."", 'You are right though that we *could* in theory represent something like |{{singlechart|..}} as a special case of a multi-part templated construct.', 'This would run counter to our desire to move towards self-contained templates though that are easier to edit both in wikitext and the VE.', 'Removing the pipes in the page and returning the full table row from singlechart would be better in that regard.', ""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIndeed, it seems that we don't recognize single-line rows that don't start with ||."", ""As a workaround, it should be possible to emit '||' from the template instead."", ""I'll file a bug for our table row tokenization bug.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+248227,Templates that create multiple table cells don't work,"**kwwilliams** wrote:
+
+As a help: there are only a few dozen templates that do things like this. I would have no problem at all adding something in the TemplateData that gave VE a clue as to what was going on, like
+
+ ""table"":
+  {
+    ""cells"": 2,
+    ""rowheader"": ""true"",
+  }",task_subcomment,"['**kwwilliams** wrote:\n\nAs a help: there are only a few dozen templates that do things like this.', 'I would have no problem at all adding something in the TemplateData that gave VE a clue as to what was going on, like\n\n ""table"":\n  {\n    ""cells"": 2,\n    ""rowheader"": ""true"",\n  }']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+248220,Templates that create multiple table cells don't work,"**kwwilliams** wrote:
+
+Hadn't noticed the leading | character. That is wrong, albeit harmless in most cases (if someone set rowheader=true, it would be a visible error). I removed all of those in a bot run before, and it looks like it's time to do it again.
+
+Removing the pipe doesn't quite work, though: take a peek at http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?veaction=edit vs. http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29 and notice how the manual entries and the templated entries align in the normal view but scramble in the edit view.
+
+You really need to be parsing *after* template expansion and tracking all the text that the templates generate. That template should display as the chart and reference in the first column followed by a position in the second column, because that's what the wikitext the template generates says to do. Once the editor tries to edit any of those fields, the editor should be taken to the template editor. Displaying the output as a doublespaced item without any table boundaries that doesn't align with other entries is not the right answer to this problem.",task_subcomment,"[""**kwwilliams** wrote:\n\nHadn't noticed the leading | character."", 'That is wrong, albeit harmless in most cases (if someone set rowheader=true, it would be a visible error).', ""I removed all of those in a bot run before, and it looks like it's time to do it again."", ""Removing the pipe doesn't quite work, though: take a peek at URL vs. URL and notice how the manual entries and the templated entries align in the normal view but scramble in the edit view."", 'You really need to be parsing *after* template expansion and tracking all the text that the templates generate.', ""That template should display as the chart and reference in the first column followed by a position in the second column, because that's what the wikitext the template generates says to do."", 'Once the editor tries to edit any of those fields, the editor should be taken to the template editor.', ""Displaying the output as a doublespaced item without any table boundaries that doesn't align with other entries is not the right answer to this problem.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+248214,Templates that create multiple table cells don't work,and Parsoid. ;),task_subcomment,"['and Parsoid.', ';)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+248209,Templates that create multiple table cells don't work,"An example from  http://en.wikipedia.org/wiki/5_O%27Clock_%28T-Pain_song%29:
+
+|{{singlechart|Australia|29|artist=T-Pain feat. Wiz Khalifa & Lily Allen|song=5 O'Clock}}
+
+The issue here is that there is a pipe in the page source while another pipe is emitted by Singlechart. If the pipe in the page source is removed this will work in both the PHP parser and .",task_subcomment,"['An example from  URL\n\n|{{singlechart|Australia|29|artist=T-Pain feat.', ""Wiz Khalifa & Lily Allen|song=5 O'Clock}}\n\nThe issue here is that there is a pipe in the page source while another pipe is emitted by Singlechart."", 'If the pipe in the page source is removed this will work in both the PHP parser and .']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+248204,Templates that create multiple table cells don't work,My apologies for assuming that these two issues were related. Re-titling.,task_subcomment,"['My apologies for assuming that these two issues were related.', 'Re-titling.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+248196,Templates that create multiple table cells don't work,"**kwwilliams** wrote:
+
+""This can be fixed by avoiding 2""? How exactly is the template supposed to generate a row header and two table cells while ""avoiding 2)""?",task_subcomment,"['**kwwilliams** wrote:\n\n""This can be fixed by avoiding 2""?', 'How exactly is the template supposed to generate a row header and two table cells while ""avoiding 2)""?']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+248191,Templates that create multiple table cells don't work,"The problem here is 2), the extra | generated by Singlechart. The PHP parser flattens everything to a string, so it will eventually see '\n||' with one of those pipes generated by 2) and the other from 1). Parsoid on the other hand needs to keep track of where things came from, so sees those pipes as two td tags.
+
+This can be fixed by avoiding 2).",task_subcomment,"['The problem here is 2), the extra | generated by Singlechart.', ""The PHP parser flattens everything to a string, so it will eventually see '\\n||' with one of those pipes generated by 2) and the other from 1)."", 'Parsoid on the other hand needs to keep track of where things came from, so sees those pipes as two td tags.', 'This can be fixed by avoiding 2).']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+248189,Templates that create multiple table cells don't work,"This is the same as bug 50366 - merging with that one.
+
+*** This bug has been marked as a duplicate of bug 50366 ***",task_subcomment,"['This is the same as bug 50366 - merging with that one.', '*** This bug has been marked as a duplicate of bug 50366 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52577,VisualEditor: Reconsider CSS content munging,"As per http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Coords_not_displayed_in_title_when_open_in_VE , the coordinates move at the bottom of the page, where one is not expecting to find them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"['VisualEditor: Reconsider CSS content munging\n\nAs per URL , the coordinates move at the bottom of the page, where one is not expecting to find them.', '--------------------------\n**Version**: unspecified\n**Severity**: major']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+446997,VisualEditor: Reconsider CSS content munging,"Indeed we did, this was done by the invaluable Ed in ee5b69772963c5d3f17b15742023cf33fc5dd48a.",task_subcomment,"['Indeed we did, this was done by the invaluable Ed in ee5b69772963c5d3f17b15742023cf33fc5dd48a.']",['SOLUTION DISCUSSION']
+446011,VisualEditor: Reconsider CSS content munging,"Dunno what happened here, but all three of the subtasks seem to no longer be a problem. Did we kill this?",task_subcomment,"['Dunno what happened here, but all three of the subtasks seem to no longer be a problem.', 'Did we kill this?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247630,VisualEditor: Reconsider CSS content munging,"CSS content munging in general is a real pain, and we should find a way around it.",task_subcomment,"['CSS content munging in general is a real pain, and we should find a way around it.']",['SOLUTION DISCUSSION']
+52549,VisualEditor: round-trip adjacent and nested annotations,"VisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, http://en.wikipedia.org/w/index.php?title=Bose%E2%80%93Einstein_condensate&diff=prev&oldid=562481552).
+
+Both will lead to a DOM diff and thus likely to a dirty wikitext diff.
+
+Note that this only applies to existing content- merging identical annotations in new content is fine.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: round-trip adjacent and nested annotations\n\nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations.', 'Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, URL\n\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff.', 'Note that this only applies to existing content- merging identical annotations in new content is fine.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+246146,VisualEditor: round-trip adjacent and nested annotations,This has been fixed for some time in the DM. Marking as such.,task_subcomment,"['This has been fixed for some time in the DM.', 'Marking as such.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+246142,VisualEditor: round-trip adjacent and nested annotations,"Also, don't cut annotations. This is what I suspect happened here:
+http://en.wikipedia.org/w/index.php?title=List_of_Mystery_Science_Theater_3000_episodes&diff=prev&oldid=562488147",task_subcomment,"[""Also, don't cut annotations."", 'This is what I suspect happened here:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52539,./ still appearing in links.,"See https://en.wikipedia.org/w/index.php?title=Russkaya_Mysl&curid=38914039&diff=562427330&oldid=555891306
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50720",task_description,"['./ still appearing in links.', 'See URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245337,./ still appearing in links.,"
+
+*** This bug has been marked as a duplicate of bug 50720 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50720 ***'],['ISSUE CONTENT MANAGEMENT']
+245329,./ still appearing in links.,"Still getting this occurring. Examples
+
+
+https://en.wikipedia.org/w/index.php?title=Austropotamobius_pallipes&curid=3945333&diff=562783871&oldid=545518009
+https://en.wikipedia.org/w/index.php?title=Ron_Davies_(songwriter)&curid=31118393&diff=562723238&oldid=553701771
+https://en.wikipedia.org/w/index.php?title=Sibling_relationship&curid=22409572&diff=562636237&oldid=561958868
+https://en.wikipedia.org/w/index.php?title=Double_Rainbow_(viral_video)&curid=28129724&diff=562626607&oldid=560477885
+https://en.wikipedia.org/w/index.php?title=Roger_Mompesson&curid=39389398&diff=562625481&oldid=560045122
+(also changed a category link)",task_subcomment,"['Still getting this occurring.', 'Examples\n\n\nURL\nURL\nURL\nURL\nURL\n(also changed a category link)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+245319,./ still appearing in links.,The visualeditor-needcheck tag also suggests that there was an issue in VE round-tripping. Reassigning to VE for investigation.,task_subcomment,"['The visualeditor-needcheck tag also suggests that there was an issue in VE round-tripping.', 'Reassigning to VE for investigation.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+245312,./ still appearing in links.,"Roan has not been able to reproduce this with VE, and parsoid.wmflabs.org/_rt/en/Russkaya_Mysl?oldid=555891306 does not show this issue either.
+
+Maybe bug 50428 is related?",task_subcomment,"['Roan has not been able to reproduce this with VE, and parsoid.wmflabs.org/_rt/en/Russkaya_Mysl?oldid=555891306 does not show this issue either.', 'Maybe bug 50428 is related?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52526,VisualEditor: Permit removal of parent template while retaining subtemplate,"English Wikipedia editor notes that sometimes when parent templates are removed, a subtemplate (or two) should remain, such as with Template:Multiple issues (http://en.wikipedia.org/wiki/Template:Multiple_issues). It would be a nice feature to allow the parent cat to be removed without removing all parameter, or permitting them to be ""escalated"" into templates themselves.
+
+Realizing this is not likely to be a high priority, given more urgent issues, just putting in the request. :)
+
+See
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562454889#Can.27t_unwrap_template_within_template
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Permit removal of parent template while retaining subtemplate\n\nEnglish Wikipedia editor notes that sometimes when parent templates are removed, a subtemplate (or two) should remain, such as with Template:Multiple issues (URL It would be a nice feature to allow the parent cat to be removed without removing all parameter, or permitting them to be ""escalated"" into templates themselves.', 'Realizing this is not likely to be a high priority, given more urgent issues, just putting in the request.', ':)\n\nSee\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+52514,Complete and document VisualEditor's integration and plugin system,"We need an integration and plugin system for VisualEditor, both for extra tools (e.g. ""YouTube video node handler"") and tool over-rides (e.g. ""MediaWiki-specific H3 handler""), as well as a more generalised system to do init and integration.
+
+Enjoy.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""Complete and document VisualEditor's integration and plugin system\n\nWe need an integration and plugin system for VisualEditor, both for extra tools (e.g."", '""YouTube video node handler"") and tool over-rides (e.g.', '""MediaWiki-specific H3 handler""), as well as a more generalised system to do init and integration.', 'Enjoy.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243758,Complete and document VisualEditor's integration and plugin system,"At this point, closing this bug is blocked on some reasonable documentation being available. Third parties that want to try to implement things and report what's missing functionality (or more likely, unclear because there's no documentation) would be very welcome. :-)",task_subcomment,"['At this point, closing this bug is blocked on some reasonable documentation being available.', ""Third parties that want to try to implement things and report what's missing functionality (or more likely, unclear because there's no documentation) would be very welcome."", ':-)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243752,Complete and document VisualEditor's integration and plugin system,"Change 75271 merged by jenkins-bot:
+Infrastructure for loading plugins in the MW integration
+
+https://gerrit.wikimedia.org/r/75271",task_subcomment,['Change 75271 merged by jenkins-bot:\nInfrastructure for loading plugins in the MW integration\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+243744,Complete and document VisualEditor's integration and plugin system,"Change 75271 had a related patch set uploaded by Catrope:
+Infrastructure for loading plugins in the MW integration
+
+https://gerrit.wikimedia.org/r/75271",task_subcomment,['Change 75271 had a related patch set uploaded by Catrope:\nInfrastructure for loading plugins in the MW integration\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+52508,VisualEditor: Close icon shown at 2x size and so truncated,"Screenshot
+
+See screenshot - monobook, windows 7, firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11469}",task_description,"['VisualEditor: Close icon shown at 2x size and so truncated\n\nScreenshot\n\nSee screenshot - monobook, windows 7, firefox 22.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11469}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243405,VisualEditor: Close icon shown at 2x size and so truncated,"I'm going to close this as a one-off appearance of HiDPI icons for a user - if it's repeated, please re-open.",task_subcomment,"[""I'm going to close this as a one-off appearance of HiDPI icons for a user - if it's repeated, please re-open.""]",['ACTION ON ISSUE']
+52505,VisualEditor: Share ref / references re-rendering code with Parsoid,">>! In T52505#562403, @GWicke wrote:
+> We have a relatively complete DOM-based references rendering implementation in Parsoid that could be reused by VisualEditor. This would avoid us implementing two versions of essentially the same code, and with combined effort should result in a better implementation.
+
+--------------------------
+
+**See Also**:
+{T52474}",task_description,['VisualEditor: Share ref / references re-rendering code with Parsoid\n\nQUOTE\nQUOTE\n\n--------------------------\n\n**See Also**:\n{T52474}'],['MOTIVATION']
+1424138,VisualEditor: Share ref / references re-rendering code with Parsoid,">>! In T52505#5795834, @Izno wrote:
+> Is this exact task still going to happen given PHP Parsoid? (One system being Javascript and the other PHP now.)
+
+Sadly, no.",task_subcomment,"['QUOTE\nQUOTE\n\nSadly, no.']",['INVESTIGATION AND EXPLORATION']
+1423582,VisualEditor: Share ref / references re-rendering code with Parsoid,Is this exact task still going to happen given PHP Parsoid? (One system being Javascript and the other PHP now.),task_subcomment,"['Is this exact task still going to happen given PHP Parsoid?', '(One system being Javascript and the other PHP now.)']","['FUTURE PLAN', 'INVESTIGATION AND EXPLORATION']"
+243298,VisualEditor: Share ref / references re-rendering code with Parsoid,"Indeed, basically the logic we currently have (or call from) ve.ce.MWReferenceListNode and ve.ce.MWReferenceNode. Converting data-mw into a the dom as it should be given to the browser (html tag name, class name, children composition and attributes etc.). And for ref nodes the sequence between different ones as well. Though VE may have to run the logic more often (where parsoid presumably only runs it once per document) it'd be nice to share this logic.
+
+The HTML rendered by MediaWiki extension tags and/or parser functions should not be hardcoded in VE. Perhaps in a VE plugin, but since it'd be the same for Parsoid as for VE, it'd be nice if this can be shared so that a MediaWiki extension that wants to have logic for Parsoid/VE only needs 1 type of plugin that both can use.",task_subcomment,"['Indeed, basically the logic we currently have (or call from) ve.ce.MWReferenceListNode and ve.ce.MWReferenceNode.', 'Converting data-mw into a the dom as it should be given to the browser (html tag name, class name, children composition and attributes etc.).', 'And for ref nodes the sequence between different ones as well.', ""Though VE may have to run the logic more often (where parsoid presumably only runs it once per document) it'd be nice to share this logic."", 'The HTML rendered by MediaWiki extension tags and/or parser functions should not be hardcoded in VE.', ""Perhaps in a VE plugin, but since it'd be the same for Parsoid as for VE, it'd be nice if this can be shared so that a MediaWiki extension that wants to have logic for Parsoid/VE only needs 1 type of plugin that both can use.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243291,VisualEditor: Share ref / references re-rendering code with Parsoid,I would not recommend to hack something around the numbering we give you. We should rather share the ref / references rendering code so that you can simply call that code to fully renumber refs and re-render the references blocks.,task_subcomment,"['I would not recommend to hack something around the numbering we give you.', 'We should rather share the ref / references rendering code so that you can simply call that code to fully renumber refs and re-render the references blocks.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+243285,VisualEditor: Share ref / references re-rendering code with Parsoid,"Parsoid gives us a DOM with references already numbered, so we probably want to use their numbering and reference list as a base, then update that as required.",task_subcomment,"['Parsoid gives us a DOM with references already numbered, so we probably want to use their numbering and reference list as a base, then update that as required.']",['SOLUTION DISCUSSION']
+243276,VisualEditor: Share ref / references re-rendering code with Parsoid,"Possibly also relevant for bug 50474, in case that turns out to be hard to fix in your current implementation.",task_subcomment,"['Possibly also relevant for bug 50474, in case that turns out to be hard to fix in your current implementation.']",['INVESTIGATION AND EXPLORATION']
+243268,VisualEditor: Share ref / references re-rendering code with Parsoid,"Sorry, somehow managed to hit return.
+
+We have a relatively complete DOM-based references rendering implementation in Parsoid that could be reused by VisualEditor. This would avoid us implementing two versions of essentially the same code, and with combined effort should result in a better implementation.",task_subcomment,"['Sorry, somehow managed to hit return.', 'We have a relatively complete DOM-based references rendering implementation in Parsoid that could be reused by VisualEditor.', 'This would avoid us implementing two versions of essentially the same code, and with combined effort should result in a better implementation.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52490,VisualEditor: Link input widget is not oriented for RTL,"A very simple mockup that I made in GIMP to show how it is supposed to look
+
+VisualEditor: Link inspector is not oriented for RTL.
+
+The arrow icon is supposed to point to the right, and be placed in the right corner, separated by a vertical line.
+
+The title is supposed to be aligned to the right.
+
+The chain icon is supposed to be next to the title on its left side.
+
+The trash bin is supposed to be in the left corner.
+
+See the attached file for a very simple mock-up of how it is supposed to look (it is off by a few pixels here and there - I'm not much of a graphic designer).
+
+This bug is similar to bug 49613.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+//attachment link-inspector-rtl.png ignored as obsolete//",task_description,"['VisualEditor: Link input widget is not oriented for RTL\n\nA very simple mockup that I made in GIMP to show how it is supposed to look\n\nVisualEditor: Link inspector is not oriented for RTL.', 'The arrow icon is supposed to point to the right, and be placed in the right corner, separated by a vertical line.', 'The title is supposed to be aligned to the right.', 'The chain icon is supposed to be next to the title on its left side.', 'The trash bin is supposed to be in the left corner.', ""See the attached file for a very simple mock-up of how it is supposed to look (it is off by a few pixels here and there - I'm not much of a graphic designer)."", 'This bug is similar to bug 49613.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n//attachment link-inspector-rtl.png ignored as obsolete//']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242468,VisualEditor: Link input widget is not oriented for RTL,The current layout is good. There's a mistake in my image. Marking as FIXED.,task_subcomment,"['The current layout is good.', ""There's a mistake in my image."", 'Marking as FIXED.']","['EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']"
+242463,VisualEditor: Link input widget is not oriented for RTL,"En layout is currently:
+
+< (chain icon) 'Hyperlink'    (trash icon)
+
+He layout is currently:
+
+(trash icon)     '(Hyperlink in Hebrew)' (chain icon) >
+
+This is not quite Amir's design attached:
+
+(trash icon)     (chain icon) '(Hyperlink in Hebrew)' >",task_subcomment,"[""En layout is currently:\n\n< (chain icon) 'Hyperlink'    (trash icon)\n\nHe layout is currently:\n\n(trash icon)     '(Hyperlink in Hebrew)' (chain icon) >\n\nThis is not quite Amir's design attached:\n\n(trash icon)     (chain icon) '(Hyperlink in Hebrew)' >""]",['INVESTIGATION AND EXPLORATION']
+242457,VisualEditor: Link input widget is not oriented for RTL,"Change 72056 abandoned by Mooeypoo:
+Layout fix for Link Surface in RTL
+
+Reason:
+This was fixed in another (much more massive) gerrit fix that was merged. Works in master.
+
+https://gerrit.wikimedia.org/r/72056",task_subcomment,"['Change 72056 abandoned by Mooeypoo:\nLayout fix for Link Surface in RTL\n\nReason:\nThis was fixed in another (much more massive) gerrit fix that was merged.', 'Works in master.', 'GERRIT_URL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+242450,VisualEditor: Link input widget is not oriented for RTL,"Change 72056 had a related patch set uploaded by Mooeypoo:
+Layout fix for Link Surface in RTL
+
+https://gerrit.wikimedia.org/r/72056",task_subcomment,['Change 72056 had a related patch set uploaded by Mooeypoo:\nLayout fix for Link Surface in RTL\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+242444,VisualEditor: Link input widget is not oriented for RTL,"This depends on the Frame rtl fix, which will add directionality inside frames, and allow for conditional flips (and/or also allow CSSJanus to eventually work inside the frames)
+
+I took a look at the code, the flip itself is relatively easy, but I am missing the ve-rtl/ve-ltr classes that would be there after the frame fix.",task_subcomment,"['This depends on the Frame rtl fix, which will add directionality inside frames, and allow for conditional flips (and/or also allow CSSJanus to eventually work inside the frames)\n\nI took a look at the code, the flip itself is relatively easy, but I am missing the ve-rtl/ve-ltr classes that would be there after the frame fix.']",['INVESTIGATION AND EXPLORATION']
+242438,VisualEditor: Link input widget is not oriented for RTL,"Created attachment 12713
+A simple mockup that I made in GIMP to show how it is supposed to look
+
+The V icon in the menu is supposed to be moved to the right side, too.
+
+Updated screenshot.
+
+**Attached**: {F11431}",task_subcomment,"['Created attachment 12713\nA simple mockup that I made in GIMP to show how it is supposed to look\n\nThe V icon in the menu is supposed to be moved to the right side, too.', 'Updated screenshot.', '**Attached**: {F11431}']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52481,"VisualEditor:  created, and meta-data removed, from [[Bahá'u'lláh]] on edit","https://en.wikipedia.org/w/index.php?title=Bah%C3%A1%27u%27ll%C3%A1h&diff=562302216&oldid=561967071 - finding out browser/OS now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor:  created, and meta-data removed, from [[Bahá'u'lláh]] on edit\n\nURL - finding out browser/OS now."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241956,"VisualEditor:  created, and meta-data removed, from [[Bahá'u'lláh]] on edit","Do we know how this was caused, how to reproduce the issue, if VE was even responsible for it (rather than Parsoid), or if it's since been fixed?",task_subcomment,"[""Do we know how this was caused, how to reproduce the issue, if VE was even responsible for it (rather than Parsoid), or if it's since been fixed?""]",['OBSERVED BUG BEHAVIOR']
+241952,"VisualEditor:  created, and meta-data removed, from [[Bahá'u'lláh]] on edit","It's Windows 7, Firefox 21.0; I attempted to make a similar edit to the article using Chrome and received a message that said, ""Warning: Your edit may have been corrupted – please review before saving."" I've asked at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Addition_of_.3Cu.3E.3C.2Fu.3E.3Cu.3E.3C.2Fu.3E_and_removal_of_categories. if he sees it, too.",task_subcomment,"['It\'s Windows 7, Firefox 21.0; I attempted to make a similar edit to the article using Chrome and received a message that said, ""Warning: Your edit may have been corrupted – please review before saving.""', ""I've asked at URL if he sees it, too.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52475,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"Trying to ""Edit"" on http://en.wikipedia.org/wiki/List_of_Advanced_Dungeons_%26_Dragons_2nd_edition_monsters after a minute or so results in a popup ""Error loading data from server: error. Would you like to retry?"". Trying again, repeats the issue
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39057",task_description,"['VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504)\n\nTrying to ""Edit"" on URL after a minute or so results in a popup ""Error loading data from server: error.', 'Would you like to retry?"".', 'Trying again, repeats the issue\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+241657,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"Change 118398 merged by jenkins-bot:
+More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504)
+
+https://gerrit.wikimedia.org/r/118398",task_subcomment,['Change 118398 merged by jenkins-bot:\nMore gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241651,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"Change 118398 had a related patch set uploaded by Alex Monk:
+More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504)
+
+https://gerrit.wikimedia.org/r/118398",task_subcomment,['Change 118398 had a related patch set uploaded by Alex Monk:\nMore gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+241646,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"(In reply to James Forrester from comment #4)
+> Possibily we could, instead of giving the user the error code, we could have
+> a pop-up saying ""It looks like editor is currently unavailable; would you
+> like to edit in source mode instead?"" with an OK that takes you to
+> action=edit and a cancel that returns you to action=view? Maybe for
+> error-tracking purposes we could add Parsoid returned 504 or
+> Parsoid not available after the general call-to-action?
+
+Basically done this after checking with Roan about how to reproduce this error, without the small text underneath. Confirm dialogs don't allow you to use HTML markup.",task_subcomment,"['(In reply to James Forrester from comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBasically done this after checking with Roan about how to reproduce this error, without the small text underneath.', ""Confirm dialogs don't allow you to use HTML markup.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+241643,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),We'll help. :-),task_subcomment,"[""We'll help."", ':-)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+241640,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),(resetting assignee - I had issues trying to properly reproduce Parsoid timeouts like this on my machine),task_subcomment,['(resetting assignee - I had issues trying to properly reproduce Parsoid timeouts like this on my machine)'],['OBSERVED BUG BEHAVIOR']
+241638,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"I'm pulling this from being a blocker to bug 50848, given the reduced impact now that it works on the second try.",task_subcomment,"[""I'm pulling this from being a blocker to bug 50848, given the reduced impact now that it works on the second try.""]",['BUG REPRODUCTION']
+241636,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"VE currently sets a 100s timeout, but in practice we often don't get there because the nginx proxies that terminate HTTPS and IPv6 traffic have a 60s timeout.",task_subcomment,"[""VE currently sets a 100s timeout, but in practice we often don't get there because the nginx proxies that terminate HTTPS and IPv6 traffic have a 60s timeout.""]",['OBSERVED BUG BEHAVIOR']
+241632,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"(In reply to comment #5)
+> Previewing that page also works in about 30 seconds.
+
+Actually closer to 70 on re-test.",task_subcomment,['(In reply to comment #5)\nQUOTE\n\nActually closer to 70 on re-test.'],['OBSERVED BUG BEHAVIOR']
+241627,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"After upping the Varnish backend timeout to 5 minutes http://en.wikipedia.org/wiki/List_of_Advanced_Dungeons_%26_Dragons_2nd_edition_monsters?veaction=edit works now despite timing out in VE once. Hitting 'retry' re-joins the ongoing render, and returns the page pretty quickly. Previewing that page also works in about 30 seconds.
+
+You might want to tweak your timeouts / UI to reflect this change. As long as there is no timout from Varnish the render is still ongoing.
+
+More testing is needed with even larger pages. Bug 51053 will be closed when that is done.",task_subcomment,"['After upping the Varnish backend timeout to 5 minutes URL works now despite timing out in VE once.', ""Hitting 'retry' re-joins the ongoing render, and returns the page pretty quickly."", 'Previewing that page also works in about 30 seconds.', 'You might want to tweak your timeouts / UI to reflect this change.', 'As long as there is no timout from Varnish the render is still ongoing.', 'More testing is needed with even larger pages.', 'Bug 51053 will be closed when that is done.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+241623,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"Possibily we could, instead of giving the user the error code, we could have a pop-up saying ""It looks like editor is currently unavailable; would you like to edit in source mode instead?"" with an OK that takes you to action=edit and a cancel that returns you to action=view? Maybe for error-tracking purposes we could add Parsoid returned 504 or Parsoid not available after the general call-to-action?",task_subcomment,"['Possibily we could, instead of giving the user the error code, we could have a pop-up saying ""It looks like editor is currently unavailable; would you like to edit in source mode instead?""', 'with an OK that takes you to action=edit and a cancel that returns you to action=view?', 'Maybe for error-tracking purposes we could add Parsoid returned 504 or Parsoid not available after the general call-to-action?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+241619,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),Looks like the timeout here is on the Varnish/Parsoid side (API request on edit fails with error 504 after 60 secs).,task_subcomment,['Looks like the timeout here is on the Varnish/Parsoid side (API request on edit fails with error 504 after 60 secs).'],['OBSERVED BUG BEHAVIOR']
+241613,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),"Re: timeouts, need to be either handled more gracefully or we'll need to VE-blacklist articles where it occurs for now.",task_subcomment,"[""Re: timeouts, need to be either handled more gracefully or we'll need to VE-blacklist articles where it occurs for now.""]",['BUG REPRODUCTION']
+241606,VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),I think this is probably related - editing on large pages such as California is considerably slower when using VE than it is using the old editor. A contributor complained of slowness with this edit (http://en.wikipedia.org/w/index.php?title=California&diff=562339624&oldid=562339237) and I found the same issue with mine (http://en.wikipedia.org/w/index.php?title=California&diff=562390635&oldid=562351322),task_subcomment,"['I think this is probably related - editing on large pages such as California is considerably slower when using VE than it is using the old editor.', 'A contributor complained of slowness with this edit (URL and I found the same issue with mine (URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52474,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","References added by templates are currently not very well integrated into the #visualeditor UI. Their footnotes are visible as #parsoid parsed output on the surface, but:
+
+1. the number in square brackets on the footnote does not necessarily fit with other numbers visible from other footnotes
+2. they do not appear in the reference lists in the editor
+3. they do not appear in the list of references to re-use
+
+A simple demonstration of the first two issues can be seen here:
+
+| Reading | VisualEditor |
+| {F56437741} | {F56437750} |
+
+-----------------------------------
+
+For example, look at [[https://en.wikipedia.org/w/index.php?title=Popocatépetl&oldid=667057679|this old version of w:en:Popocatépetl]]. It has 21 references, 3 of them in the infobox only. When you [[https://en.wikipedia.org/w/index.php?title=Popocat%C3%A9petl&oldid=667057679&veaction=edit|open it in VE]], those first 3 cannot be accessed from the re-use menu. In addition, all 21 appear in the references list, but each reference x in the text corresponds to entry x + 3 in the references list. 
+
+**See Also**:
+{T52505}
+{T53289}
+{T54398}
+{T55777}
+{T54262}
+
+Possible duplicate but might have additional implications: 
+{T87134}",task_description,"['In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.', 'References added by templates are currently not very well integrated into the #visualeditor UI.', 'Their footnotes are visible as #parsoid parsed output on the surface, but:\n\n1. the number in square brackets on the footnote does not necessarily fit with other numbers visible from other footnotes\n2. they do not appear in the reference lists in the editor\n3. they do not appear in the list of references to re-use\n\nA simple demonstration of the first two issues can be seen here:\n\n| Reading | VisualEditor |\n| {F56437741} | {F56437750} |\n\n-----------------------------------\n\nFor example, look at [[URL old version of w:en:Popocatépetl]].', 'It has 21 references, 3 of them in the infobox only.', 'When you [[URL it in VE]], those first 3 cannot be accessed from the re-use menu.', 'In addition, all 21 appear in the references list, but each reference x in the text corresponds to entry x + 3 in the references list.', '**See Also**:\n{T52505}\n{T53289}\n{T54398}\n{T55777}\n{T54262}\n\nPossible duplicate but might have additional implications: \n{T87134}']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'MOTIVATION', 'BUG REPRODUCTION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+2378204,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","I took the freedom to summarize the overall problems surfacing in this task. I guess it makes sense to try to solve the first two issues described so it's less confusing for the users.
+
+The third options seems not so straight forward at the moment. Templates of any kind can include a references and it would be unclear on how a re-use should look like or even how a reference transcluded from a template can get a name that's needed for the re-use.",task_subcomment,"['I took the freedom to summarize the overall problems surfacing in this task.', ""I guess it makes sense to try to solve the first two issues described so it's less confusing for the users."", 'The third options seems not so straight forward at the moment.', ""Templates of any kind can include a references and it would be unclear on how a re-use should look like or even how a reference transcluded from a template can get a name that's needed for the re-use.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1068586,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",Solving this (and its subtasks) would be a huge success. I'd be grateful.,task_subcomment,"['Solving this (and its subtasks) would be a huge success.', ""I'd be grateful.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+759604,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",">>! In T52474#1772377, @Halibutt wrote:
+> Since T114105 was merged into this ticket
+
+In case anyone following that original ticket (or several like it) is confused about why these get merged here: 
+
+VisualEditor handles regular ""Harvard"" (parenthetical) citations perfectly; see true Harvard style at https://en.wikipedia.org/w/index.php?oldid=521737742&veaction=edit as an example.   Plain Harvard is just plain text, after all; a proper Harvard citation is just `(Author Date)` with an optional page number.  Any system that lets you type common characters can handle plain Harvard citations.
+
+The problem is when it's not truly Harvard citations, but instead it's a non-Harvard [[https://en.wikipedia.org/wiki/Wikipedia:Citing_sources#Short_citations|short citation]] wrapped up in ref tags using a template such as {{sfn}} – when the system is presented with `{{sfn|Author|Date|123}}` instead of  `Author Date, page 123.` (which VisualEditor can handle) or `(Author Date, page 123)` (which VisualEditor can also handle). 
+
+In that case, the main technical issue is exactly the same as `{{infobox|field=dataSource}}`:  the ref is stuck in a transclusion rather than in the article being edited.  This has multiple effects, including impossible numbering and bad displays (because the transcluded doc gets its own  list; see T114105 for a screenshot).  As I understand it, some of these problems will be solved here, and others may be fixed through other mechanisms, e.g., {T110909}.  But the bugs get merged here, because it's not possible to merge them to multiple related tasks.
+",task_subcomment,"['QUOTE\nQUOTE\n\nIn case anyone following that original ticket (or several like it) is confused about why these get merged here: \n\nVisualEditor handles regular ""Harvard"" (parenthetical) citations perfectly; see true Harvard style at URL as an example.', 'Plain Harvard is just plain text, after all; a proper Harvard citation is just CODE with an optional page number.', 'Any system that lets you type common characters can handle plain Harvard citations.', ""The problem is when it's not truly Harvard citations, but instead it's a non-Harvard [[URL citation]] wrapped up in ref tags using a template such as {{sfn}} –\xa0when the system is presented with CODE instead of  CODE (which VisualEditor can handle) or CODE (which VisualEditor can also handle)."", 'In that case, the main technical issue is exactly the same as CODE:  the ref is stuck in a transclusion rather than in the article being edited.', 'This has multiple effects, including impossible numbering and bad displays (because the transcluded doc gets its own  list; see T114105 for a screenshot).', 'As I understand it, some of these problems will be solved here, and others may be fixed through other mechanisms, e.g., {T110909}.', ""But the bugs get merged here, because it's not possible to merge them to multiple related tasks.""]","['WORKAROUNDS', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'POTENTIAL NEW ISSUES AND REQUESTS']"
+556154,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Since T114105 was merged into this ticket, is there anything I could do to help solve this issue? ",task_subcomment,"['Since T114105 was merged into this ticket, is there anything I could do to help solve this issue?']",['SOLUTION DISCUSSION']
+556153,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Just a friendly reminder, that while T114105 was merged into this ticket, it has nothing to do with it. Nothing to do with ref numbering or with ref accessibility from the re-use menu. Actually, it's more about how VE displays templates as such, not how it handles references. See the attached screenshot to see what I'm talking about.
+
+But since it was merged here, is there anything I could do to help solve this issue? ",task_subcomment,"['Just a friendly reminder, that while T114105 was merged into this ticket, it has nothing to do with it.', 'Nothing to do with ref numbering or with ref accessibility from the re-use menu.', ""Actually, it's more about how VE displays templates as such, not how it handles references."", ""See the attached screenshot to see what I'm talking about."", 'But since it was merged here, is there anything I could do to help solve this issue?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'CONTRIBUTION AND COMMITMENT']"
+556151,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Just a friendly reminder, that while T114105 was merged into this ticket, it has nothing to do with it. Nothing to do with ref numbering or with ref accessibility from the re-use menu. Actually, it's more about how VE displays templates as such, not how it handles references. 
+
+But since it was merged here, is there anything I could do to help solve this issue? ",task_subcomment,"['Just a friendly reminder, that while T114105 was merged into this ticket, it has nothing to do with it.', 'Nothing to do with ref numbering or with ref accessibility from the re-use menu.', ""Actually, it's more about how VE displays templates as such, not how it handles references."", 'But since it was merged here, is there anything I could do to help solve this issue?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'CONTRIBUTION AND COMMITMENT']"
+516775,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",This information is already shown in context and the reference list. If we change the numbering that will probably be more confusing.,task_subcomment,"['This information is already shown in context and the reference list.', 'If we change the numbering that will probably be more confusing.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+516762,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","As a stop-gap measure, is it feasible to have the footnotes that are contained in templates (and therefore not ""in"" the document) be displayed differently?  You would get the usual [1] for whatever is the first footnote in the article body, but the first one in an infobox would be marked as [X] or [Template 1] or something that doesn't match the typical ones. ",task_subcomment,"['As a stop-gap measure, is it feasible to have the footnotes that are contained in templates (and therefore not ""in"" the document) be displayed differently?', ""You would get the usual [1] for whatever is the first footnote in the article body, but the first one in an infobox would be marked as [X] or [Template 1] or something that doesn't match the typical ones.""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+454943,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","In the weekly triage meeting on 2015-05-06, we discussed this task. Though we acknowledge that this is moderately confusing for users, fixing this is a very large piece of work (which reflects why it has not been completed in the past two years either). I've marked this as blocked by a piece of work that we hope to finish out this quarter, which will hopefully help make this slightly less epic to fix.",task_subcomment,"['In the weekly triage meeting on 2015-05-06, we discussed this task.', 'Though we acknowledge that this is moderately confusing for users, fixing this is a very large piece of work (which reflects why it has not been completed in the past two years either).', ""I've marked this as blocked by a piece of work that we hope to finish out this quarter, which will hopefully help make this slightly less epic to fix.""]","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+450272,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","See [[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Citation_numbers_messing_up | en-Wiki feedback ""Citation numbers messing up""]]. This problem is repeatedly mentioned on en-Wiki, confuses editors and hinders editing of developed articles with complex reference structures. I would like to propose the whole issue with ""references in templates"" and ""references generated by templates"" as blocker. I am aware, that 5 other tasks are possible related to this problem (See also), maybe the whole topic area needs another fresh look for a solution. - the problem is known for almost 2 years now, and should get a higher priority and more frequent updates on its status.",task_subcomment,"['See [[URL | en-Wiki feedback ""Citation numbers messing up""]].', 'This problem is repeatedly mentioned on en-Wiki, confuses editors and hinders editing of developed articles with complex reference structures.', 'I would like to propose the whole issue with ""references in templates"" and ""references generated by templates"" as blocker.', 'I am aware, that 5 other tasks are possible related to this problem (See also), maybe the whole topic area needs another fresh look for a solution.', '- the problem is known for almost 2 years now, and should get a higher priority and more frequent updates on its status.']","['URL | en-Wiki feedback ""Citation numbers messing up""', 'BUG REPRODUCTION', 'FUTURE PLAN', 'FUTURE PLAN', 'FUTURE PLAN']"
+399306,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","It doesn't seem to have been mentioned above that this bug can cause the loss of a citation, which might affect the severity or priority.  If you have a ref inside a group note (e.g. inside a tag) and delete all other copies of the ref, including the base copy, VE is unable to transfer the base text to the copy of the ref in the tag, so the citation is lost.",task_subcomment,"[""It doesn't seem to have been mentioned above that this bug can cause the loss of a citation, which might affect the severity or priority."", 'If you have a ref inside a group note (e.g.', 'inside a tag) and delete all other copies of the ref, including the base copy, VE is unable to transfer the base text to the copy of the ref in the tag, so the citation is lost.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+392866,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Notes for testing the future fix: 
+
+- The references placed in the Infobox template should be numbered correctly along with the other page references
+- There should be no discrepancy in displaying reference numbering in Read mode or VE mode
+- also, check reference for class=""toccolours"" - the warning msg should be displayed: ""This reference is defined in a template or other generated block, and for now can only be edited in source mode.""
+",task_subcomment,"['Notes for testing the future fix: \n\n- The references placed in the Infobox template should be numbered correctly along with the other page references\n- There should be no discrepancy in displaying reference numbering in Read mode or VE mode\n- also, check reference for class=""toccolours"" - the warning msg should be displayed: ""This reference is defined in a template or other generated block, and for now can only be edited in source mode.""']",['INVESTIGATION AND EXPLORATION']
+241574,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 69373 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 69373 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241570,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 52742 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52742 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241567,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 63210 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 63210 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241563,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 51058 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51058 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241559,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 53777 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53777 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241554,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","**kwwilliams** wrote:
+
+(In reply to comment #25)
+> (In reply to comment #23)
+> > There's no way to code a single template that generates both a reference and
+> > table markup without using {{#tag:ref}}. 
+> 
+> True. This should have given you pause to consider /why/ it wasn't available
+> until recently. :-)
+
+Laughing while you dismiss my comments adds a layer of rudeness to the discussion that is completely unnecessary.",task_subcomment,['**kwwilliams** wrote:\n\n(In reply to comment #25)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nLaughing while you dismiss my comments adds a layer of rudeness to the discussion that is completely unnecessary.'],['SOCIAL CONVERSATION']
+241547,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 53486 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 53486 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241542,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","(In reply to comment #23)
+> There's no way to code a single template that generates both a reference and
+> table markup without using {{#tag:ref}}. 
+
+True. This should have given you pause to consider /why/ it wasn't available until recently. :-)
+
+> If you didn't think ""any reference created by a template shouldn't work,
+> deliberately"" would be read as a refusal to fix that particular aspect of
+> this bug, I have no idea what you intended it to mean.
+
+Translation: When we made MW's citation system, the intent right from the start was to never, ever let people create nested references, or references that need to be parsed multiple times, because it creates endless issues.
+
+Unfortunately, when later the {{#tag:xxx}} system was created, the person implementing that didn't remember this issue and instead has indeed given rise to all manner of epic problems.
+
+> I also don't see that this bugzilla specifically addresses the ability for
+> the names and contents of template generated references to be available to an
+> editor that is using the ""add reference"" dialog.
+
+That would be the ""don't show up as references to insert"" part of the title. :-)",task_subcomment,"['(In reply to comment #23)\nQUOTE\nQUOTE\n\nTrue.', ""This should have given you pause to consider /why/ it wasn't available until recently."", "":-)\n\nQUOTE\nQUOTE\nQUOTE\n\nTranslation: When we made MW's citation system, the intent right from the start was to never, ever let people create nested references, or references that need to be parsed multiple times, because it creates endless issues."", ""Unfortunately, when later the {{#tag:xxx}} system was created, the person implementing that didn't remember this issue and instead has indeed given rise to all manner of epic problems."", 'QUOTE\nQUOTE\nQUOTE\n\nThat would be the ""don\'t show up as references to insert"" part of the title.', ':-)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+241534,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","We might actually be able to use the same CSS technique I developed for auto-numbered external links in bug 53505 for citations. That would at least fix the numbering without extra effort, but won't help with  rendering and editing.",task_subcomment,"['We might actually be able to use the same CSS technique I developed for auto-numbered external links in bug 53505 for citations.', ""That would at least fix the numbering without extra effort, but won't help with  rendering and editing.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+241527,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","**kwwilliams** wrote:
+
+There's no way to code a single template that generates both a reference and table markup without using {{#tag:ref}}. 
+
+If you didn't think ""any reference created by a template shouldn't work, deliberately"" would be read as a refusal to fix that particular aspect of this bug, I have no idea what you intended it to mean.
+
+I also don't see that this bugzilla specifically addresses the ability for the names and contents of template generated references to be available to an editor that is using the ""add reference"" dialog.",task_subcomment,"[""**kwwilliams** wrote:\n\nThere's no way to code a single template that generates both a reference and table markup without using {{#tag:ref}}."", 'If you didn\'t think ""any reference created by a template shouldn\'t work, deliberately"" would be read as a refusal to fix that particular aspect of this bug, I have no idea what you intended it to mean.', 'I also don\'t see that this bugzilla specifically addresses the ability for the names and contents of template generated references to be available to an editor that is using the ""add reference"" dialog.']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+241519,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","(In reply to comment #21)
+> Describing a widely used template as a ""hack"" and refusing to fix the bugs
+> associated with VE in terms of editing it is not a valid solution.
+
+Who said I was refusing to fix it?
+
+> The template does work and the references work fine using the normal editor.
+> There's no way to code the template to not include the #ref.
+
+{{foo}} works just fine, because that's how it was designed to be used. If you want an easier way to edit, use VE. ;-)
+
+> It is not within the scope of the VE project to refuse to fix problems
+> because they are hard.
+
+This is off-topic, but actually, it is very much part of Wikimedia's job to make decisions about whether it is worth spending large amounts of donor funds on marginal use cases rather than features that can't be done in other ways.
+
+> I strongly, strongly object to the implication in the addition to 52478 that
+> implies that this bug in VE will never be fixed.
+
+There is no such implication; there is clearly the inference in your reading of it, however. We will fix this bug - the comment just explains the priority of this bug in relation to others.",task_subcomment,"['(In reply to comment #21)\nQUOTE\nQUOTE\n\nWho said I was refusing to fix it?', ""QUOTE\nQUOTE\n\n{{foo}} works just fine, because that's how it was designed to be used."", 'If you want an easier way to edit, use VE.', "";-)\n\nQUOTE\nQUOTE\n\nThis is off-topic, but actually, it is very much part of Wikimedia's job to make decisions about whether it is worth spending large amounts of donor funds on marginal use cases rather than features that can't be done in other ways."", 'QUOTE\nQUOTE\n\nThere is no such implication; there is clearly the inference in your reading of it, however.', 'We will fix this bug - the comment just explains the priority of this bug in relation to others.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'MOTIVATION', 'MOTIVATION', 'POTENTIAL NEW ISSUES AND REQUESTS']"
+241508,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","**kwwilliams** wrote:
+
+Describing a widely used template as a ""hack"" and refusing to fix the bugs associated with VE in terms of editing it is not a valid solution. The template does work and the references work fine using the normal editor. There's no way to code the template to not include the #ref.
+
+It is not within the scope of the VE project to refuse to fix problems because they are hard.
+
+I strongly, strongly object to the implication in the addition to 52478 that implies that this bug in VE will never be fixed.",task_subcomment,"['**kwwilliams** wrote:\n\nDescribing a widely used template as a ""hack"" and refusing to fix the bugs associated with VE in terms of editing it is not a valid solution.', 'The template does work and the references work fine using the normal editor.', ""There's no way to code the template to not include the #ref."", 'It is not within the scope of the VE project to refuse to fix problems because they are hard.', 'I strongly, strongly object to the implication in the addition to 52478 that implies that this bug in VE will never be fixed.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+241500,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 52478 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52478 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241491,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",Resolving Bug 28980 could relieve at least part of this problem by lifting the need to use  because of localization issues.,task_subcomment,['Resolving Bug 28980 could relieve at least part of this problem by lifting the need to use  because of localization issues.'],['INVESTIGATION AND EXPLORATION']
+241483,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",*** Bug 52083 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52083 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241478,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","The ref duplication issue (last bullet point) was actually a Parsoid bug which is fixed with the commit above. It only manifested itself in templated references sections which are not rendered by VE. The fix is deployed to production.
+
+The other VE issues remain, but fortunately are less visible to users unless they modify references.",task_subcomment,"['The ref duplication issue (last bullet point) was actually a Parsoid bug which is fixed with the commit above.', 'It only manifested itself in templated references sections which are not rendered by VE.', 'The fix is deployed to production.', 'The other VE issues remain, but fortunately are less visible to users unless they modify references.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+241473,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Change 71528 merged by jenkins-bot:
+Bug 50474: Remove children of references node
+
+https://gerrit.wikimedia.org/r/71528",task_subcomment,['Change 71528 merged by jenkins-bot:\nBug 50474: Remove children of references node\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+241467,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Change 71528 had a related patch set uploaded by GWicke:
+WIP Bug 50474: Remove children of references node
+
+https://gerrit.wikimedia.org/r/71528",task_subcomment,['Change 71528 had a related patch set uploaded by GWicke:\nWIP Bug 50474: Remove children of references node\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+241463,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","I think so far we have seen several issues in this area:
+
+* References from templated content are not being picked up by VE, which causes
+
+** the numbering to be off
+
+** those references to be missing in references
+
+** edits to refs whose primary (first in DOM order) definition is templated just update the first non-templated ref alias in the page. Those changes are then not rendered in the PHP parser. Correct behavior would be to explain why that reference cannot be edited.
+
+* Some refs are duplicated in the references section",task_subcomment,"['I think so far we have seen several issues in this area:\n\n* References from templated content are not being picked up by VE, which causes\n\n** the numbering to be off\n\n** those references to be missing in references\n\n** edits to refs whose primary (first in DOM order) definition is templated just update the first non-templated ref alias in the page.', 'Those changes are then not rendered in the PHP parser.', 'Correct behavior would be to explain why that reference cannot be edited.', '* Some refs are duplicated in the references section']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241458,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Parsoid provides ref info also inside template-generated content, and our ref / references rendering code make use of that. I have proposed to share that code in bug 50505. 
+
+Using the Parsoid rendering on first load could be a workaround, but hacking dynamic updates into that sounds like more trouble than it's worth.",task_subcomment,"['Parsoid provides ref info also inside template-generated content, and our ref / references rendering code make use of that.', 'I have proposed to share that code in bug 50505.', ""Using the Parsoid rendering on first load could be a workaround, but hacking dynamic updates into that sounds like more trouble than it's worth.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+241452,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",This also prohibits references utilised in templates from being used elsewhere on the page via the template inspector. Blah :/.,task_subcomment,"['This also prohibits references utilised in templates from being used elsewhere on the page via the template inspector.', 'Blah :/.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+241449,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","(In reply to comment #9)
+> IIRC the VE renders (and numbers) references natively without using our
+> rendering at all. Which would make this a VE bug. Trying to confirm.
+That's correct. VE does not see the first two references because they are in a template, and so it mistakenly believes the one in ""Early years"" is the first one.
+
+We could mitigate this by using the numbering Parsoid gives us.",task_subcomment,"[""(In reply to comment #9)\nQUOTE\nQUOTE\nThat's correct."", 'VE does not see the first two references because they are in a template, and so it mistakenly believes the one in ""Early years"" is the first one.', 'We could mitigate this by using the numbering Parsoid gives us.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+241443,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Moved to VE, as the numbering seems to be re-done in VE.",task_subcomment,"['Moved to VE, as the numbering seems to be re-done in VE.']",['BUG REPRODUCTION']
+241437,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",IIRC the VE renders (and numbers) references natively without using our rendering at all. Which would make this a VE bug. Trying to confirm.,task_subcomment,"['IIRC the VE renders (and numbers) references natively without using our rendering at all.', 'Which would make this a VE bug.', 'Trying to confirm.']","['OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+241431,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","It seems that this bug doesn't cause any wikitext corruption, but only affects display in VE.  Still something we should fix on the Parsoid end, but not as troublesome as I initially thought this was.",task_subcomment,"[""It seems that this bug doesn't cause any wikitext corruption, but only affects display in VE."", 'Still something we should fix on the Parsoid end, but not as troublesome as I initially thought this was.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241425,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Looks like the ref-counter has been reset after the 2nd ref-tag was processed and also, 13 references are duplicated (the first 2 are not duplicated).
+
+The bug cannot be duplicated locally.  So, I suspect something is off when refs are being reused from Varnish caches.",task_subcomment,"['Looks like the ref-counter has been reset after the 2nd ref-tag was processed and also, 13 references are duplicated (the first 2 are not duplicated).', 'The bug cannot be duplicated locally.', 'So, I suspect something is off when refs are being reused from Varnish caches.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241417,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.",Indeed. In my defence it's 10pm on a Sunday :/,task_subcomment,"['Indeed.', ""In my defence it's 10pm on a Sunday :/""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241411,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Ah, I see the new screenshot. You wanted to write ""Early years""?",task_subcomment,"['Ah, I see the new screenshot.', 'You wanted to write ""Early years""?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241403,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","Yes, there are references with the same name, split into multiple entries but I don't understand how the screenshots you attached should demonstrate that.",task_subcomment,"[""Yes, there are references with the same name, split into multiple entries but I don't understand how the screenshots you attached should demonstrate that.""]",['OBSERVED BUG BEHAVIOR']
+241397,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","How it actually looks
+
+**Attached**: {F11401}",task_subcomment,['How it actually looks\n\n**Attached**: {F11401}'],['OBSERVED BUG BEHAVIOR']
+241391,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","How it actually looks
+
+//attachment Screen Shot 2013-06-30 at 12.24.02 PM.png ignored as obsolete//",task_subcomment,['How it actually looks\n\n//attachment Screen Shot 2013-06-30 at 12.24.02 PM.png ignored as obsolete//'],['OBSERVED BUG BEHAVIOR']
+241386,"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","How it should look
+
+**Attached**: {F11400}",task_subcomment,['How it should look\n\n**Attached**: {F11400}'],['OBSERVED BUG BEHAVIOR']
+52465,"VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore","https://en.wikipedia.org/w/index.php?title=Edamattom&diff=562268939&oldid=562266260 <- this was from an attempt to swap a references section and an external links section. We cannot have this scale corruption on launch. I'd be most grateful if someone could find out what the heck happened, and also confirm with some degree of certainty that it won't happen again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51677",task_description,"['VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore\n\nURL <- this was from an attempt to swap a references section and an external links section.', 'We cannot have this scale corruption on launch.', ""I'd be most grateful if someone could find out what the heck happened, and also confirm with some degree of certainty that it won't happen again."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+240813,"VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore",I think this has been fixed for a while. Re-open if you can reproduce it.,task_subcomment,"['I think this has been fixed for a while.', 'Re-open if you can reproduce it.']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+240807,"VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore","I can reproduce it.  With a lot of the pawn bugs fixed now, maybe it has disappeared.",task_subcomment,"['I can reproduce it.', 'With a lot of the pawn bugs fixed now, maybe it has disappeared.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240803,"VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore","Oh, meant to add that the loop may well have been infinite but I tried to force the save (with ultimate success).",task_subcomment,"['Oh, meant to add that the loop may well have been infinite but I tried to force the save (with ultimate success).']",['OBSERVED BUG BEHAVIOR']
+240800,"VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore","Given the severity, I'll try to recreate what I was doing but it was basically an attempt to cut the existing External Links section and paste it after the References. As I had made other changes, I can't rule out the idea that I could have stopped editing at the first sight of white pawns; certainly, I saw a couple just before the main ""whumpfh"" of the loop kicking in, but the loop might have already started by then.
+
+Browser: Chrome latest (27.0.1453.116) running on Windows 7. Plenty of RAM (before the loop, anyway :P).",task_subcomment,"[""Given the severity, I'll try to recreate what I was doing but it was basically an attempt to cut the existing External Links section and paste it after the References."", 'As I had made other changes, I can\'t rule out the idea that I could have stopped editing at the first sight of white pawns; certainly, I saw a couple just before the main ""whumpfh"" of the loop kicking in, but the loop might have already started by then.', 'Browser: Chrome latest (27.0.1453.116) running on Windows 7.', 'Plenty of RAM (before the loop, anyway :P).']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52442,VisualEditor: One should be able to select (and copy) the text of an edit notice,"When a notice is shown (on beta), it's not possible for the user to mark the text and copy.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: One should be able to select (and copy) the text of an edit notice\n\nWhen a notice is shown (on beta), it's not possible for the user to mark the text and copy."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239625,VisualEditor: One should be able to select (and copy) the text of an edit notice,This was fixed as part of the toolbar fixes last week.,task_subcomment,['This was fixed as part of the toolbar fixes last week.'],['BUG REPRODUCTION']
+239619,VisualEditor: One should be able to select (and copy) the text of an edit notice,"Text selection of the toolbar and descendants of it was intentionally disabled for design and user experience reasons.
+
+I can understand that it may be useful to re-enable it for the edit notice part of the toolbar though.",task_subcomment,"['Text selection of the toolbar and descendants of it was intentionally disabled for design and user experience reasons.', 'I can understand that it may be useful to re-enable it for the edit notice part of the toolbar though.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52439,VisualEditor: Transclusion dialog should truncate spaces from parameter input,"When adding/modifying a template, you can append a space to the parameter, and even if you have that parameter already used, you can add one more. As well you can add a (multiple) empty "" "" parameter.
+
+Example template I made ended up as:
+
+{{test|name = ""
+
+
+
+
+
+
+
+|logo = '
+""| = |  = |logo = }}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61049",task_description,"['VisualEditor: Transclusion dialog should truncate spaces from parameter input\n\nWhen adding/modifying a template, you can append a space to the parameter, and even if you have that parameter already used, you can add one more.', 'As well you can add a (multiple) empty "" "" parameter.', 'Example template I made ended up as:\n\n{{test|name = ""\n\n\n\n\n\n\n\n|logo = \'\n""| = |  = |logo = }}\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+239402,VisualEditor: Transclusion dialog should truncate spaces from parameter input,"This appears to be fixed now. You can't create both ""foo"" and ""foo "" any more.",task_subcomment,"['This appears to be fixed now.', 'You can\'t create both ""foo"" and ""foo "" any more.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+239396,VisualEditor: Transclusion dialog should truncate spaces from parameter input,"Clarification: the transclusion dialog allows the user to create both ""foo"" and ""foo "" as separate parameters, but it shouldn't. It also allows the user to create the empty parameter ("" "") multiple times.",task_subcomment,"['Clarification: the transclusion dialog allows the user to create both ""foo"" and ""foo "" as separate parameters, but it shouldn\'t.', 'It also allows the user to create the empty parameter ("" "") multiple times.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+52436,TemplateData: Creating TemplateData blocks should be direction neutral,"This is a bug/design issuse with TemplateData.
+
+To use TemplateData in RTL wikis, the syntax mix English and Arabic/Hebrew (etc).
+
+Editing mixed languages with different direction is hard and should be avoided as much as possible because of BiDi issues. (in some cases, such as Lua modules it isn't possible to completely avoid it).
+
+Example :
+
+{
+        ""description"": ""תבנית כלשהי."",
+        ""params"": {
+                ""שם"": {
+                        ""label"": ""שם"",
+                        ""type"": ""string/wiki-user-name"",
+                        ""required"": true,
+                        ""description"": ""שם של משתמש"",
+                        ""aliases"": [""1""]
+                }
+        },
+        ""sets"": [
+                {
+                        ""label"": ""Date"",
+                        ""params"": [""שנה"", ""חודש"", ""יום""]
+                }
+        ]
+}
+
+It is very hard to edit such syntax as above. ( is OK since it is in different line - but the JSON isn't [if we don't want to define special indentation convention due to direction issues])
+The syntax for the JSON keywords (description, params, label etc) should be either translatable or should have some neutral direction alternative to defines it (JSON by itself is directionless - [{}:,] doesn't have direction information).
+
+See also:
+* bug 50169 - implementing this feature may reduce the severity of this bug (this solution will force template editors in RTL wiki to use visual editor at least for templatedata definitions).
+* bug 50370 - translation of interface items
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50370",task_description,"['TemplateData: Creating TemplateData blocks should be direction neutral\n\nThis is a bug/design issuse with TemplateData.', 'To use TemplateData in RTL wikis, the syntax mix English and Arabic/Hebrew (etc).', 'Editing mixed languages with different direction is hard and should be avoided as much as possible because of BiDi issues.', ""(in some cases, such as Lua modules it isn't possible to completely avoid it)."", 'Example :\n\n{\n        ""description"": ""תבנית כלשהי.', '"",\n        ""params"": {\n                ""שם"": {\n                        ""label"": ""שם"",\n                        ""type"": ""string/wiki-user-name"",\n                        ""required"": true,\n                        ""description"": ""שם של משתמש"",\n                        ""aliases"": [""1""]\n                }\n        },\n        ""sets"": [\n                {\n                        ""label"": ""Date"",\n                        ""params"": [""שנה"", ""חודש"", ""יום""]\n                }\n        ]\n}\n\nIt is very hard to edit such syntax as above.', ""( is OK since it is in different line - but the JSON isn't [if we don't want to define special indentation convention due to direction issues])\nThe syntax for the JSON keywords (description, params, label etc) should be either translatable or should have some neutral direction alternative to defines it (JSON by itself is directionless - [{}:,] doesn't have direction information)."", 'See also:\n* bug 50169 - implementing this feature may reduce the severity of this bug (this solution will force template editors in RTL wiki to use visual editor at least for templatedata definitions).', '* bug 50370 - translation of interface items\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+239277,TemplateData: Creating TemplateData blocks should be direction neutral,"This is now effectively ""solved"" through general availability of the GUI to edit TemplateData.",task_subcomment,"['This is now effectively ""solved"" through general availability of the GUI to edit TemplateData.']",['SOLUTION USAGE']
+239274,TemplateData: Creating TemplateData blocks should be direction neutral,Would be nice to deploy it the template data editor to Hebrew Wikipedia  - it is more important then in other wikis because of this bug,task_subcomment,['Would be nice to deploy it the template data editor to Hebrew Wikipedia  - it is more important then in other wikis because of this bug'],['INVESTIGATION AND EXPLORATION']
+239271,TemplateData: Creating TemplateData blocks should be direction neutral,"(In reply to comment #15)
+> How about marking it as a duplicate of bug 51734?
+
+I don't think it's really a duplicate, though; the problem remains (so if you want to edit the source directly you still have to deal with it).
+
+(In reply to comment #16)
+> Thanks Moriel for implementing a nice workaround to this bug.
+> I think this bug can be disposed after template editor will be deployed to
+> all wikis.
+
+That seems like a reasonable resolution. Will do.",task_subcomment,"[""(In reply to comment #15)\nQUOTE\n\nI don't think it's really a duplicate, though; the problem remains (so if you want to edit the source directly you still have to deal with it)."", '(In reply to comment #16)\nQUOTE\nQUOTE\nQUOTE\n\nThat seems like a reasonable resolution.', 'Will do.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239264,TemplateData: Creating TemplateData blocks should be direction neutral,"Thanks Moriel for implementing a nice workaround to this bug.
+I think this bug can be disposed after template editor will be deployed to all wikis.",task_subcomment,"['Thanks Moriel for implementing a nice workaround to this bug.', 'I think this bug can be disposed after template editor will be deployed to all wikis.']","['ACTION ON ISSUE', 'FUTURE PLAN']"
+239257,TemplateData: Creating TemplateData blocks should be direction neutral,How about marking it as a duplicate of bug 51734?,task_subcomment,['How about marking it as a duplicate of bug 51734?'],['ACTION ON ISSUE']
+239251,TemplateData: Creating TemplateData blocks should be direction neutral,"So… I'm not sure how to dispose of this bug:
+
+* FIXED – except it's not fixed, it's just ""worked around"" by bug 51734
+* INVALID – except it's still a valid concern
+* WORKSFORME – but only because I'm willing to put up with this (and I don't do RTL much)
+* WONTFIX – closest to the truth, but feels a little blunt
+
+Perhaps we should wait for the template editor to be deployed for all languages, then close this as WONTFIX?",task_subcomment,"['So… I\'m not sure how to dispose of this bug:\n\n* FIXED – except it\'s not fixed, it\'s just ""worked around"" by bug 51734\n* INVALID – except it\'s still a valid concern\n* WORKSFORME –\xa0but only because I\'m willing to put up with this (and I don\'t do RTL much)\n* WONTFIX – closest to the truth, but feels a little blunt\n\nPerhaps we should wait for the template editor to be deployed for all languages, then close this as WONTFIX?']",['WORKAROUNDS']
+239245,TemplateData: Creating TemplateData blocks should be direction neutral,"Change 85400 merged by jenkins-bot:
+Implement edit interface for TemplateData documentation
+
+https://gerrit.wikimedia.org/r/85400",task_subcomment,['Change 85400 merged by jenkins-bot:\nImplement edit interface for TemplateData documentation\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239241,TemplateData: Creating TemplateData blocks should be direction neutral,"Change 85400 had a related patch set uploaded by Mooeypoo:
+TemplateData Generator GUI
+
+https://gerrit.wikimedia.org/r/85400",task_subcomment,['Change 85400 had a related patch set uploaded by Mooeypoo:\nTemplateData Generator GUI\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239236,TemplateData: Creating TemplateData blocks should be direction neutral,"(In reply to comment #10)
+> Michal tool seems interesting but it currently lacks the ability to edit an
+> existing templatedata. Michal, is that something you're planning to add?
+
+Absolutely! Working on that now. At first you'll have to copy JSON data to the tool, but I'll try to add auto copying from a given template.",task_subcomment,"['(In reply to comment #10)\nQUOTE\nQUOTE\n\nAbsolutely!', 'Working on that now.', ""At first you'll have to copy JSON data to the tool, but I'll try to add auto copying from a given template.""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239230,TemplateData: Creating TemplateData blocks should be direction neutral,"Ltrlg's script can edit an existing templatedata. I don't know if it works correctly with rtl languages, but if it doesn't you could always ask Ltrlg to fix it.
+
+Michal tool seems interesting but it currently lacks the ability to edit an existing templatedata. Michal, is that something you're planning to add?",task_subcomment,"[""Ltrlg's script can edit an existing templatedata."", ""I don't know if it works correctly with rtl languages, but if it doesn't you could always ask Ltrlg to fix it."", 'Michal tool seems interesting but it currently lacks the ability to edit an existing templatedata.', ""Michal, is that something you're planning to add?""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239224,TemplateData: Creating TemplateData blocks should be direction neutral,"I forgot to attach the link... here it is:
+
+https://github.com/mooeypoo/MediaWiki-TemplateDataGenerator
+
+It's still being tested, and there are a couple of changes we should still implement, but it's getting there. I hope it will be ready for wider test in the next few days.",task_subcomment,"[""I forgot to attach the link... here it is:\n\nURL\n\nIt's still being tested, and there are a couple of changes we should still implement, but it's getting there."", 'I hope it will be ready for wider test in the next few days.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239221,TemplateData: Creating TemplateData blocks should be direction neutral,"I'm working on a TemplateData Generator extension that will allow the editing or creation from scratch of templatedata json. It will allow the editing of the json data visually, so you could maintain the parameters or description as you please with a GUI.
+
+I'm also making sure it works with RTL languages and the GUI is completely translation-ready. I hope it will be ready in the next few days (at least a basic working version of it)",task_subcomment,"[""I'm working on a TemplateData Generator extension that will allow the editing or creation from scratch of templatedata json."", 'It will allow the editing of the json data visually, so you could maintain the parameters or description as you please with a GUI.', ""I'm also making sure it works with RTL languages and the GUI is completely translation-ready."", 'I hope it will be ready in the next few days (at least a basic working version of it)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239217,TemplateData: Creating TemplateData blocks should be direction neutral,"Is it possible to edit templatedata or just create new? Is it possible to populate the form with existing tempaltedata?
+
+The main problem isn't creation of tempaltedata (which for many cases can be done by bots), but to maintain it - e.g changing the description, adding/removing parameters etc.",task_subcomment,"['Is it possible to edit templatedata or just create new?', 'Is it possible to populate the form with existing tempaltedata?', ""The main problem isn't creation of tempaltedata (which for many cases can be done by bots), but to maintain it - e.g changing the description, adding/removing parameters etc.""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239210,TemplateData: Creating TemplateData blocks should be direction neutral,I've addded rtl support to my editor (http://tools.wikimedia.pl/~mlazowik/templatedata/). You can send me translations. More info in the bottom of the page.,task_subcomment,"[""I've addded rtl support to my editor (URL You can send me translations."", 'More info in the bottom of the page.']","['CONTRIBUTION AND COMMITMENT', 'OBSERVED BUG BEHAVIOR']"
+239203,TemplateData: Creating TemplateData blocks should be direction neutral,"A user interface exists also as a script on enwiki (which can be used directly from other wikis)
+http://en.wikipedia.org/wiki/User:NicoV/TemplateDataEditor
+
+It was written by Ltrlg (see 2 posts above) on frwiki, I translated it into English.",task_subcomment,"['A user interface exists also as a script on enwiki (which can be used directly from other wikis)\nURL\n\nIt was written by Ltrlg (see 2 posts above) on frwiki, I translated it into English.']",['INVESTIGATION AND EXPLORATION']
+239197,TemplateData: Creating TemplateData blocks should be direction neutral,"(In reply to comment #2)
+> The ideal thing here would be to build a tree-like visual TemplateData
+> editor,
+> that would save its data to JSON. Kinda like http://www.jsoneditoronline.org/
+> (first Google result for ""json editor"").
+
+It kinda exists now, http://tools.wikimedia.pl/~mlazowik/templatedata/, but is currently not translateable (only in Polish). The code is on GitHub (https://github.com/mlazowik/templatedata/) and author accepts pull requests :) (CC'ing him).",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIt kinda exists now, URL but is currently not translateable (only in Polish).', ""The code is on GitHub (URL and author accepts pull requests :) (CC'ing him).""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239190,TemplateData: Creating TemplateData blocks should be direction neutral,See bug 51734 (Create a non-VisualEditor plugin tool to add/edit template hinting) for visual interface.,task_subcomment,['See bug 51734 (Create a non-VisualEditor plugin tool to add/edit template hinting) for visual interface.'],['INVESTIGATION AND EXPLORATION']
+239186,TemplateData: Creating TemplateData blocks should be direction neutral,"The ideal thing here would be to build a tree-like visual TemplateData editor, that would save its data to JSON. Kinda like http://www.jsoneditoronline.org/ (first Google result for ""json editor"").
+
+Separating labels and data would easily solve the RTL problem, and would also make TemplateData easier to edit for users in all languages.",task_subcomment,"['The ideal thing here would be to build a tree-like visual TemplateData editor, that would save its data to JSON.', 'Kinda like URL (first Google result for ""json editor"").', 'Separating labels and data would easily solve the RTL problem, and would also make TemplateData easier to edit for users in all languages.']","['EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239181,TemplateData: Creating TemplateData blocks should be direction neutral,"Timo, thoughts?",task_subcomment,"['Timo, thoughts?']",['SOLUTION DISCUSSION']
+52420,Wikitext list after implicit  not properly recognized,"I did not add this to closed bug 50012 because while it may be related it's not exactly the same.
+
+This edit to the text of the article added extraneous pipes throughout (http://en.wikipedia.org/w/index.php?title=List_of_male_kickboxers&diff=562103247&oldid=561869162) and also dropped some formatting on the end (|}|}|}|}|}|})
+
+See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Unwanted_format_changes_throughout_article
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""Wikitext list after implicit  not properly recognized\n\nI did not add this to closed bug 50012 because while it may be related it's not exactly the same."", 'This edit to the text of the article added extraneous pipes throughout (URL and also dropped some formatting on the end (|}|}|}|}|}|})\n\nSee URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+238072,Wikitext list after implicit  not properly recognized,"Change 71744 merged by jenkins-bot:
+(Bug 50420) Recognize sol-content in implicit  after a 
+
+https://gerrit.wikimedia.org/r/71744",task_subcomment,['Change 71744 merged by jenkins-bot:\n(Bug 50420) Recognize sol-content in implicit  after a \n\nGERRIT_URL'],['BUG REPRODUCTION']
+238071,Wikitext list after implicit  not properly recognized,"Change 71744 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 50420) Recognize sol-content in implicit  after a 
+
+https://gerrit.wikimedia.org/r/71744",task_subcomment,['Change 71744 had a related patch set uploaded by Subramanya Sastry:\nWIP: (Bug 50420) Recognize sol-content in implicit  after a \n\nGERRIT_URL'],['ACTION ON ISSUE']
+238069,Wikitext list after implicit  not properly recognized,"Ok, renamed the bug to reflect the repurposing.",task_subcomment,"['Ok, renamed the bug to reflect the repurposing.']",['SOLUTION DISCUSSION']
+238066,Wikitext list after implicit  not properly recognized,"Change 71314 merged by jenkins-bot:
+(Bug 50420) Tweaked selser to reuse td/th/tr wrappers from source
+
+https://gerrit.wikimedia.org/r/71314",task_subcomment,['Change 71314 merged by jenkins-bot:\n(Bug 50420) Tweaked selser to reuse td/th/tr wrappers from source\n\nGERRIT_URL'],['BUG REPRODUCTION']
+238063,Wikitext list after implicit  not properly recognized,"I was wrong.  This bug was fixed by tweaking selser as in the patch above since VE does not have table-editing capability yet (only table contents, not table structure).
+
+There is an unrelated bug in the parser where leading list wikitext in a td-cell is parsed as plain text rather than as a list item.  So, the pipe problem is fixed by the above commit, but there will still be a dirty-diff (the first list item will be wrapped in nowiki on serialization).  That will be addressed separately.",task_subcomment,"['I was wrong.', 'This bug was fixed by tweaking selser as in the patch above since VE does not have table-editing capability yet (only table contents, not table structure).', 'There is an unrelated bug in the parser where leading list wikitext in a td-cell is parsed as plain text rather than as a list item.', 'So, the pipe problem is fixed by the above commit, but there will still be a dirty-diff (the first list item will be wrapped in nowiki on serialization).', 'That will be addressed separately.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+238058,Wikitext list after implicit  not properly recognized,"Change 71314 had a related patch set uploaded by Subramanya Sastry:
+(Bug 50420) Tweak selser to reuse td/th/tr wrappers from source
+
+https://gerrit.wikimedia.org/r/71314",task_subcomment,['Change 71314 had a related patch set uploaded by Subramanya Sastry:\n(Bug 50420) Tweak selser to reuse td/th/tr wrappers from source\n\nGERRIT_URL'],['BUG REPRODUCTION']
+238051,Wikitext list after implicit  not properly recognized,"https://en.wikipedia.org/w/index.php?title=List_of_male_kickboxers&diff=562167553&oldid=562162447 shows an instance where converting an implicit  into an explicit  on serialization is a semantic error.
+
+Reduced test case:
+
+{|
+|-
+*a
+|}
+
+This cannot be fixed by selser since on editing the list item, the  will go through regular serialization.
+
+We should be able to safely use the autoInserted* flags from data-parsoid in this instance since VE does not have table-editing capability yet.",task_subcomment,"['URL shows an instance where converting an implicit  into an explicit  on serialization is a semantic error.', 'Reduced test case:\n\n{|\n|-\n*a\n|}\n\nThis cannot be fixed by selser since on editing the list item, the  will go through regular serialization.', 'We should be able to safely use the autoInserted* flags from data-parsoid in this instance since VE does not have table-editing capability yet.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+238043,Wikitext list after implicit  not properly recognized,"The problem is that this page had about 13 tables that were unclosed (missing |} wikitext).  Parsoid does handle a lot of corner cases, but at this time, unclosed tables (especially when there are lots of them) are harder for Parsoid to recover from.  But, we have some ideas for recovering from them in the future.  But, till such time, it is easier to fix the wikitext of the page like I did (https://en.wikipedia.org/w/index.php?title=List_of_male_kickboxers&diff=562162447&oldid=562113696)
+
+However, there is definitely a bug there which is about adding ""|"" after the first table row for which I'll repurpose this bug for fixing in Parsoid.",task_subcomment,"['The problem is that this page had about 13 tables that were unclosed (missing |} wikitext).', 'Parsoid does handle a lot of corner cases, but at this time, unclosed tables (especially when there are lots of them) are harder for Parsoid to recover from.', 'But, we have some ideas for recovering from them in the future.', 'But, till such time, it is easier to fix the wikitext of the page like I did (URL\n\nHowever, there is definitely a bug there which is about adding ""|"" after the first table row for which I\'ll repurpose this bug for fixing in Parsoid.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']"
+238034,Wikitext list after implicit  not properly recognized,"I would consider this a blocker on Monday's deployment. Things not having support (browsers or features) I can deal with, but we cannot have this sort of corruption being introduced.",task_subcomment,"[""I would consider this a blocker on Monday's deployment."", 'Things not having support (browsers or features) I can deal with, but we cannot have this sort of corruption being introduced.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52411,VisualEditor: Reference list display being cut off in some pages,"Screenshot, cut-off notes list
+
+In some formatting, the ""Notes"" section of an article gets cut off in editing mode display.  Additionally, ""a,"" ""b,"" ""c,"" etc. get turned into 1.0, 1.1, 1.2 while in editing mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11283}",task_description,"['VisualEditor: Reference list display being cut off in some pages\n\nScreenshot, cut-off notes list\n\nIn some formatting, the ""Notes"" section of an article gets cut off in editing mode display.', 'Additionally, ""a,"" ""b,"" ""c,"" etc.', 'get turned into 1.0, 1.1, 1.2 while in editing mode.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11283}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237594,VisualEditor: Reference list display being cut off in some pages,"(In reply to comment #2)
+> Could this be the same as bug 52371?
+
+No, this was a graphical glitch that we fixed (but I forgot to mark as such) - closing.",task_subcomment,"['(In reply to comment #2)\nQUOTE\n\nNo, this was a graphical glitch that we fixed (but I forgot to mark as such) - closing.']",['ACTION ON ISSUE']
+237589,VisualEditor: Reference list display being cut off in some pages,Could this be the same as bug 52371?,task_subcomment,['Could this be the same as bug 52371?'],['BUG REPRODUCTION']
+237580,VisualEditor: Reference list display being cut off in some pages,"I couldn't reproduce on Firefox or Chrome, Linux or Windows.  The article hasnt changed since the bug was raised.
+https://en.wikipedia.org/wiki/Arc_diagram?veaction=edit
+
+Did you experience this on any other article?",task_subcomment,"[""I couldn't reproduce on Firefox or Chrome, Linux or Windows."", 'The article hasnt changed since the bug was raised.', 'URL\n\nDid you experience this on any other article?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52406,"VisualEditor: ""TypeError: focusedNode is null"" thrown when applying a link to a template","Creating a template entry, marking it and click on ""Link"" button results in following error (twice in a row):
+
+TypeError: focusedNode is null
+https://bits.wikimedia.org/static-1.22wmf9/extensions/VisualEditor/modules/ve/ui/ve.ui.Context.js
+Line 260
+
+VE is in a bad state after this cannot access template edit at all after this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: ""TypeError: focusedNode is null"" thrown when applying a link to a template\n\nCreating a template entry, marking it and click on ""Link"" button results in following error (twice in a row):\n\nTypeError: focusedNode is null\nURL\nLine 260\n\nVE is in a bad state after this cannot access template edit at all after this.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+237272,"VisualEditor: ""TypeError: focusedNode is null"" thrown when applying a link to a template","Changing the status to Resolved -Worksforme.
+If you still experience the error , please reopen the bug.",task_subcomment,"['Changing the status to Resolved -Worksforme.', 'If you still experience the error , please reopen the bug.']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+237263,"VisualEditor: ""TypeError: focusedNode is null"" thrown when applying a link to a template","Not getting this error now in FireFox 20 and Chrome Version 26.0.1410.65 using MAC OS X 10.8.5.
+
+Right now clicking on ""Link"" button while selecting a template adds the link to the left of the template and can access  template edit after that.",task_subcomment,"['Not getting this error now in FireFox 20 and Chrome Version 26.0.1410.65 using MAC OS X 10.8.5.', 'Right now clicking on ""Link"" button while selecting a template adds the link to the left of the template and can access  template edit after that.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52402,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","When VE is active on a page it inserts its own ""edit"" tab (veaction=edit) and renames the legacy edit tab (action=edit) to ""Edit source"".
+
+Since VE is not active on all pages though the ""edit"" tab's functionality is inconsistent across pages (sometimes opening VE, sometimes opening the Wikitext editor).
+
+VE should rename the legacy edit tab to ""Edit source"" on *every* page (even if it is not active and therefore not inserting it's own ""edit"" link so the button's functionality keeps consistent across pages.
+
+
+This was also discussed on http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Change_the_.22Edit.22_tab_to_.22Edit_source.22_in_all_namespaces.
+Please note (as discussed in the linked section) that renaming the legacy edit tab globally by simply changing the existing interface message is *not* an option. People not using the visual editor should not see ""edit source"" by default but should continue to see the same text that was always there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50424",task_description,"['VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)\n\nWhen VE is active on a page it inserts its own ""edit"" tab (veaction=edit) and renames the legacy edit tab (action=edit) to ""Edit source"".', 'Since VE is not active on all pages though the ""edit"" tab\'s functionality is inconsistent across pages (sometimes opening VE, sometimes opening the Wikitext editor).', 'VE should rename the legacy edit tab to ""Edit source"" on *every* page (even if it is not active and therefore not inserting it\'s own ""edit"" link so the button\'s functionality keeps consistent across pages.', 'This was also discussed on URL\nPlease note (as discussed in the linked section) that renaming the legacy edit tab globally by simply changing the existing interface message is *not* an option.', 'People not using the visual editor should not see ""edit source"" by default but should continue to see the same text that was always there.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+237068,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)",Now fixed and deployed.,task_subcomment,['Now fixed and deployed.'],['ACTION ON ISSUE']
+237063,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","Change 77165 had a related patch set uploaded by Catrope:
+Move edit tab generation into PHP and make it more configurable
+
+https://gerrit.wikimedia.org/r/77165",task_subcomment,['Change 77165 had a related patch set uploaded by Catrope:\nMove edit tab generation into PHP and make it more configurable\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237059,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","Changing CSS id tags doesn't seem like all that much of a programming challenge, but it would enable all language Wikipedias to deal with this problem of inconsistent names appearing on ""edit"" tabs. So the payoff here, per hour of programming time, is really large. This isn't in any way a controversial change (it's invisible, directly, to users); it would be great if someone would deal with it and we could make progress in reducing user confusion.",task_subcomment,"['Changing CSS id tags doesn\'t seem like all that much of a programming challenge, but it would enable all language Wikipedias to deal with this problem of inconsistent names appearing on ""edit"" tabs.', 'So the payoff here, per hour of programming time, is really large.', ""This isn't in any way a controversial change (it's invisible, directly, to users); it would be great if someone would deal with it and we could make progress in reducing user confusion.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237054,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","(In reply to comment #3)
+> I'm think the following request by English Wikipedia user Reaper Eternal is
+> relevant to this bug (sorry if it isn't).
+
+Yes, that would get fixed by us doing this.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\n\nYes, that would get fixed by us doing this.']",['SOLUTION DISCUSSION']
+237049,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","(In reply to comment #3)
+
+Reaper Eternal's proposal is an excellent solution to the issue of what the ""Edit source"" tab should be named, and partly addresses whether ""Edit"" should be ""Edit source"" even when VE is not available (and thus there is one edit tab, not two). His proposal is a good solution because it then allows individual editors to alter these labels (I  would prefer ""VE"" rather than ""Edit"", and ""Wikitext"" rather than ""Edit source"",for example) via their own CSS, while leaving the defaults as is for newer editors. 
+
+> I'm think the following request by English Wikipedia user Reaper Eternal is
+> relevant to this bug (sorry if it isn't).
+> 
+> ""Currently, on articles and userpages, editing using the VisualEditor uses
+> the
+> #ca-edit CSS id and editing the source uses the #ca-editsource CSS id.
+> However,
+> in all other namespaces, #ca-edit is the only edit link. For people like me
+> who
+> like to change the titling or styling of the tabs, this inconsistency is
+> annoying. (For me, it makes the ""edit"" tab on this page display as ""VE""
+> rather
+> than ""Source"".) Could the CSS id tags be made consistent (use #ca-editsource
+> for all non-VE editing)? Thanks.""",task_subcomment,"['(In reply to comment #3)\n\nReaper Eternal\'s proposal is an excellent solution to the issue of what the ""Edit source"" tab should be named, and partly addresses whether ""Edit"" should be ""Edit source"" even when VE is not available (and thus there is one edit tab, not two).', 'His proposal is a good solution because it then allows individual editors to alter these labels (I  would prefer ""VE"" rather than ""Edit"", and ""Wikitext"" rather than ""Edit source"",for example) via their own CSS, while leaving the defaults as is for newer editors.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237044,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","I'm think the following request by English Wikipedia user Reaper Eternal is relevant to this bug (sorry if it isn't).
+
+""Currently, on articles and userpages, editing using the VisualEditor uses the #ca-edit CSS id and editing the source uses the #ca-editsource CSS id. However, in all other namespaces, #ca-edit is the only edit link. For people like me who like to change the titling or styling of the tabs, this inconsistency is annoying. (For me, it makes the ""edit"" tab on this page display as ""VE"" rather than ""Source"".) Could the CSS id tags be made consistent (use #ca-editsource for all non-VE editing)? Thanks.""",task_subcomment,"[""I'm think the following request by English Wikipedia user Reaper Eternal is relevant to this bug (sorry if it isn't)."", '""Currently, on articles and userpages, editing using the VisualEditor uses the #ca-edit CSS id and editing the source uses the #ca-editsource CSS id.', 'However, in all other namespaces, #ca-edit is the only edit link.', 'For people like me who like to change the titling or styling of the tabs, this inconsistency is annoying.', '(For me, it makes the ""edit"" tab on this page display as ""VE"" rather than ""Source"".)', 'Could the CSS id tags be made consistent (use #ca-editsource for all non-VE editing)?', 'Thanks.""']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+237037,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","I agree that relabelling it immediately for all MediaWiki installations is a poor choice, as (a) some people, (b) some WMF wikis, and (c) almost all MediaWiki wikis not hosted by WMF do not have VisualEditor enabled at this point.
+
+When VisualEditor is on for everyone, labelling the tab ""edit source"" (even when ""edit"", i.e. VisualEditor, is not available) seems like the best solution for our cluster. (If we wanted to, we could over-ride the value of the ""edit"" tab with a message from the Wikimedia-Messages system to do a WMF-specific over-ride of the MediaWiki default.) However, fixing this before (b) is fixed, let alone whilst (a) is fixed, feels like the wrong way to do this.
+
+A shorter-term fix is indeed to re-label ""edit"" to ""edit source"" for all pages visited by all users with VisualEditor. Maybe we could do that. Thoughts, Timo?",task_subcomment,"['I agree that relabelling it immediately for all MediaWiki installations is a poor choice, as (a) some people, (b) some WMF wikis, and (c) almost all MediaWiki wikis not hosted by WMF do not have VisualEditor enabled at this point.', 'When VisualEditor is on for everyone, labelling the tab ""edit source"" (even when ""edit"", i.e.', 'VisualEditor, is not available) seems like the best solution for our cluster.', '(If we wanted to, we could over-ride the value of the ""edit"" tab with a message from the Wikimedia-Messages system to do a WMF-specific over-ride of the MediaWiki default.)', 'However, fixing this before (b) is fixed, let alone whilst (a) is fixed, feels like the wrong way to do this.', 'A shorter-term fix is indeed to re-label ""edit"" to ""edit source"" for all pages visited by all users with VisualEditor.', 'Maybe we could do that.', 'Thoughts, Timo?']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+237033,"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)","I initially suggested updating the wording from ""Edit"" to ""Edit source"" at that VPT thread, and at https://en.wikipedia.org/wiki/MediaWiki_talk:Edit and at https://en.wikipedia.org/wiki/MediaWiki_talk:Vector-view-edit
+
+There are some good (and some not so good) suggestions and comments in the VPT thread. 
+
+Consistency would be ideal, and Eduard's suggestion above, seems to make the most sense.",task_subcomment,"['I initially suggested updating the wording from ""Edit"" to ""Edit source"" at that VPT thread, and at URL and at URL\n\nThere are some good (and some not so good) suggestions and comments in the VPT thread.', ""Consistency would be ideal, and Eduard's suggestion above, seems to make the most sense.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52395,VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it,"Try editing the professional ratings template in https://en.wikipedia.org/wiki/All_6%27s_and_7%27s?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50551
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50910
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51708",task_description,"[""VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it\n\nTry editing the professional ratings template in URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\nURL""]",['OBSERVED BUG BEHAVIOR']
+236683,VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it,"This issue also occurs for the following case:
+
+1.Add an image
+2.Add a gallery 
+3.Change the position of the image to the left 
+4.Select the gallery
+5.Try to select the image 
+
+Observed Result:
+Since the width of the phantom for the gallery is 100% , it is overlapping with the image and it becomes difficult to select the image after that.",task_subcomment,"['This issue also occurs for the following case:\n\n1.Add an image\n2.Add a gallery \n3.Change the position of the image to the left \n4.Select the gallery\n5.Try to select the image \n\nObserved Result:\nSince the width of the phantom for the gallery is 100% , it is overlapping with the image and it becomes difficult to select the image after that.']",['BUG REPRODUCTION']
+236678,VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it,*** Bug 51048 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51048 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236675,VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it,*** Bug 50443 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50443 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236669,VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it,*** Bug 50211 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50211 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236662,VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it,"Changed title to ""Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play. This can make it impossible to edit the floated item.",task_subcomment,"['Changed title to ""Phantoms can be width:100% when the object they\'re meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play.', 'This can make it impossible to edit the floated item.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52379,VisualEditor: Do not add size for standard thumbnail images when inserting them,"Wikicode for inserting animage in a standard ways into Wikipedia: 
+
+[[File:Name.jpg|thumb|Text]] without any size.
+
+VE adds a fixed size of 225x225px (why these numbers?) to the wikicode which is wrong for most Wikipedias.
+
+The size of a standard thumbnail depends on $wgThumbLimits and $wmgThumbsizeIndex or the size set in the user preference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://fr.wikipedia.org/w/index.php?title=Yael_Bartana&diff=94503286&oldid=90892725
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47804",task_description,"['VisualEditor: Do not add size for standard thumbnail images when inserting them\n\nWikicode for inserting animage in a standard ways into Wikipedia: \n\n[[File:Name.jpg|thumb|Text]] without any size.', 'VE adds a fixed size of 225x225px (why these numbers?)', 'to the wikicode which is wrong for most Wikipedias.', 'The size of a standard thumbnail depends on $wgThumbLimits and $wmgThumbsizeIndex or the size set in the user preference.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n**See Also**:\nURL']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+235724,VisualEditor: Do not add size for standard thumbnail images when inserting them,Done in gerrit 114420.,task_subcomment,['Done in gerrit 114420.'],['SOLUTION DISCUSSION']
+235719,VisualEditor: Do not add size for standard thumbnail images when inserting them,"I support this bug. Please dont add a size to the image by default. And show the size as tooltip, if user resizes it.",task_subcomment,"['I support this bug.', 'Please dont add a size to the image by default.', 'And show the size as tooltip, if user resizes it.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235713,VisualEditor: Do not add size for standard thumbnail images when inserting them,This bug doesn't depend on bug 38129 (and neither does it block it).,task_subcomment,"[""This bug doesn't depend on bug 38129 (and neither does it block it).""]",['BUG REPRODUCTION']
+235709,VisualEditor: Do not add size for standard thumbnail images when inserting them,"(In reply to comment #2)
+> Further the manual of style policy on image size
+> http://en.wikipedia.org/wiki/Wikipedia:IMGSIZE#Displayed_image_size
+> states that most images on the right hand side of the page should be scaled
+> to
+> 220 pixels wide. There need to be a way of specifying a precise numerical
+> size.
+
+No. This is a setting specified in the configuration file. No need to enter a precise numerical value. Per above policy: ""In general, do not define the size of an image"".",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo.', 'This is a setting specified in the configuration file.', 'No need to enter a precise numerical value.', 'Per above policy: ""In general, do not define the size of an image"".']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+235703,VisualEditor: Do not add size for standard thumbnail images when inserting them,"(In reply to comment #2)
+> Further the manual of style policy on image size
+> http://en.wikipedia.org/wiki/Wikipedia:IMGSIZE#Displayed_image_size
+> states that most images on the right hand side of the page should be scaled
+> to 220 pixels wide. There need to be a way of specifying a precise
+> numerical size.
+
+That will be done as part of bug 38129.",task_subcomment,['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat will be done as part of bug 38129.'],['SOLUTION DISCUSSION']
+235697,VisualEditor: Do not add size for standard thumbnail images when inserting them,"Further the manual of style policy on image size http://en.wikipedia.org/wiki/Wikipedia:IMGSIZE#Displayed_image_size
+states that most images on the right hand side of the page should be scaled to 220 pixels wide. There need to be a way of specifying a precise numerical size.",task_subcomment,"['Further the manual of style policy on image size URL\nstates that most images on the right hand side of the page should be scaled to 220 pixels wide.', 'There need to be a way of specifying a precise numerical size.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+235691,VisualEditor: Do not add size for standard thumbnail images when inserting them,*** Bug 50766 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50766 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52372,Updated TemplateData from transcluded items take a long time to show up,"TemplateData from transcluded items (i.e. doc pages) takes a long time to show up in the API. 
+
+A temporary solution to this is to do a [[ https://www.mediawiki.org/wiki/Manual:Purge#Null_edits | null edit  ]] (opening the page, and saving, without making any changes) which will cause the template data to propagate immediately. 
+",task_description,"['Updated TemplateData from transcluded items take a long time to show up\n\nTemplateData from transcluded items (i.e.', 'doc pages) takes a long time to show up in the API.', 'A temporary solution to this is to do a [[ URL | null edit  ]] (opening the page, and saving, without making any changes) which will cause the template data to propagate immediately.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'WORKAROUNDS']"
+2283032,Updated TemplateData from transcluded items take a long time to show up,"How about...
+Either
+A) add a shortcut somewhere in MW software to do a null template edit whenever its /doc page is saved (not everything has to be perfect)
+or
+B) add a note next to ""This template is missing TemplateData, and its parameters have been autogenerated"" so people know what's happening.
+
+TemplateData is already too cryptic, though helpful, and it's frustrating when things are not showing up in VE for days (10 days in my latest case), for no obvious reason. ",task_subcomment,"['How about...', 'Either\nA) add a shortcut somewhere in MW software to do a null template edit whenever its /doc page is saved (not everything has to be perfect)\nor\nB) add a note next to ""This template is missing TemplateData, and its parameters have been autogenerated"" so people know what\'s happening.', ""TemplateData is already too cryptic, though helpful, and it's frustrating when things are not showing up in VE for days (10 days in my latest case), for no obvious reason.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+1583940,Updated TemplateData from transcluded items take a long time to show up,A 7 year old task isn't UBN,task_subcomment,"[""A 7 year old task isn't UBN""]",['OBSERVED BUG BEHAVIOR']
+1583939,Updated TemplateData from transcluded items take a long time to show up,"> Quoted Text
+
+",task_subcomment,['QUOTE'],['SOLUTION DISCUSSION']
+1549544,Updated TemplateData from transcluded items take a long time to show up,"This continues to be a serious problem. 
+
+Someone deleted some template data on cy wiki from a template on June 24, and it actually broke automatic citaitons on visual editor for *a month* for all citations using the cite web template; even though the edits had since been reverted, but because it will still pulling through templatedata that was a month outdated (i.e. missing.) It wasn't fixed until I did a null edit. 
+
+Details here: T258335",task_subcomment,"['This continues to be a serious problem.', 'Someone deleted some template data on cy wiki from a template on June 24, and it actually broke automatic citaitons on visual editor for *a month* for all citations using the cite web template; even though the edits had since been reverted, but because it will still pulling through templatedata that was a month outdated (i.e.', 'missing.)', ""It wasn't fixed until I did a null edit."", 'Details here: T258335']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+1549542,Updated TemplateData from transcluded items take a long time to show up,"This continues to be a serious problem. 
+
+Someone deleted some template data on cy wiki from a template on June 24, and it actually broke automatic citaitons on visual editor for *a month* for all citations using the cite web template; even though the edits had since been reverted, but because it will still pulling through templatedata that was a month outdated (i.e. missing.)
+
+Details here: T258335",task_subcomment,"['This continues to be a serious problem.', 'Someone deleted some template data on cy wiki from a template on June 24, and it actually broke automatic citaitons on visual editor for *a month* for all citations using the cite web template; even though the edits had since been reverted, but because it will still pulling through templatedata that was a month outdated (i.e.', 'missing.)', 'Details here: T258335']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+1549541,Updated TemplateData from transcluded items take a long time to show up,"This continues to be a serious problem. 
+
+Someone deleted some template data on cy wiki from a template on June 24, and it actually broke automatic citaitons on visual editor for *a month* for all citations using the cite web template; even though the edits had since been reverted. 
+
+Details here: T258335",task_subcomment,"['This continues to be a serious problem.', 'Someone deleted some template data on cy wiki from a template on June 24, and it actually broke automatic citaitons on visual editor for *a month* for all citations using the cite web template; even though the edits had since been reverted.', 'Details here: T258335']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+1261760,Updated TemplateData from transcluded items take a long time to show up,"Content translation relies in templateData to transfer templates across languages. In particular, templateData is used to check the names and aliases of the parameters of the corresponding templates across languages. The current issue makes the process of fixing this even more complex for editors as the case of T219346 illustrates.",task_subcomment,"['Content translation relies in templateData to transfer templates across languages.', 'In particular, templateData is used to check the names and aliases of the parameters of the corresponding templates across languages.', 'The current issue makes the process of fixing this even more complex for editors as the case of T219346 illustrates.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+1185579,Updated TemplateData from transcluded items take a long time to show up,"This issue seems to be the reason why templates of the citation tool are not displayed in VisualEditor. Even a null commit does not resolve the problem, at least for me. Can we expect any bug resolution soon or is it too early/the task is too much difficult to handle it for now? I (and probably other users) really need to use templates.
+
+Thanks.
+
+EDIT: Making a null edit is still useful. However, if someone does not see a template after that, manually running all the job tasks will help, in case they appear to be frozen (or if it takes a really long time to execute all the tasks by the wiki). To do so, execute: ""php /maintenance/runJobs.php"".",task_subcomment,"['This issue seems to be the reason why templates of the citation tool are not displayed in VisualEditor.', 'Even a null commit does not resolve the problem, at least for me.', 'Can we expect any bug resolution soon or is it too early/the task is too much difficult to handle it for now?', 'I (and probably other users) really need to use templates.', 'Thanks.', 'EDIT: Making a null edit is still useful.', 'However, if someone does not see a template after that, manually running all the job tasks will help, in case they appear to be frozen (or if it takes a really long time to execute all the tasks by the wiki).', 'To do so, execute: ""php /maintenance/runJobs.php"".']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+1182940,Updated TemplateData from transcluded items take a long time to show up,"This issue seems to be the reason why templates of the citation tool are not displayed in VisualEditor. Even a null commit does not resolve the problem, at least for me. Can we expect any bug resolution soon or is it too early/the task is too much difficult to handle it for now? I (and probably other users) really need to use templates.
+
+Thanks.",task_subcomment,"['This issue seems to be the reason why templates of the citation tool are not displayed in VisualEditor.', 'Even a null commit does not resolve the problem, at least for me.', 'Can we expect any bug resolution soon or is it too early/the task is too much difficult to handle it for now?', 'I (and probably other users) really need to use templates.', 'Thanks.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1177245,Updated TemplateData from transcluded items take a long time to show up,"This is an ongoing issue. I was contacted today from a third party wiki wondering why their VE citation tool wasn't working, and the template data wasn't coming through. It was this problem. ",task_subcomment,"['This is an ongoing issue.', ""I was contacted today from a third party wiki wondering why their VE citation tool wasn't working, and the template data wasn't coming through."", 'It was this problem.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+438402,Updated TemplateData from transcluded items take a long time to show up,">>! In T52372#544516, @SalixAlba wrote:
+> What would be nice is if action=purge would force templatedata updates, like null edits do. This is necessary as many templates are protected so only admins can do null edits. Any editor can do an action=purge (I believe).
+
+Hear, hear!  And yes, I certainly //seem// to be able to purge pages I can't edit.",task_subcomment,"['QUOTE\nQUOTE\n\nHear, hear!', ""And yes, I certainly //seem// to be able to purge pages I can't edit.""]","['SOCIAL CONVERSATION', 'OBSERVED BUG BEHAVIOR']"
+235283,Updated TemplateData from transcluded items take a long time to show up,*** Bug 69647 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 69647 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235273,Updated TemplateData from transcluded items take a long time to show up,"(In reply to comment #23)
+> Thanks to Tim's fix this isn't
+> critical any more (users can 'just' null-edit touch the relevant template to
+> cause TemplateData content to come through)
+
+Note: This workaround only works for templates that aren't widely used.
+
+Widely-used templates are protected, and users can't null-edit them unless they are an admin (which drastically reduces the population of people who can add and edit TemplateData on the exact templates which would benefit from TemplateData most).",task_subcomment,"[""(In reply to comment #23)\nQUOTE\nQUOTE\nQUOTE\n\nNote: This workaround only works for templates that aren't widely used."", ""Widely-used templates are protected, and users can't null-edit them unless they are an admin (which drastically reduces the population of people who can add and edit TemplateData on the exact templates which would benefit from TemplateData most).""]","['SOLUTION USAGE', 'SOLUTION DISCUSSION']"
+235263,Updated TemplateData from transcluded items take a long time to show up,"Moving this to be a site issue, and re-grading. Thanks to Tim's fix this isn't critical any more (users can 'just' null-edit touch the relevant template to cause TemplateData content to come through), but it's very irritating and we need to fix it.",task_subcomment,"['Moving this to be a site issue, and re-grading.', ""Thanks to Tim's fix this isn't critical any more (users can 'just' null-edit touch the relevant template to cause TemplateData content to come through), but it's very irritating and we need to fix it.""]","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION']"
+235258,Updated TemplateData from transcluded items take a long time to show up,"What would be nice is if action=purge would force templatedata updates, like null edits do. This is necessary as many templates are protected so only admins can do null edits. Any editor can do an action=purge (I believe).",task_subcomment,"['What would be nice is if action=purge would force templatedata updates, like null edits do.', 'This is necessary as many templates are protected so only admins can do null edits.', 'Any editor can do an action=purge (I believe).']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+235253,Updated TemplateData from transcluded items take a long time to show up,"Tim's change https://gerrit.wikimedia.org/r/#/c/72679/ (deployed) seems to have made it possible to force templatedata updates by just performing a null edit on the affected template, which is now safe to do on highly-used templates. Note that a null edit is an edit made by just pressing ""Save page"" without making _any_ changes to the template code itself.",task_subcomment,"[""Tim's change URL (deployed) seems to have made it possible to force templatedata updates by just performing a null edit on the affected template, which is now safe to do on highly-used templates."", 'Note that a null edit is an edit made by just pressing ""Save page"" without making _any_ changes to the template code itself.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+235249,Updated TemplateData from transcluded items take a long time to show up,"You appear to just be seeing the effect of weeks of job queue lag, i.e. a system problem, not a MediaWiki problem.",task_subcomment,"['You appear to just be seeing the effect of weeks of job queue lag, i.e.', 'a system problem, not a MediaWiki problem.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+686122,Updated TemplateData from transcluded items take a long time to show up,"Observation:
+
+- Edite  block on Template:Pagetype/doc.
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype/doc
+  (with random query params to bust frontend cache)
+  It shows the updated data.
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype
+  (with random query to bust frontend cache)
+  It shows the old version still.
+- View https://en.wikipedia.org/wiki/Template:Pagetype
+  It shows the updated version in the HTML version of the data
+  (not sure whether the html update was triggered by a deferred update
+  as a result of me editing the sub page or by me viewing the page,
+  either way the output is updated).
+
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype/doc
+  (with random query to bust frontend cache)
+  It shows the updated data.
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype
+  (with random query to bust cache)
+  It shows the old version still.
+
+- Check https://en.wikipedia.org/w/api.php?format=jsonfm&action=query&meta=siteinfo&siprop=statistics and saw there are no pending jobs (not sure if this data is accurate though, it seemed to be accurate as edit count was going up on each refresh).
+
+
+- Make a null edit to ""Template:Pagetype"".
+
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype
+  (with random query to bust cache)
+
+  It now shows the latest data, update succeeded.
+
+
+So what is causing this to not be auto updated? I think T7382. But having trouble figuring out how come bug 5382 exists since we do have LinkUpdate and RefreshLinks2 which are triggered on edit from the job queue and update all pages linking to it, and the code in LinkUpdate includes all link tables and page properties.",task_subcomment,"['Observation:\n\n- Edite  block on Template:Pagetype/doc.', '- View URL\n  (with random query params to bust frontend cache)\n  It shows the updated data.', '- View URL\n  (with random query to bust frontend cache)\n  It shows the old version still.', '- View URL\n  It shows the updated version in the HTML version of the data\n  (not sure whether the html update was triggered by a deferred update\n  as a result of me editing the sub page or by me viewing the page,\n  either way the output is updated).', '- View URL\n  (with random query to bust frontend cache)\n  It shows the updated data.', '- View URL\n  (with random query to bust cache)\n  It shows the old version still.', '- Check URL and saw there are no pending jobs (not sure if this data is accurate though, it seemed to be accurate as edit count was going up on each refresh).', '- Make a null edit to ""Template:Pagetype"".', '- View URL\n  (with random query to bust cache)\n\n  It now shows the latest data, update succeeded.', 'So what is causing this to not be auto updated?', 'I think T7382.', 'But having trouble figuring out how come bug 5382 exists since we do have LinkUpdate and RefreshLinks2 which are triggered on edit from the job queue and update all pages linking to it, and the code in LinkUpdate includes all link tables and page properties.']","['SOLUTION DISCUSSION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+235245,Updated TemplateData from transcluded items take a long time to show up,"Observation:
+
+- Edite  block on Template:Pagetype/doc.
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype/doc
+  (with random query params to bust frontend cache)
+  It shows the updated data.
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype
+  (with random query to bust frontend cache)
+  It shows the old version still.
+- View https://en.wikipedia.org/wiki/Template:Pagetype
+  It shows the updated version in the HTML version of the data
+  (not sure whether the html update was triggered by a deferred update
+  as a result of me editing the sub page or by me viewing the page,
+  either way the output is updated).
+
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype/doc
+  (with random query to bust frontend cache)
+  It shows the updated data.
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype
+  (with random query to bust cache)
+  It shows the old version still.
+
+- Check https://en.wikipedia.org/w/api.php?format=jsonfm&action=query&meta=siteinfo&siprop=statistics and saw there are no pending jobs (not sure if this data is accurate though, it seemed to be accurate as edit count was going up on each refresh).
+
+
+- Make a null edit to ""Template:Pagetype"".
+
+- View https://en.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Template:Pagetype
+  (with random query to bust cache)
+
+  It now shows the latest data, update succeeded.
+
+
+So what is causing this to not be auto updated? I think bug 5382. But having trouble figuring out how come bug 5382 exists since we do have LinkUpdate and RefreshLinks2 which are triggered on edit from the job queue and update all pages linking to it, and the code in LinkUpdate includes all link tables and page properties.",task_subcomment,"['Observation:\n\n- Edite  block on Template:Pagetype/doc.', '- View URL\n  (with random query params to bust frontend cache)\n  It shows the updated data.', '- View URL\n  (with random query to bust frontend cache)\n  It shows the old version still.', '- View URL\n  It shows the updated version in the HTML version of the data\n  (not sure whether the html update was triggered by a deferred update\n  as a result of me editing the sub page or by me viewing the page,\n  either way the output is updated).', '- View URL\n  (with random query to bust frontend cache)\n  It shows the updated data.', '- View URL\n  (with random query to bust cache)\n  It shows the old version still.', '- Check URL and saw there are no pending jobs (not sure if this data is accurate though, it seemed to be accurate as edit count was going up on each refresh).', '- Make a null edit to ""Template:Pagetype"".', '- View URL\n  (with random query to bust cache)\n\n  It now shows the latest data, update succeeded.', 'So what is causing this to not be auto updated?', 'I think bug 5382.', 'But having trouble figuring out how come bug 5382 exists since we do have LinkUpdate and RefreshLinks2 which are triggered on edit from the job queue and update all pages linking to it, and the code in LinkUpdate includes all link tables and page properties.']","['SOLUTION DISCUSSION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+235240,Updated TemplateData from transcluded items take a long time to show up,"Timo has narrowed down the issue to bug 5382 - we're working now to see whether we can fix that bug and so resolve this, or whether that will put too much weight on the cluster.",task_subcomment,"[""Timo has narrowed down the issue to bug 5382 - we're working now to see whether we can fix that bug and so resolve this, or whether that will put too much weight on the cluster.""]",['INVESTIGATION AND EXPLORATION']
+235235,Updated TemplateData from transcluded items take a long time to show up,"Thought I'd drop a note and say that when I tried a null edit on https://en.wikipedia.org/wiki/Template:Mileposts, the overall template description loaded right away on https://en.wikipedia.org/wiki/British_Columbia_Highway_7. However, the parameter description (km=) did not load until I deleted the template from the article and reinserted the template anew.",task_subcomment,"[""Thought I'd drop a note and say that when I tried a null edit on URL the overall template description loaded right away on URL However, the parameter description (km=) did not load until I deleted the template from the article and reinserted the template anew.""]",['OBSERVED BUG BEHAVIOR']
+235228,Updated TemplateData from transcluded items take a long time to show up,"I added[1] templatedata to en.wiki [[Template:Redirect]] yesterday (through the /doc transclusion) and also noticed that the main template page wasn't updating (I waited for about 10 minutes).
+
+Then I did a null-edit on Template:Redirect and it was instantly there.
+
+Roan mentioned something earlier (IRC or IRL, don't remember) about this perhaps being caused by the JobQueue (which we use to invalidate pages transcluding other pages, in this case the transclusion of /doc into Template:. *NOT* the transclusion of Template into articles, of course, that'd be insane).
+
+CC-ing Roan, Tim and Aaron who may have more ideas about the cause of this.
+
+As for TemplateData itself, it is triggered as a extension parser tag () and during the parsing it adds page properties which MediaWiki ends up storing in the page_props db table. The API does a read query from that same table. Pretty basic.
+
+So what could cause the read query to the page_props table to be delayed (or perhaps even not happen at all?) from the page properties added by a page that is transcluded (Template:Foo/doc) into a template page (Template:Foo).
+
+JobQueue? Database replication? Something else?
+
+Note that in my testing yesterday on Template:Redirect I ruled out HTTP caching (API cluster Squid) by making unique urls each time.
+
+
+[1] https://en.wikipedia.org/w/index.php?title=Template%3ARedirect%2Fdoc&diff=562472124&oldid=562471783",task_subcomment,"[""I added[1] templatedata to en.wiki [[Template:Redirect]] yesterday (through the /doc transclusion) and also noticed that the main template page wasn't updating (I waited for about 10 minutes)."", 'Then I did a null-edit on Template:Redirect and it was instantly there.', ""Roan mentioned something earlier (IRC or IRL, don't remember) about this perhaps being caused by the JobQueue (which we use to invalidate pages transcluding other pages, in this case the transclusion of /doc into Template:."", ""*NOT* the transclusion of Template into articles, of course, that'd be insane)."", 'CC-ing Roan, Tim and Aaron who may have more ideas about the cause of this.', 'As for TemplateData itself, it is triggered as a extension parser tag () and during the parsing it adds page properties which MediaWiki ends up storing in the page_props db table.', 'The API does a read query from that same table.', 'Pretty basic.', 'So what could cause the read query to the page_props table to be delayed (or perhaps even not happen at all?)', 'from the page properties added by a page that is transcluded (Template:Foo/doc) into a template page (Template:Foo).', 'JobQueue?', 'Database replication?', 'Something else?', 'Note that in my testing yesterday on Template:Redirect I ruled out HTTP caching (API cluster Squid) by making unique urls each time.', '[1] URL']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+235224,Updated TemplateData from transcluded items take a long time to show up,"Wouldn't we avoid this delay if the template data were in a specific namespace, instead of being saved in one page, which is transcluded in another, which on its turn may be transcluded another, and so on, until the data finally gets to the template? See bug 50512.",task_subcomment,"[""Wouldn't we avoid this delay if the template data were in a specific namespace, instead of being saved in one page, which is transcluded in another, which on its turn may be transcluded another, and so on, until the data finally gets to the template?"", 'See bug 50512.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+235218,Updated TemplateData from transcluded items take a long time to show up,"The extension page says:
+
+""The TemplateData extension works through having a  tag defined in the wikitext of a template page (optionally it can be transcluded into the template page as well). This is designed to be compatible with the common layout many wikis have of transcluding template documentation from a separate page (but is not required).""
+
+And this seems to work partly, e.g. for https://en.wikipedia.org/wiki/Template:Italic_title.  TemplateData is at https://en.wikipedia.org/wiki/Template:Italic_title/doc and it comes up at https://en.wikipedia.org/w/api.php?action=templatedata&titles=Template:Italic%20title&format=jsonfm , but it doesn't seem to actually work in VE (e.g. no description).
+
+Then, https://en.wikipedia.org/wiki/Template:Dead_link appears set up similar, with TemplateData at https://en.wikipedia.org/wiki/Template:Dead_link/doc .  But it does not come up at https://en.wikipedia.org/w/api.php?action=templatedata&titles=Template:Dead%20link&format=jsonfm .  It does come up at https://en.wikipedia.org/w/api.php?action=templatedata&titles=Template:Dead%20link/doc&format=jsonfm (explicitly asking for the /doc page).",task_subcomment,"['The extension page says:\n\n""The TemplateData extension works through having a  tag defined in the wikitext of a template page (optionally it can be transcluded into the template page as well).', 'This is designed to be compatible with the common layout many wikis have of transcluding template documentation from a separate page (but is not required).""', 'And this seems to work partly, e.g.', ""for URL  TemplateData is at URL and it comes up at URL , but it doesn't seem to actually work in VE (e.g."", 'no description).', 'Then, URL appears set up similar, with TemplateData at URL .', 'But it does not come up at URL .', 'It does come up at URL (explicitly asking for the /doc page).']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235211,Updated TemplateData from transcluded items take a long time to show up,"Indeed, I cannot see templatedata hinting on en.wp for _any_ templates supposedly annotated per https://en.wikipedia.org/w/api.php?action=query&list=pageswithprop&pwppropname=templatedata&pwpprop=ids|title|value&format=jsonfm and https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/TemplateData . Escalating priority.",task_subcomment,"['Indeed, I cannot see templatedata hinting on en.wp for _any_ templates supposedly annotated per URL and URL .', 'Escalating priority.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+235205,Updated TemplateData from transcluded items take a long time to show up,https://en.wikipedia.org/wiki/Template:Mileposts was updated 48 hours ago and still hasn't shown. That seems like a time period even the squids should blink at.,task_subcomment,"[""URL was updated 48 hours ago and still hasn't shown."", 'That seems like a time period even the squids should blink at.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+235199,Updated TemplateData from transcluded items take a long time to show up,"Though it is possible that VisualEditor and/or TemplateData do something wrong, in general there's nothing relevant in either VisualEditor or TemplateData that can delay the updating of the data.
+
+The template data is changes by users by editing the wikitext of a Template page (or a page transcluded into a Template page). When they click ""Save page"", the MediaWiki parser detects the  tag, tells the TemplateData extension to make sense of it, which then adds (or replaces) the parsed data in the database.
+
+There is no deferred update here, it is replaced directly.
+
+The API request to fetch templatedata grabs it directly from the database. This isn't specifically cached in anyway.
+
+The only caching layer is in your browser cache and the general cache in the Wikimedia cluster for HTTP requests to content domain names (e.g. ""en.wikipedia.org"") which is Squid.",task_subcomment,"[""Though it is possible that VisualEditor and/or TemplateData do something wrong, in general there's nothing relevant in either VisualEditor or TemplateData that can delay the updating of the data."", 'The template data is changes by users by editing the wikitext of a Template page (or a page transcluded into a Template page).', 'When they click ""Save page"", the MediaWiki parser detects the  tag, tells the TemplateData extension to make sense of it, which then adds (or replaces) the parsed data in the database.', 'There is no deferred update here, it is replaced directly.', 'The API request to fetch templatedata grabs it directly from the database.', ""This isn't specifically cached in anyway."", 'The only caching layer is in your browser cache and the general cache in the Wikimedia cluster for HTTP requests to content domain names (e.g.', '""en.wikipedia.org"") which is Squid.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+235193,Updated TemplateData from transcluded items take a long time to show up,"The behavior seems inconsistent. Today, TemplateData was available in transclusions immediately after adding it to the template's documentation subpage. (tested with https://fr.wikipedia.org/wiki/Mod%C3%A8le:Unit%C3%A9 )",task_subcomment,"['The behavior seems inconsistent.', ""Today, TemplateData was available in transclusions immediately after adding it to the template's documentation subpage."", '(tested with URL )']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+235187,Updated TemplateData from transcluded items take a long time to show up,"Argh, that's not good - https://en.wikipedia.org/w/api.php?action=templatedata&titles=Template:Talkback is not updated even though it appears in transclusion, even after purge. Timo, thoughts?",task_subcomment,"[""Argh, that's not good - URL is not updated even though it appears in transclusion, even after purge."", 'Timo, thoughts?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+235179,Updated TemplateData from transcluded items take a long time to show up,https://en.wikipedia.org/wiki/User:Okeyes_%28WMF%29/sandbox?veaction=edit <- check out the talkpage template.,task_subcomment,['URL <- check out the talkpage template.'],['SOLUTION DISCUSSION']
+235173,Updated TemplateData from transcluded items take a long time to show up,"(In reply to comment #6)
+> Nope; remember that time I added it to the bugzilla tracked template, and
+> nothing happened?
+
+No.
+
+> Well, it started working finally some time today.
+
+That's not good. Did you purge the template, or did it get purged somehow (e.g. it was edited)?
+
+> I'm going to try implementing it in a couple of other minor places and look
+> at what happens.
+
+OK.",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\n\nNo.', ""QUOTE\n\nThat's not good."", 'Did you purge the template, or did it get purged somehow (e.g.', 'it was edited)?', 'QUOTE\nQUOTE\n\nOK.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+235167,Updated TemplateData from transcluded items take a long time to show up,"Nope; remember that time I added it to the bugzilla tracked template, and nothing happened? Well, it started working finally some time today. I'm going to try implementing it in a couple of other minor places and look at what happens.",task_subcomment,"['Nope; remember that time I added it to the bugzilla tracked template, and nothing happened?', 'Well, it started working finally some time today.', ""I'm going to try implementing it in a couple of other minor places and look at what happens.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+235160,Updated TemplateData from transcluded items take a long time to show up,"(In reply to comment #4)
+> I'd go with A and C, Chris. If I add TemplateData to a template, go to an
+> implementation of it that already exists and click the jigsaw piece, how long
+> do I need between those actions to see the TemplateData?
+
+A: This should be instantaneous - if not, action=purge on the template should do it; if not, this is an issue we need to follow-up in general with how MW works.
+B: This is not yet done (bug 49778 which is being worked on right now).
+C: This should be near-instantaneous (but we're about to change how this works to make it faster).
+
+For A & C in particular as you've asked, seconds or even less. Was this during a time of serious server strain, maybe? Otherwise it sounds worrying.",task_subcomment,"['(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\n\nA: This should be instantaneous - if not, action=purge on the template should do it; if not, this is an issue we need to follow-up in general with how MW works.', 'B: This is not yet done (bug 49778 which is being worked on right now).', ""C: This should be near-instantaneous (but we're about to change how this works to make it faster)."", ""For A & C in particular as you've asked, seconds or even less."", 'Was this during a time of serious server strain, maybe?', 'Otherwise it sounds worrying.']","['ACTION ON ISSUE', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235155,Updated TemplateData from transcluded items take a long time to show up,"I'd go with A and C, Chris. If I add TemplateData to a template, go to an implementation of it that already exists and click the jigsaw piece, how long do I need between those actions to see the TemplateData?",task_subcomment,"[""I'd go with A and C, Chris."", 'If I add TemplateData to a template, go to an implementation of it that already exists and click the jigsaw piece, how long do I need between those actions to see the TemplateData?']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+235150,Updated TemplateData from transcluded items take a long time to show up,"(In reply to comment #2)
+> As does the fr implementation. I guess the question here is ""how long does it
+> take for TemplateData implementations to show up?""
+
+Do you mean,
+
+* ""how long does it take newly-added TemplateData hinting to become available in the API for use in VisualEditor?"",
+* ""how long does it take the VisualEditor transclusions dialog to show with the TemplateData hinting when adding a template in?"", or
+* ""how long does it take the VisualEditor transclusions dialog to show with the TemplateData hinting on load?""
+
+… or something else?",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\n\nDo you mean,\n\n* ""how long does it take newly-added TemplateData hinting to become available in the API for use in VisualEditor?', '"",\n* ""how long does it take the VisualEditor transclusions dialog to show with the TemplateData hinting when adding a template in?', '"", or\n* ""how long does it take the VisualEditor transclusions dialog to show with the TemplateData hinting on load?""', '… or something else?']","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+235144,Updated TemplateData from transcluded items take a long time to show up,"As does the fr implementation. I guess the question here is ""how long does it take for TemplateData implementations to show up?""",task_subcomment,"['As does the fr implementation.', 'I guess the question here is ""how long does it take for TemplateData implementations to show up?""']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235139,Updated TemplateData from transcluded items take a long time to show up,"Belay that, {{tracked}} works.",task_subcomment,"['Belay that, {{tracked}} works.']",['SOLUTION DISCUSSION']
+52369,Section edit links disappear following an unclosed {{,"This was seen in revisions prior to https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=561926823&oldid=561926781 and fixed in that revision.
+
+For a reduced testcase see . The cause seems to be the unclosed `{{`. Of course, this is broken wikitext, but the parser seems to be able to handle it fine (other than leaving out section edit links).
+
+Sorry I can't be more specific.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=73182",task_description,"['Section edit links disappear following an unclosed {{\n\nThis was seen in revisions prior to URL and fixed in that revision.', 'For a reduced testcase see  This cannot easily be parsed in Parsoid while also retaining round-trip
+> information. And even if we could, this would be very hard to represent in
+> HTML so that the VisualEditor can present a sensible user interface for it. So
+> this will remain a limitation of Parsoid.
+
+I'd like to know how many pages are affected by this bug across Wikimedia wikis before it's marked wontfix. Re-opening this for now.",task_subcomment,"[""(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI'd like to know how many pages are affected by this bug across Wikimedia wikis before it's marked wontfix."", 'Re-opening this for now.']","['INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE']"
+234759,Templates that create part (but not all) of a table cell don't work,"The issue is normally something of this form:
+
+{|
+| {{style-and-cell}}
+|}
+
+The transclusion returns some attributes and possibly table content.
+
+This cannot easily be parsed in Parsoid while also retaining round-trip information. And even if we could, this would be very hard to represent in HTML so that the VisualEditor can present a sensible user interface for it. So this will remain a limitation of Parsoid.
+
+This issue can however be avoided by changing the template to return the entire table cell including the leading pipe:
+
+{|
+{{style-and-cell}}
+|}
+
+with {{style-and-cell}} containing:
+
+| style=""the style"" | The cell content",task_subcomment,"['The issue is normally something of this form:\n\n{|\n| {{style-and-cell}}\n|}\n\nThe transclusion returns some attributes and possibly table content.', 'This cannot easily be parsed in Parsoid while also retaining round-trip information.', 'And even if we could, this would be very hard to represent in HTML so that the VisualEditor can present a sensible user interface for it.', 'So this will remain a limitation of Parsoid.', 'This issue can however be avoided by changing the template to return the entire table cell including the leading pipe:\n\n{|\n{{style-and-cell}}\n|}\n\nwith {{style-and-cell}} containing:\n\n| style=""the style"" | The cell content']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+234755,Templates that create part (but not all) of a table cell don't work,"Parsoid bug, it doesn't seem to like {{won}} and {{nom}}, see http://parsoid.wmflabs.org/en/Rage_Against_the_Machine",task_subcomment,"[""Parsoid bug, it doesn't seem to like {{won}} and {{nom}}, see URL""]",['OBSERVED BUG BEHAVIOR']
+234748,Templates that create part (but not all) of a table cell don't work,See also https://en.wikipedia.org/wiki/Akon_discography?veaction=edit from bug 50532.,task_subcomment,['See also URL from bug 50532.'],['OBSERVED BUG BEHAVIOR']
+234743,Templates that create part (but not all) of a table cell don't work,*** Bug 50532 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50532 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52363,VisualEditor: Hatnote templates not displaying properly,"How the hatnote appears in the VE when it is added
+
+This takes some effort to replicate, so bear with me; if you insert a hatnote at the beginning of a line, it renders improperly in the VisualEditor - despite rendering properly in the article text, /and/ in subsequent loads of the VE. Screenshots of each attached.
+
+As User:PamD adeptly summarises, ""if VE doesn't display the result of a change, or displays it looking wrong, editors are going to assume that their edit didn't work and struggle to ""fix"" it""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11145}",task_description,"['VisualEditor: Hatnote templates not displaying properly\n\nHow the hatnote appears in the VE when it is added\n\nThis takes some effort to replicate, so bear with me; if you insert a hatnote at the beginning of a line, it renders improperly in the VisualEditor - despite rendering properly in the article text, /and/ in subsequent loads of the VE.', 'Screenshots of each attached.', 'As User:PamD adeptly summarises, ""if VE doesn\'t display the result of a change, or displays it looking wrong, editors are going to assume that their edit didn\'t work and struggle to ""fix"" it""\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11145}']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+234589,VisualEditor: Hatnote templates not displaying properly,"Fair play; marking as duplicate.
+
+%%%*** This bug has been marked as a duplicate of bug 49784 ***%%%",task_subcomment,"['Fair play; marking as duplicate.', '%%%*** This bug has been marked as a duplicate of bug 49784 ***%%%']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+234585,VisualEditor: Hatnote templates not displaying properly,"So, I've read this a number of times and I'm not quite sure I know what you're getting at.
+
+Steps:
+
+1. Go into a page
+2. Click into a blank line; insert template ""Hatnote"", parameter 1 = ""Foo"".
+3. Template appears on its own line, as expected.
+4. Template saves on its own line, as expected.
+5. Page rendered with template in the right place, as expected
+6. Edit article.
+7. Template is still there in VisualEditor, as expected.
+
+Try two:
+
+1. Go into a page
+2. Click into the start of a non-blank line; insert template ""Hatnote"", parameter 1 = ""Foo"".
+3. Template appears at the start of the line, a little oddly as it's a 
    , because of bug 49784.
+4. Template saves at the start of the line, as expected.
+5. Page rendered with template on its own line, as expected.
+6. Edit article.
+7. Template is still there in VisualEditor at the start of the line, as before.
+
+I assume you mean that this is an issue because it doesn't show up on its own line? If so, this is just a plain duplicate of bug 49784.",task_subcomment,"[""So, I've read this a number of times and I'm not quite sure I know what you're getting at."", 'Steps:\n\n1.', 'Go into a page\n2.', 'Click into a blank line; insert template ""Hatnote"", parameter 1 = ""Foo"".', '3.', 'Template appears on its own line, as expected.', '4.', 'Template saves on its own line, as expected.', '5.', 'Page rendered with template in the right place, as expected\n6.', 'Edit article.', '7.', 'Template is still there in VisualEditor, as expected.', 'Try two:\n\n1.', 'Go into a page\n2.', 'Click into the start of a non-blank line; insert template ""Hatnote"", parameter 1 = ""Foo"".', '3.', ""Template appears at the start of the line, a little oddly as it's a 
    , because of bug 49784."", '4.', 'Template saves at the start of the line, as expected.', '5.', 'Page rendered with template on its own line, as expected.', '6.', 'Edit article.', '7.', 'Template is still there in VisualEditor at the start of the line, as before.', ""I assume you mean that this is an issue because it doesn't show up on its own line?"", 'If so, this is just a plain duplicate of bug 49784.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+234579,VisualEditor: Hatnote templates not displaying properly,"How the hatnote appears in subsequent VE loads.
+
+**Attached**: {F11148}",task_subcomment,"['How the hatnote appears in subsequent VE loads.', '**Attached**: {F11148}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+234573,VisualEditor: Hatnote templates not displaying properly,"How the hatnote appears in ""read"" mode
+
+**Attached**: {F11146}",task_subcomment,"['How the hatnote appears in ""read"" mode\n\n**Attached**: {F11146}']",['OBSERVED BUG BEHAVIOR']
+52358,VisualEditor: backspacing sometimes inserts a breaking space,"See Kelvinsong's wonderfully detailed bug report at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=561944647#The_Chloroplast_Test.E2.80.94June_26_C
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: backspacing sometimes inserts a breaking space\n\nSee Kelvinsong's wonderfully detailed bug report at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal""]",['OBSERVED BUG BEHAVIOR']
+445979,VisualEditor: backspacing sometimes inserts a breaking space,"Perhaps I am dense, but I do not understand what this bug was about even after reading the linked discussion.",task_subcomment,"['Perhaps I am dense, but I do not understand what this bug was about even after reading the linked discussion.']",['OBSERVED BUG BEHAVIOR']
+52355,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","Many templates serve merely as wrapper around free-form wikitext content. TemplateData specifies the parameter type ""content"" for this purpose.
+
+This task tracks the implementation in VisualEditor to provide an edit surface for editing the values of these parameter. Similar to how we already support rich editing of the content inside References.
+
+Use cases:
+* Wrap-templates. Such as message boxes, and the parameter-consuming variants of the ""something-start""/""something-end"" templates.
+* Nested infoboxes.
+* Simple infobox fields that support text but allow/encourage use of inline templates for formatting. Currently these expose raw wikitext to end-users.
+
+>>! @Ironholds wrote
+> A lot of infoboxes et al - the one on https://en.wikipedia.org/wiki/Fulgencio_(Modern_Family) comes to mind - have infoboxes /within/ the infoboxes that need editing. I'm not sure what the answer is here - it feels wrong, somehow, to offer an infinitely deep template inspector inside a template inspector inside...etc, but I can't think of another solution short of manually going around making the template namespace make sense or accepting that users will always have to learn markup, just not immediately.
+
+",task_description,"['VisualEditor: Add support for editing templates\' parameters as DOM elements (""visually""), including supporting nested templates\n\nMany templates serve merely as wrapper around free-form wikitext content.', 'TemplateData specifies the parameter type ""content"" for this purpose.', 'This task tracks the implementation in VisualEditor to provide an edit surface for editing the values of these parameter.', 'Similar to how we already support rich editing of the content inside References.', 'Use cases:\n* Wrap-templates.', 'Such as message boxes, and the parameter-consuming variants of the ""something-start""/""something-end"" templates.', '* Nested infoboxes.', '* Simple infobox fields that support text but allow/encourage use of inline templates for formatting.', 'Currently these expose raw wikitext to end-users.', 'QUOTE\nQUOTE']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1623159,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates",https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Editing_templates_recursively,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+1198564,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","Basically, the central thing for me would be this:
+
+Some templates are difficult (infoboxes) and some templates are easy ({{[[ http://en.wikipedia.org/wiki/Template:Quote | Quote ]]}}, {{[[ https://en.wikipedia.org/wiki/Template:Lang-it | lang-it ]]}}). VE allows editing links and bold text directly as first-class content element, but all templates are seen by VE as templates and not as formatting, and forces users to edit their content using the dialog. The result is that it's easier to edit such templates in wiki syntax (if you know which parameter to change, of course) than in VE for everyone: both wiki syntax lovers and newer people who like VE.
+
+If VE could allow editing at least //some// simpler templates as just text, and treat them as custom formatting rather than a complex form, this would make editing much easier. Perhaps TemplateData could be modified to allow specifying some parameters as ""directly-editable"" or something.
+
+I understand it's not trivial and requires some development time, but it's worth revisiting this.",task_subcomment,"['Basically, the central thing for me would be this:\n\nSome templates are difficult (infoboxes) and some templates are easy ({{[[ URL | Quote ]]}}, {{[[ URL | lang-it ]]}}).', 'VE allows editing links and bold text directly as first-class content element, but all templates are seen by VE as templates and not as formatting, and forces users to edit their content using the dialog.', ""The result is that it's easier to edit such templates in wiki syntax (if you know which parameter to change, of course) than in VE for everyone: both wiki syntax lovers and newer people who like VE."", 'If VE could allow editing at least //some// simpler templates as just text, and treat them as custom formatting rather than a complex form, this would make editing much easier.', 'Perhaps TemplateData could be modified to allow specifying some parameters as ""directly-editable"" or something.', ""I understand it's not trivial and requires some development time, but it's worth revisiting this.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1194819,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","Change 451020 abandoned by Bartosz Dziewoński:
+Working on Task #T52355 - ve.ui.MWTemplateDialog and ve.ui.MWParameterPage changed.
+
+Reason:
+Patch doesn't seem to actually do anything related to task T52355, no response from submitter
+
+[[https://gerrit.wikimedia.org/r/451020]]",task_subcomment,"['Change 451020 abandoned by Bartosz Dziewoński:\nWorking on Task #T52355 - ve.ui.MWTemplateDialog and ve.ui.MWParameterPage changed.', ""Reason:\nPatch doesn't seem to actually do anything related to task T52355, no response from submitter\n\n[[GERRIT_URL]]""]","['INVESTIGATION AND EXPLORATION', 'GERRIT_URL']"
+1118225,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","Change 451020 had a related patch set uploaded (by Chris Barnard; owner: Chris Barnard):
+[mediawiki/extensions/VisualEditor@master] Working on Task #T52355 - ve.ui.MWTemplateDialog and ve.ui.MWParameterPage changed.
+
+[[https://gerrit.wikimedia.org/r/451020]]",task_subcomment,"['Change 451020 had a related patch set uploaded (by Chris Barnard; owner: Chris Barnard):\n[mediawiki/extensions/VisualEditor@master] Working on Task #T52355 - ve.ui.MWTemplateDialog and ve.ui.MWParameterPage changed.', '[[GERRIT_URL]]']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+1035824,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","There is no facepalm token, so consider this little goat as the facepalm token, because still we literally force VE users to use wikicode for nested templates.",task_subcomment,"['There is no facepalm token, so consider this little goat as the facepalm token, because still we literally force VE users to use wikicode for nested templates.']",['SOLUTION DISCUSSION']
+1035822,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","There is no facepalm token, so consider this little goat as the facepalm token, because we literally force VE users to use wikicode for nested templates.",task_subcomment,"['There is no facepalm token, so consider this little goat as the facepalm token, because we literally force VE users to use wikicode for nested templates.']",['SOLUTION DISCUSSION']
+622141,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","> Wikitext button should look depressed when used. MW theme needs this to be improved mode generally. Need to avoid mode error
+
+Would a ButtonSelectWidget make sense here?",task_subcomment,['QUOTE\n\nWould a ButtonSelectWidget make sense here?'],['SOLUTION DISCUSSION']
+621649,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","Comments from discussion about this:
+
+* Wikitext button should look depressed when used. MW theme needs this to be improved mode generally. Need to avoid mode error
+* Important to remember that the types aren’t for validation, just hints – don’t frustrate the user if they want to over-ride, make it easy to replace.
+* Styling of wikitext mode needs improving.
+* Need to separate “allowing to use VE” from “helping with type hinting”
+* Flow has this issue too (switching mode) – share feature design?
+* Edge case (partial wikitext) for not being able to use VE isn’t very common, we believe?
+* One switch for the whole dialog?
+** Issues?
+** In Advanced mode? (alongside multi-template transclusion editing)
+* Possibly get rid of the (i) too, to simplify the clutter around boxes?
+",task_subcomment,"['Comments from discussion about this:\n\n* Wikitext button should look depressed when used.', 'MW theme needs this to be improved mode generally.', 'Need to avoid mode error\n* Important to remember that the types aren’t for validation, just hints – don’t frustrate the user if they want to over-ride, make it easy to replace.', '* Styling of wikitext mode needs improving.', '* Need to separate “allowing to use VE” from “helping with type hinting”\n* Flow has this issue too (switching mode) – share feature design?', '* Edge case (partial wikitext) for not being able to use VE isn’t very common, we believe?', '* One switch for the whole dialog?', '** Issues?', '** In Advanced mode?', '(alongside multi-template transclusion editing)\n* Possibly get rid of the (i) too, to simplify the clutter around boxes?']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+621561,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates",">>! In T52355#2079713, @Esanders wrote:
+> @Ironholds the page has become a disambig since you filed. Looking at the history were you linking to https://en.wikipedia.org/wiki/Fulgencio_(Modern_Family) originally?
+
+I fixed the link.",task_subcomment,['QUOTE\nQUOTE\n\nI fixed the link.'],['SOLUTION USAGE']
+621413,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","I have literally no idea, it was in 2014.",task_subcomment,"['I have literally no idea, it was in 2014.']",['OBSERVED BUG BEHAVIOR']
+621352,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates",@Ironholds the page has become a disambig since you filed. Looking at the history were you linking to https://en.wikipedia.org/wiki/Fulgencio_(Modern_Family) originally?,task_subcomment,"['SCREEN_NAME the page has become a disambig since you filed.', 'Looking at the history were you linking to URL originally?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+620273,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","Current thinking about switching modes:
+
+| Basic appearance | {F3459623}
+| Editing with support | {F3459624}
+| Switched to 'wikitext' mode | {F3459622}
+",task_subcomment,"[""Current thinking about switching modes:\n\n| Basic appearance | {F3459623}\n| Editing with support | {F3459624}\n| Switched to 'wikitext' mode | {F3459622}""]",['INVESTIGATION AND EXPLORATION']
+234152,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","Re-wording; this isn't a duplicate of bug 50182, which is about non-dialog editing of templates.",task_subcomment,"[""Re-wording; this isn't a duplicate of bug 50182, which is about non-dialog editing of templates.""]",['OBSERVED BUG BEHAVIOR']
+234146,"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","
+
+*** This bug has been marked as a duplicate of bug 50182 ***",task_subcomment,['\n\n*** This bug has been marked as a duplicate of bug 50182 ***'],['ACTION ON ISSUE']
+52354,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"The current workflow for adding a new template; you add the template, you add parameter 1, you go to add parameter 2...only you can't, because adding parameter 1 jumped you to an entirely new tab that doesn't contain a mechanism for adding parameter 2.
+
+It'd be good to have some mechanism to add additional parameters that is more intuitive - something as simple as not jumping a user to the parameter page, even. I appreciate bug 49778 partially solves for this but it's going to be a looong time before all our templates have templatedata.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51774
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49772",task_description,"[""VisualEditor: Transclusion dialog should make it easier to add parameters and see other values\n\nThe current workflow for adding a new template; you add the template, you add parameter 1, you go to add parameter 2...only you can't, because adding parameter 1 jumped you to an entirely new tab that doesn't contain a mechanism for adding parameter 2."", ""It'd be good to have some mechanism to add additional parameters that is more intuitive - something as simple as not jumping a user to the parameter page, even."", ""I appreciate bug 49778 partially solves for this but it's going to be a looong time before all our templates have templatedata."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+234089,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"I think these are all now tracked in bug 53604's dependencies, which is a more scalable way to find, triage and fix bugs; consequently, closing this as INVALID (though each of its suggestions are of course real bugs or enhancements).",task_subcomment,"[""I think these are all now tracked in bug 53604's dependencies, which is a more scalable way to find, triage and fix bugs; consequently, closing this as INVALID (though each of its suggestions are of course real bugs or enhancements).""]",['BUG REPRODUCTION']
+234083,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"(In reply to comment #11)
+> << For templates, it would be helpful to provide some links to the actual
+> template page from the transclusion dialog. At least a direct link, but
+> perhaps
+> something like v*t*e (view/talk/edit) like included in many navigation
+> templates. --[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:12,
+> 6
+> August 2013 (UTC) >>
+
+Links to template documentation pages from the transclusion editor is bug 49772",task_subcomment,['(In reply to comment #11)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nLinks to template documentation pages from the transclusion editor is bug 49772'],['ACTION ON ISSUE']
+234079,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"<< For templates, it would be helpful to provide some links to the actual template page from the transclusion dialog. At least a direct link, but perhaps something like v*t*e (view/talk/edit) like included in many navigation templates. --[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:12, 6 August 2013 (UTC) >>",task_subcomment,"['<< For templates, it would be helpful to provide some links to the actual template page from the transclusion dialog.', 'At least a direct link, but perhaps something like v*t*e (view/talk/edit) like included in many navigation templates.', '--[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:12, 6 August 2013 (UTC) >>']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+234076,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"<< When the templatedata does not take any parameters, as specified by the corresponding templatedata (e.g. {{fixed}}, don't show the add parameter heading/text field and 'no unused parameters'. --[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:08, 6 August 2013 (UTC) >>",task_subcomment,"['<< When the templatedata does not take any parameters, as specified by the corresponding templatedata (e.g.', ""{{fixed}}, don't show the add parameter heading/text field and 'no unused parameters'."", '--[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:08, 6 August 2013 (UTC) >>']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+234073,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"I've added bug 51774 as a see-also. That bug is about making it easier to see long descriptions by use of a tooltip. I don't think it is dependent on or duplicative of this though.
+
+Bug 49772 is also relevant here, that asks for links to extended documentation.",task_subcomment,"[""I've added bug 51774 as a see-also."", 'That bug is about making it easier to see long descriptions by use of a tooltip.', ""I don't think it is dependent on or duplicative of this though."", 'Bug 49772 is also relevant here, that asks for links to extended documentation.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'FUTURE PLAN']"
+234068,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"The treatment of ""required parameters"" is positively unhelpful. I suggest that they should be listed below the input box, like the other parameters, with a note saying ""Required"". At present it's easy not to notice that they're there, at the top of the left-hand column, while a few of the other parameters and their descriptions are listed conspicuosly below the input box.
+
+Steps to add a non-required parameter:
+#See it listed below the box, with its descriptionm and click (or, remember its name and type it)
+#type the value into the displayed box
+# (non-intuitively) click on the template name top left to add another parameter (please give us an ""Add another parameter"" box!)
+
+Steps to add a required parameter:
+# Notice that it's listed, top left - just the name, no description
+# Recognise that it's an important and required parameter, even if the name is a bit cryptic
+# Move mouse up there and click on it
+#Now see it displayed with its description
+# type the value into the displayed box
+#...
+
+I don't think the editor benefits from the current situation: I've tried adding a few templates and been flummoxed by it: sometimes the parameter name doesn't convey what it is, while if it was listed below the input box with its description it would be much clearer. Stick a red ""Required""  note beside it: editors are used to this on all sorts of other web forms.",task_subcomment,"['The treatment of ""required parameters"" is positively unhelpful.', 'I suggest that they should be listed below the input box, like the other parameters, with a note saying ""Required"".', ""At present it's easy not to notice that they're there, at the top of the left-hand column, while a few of the other parameters and their descriptions are listed conspicuosly below the input box."", 'Steps to add a non-required parameter:\n#See it listed below the box, with its descriptionm and click (or, remember its name and type it)\n#type the value into the displayed box\n# (non-intuitively) click on the template name top left to add another parameter (please give us an ""Add another parameter"" box!)', ""Steps to add a required parameter:\n# Notice that it's listed, top left - just the name, no description\n# Recognise that it's an important and required parameter, even if the name is a bit cryptic\n# Move mouse up there and click on it\n#Now see it displayed with its description\n# type the value into the displayed box\n#..."", ""I don't think the editor benefits from the current situation: I've tried adding a few templates and been flummoxed by it: sometimes the parameter name doesn't convey what it is, while if it was listed below the input box with its description it would be much clearer."", 'Stick a red ""Required""  note beside it: editors are used to this on all sorts of other web forms.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+234062,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"More user suggestions:
+
+
+    After selecting a template and clicking ""Add template"", the left side of the box should read (in descending order): (1) Dialog box name (which should be ""New template"", not ""Transclusion""); (2) the name of the new template [done now, but this should not be clickable - see (6)]; (3) A title, ""Required parameters"" [new], (4) a list of the required parameters [done now; done now], (5) a title, ""Added parameters"" [new], (6) A button, ""Add a parameter"", which when clicked, changes the right side of the box to the ""Add parameter"" dialog; and (7) a list of added parameters [done now; may be blank]. The button should be greyed out if the editor cannot add any new parameters (the only allowed parameters are required; all possible added parameters have been added)
+
+    After clicking ""Add template"", the left side of the dialog box highlights the template name, and always shows, on the right side, the ""Add parameter"" dialog. This is wrong if there are any required parameters. What should be highlighted on the left is the first required parameter. Editors should be completing the required parameters first, then turning to adding optional parameters.
+
+    When a editor clicks, on the left side, on a parameter, the right side shows an input box. It isn't clear, after the editor has added the desired information, what to do. Pressing [Enter] (or [Return]) just puts a newline character into the box (starts a new line). Clicking on ""Apply changes"", which seems like a possible solution, actually saves the template and exits the dialog box - that's frustrating. There should be a ""Done"" button that closes the edit window, and moves the left-side focus to (a) the top-most required parameter without information, or (b) the ""Add a parameter"" button/option.
+
+    When a parameter listed in the left side of the box gets its information added by the editor, the visible format of the parameter does not change. This is a particular problem if there are a lot of mandatory parameters, and the editor is not adding information linearly. It would be helpful if the text of the name of the parameter were to turn green once the parameter has been filled out; that's also positive feedback to an editor looking at anything with more than a few required parameters.
+
+    How to add a parameter is not obvious, as indicated by the frustration voiced by an editor previously. It looks like an editor can click on a parameter in the list, and then click the boxed parameter name towards the right side of the areas that has turned blue (that is, to click on what appears to be a button with the parameter name within it). But clicking on that ""button"" does nothing. Nor does clicking on a parameter result in the name of that parameter being put into the search box. The secret of adding a parameter [I guess; I've not been able to figure out anything else] is to ignore the fact that parameter names can be selected by clicking on them, instead (a) typing the parameter name into the search box, and (b) pressing [Enter]. I admit to being baffled by the rationale here: why make (the parameter name) clickable, yet have the click do absolutely nothing useful? Clicking on a small button within the parameter description, or double-clicking (or best, either way) is much more what editors would expect. [I also note that the user guide is not helpful, saying in its entirety, on this issue: ""You can add parameters or edit those already listed.""]
+
+    What makes the ""type in the parameter name and press enter"" approach particularly problematical is that if you misspell the name of an optional parameter, you get no feedback that you have done so. That's because VE assumes you're adding a parameter that's not covered by templatedata, but still is valid. That's a necessary assumption now, but clicking to add a parameter, rather than typing to add one, would remove the potential for this problem.
+
+    When adding a parameter, the list of parameters includes a description (e.g., ""Full date when the source was published; if unknown, use accessdate ...""). It would be extremely useful if this description was also visible when the enter enters information for that parameter. (Bug exists for this, I believe.)
+
+    VE should prevent an editor from adding a template to the page text unless information has been entered for all required parameters. This could be done by greying out the final button (currently ""Apply changes""), or by an appropriate error message if that button were clicked while a required parameter was still blank. If the first approach is taken, then it's particularly important to show the editor his/her progress in filling out parameters (the fourth suggestion, above), perhaps even turning red the required parameters that still require information.
+
+    The final step, for a different process, adding images, is to click a button labeled ""Insert media"". Similarly, the final step for the template process should be a button labeled ""Insert template"", rather than ""Apply changes"".",task_subcomment,"['More user suggestions:\n\n\n    After selecting a template and clicking ""Add template"", the left side of the box should read (in descending order): (1) Dialog box name (which should be ""New template"", not ""Transclusion""); (2) the name of the new template [done now, but this should not be clickable - see (6)]; (3) A title, ""Required parameters"" [new], (4) a list of the required parameters [done now; done now], (5) a title, ""Added parameters"" [new], (6) A button, ""Add a parameter"", which when clicked, changes the right side of the box to the ""Add parameter"" dialog; and (7) a list of added parameters [done now; may be blank].', 'The button should be greyed out if the editor cannot add any new parameters (the only allowed parameters are required; all possible added parameters have been added)\n\n    After clicking ""Add template"", the left side of the dialog box highlights the template name, and always shows, on the right side, the ""Add parameter"" dialog.', 'This is wrong if there are any required parameters.', 'What should be highlighted on the left is the first required parameter.', 'Editors should be completing the required parameters first, then turning to adding optional parameters.', 'When a editor clicks, on the left side, on a parameter, the right side shows an input box.', ""It isn't clear, after the editor has added the desired information, what to do."", 'Pressing [Enter] (or [Return]) just puts a newline character into the box (starts a new line).', 'Clicking on ""Apply changes"", which seems like a possible solution, actually saves the template and exits the dialog box - that\'s frustrating.', 'There should be a ""Done"" button that closes the edit window, and moves the left-side focus to (a) the top-most required parameter without information, or (b) the ""Add a parameter"" button/option.', 'When a parameter listed in the left side of the box gets its information added by the editor, the visible format of the parameter does not change.', 'This is a particular problem if there are a lot of mandatory parameters, and the editor is not adding information linearly.', ""It would be helpful if the text of the name of the parameter were to turn green once the parameter has been filled out; that's also positive feedback to an editor looking at anything with more than a few required parameters."", 'How to add a parameter is not obvious, as indicated by the frustration voiced by an editor previously.', 'It looks like an editor can click on a parameter in the list, and then click the boxed parameter name towards the right side of the areas that has turned blue (that is, to click on what appears to be a button with the parameter name within it).', 'But clicking on that ""button"" does nothing.', 'Nor does clicking on a parameter result in the name of that parameter being put into the search box.', ""The secret of adding a parameter [I guess; I've not been able to figure out anything else] is to ignore the fact that parameter names can be selected by clicking on them, instead (a) typing the parameter name into the search box, and (b) pressing [Enter]."", 'I admit to being baffled by the rationale here: why make (the parameter name) clickable, yet have the click do absolutely nothing useful?', 'Clicking on a small button within the parameter description, or double-clicking (or best, either way) is much more what editors would expect.', '[I also note that the user guide is not helpful, saying in its entirety, on this issue: ""You can add parameters or edit those already listed.""]', 'What makes the ""type in the parameter name and press enter"" approach particularly problematical is that if you misspell the name of an optional parameter, you get no feedback that you have done so.', ""That's because VE assumes you're adding a parameter that's not covered by templatedata, but still is valid."", ""That's a necessary assumption now, but clicking to add a parameter, rather than typing to add one, would remove the potential for this problem."", 'When adding a parameter, the list of parameters includes a description (e.g., ""Full date when the source was published; if unknown, use accessdate ..."").', 'It would be extremely useful if this description was also visible when the enter enters information for that parameter.', '(Bug exists for this, I believe.)', 'VE should prevent an editor from adding a template to the page text unless information has been entered for all required parameters.', 'This could be done by greying out the final button (currently ""Apply changes""), or by an appropriate error message if that button were clicked while a required parameter was still blank.', ""If the first approach is taken, then it's particularly important to show the editor his/her progress in filling out parameters (the fourth suggestion, above), perhaps even turning red the required parameters that still require information."", 'The final step, for a different process, adding images, is to click a button labeled ""Insert media"".', 'Similarly, the final step for the template process should be a button labeled ""Insert template"", rather than ""Apply changes"".']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+234057,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"Retitling this ticket to keep it more focussed as a generic ""improve X"" is hard to actually resolve definitely. I suppose the main goal here is:
+
+* It should be easier to add the Nth parameter after having added one already (e.g. not having to go back to the template page from the navigation sidebar and adding a new one).
+
+* One should be able to see other parameters (including their values) at a glance.
+
+I've been thinking about the following UI changes (in no particular order, some options are mutually exclusive):
+
+* Though having sidebar entries for each parameter (as opposed to just the template) is a nice way to jump to a specific parameter at once, but for other purposes it is imho too big and unhelpful. I can't justify its prominence other than that this is the only method we have in the UI right now to allow navigation to other pages in the dialog.
+
+* I'd like to try for a Template to be a single page in the dialog where one can scroll from one parameter to another (e.g. more like a regular form).
+
+* The sidebar should probably be reduced (parameters either not in there, or significantly less prominent (e.g. a third of the height and indented from the parent item). The navigation sub-items for parameters wouldn't be for separate pages in the dialog, but would trigger a scroll to the param section and (if not already) to go to that template page the parameter section is inside of. We could go fancy and update the sidebar in two-directions (e.g. clicking an item will scroll there, and if you scroll there manually, we update the sidebar active item.  This principle is quite common on one-page sites, example implementation of such principle: 
+http://webdesign.tutsplus.com/tutorials/javascript-tutorials/create-a-sticky-navigation-header-using-jquery-waypoints/
+https://webdesigntutsplus.s3.amazonaws.com/tuts/313_waypoints/demo/index.html
+
+* As for bigger templates the ""Template"" page would now be very long, it becomes important that our ""Add parameter"" button is not only on top or bottom of the Template page, but accessible at all times (e.g. sticky on the bottom, and when clicked we attach a new section, add it to the list and scroll to it).
+
+* Separate: I'd like to get rid of the [+] -> [+ {template}] button we have right now. It is quite counter intuitive in my opinion. Aside from the ""+"" being unclickable (one has to hover it, then find out there are different options and pick one, even though there was only 1 option, now there are 2: template and content), it is also too small. I'd recommend we either have both + buttons visible at all times (+template, +content) or put them in the sidebar are sticky bottom-positioned slugs/placeholders (e.g. each + item would be its own row in the sidebar, clicking it will add an entry to the sidebar).
+
+",task_subcomment,"['Retitling this ticket to keep it more focussed as a generic ""improve X"" is hard to actually resolve definitely.', 'I suppose the main goal here is:\n\n* It should be easier to add the Nth parameter after having added one already (e.g.', 'not having to go back to the template page from the navigation sidebar and adding a new one).', '* One should be able to see other parameters (including their values) at a glance.', ""I've been thinking about the following UI changes (in no particular order, some options are mutually exclusive):\n\n* Though having sidebar entries for each parameter (as opposed to just the template) is a nice way to jump to a specific parameter at once, but for other purposes it is imho too big and unhelpful."", ""I can't justify its prominence other than that this is the only method we have in the UI right now to allow navigation to other pages in the dialog."", ""* I'd like to try for a Template to be a single page in the dialog where one can scroll from one parameter to another (e.g."", 'more like a regular form).', '* The sidebar should probably be reduced (parameters either not in there, or significantly less prominent (e.g.', 'a third of the height and indented from the parent item).', ""The navigation sub-items for parameters wouldn't be for separate pages in the dialog, but would trigger a scroll to the param section and (if not already) to go to that template page the parameter section is inside of."", 'We could go fancy and update the sidebar in two-directions (e.g.', 'clicking an item will scroll there, and if you scroll there manually, we update the sidebar active item.', 'This principle is quite common on one-page sites, example implementation of such principle: \nURL\nURL\n\n* As for bigger templates the ""Template"" page would now be very long, it becomes important that our ""Add parameter"" button is not only on top or bottom of the Template page, but accessible at all times (e.g.', 'sticky on the bottom, and when clicked we attach a new section, add it to the list and scroll to it).', ""* Separate: I'd like to get rid of the [+] -> [+ {template}] button we have right now."", 'It is quite counter intuitive in my opinion.', 'Aside from the ""+"" being unclickable (one has to hover it, then find out there are different options and pick one, even though there was only 1 option, now there are 2: template and content), it is also too small.', ""I'd recommend we either have both + buttons visible at all times (+template, +content) or put them in the sidebar are sticky bottom-positioned slugs/placeholders (e.g."", 'each + item would be its own row in the sidebar, clicking it will add an entry to the sidebar).', '']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+234048,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"**euro** wrote:
+
+(In reply to comment #4)
+> I'd also request the elimination and replacement of the word ""transclusion"";
+> it's very opaque to non-wikimedians (and also potentially incorrect).
+
+Agreed...Perhaps it would be helpful in ""dumbing down"" the term to review the Free Dictionary treatise on ""transclusion"":
+
+http://encyclopedia.thefreedictionary.com/Transclusion
+
+--It pretty much comes down to the age-old issue of taking whatever is somewhere originally and replicating it somewhere else. The catch: no matter what happens to the original material, it's reflected immediately in the replicated copy. So within the context of ""Wikistuff"", how about ""replicate""?
+
+Webbie",task_subcomment,"['**euro** wrote:\n\n(In reply to comment #4)\nQUOTE\nQUOTE\n\nAgreed...Perhaps it would be helpful in ""dumbing down"" the term to review the Free Dictionary treatise on ""transclusion"":\n\nURL\n\n--It pretty much comes down to the age-old issue of taking whatever is somewhere originally and replicating it somewhere else.', ""The catch: no matter what happens to the original material, it's reflected immediately in the replicated copy."", 'So within the context of ""Wikistuff"", how about ""replicate""?', 'Webbie']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+234036,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"I'd also request the elimination and replacement of the word ""transclusion""; it's very opaque to non-wikimedians (and also potentially incorrect).",task_subcomment,"['I\'d also request the elimination and replacement of the word ""transclusion""; it\'s very opaque to non-wikimedians (and also potentially incorrect).']",['INVESTIGATION AND EXPLORATION']
+234024,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"Another editor doing a lot of work with templates suggests that in commonly used templates with regular parameters, it might be a good idea to have the parameters preloaded. Speaking of the common ""cite web"" template, she says:
+
+""I think it would be easier for the parameteres to already being added, at least the basic ones, to the template. For example, to the ""cite web"" template, the parameters that most people use (title, url, author, publisher and date). So, when the editor adds the ""cite web"" template, would only have to add the content of each parameter and not the parameters themselves. If the editor wants to add an extra parameter, they could choose it from the list and add it. I am sure that this is difficult to be done knowing that there are lots of templates to go through but maybe keep it as a thought if it can be done?""",task_subcomment,"['Another editor doing a lot of work with templates suggests that in commonly used templates with regular parameters, it might be a good idea to have the parameters preloaded.', 'Speaking of the common ""cite web"" template, she says:\n\n""I think it would be easier for the parameteres to already being added, at least the basic ones, to the template.', 'For example, to the ""cite web"" template, the parameters that most people use (title, url, author, publisher and date).', 'So, when the editor adds the ""cite web"" template, would only have to add the content of each parameter and not the parameters themselves.', 'If the editor wants to add an extra parameter, they could choose it from the list and add it.', 'I am sure that this is difficult to be done knowing that there are lots of templates to go through but maybe keep it as a thought if it can be done?""']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+234015,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"Additional thoughts - copied from En Wikipedia. Pam has done a ton of work with templates in VE and is at this point pretty dead familiar with how it impacts her workflow.
+
+***
+Many of the templates I add most often either have no parameters (eg stub templates), or take ""date"" as a parameter (maintenance templates like {{unref}}), or take one or more positional parameters (eg {{in title}} or {{about}} or {{coord}}).
+
+The handling of templates seems to assume that each template has one or more named parameters.
+
+Inputting a 3-parameter template like {{about|this|that|the other}} is very tedious, even after you've discovered how to do it (very non-intuitive). You can't see the content of previous parameters as you go along, so have to remember where you've got to. Messy and stressful and takes a whole lot of clicking.
+
+It's probably too late to suggest this, but imagine the following scenario:
+1. I click on the jigsaw icon
+2. A box appears where I input the name of the template and click ""Add template""
+3. The next box includes a prominent ""See template documentation"" button which links to the appropriate documentation, perhaps popping it up in another window or tab.
+4. This box is divided into two columns and a note says ""use either the left-hand or right-hand column to add any parameters to this template"". One col has named parameters, the other has a set of boxes labelled ""1st parameter"", ""2nd parameter"", etc. Along with buttons for ""Next template"" and ""Apply changes"".
+
+A further refinement would be for VE to be aware of (a) templates which take no parameters (eg stub templates), and (b) templates which only take the date (many maintenance templates), and in these two cases not to prompt for parameters (but to quietly add the date for (b), saving this having to be done by a passing bot later).
+
+A yet further refinement would be for VE to recognise stub templates (they all end in ""-stub}}"", apart from {{stub}} itself, so it shouldn't be hard), offer them as a separate drop-down menu (much easier when stub-sorting), and put them in the ""right"" (per WP:MOS) place at the end of the article.
+
+Probably too much to hope for: but going back to the basics, please work out a way for parameters to be input without all the clicks involved in making ""names"" like ""1"", ""2"", etc. I haven't yet tried to add a coords parameter - something on the lines of {{coord|54|36|51|N|2|49|34|W|display=title}}. That's going to be really tedious.
+
+... Getting a bit stream-of-consciousness here: can't we just have two columns of boxes: ""parameter name if any"" and ""parameter contents"" - perhaps 10 rows and a ""More parameters"" button. Then to input that coord template I'd just leave the first column blank and put the values I've got, in order, and hit ""Apply changes"". Simple, allows you to see previous params as you go to keep track of where you've got to, etc. Ah well, perhaps it's all in hand. Good luck. PamD 14:12, 4 July 2013 (UTC)",task_subcomment,"['Additional thoughts - copied from En Wikipedia.', 'Pam has done a ton of work with templates in VE and is at this point pretty dead familiar with how it impacts her workflow.', '***\nMany of the templates I add most often either have no parameters (eg stub templates), or take ""date"" as a parameter (maintenance templates like {{unref}}), or take one or more positional parameters (eg {{in title}} or {{about}} or {{coord}}).', 'The handling of templates seems to assume that each template has one or more named parameters.', ""Inputting a 3-parameter template like {{about|this|that|the other}} is very tedious, even after you've discovered how to do it (very non-intuitive)."", ""You can't see the content of previous parameters as you go along, so have to remember where you've got to."", 'Messy and stressful and takes a whole lot of clicking.', ""It's probably too late to suggest this, but imagine the following scenario:\n1."", 'I click on the jigsaw icon\n2.', 'A box appears where I input the name of the template and click ""Add template""\n3.', 'The next box includes a prominent ""See template documentation"" button which links to the appropriate documentation, perhaps popping it up in another window or tab.', '4.', 'This box is divided into two columns and a note says ""use either the left-hand or right-hand column to add any parameters to this template"".', 'One col has named parameters, the other has a set of boxes labelled ""1st parameter"", ""2nd parameter"", etc.', 'Along with buttons for ""Next template"" and ""Apply changes"".', 'A further refinement would be for VE to be aware of (a) templates which take no parameters (eg stub templates), and (b) templates which only take the date (many maintenance templates), and in these two cases not to prompt for parameters (but to quietly add the date for (b), saving this having to be done by a passing bot later).', 'A yet further refinement would be for VE to recognise stub templates (they all end in ""-stub}}"", apart from {{stub}} itself, so it shouldn\'t be hard), offer them as a separate drop-down menu (much easier when stub-sorting), and put them in the ""right"" (per WP:MOS) place at the end of the article.', 'Probably too much to hope for: but going back to the basics, please work out a way for parameters to be input without all the clicks involved in making ""names"" like ""1"", ""2"", etc.', ""I haven't yet tried to add a coords parameter - something on the lines of {{coord|54|36|51|N|2|49|34|W|display=title}}."", ""That's going to be really tedious."", '... Getting a bit stream-of-consciousness here: can\'t we just have two columns of boxes: ""parameter name if any"" and ""parameter contents"" - perhaps 10 rows and a ""More parameters"" button.', 'Then to input that coord template I\'d just leave the first column blank and put the values I\'ve got, in order, and hit ""Apply changes"".', ""Simple, allows you to see previous params as you go to keep track of where you've got to, etc."", ""Ah well, perhaps it's all in hand."", 'Good luck.', 'PamD 14:12, 4 July 2013 (UTC)']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+234010,VisualEditor: Transclusion dialog should make it easier to add parameters and see other values,"Another thought; the different tabs for different params is something that takes a while to figure out, and introduces a lot more hoops into the system.",task_subcomment,"['Another thought; the different tabs for different params is something that takes a while to figure out, and introduces a lot more hoops into the system.']",['SOLUTION DISCUSSION']
+52353,VisualEditor: Add a block slug at the end of pages,"The cursor cannot be placed below the last line. This sounds trivial, but there are a lot of situations - adding stub templates, or defaultsort data, for example - where being able to trivially flip to the end of an article and have space to write is A Good Thing (tm). It'd be good to have a temporary line at the end of an article that isn't saved unless it contains anything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Add a block slug at the end of pages\n\nThe cursor cannot be placed below the last line.', 'This sounds trivial, but there are a lot of situations - adding stub templates, or defaultsort data, for example - where being able to trivially flip to the end of an article and have space to write is A Good Thing (tm).', ""It'd be good to have a temporary line at the end of an article that isn't saved unless it contains anything."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+410478,VisualEditor: Add a block slug at the end of pages,"We don't insert slugs if the user can create a new line by pressing enter. If the document ends in a template or other focusable item, we do.",task_subcomment,"[""We don't insert slugs if the user can create a new line by pressing enter."", 'If the document ends in a template or other focusable item, we do.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52341,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"1. Edit [[testwiki:Displaytitle]] using VE
+2. Using the transclusion dialog box, add the following ""template"":
+        DISPLAYTITLE:''displaytitle''
+3. Save the page
+
+The page title remains ""Displaytitle"" in roman type.
+
+Expected to see ""displaytitle"" in italics. This is what you see when you refresh the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49667",task_description,"['VisualEditor: Title is not updated on save if DISPLAYTITLE changed\n\n1.', 'Edit [[testwiki:Displaytitle]] using VE\n2.', 'Using the transclusion dialog box, add the following ""template"":\n        DISPLAYTITLE:\'\'displaytitle\'\'\n3.', 'Save the page\n\nThe page title remains ""Displaytitle"" in roman type.', 'Expected to see ""displaytitle"" in italics.', 'This is what you see when you refresh the page.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+233340,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"(In reply to Alex Monk from comment #13)
+> So this appears to actually be working now.
+
+Woo-hoo. :-)",task_subcomment,"['(In reply to Alex Monk from comment #13)\nQUOTE\n\nWoo-hoo.', ':-)']","['SOCIAL CONVERSATION', 'SOLUTION DISCUSSION']"
+233337,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,So this appears to actually be working now.,task_subcomment,['So this appears to actually be working now.'],['SOLUTION DISCUSSION']
+233334,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Change 141098 merged by jenkins-bot:
+Update displaytitle on save (try #3)
+
+https://gerrit.wikimedia.org/r/141098",task_subcomment,['Change 141098 merged by jenkins-bot:\nUpdate displaytitle on save (try #3)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233327,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Change 141098 had a related patch set uploaded by Alex Monk:
+Update displaytitle on save (try #3)
+
+https://gerrit.wikimedia.org/r/141098",task_subcomment,['Change 141098 had a related patch set uploaded by Alex Monk:\nUpdate displaytitle on save (try #3)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233323,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Change 140591 merged by jenkins-bot:
+Update displaytitle on save (try #2)
+
+https://gerrit.wikimedia.org/r/140591",task_subcomment,['Change 140591 merged by jenkins-bot:\nUpdate displaytitle on save (try #2)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233319,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Change 140591 had a related patch set uploaded by Alex Monk:
+Update displaytitle on save (try #2)
+
+https://gerrit.wikimedia.org/r/140591",task_subcomment,['Change 140591 had a related patch set uploaded by Alex Monk:\nUpdate displaytitle on save (try #2)\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233313,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,Patch reverted; re-opening.,task_subcomment,['Patch reverted; re-opening.'],['BUG REPRODUCTION']
+233308,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Change 139205 merged by jenkins-bot:
+Update displaytitle on save
+
+https://gerrit.wikimedia.org/r/139205",task_subcomment,['Change 139205 merged by jenkins-bot:\nUpdate displaytitle on save\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233304,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Change 139205 had a related patch set uploaded by Alex Monk:
+Update displaytitle on save
+
+https://gerrit.wikimedia.org/r/139205",task_subcomment,['Change 139205 had a related patch set uploaded by Alex Monk:\nUpdate displaytitle on save\n\nGERRIT_URL'],['ACTION ON ISSUE']
+233301,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,Yeah it's actually kind of a pain to do that. Let's update it on save.,task_subcomment,"[""Yeah it's actually kind of a pain to do that."", ""Let's update it on save.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+233299,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"So now that the dependency is merged, Parsoid now recognises {{DISPLAYTITLE:stuff}} as a meta property (instead of a template), and VE provides a box on the options page to change the display title. I think what we should do is update the title (almost) as soon as it's changed.",task_subcomment,"['So now that the dependency is merged, Parsoid now recognises {{DISPLAYTITLE:stuff}} as a meta property (instead of a template), and VE provides a box on the options page to change the display title.', ""I think what we should do is update the title (almost) as soon as it's changed.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+233296,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Confirmed that adding italics to an existing page doesnt display italics on save - it does display the italic title after save + refresh.
+
+However it does display italics on save, if the DISPLAYTITLE is set for a new page. 
+
+Tested with {{italics title}} and {{DISPLAYTITLE:''ItalicsTitle''}} on testwiki
+
+https://test.wikipedia.org/wiki/ItalicsTitle",task_subcomment,"['Confirmed that adding italics to an existing page doesnt display italics on save - it does display the italic title after save + refresh.', 'However it does display italics on save, if the DISPLAYTITLE is set for a new page.', ""Tested with {{italics title}} and {{DISPLAYTITLE:''ItalicsTitle''}} on testwiki\n\nURL""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233292,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"I think this includes my problem with {{tl|italic title}}, which is at two levels:
+# When I add it, I expect to see it take effect immediately - it doesn't (so I wonder whether I remembered to add it, whether I formatted it correctly, ... etc)
+# Even when I save the page, it doesn't take effect until I refresh the page (same set of worries).",task_subcomment,"[""I think this includes my problem with {{tl|italic title}}, which is at two levels:\n# When I add it, I expect to see it take effect immediately - it doesn't (so I wonder whether I remembered to add it, whether I formatted it correctly, ... etc)\n# Even when I save the page, it doesn't take effect until I refresh the page (same set of worries).""]",['BUG REPRODUCTION']
+233288,VisualEditor: Title is not updated on save if DISPLAYTITLE changed,"Created attachment 12689
+Wrong title displayed in ""correct title"" template.
+
+I think it's related, so I'm sticking this here.
+
+After http://it.wikipedia.org/w/index.php?title=Utente:Dry_Martini/Cricca&diff=prev&oldid=59761793, the page, containing a ""Correct title"" template, would display, after being saved, the message usually generated by that template, although it disappears if you refresh. 
+
+I tried it myself and this time I actually changed the title in the template.
+The screenshot shows what happened after http://it.wikipedia.org/w/index.php?title=Utente%3ADry_Martini%2FCricca&diff=59761896&oldid=59761793 my edit.
+Basically, the page retains its formerly given title, while displaying in the message the one I chose. Again, everything is ok if you refresh.
+(For the record, the usual title is ""There is no Cabal"", while mine reads ""There's a Cabal, and it's using VisualEditor"".)
+
+**Attached**: {F11086}",task_subcomment,"['Created attachment 12689\nWrong title displayed in ""correct title"" template.', ""I think it's related, so I'm sticking this here."", 'After URL the page, containing a ""Correct title"" template, would display, after being saved, the message usually generated by that template, although it disappears if you refresh.', 'I tried it myself and this time I actually changed the title in the template.', 'The screenshot shows what happened after URL my edit.', 'Basically, the page retains its formerly given title, while displaying in the message the one I chose.', 'Again, everything is ok if you refresh.', '(For the record, the usual title is ""There is no Cabal"", while mine reads ""There\'s a Cabal, and it\'s using VisualEditor"".)', '**Attached**: {F11086}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52321,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page","Using ctrl-click (but not middle-click) on a ""content editable"" link, does not currently work with Chromium37, but does work with Firefox39.
+Using Middle-mouse-click on links does not work in either browser
+Using Right-mouse-click to show the context menu with ""Open link in new tab/window"" does work in both browsers.
+
+(Prior description had different results for Firefox 22.
+Ed notes below, that this is all browser-specific behaviour, and rather than overriding that, we should just solve {T56759} (Done))
+
+See also: {T52741}",task_description,"['VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image\'s description page\n\nUsing ctrl-click (but not middle-click) on a ""content editable"" link, does not currently work with Chromium37, but does work with Firefox39.', 'Using Middle-mouse-click on links does not work in either browser\nUsing Right-mouse-click to show the context menu with ""Open link in new tab/window"" does work in both browsers.', '(Prior description had different results for Firefox 22.', 'Ed notes below, that this is all browser-specific behaviour, and rather than overriding that, we should just solve {T56759} (Done))\n\nSee also: {T52741}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+504444,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page",The main request here was satisfied in {T56759} and for non-links more generally in the context menu stuff done in March-ish. I agree with Ed that breaking people's browsers' behaviour isn't desireable.,task_subcomment,"['The main request here was satisfied in {T56759} and for non-links more generally in the context menu stuff done in March-ish.', ""I agree with Ed that breaking people's browsers' behaviour isn't desireable.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+504373,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page",The main request here was satisfied in {T56759} and for non-links more generally in the context menu stuff done in March-ish. I agree with Ed that breaking people's browsers' behaviour it's desireable.,task_subcomment,"['The main request here was satisfied in {T56759} and for non-links more generally in the context menu stuff done in March-ish.', ""I agree with Ed that breaking people's browsers' behaviour it's desireable.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+504282,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page","Note/update: Using ctrl-click (but not middle-click) on a ""content editable"" link, does not currently work with Chromium37, but does work with Firefox39. 
+I will update the description to clarify.",task_subcomment,"['Note/update: Using ctrl-click (but not middle-click) on a ""content editable"" link, does not currently work with Chromium37, but does work with Firefox39.', 'I will update the description to clarify.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+232007,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page","Middle click/ctrl click on *content editable* links in browser specific behaviour, and isn't necessarily going to be the same as for read-only links. Rather than override the browser's default behaviour we will provide a consistent way to follow links with bug 54759.
+
+Image nodes are protected from editing with highlights so we're not going to able to provide the normal context menu. I can't see a compelling use case, but such functionality may be available in the image dialog in the future.
+
+Suggest wontfix for this.",task_subcomment,"[""Middle click/ctrl click on *content editable* links in browser specific behaviour, and isn't necessarily going to be the same as for read-only links."", ""Rather than override the browser's default behaviour we will provide a consistent way to follow links with bug 54759."", ""Image nodes are protected from editing with highlights so we're not going to able to provide the normal context menu."", ""I can't see a compelling use case, but such functionality may be available in the image dialog in the future."", 'Suggest wontfix for this.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+232001,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page",*** Bug 64974 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 64974 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231996,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page","The mouse cursor not changing is bug 50741 
+
+CTRL+click / right click and open in a new window/tab does work for internal and external links. It does not work for images.",task_subcomment,"['The mouse cursor not changing is bug 50741 \n\nCTRL+click / right click and open in a new window/tab does work for internal and external links.', 'It does not work for images.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231990,"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page","Some more details: 
+
+* Middle mouse click on internal text links: OK (but mouse cursor wrong)
+
+* Middle mouse click on images: NOT OK
+* Middle mouse click on external links: NOT OK",task_subcomment,['Some more details: \n\n* Middle mouse click on internal text links: OK (but mouse cursor wrong)\n\n* Middle mouse click on images: NOT OK\n* Middle mouse click on external links: NOT OK'],['OBSERVED BUG BEHAVIOR']
+52289,VisualEditor: VE won't load on empty page containing only a magic word,"Try and edit this version of my sandbox http://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox&oldid=59706098 which is empty except for a __NOINDEX__ ; VE just keeps loading and won't allow to edit. Happens at least with Vector on Chrome and Monobook on FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: VE won't load on empty page containing only a magic word\n\nTry and edit this version of my sandbox URL which is empty except for a __NOINDEX__ ; VE just keeps loading and won't allow to edit."", 'Happens at least with Vector on Chrome and Monobook on FF.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+255413,VisualEditor: VE won't load on empty page containing only a magic word,"Fixed in the above commit, which we will push out today.",task_subcomment,"['Fixed in the above commit, which we will push out today.']",['SOLUTION USAGE']
+255405,VisualEditor: VE won't load on empty page containing only a magic word,"Change 73745 merged by jenkins-bot:
+Extend empty document check to check for meta-only data
+
+https://gerrit.wikimedia.org/r/73745",task_subcomment,['Change 73745 merged by jenkins-bot:\nExtend empty document check to check for meta-only data\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+255399,VisualEditor: VE won't load on empty page containing only a magic word,"Change 73745 had a related patch set uploaded by Esanders:
+Extend empty document check to check for meta-only data
+
+https://gerrit.wikimedia.org/r/73745",task_subcomment,['Change 73745 had a related patch set uploaded by Esanders:\nExtend empty document check to check for meta-only data\n\nGERRIT_URL'],['BUG REPRODUCTION']
+255392,VisualEditor: VE won't load on empty page containing only a magic word,This happens because the converter generates a document with only an alienMeta (the magic word) and an empty internal list. The logic for generating an empty paragraph to prevent an empty document doesn't kick in if the document is non-empty from the converter's perspective but only contains meta items.,task_subcomment,"['This happens because the converter generates a document with only an alienMeta (the magic word) and an empty internal list.', ""The logic for generating an empty paragraph to prevent an empty document doesn't kick in if the document is non-empty from the converter's perspective but only contains meta items.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52281,"VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message","When the transclusion editor is emptied out (e.g. by removing all the items), it should not just be blank. This looks broken and is confusing to the user (should I wait for something to appear? is it stuffed/errored out?)
+
+There needs to be some kind of textual label in the empty transclusion editor, that makes two points:
+
+1. that the user can click [+] to add something to the transclusion
+2. that by clicking ""apply changes"", it will remove the transclusion
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message\n\nWhen the transclusion editor is emptied out (e.g.', 'by removing all the items), it should not just be blank.', 'This looks broken and is confusing to the user (should I wait for something to appear?', 'is it stuffed/errored out?)', 'There needs to be some kind of textual label in the empty transclusion editor, that makes two points:\n\n1. that the user can click [+] to add something to the transclusion\n2. that by clicking ""apply changes"", it will remove the transclusion\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+433705,"VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message","Change 198131 merged by jenkins-bot:
+Fixed the empty Transclusion Box problem
+
+[[https://gerrit.wikimedia.org/r/198131]]",task_subcomment,['Change 198131 merged by jenkins-bot:\nFixed the empty Transclusion Box problem\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+433660,"VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message","Change 198131 had a related patch set uploaded (by Jforrester):
+Fixed the empty Transclusion Box problem
+
+[[https://gerrit.wikimedia.org/r/198131]]
+",task_subcomment,['Change 198131 had a related patch set uploaded (by Jforrester):\nFixed the empty Transclusion Box problem\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+254901,"VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message",*** Bug 51812 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51812 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254899,"VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message","Created attachment 12684
+Screenshot of bug
+
+Just found this lovely screenshot that I meant to upload.
+
+**Attached**: {F11889}",task_subcomment,"['Created attachment 12684\nScreenshot of bug\n\nJust found this lovely screenshot that I meant to upload.', '**Attached**: {F11889}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52279,VisualEditor: Link input widget outwits itself with the leading colon for Category/file links,"1. Go to some page and edit in VE
+2. Click the ""Link"" toolbar button, type ""Category:"" and click a category that appears
+
+The leading colon is correctly added, but the category now appears in red in the dropdown as if non-existent (although it shows up under ""matching pages"", not ""new pages"").
+
+Probably, the link inspector should be ignoring/stripping the preceding colon when checking whether the page exists.
+
+Same thing for links to File: pages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Link input widget outwits itself with the leading colon for Category/file links\n\n1.', 'Go to some page and edit in VE\n2.', 'Click the ""Link"" toolbar button, type ""Category:"" and click a category that appears\n\nThe leading colon is correctly added, but the category now appears in red in the dropdown as if non-existent (although it shows up under ""matching pages"", not ""new pages"").', 'Probably, the link inspector should be ignoring/stripping the preceding colon when checking whether the page exists.', 'Same thing for links to File: pages.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254820,VisualEditor: Link input widget outwits itself with the leading colon for Category/file links,*** Bug 63353 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 63353 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254815,VisualEditor: Link input widget outwits itself with the leading colon for Category/file links,"Change 142136 merged by jenkins-bot:
+Don't prepend extra colon to category/file links
+
+https://gerrit.wikimedia.org/r/142136",task_subcomment,"[""Change 142136 merged by jenkins-bot:\nDon't prepend extra colon to category/file links\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+254810,VisualEditor: Link input widget outwits itself with the leading colon for Category/file links,"Change 142136 had a related patch set uploaded by Alex Monk:
+Don't prepend extra colon to category/file links
+
+https://gerrit.wikimedia.org/r/142136",task_subcomment,"[""Change 142136 had a related patch set uploaded by Alex Monk:\nDon't prepend extra colon to category/file links\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+254805,VisualEditor: Link input widget outwits itself with the leading colon for Category/file links,"Two different things look like they're pre-pending the "":"". Helpful. :-)",task_subcomment,"['Two different things look like they\'re pre-pending the "":"".', 'Helpful.', ':-)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52269,VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width,"Screenshot
+
+See the screenshot (provided by a contributor). I suspect it's down to the screen resolution. Firefox 21.0, Mac OS X 10.6.8.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11863}",task_description,"['VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width\n\nScreenshot\n\nSee the screenshot (provided by a contributor).', ""I suspect it's down to the screen resolution."", 'Firefox 21.0, Mac OS X 10.6.8.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11863}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+254354,VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width,"(In reply to This, that and the other from comment #2)
+> It looks no more broken to me in VE than it does in view mode.
+
+Yeah; marking as fixed.",task_subcomment,"['(In reply to This, that and the other from comment #2)\nQUOTE\n\nYeah; marking as fixed.']",['SOLUTION USAGE']
+254350,VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width,It looks no more broken to me in VE than it does in view mode.,task_subcomment,['It looks no more broken to me in VE than it does in view mode.'],['OBSERVED BUG BEHAVIOR']
+254344,VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width,I wonder if this is related to bug 50036?,task_subcomment,['I wonder if this is related to bug 50036?'],['MOTIVATION']
+52268,VisualEditor: Let users relabel (or renumber if auto-numbered) parameters in the transclusion dialog,"See the report at https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Failed_attempt_to_use_VE_to_remove_a_template_parameter
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,['VisualEditor: Let users relabel (or renumber if auto-numbered) parameters in the transclusion dialog\n\nSee the report at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'],['BUG REPRODUCTION']
+254297,VisualEditor: Let users relabel (or renumber if auto-numbered) parameters in the transclusion dialog,"Comment from bug 51558:
+
+An en.wp [[user:3family6]] comments about [[Template:Album ratings]]:
+""This is an instance where the transclusion option on VE, while it does work,
+is more inconvenient than just wiki-markup. In wikimarkup, if you want to
+insert a new review into the middle of the template, i.e. between reviews 3 and
+4 (rev3 and rev4), you just change rev4 to rev5 (and rev5 to 6 and so on), then
+insert the new score. With VE, you have to add a new rev parameter to the
+bottom, and move the content of ALL of the parameters affected through
+copy-paste. This is much more time consuming than editing the wikitext.""
+
+For context reviews are listed in alphabetical order, initially the template
+could be something like:
+rev1 = A Magazine
+rev1Score  = 4/5
+rev2 = CTV
+rev2Score = 1/5
+rev3 = FooMusic
+rev3Score = 5/5
+rev4 = ZedNews
+rev4Score = 6/10
+
+The album then gets rereleased and reviewed by BetaMag. This needs to be added
+at the second review, in source editing it's just a matter of changing 6
+characters (4→5,3→4, etc). In VE you have to create a new rev5 and rev5
+parameter, then cut and paste the values from each of rev2 - rev4 and rev2Score
+- rev4Score to their new locations then add the new data. 
+
+One better way to handle this would be to allow the renaming of parameters.
+Either in the ""options"" section or by right clicking on the parameter name. 
+
+This is likely to affect other templates too.",task_subcomment,"['Comment from bug 51558:\n\nAn en.wp [[user:3family6]] comments about [[Template:Album ratings]]:\n""This is an instance where the transclusion option on VE, while it does work,\nis more inconvenient than just wiki-markup.', 'In wikimarkup, if you want to\ninsert a new review into the middle of the template, i.e.', 'between reviews 3 and\n4 (rev3 and rev4), you just change rev4 to rev5 (and rev5 to 6 and so on), then\ninsert the new score.', 'With VE, you have to add a new rev parameter to the\nbottom, and move the content of ALL of the parameters affected through\ncopy-paste.', 'This is much more time consuming than editing the wikitext.""', 'For context reviews are listed in alphabetical order, initially the template\ncould be something like:\nrev1 = A Magazine\nrev1Score  = 4/5\nrev2 = CTV\nrev2Score = 1/5\nrev3 = FooMusic\nrev3Score = 5/5\nrev4 = ZedNews\nrev4Score = 6/10\n\nThe album then gets rereleased and reviewed by BetaMag.', ""This needs to be added\nat the second review, in source editing it's just a matter of changing 6\ncharacters (4→5,3→4, etc)."", 'In VE you have to create a new rev5 and rev5\nparameter, then cut and paste the values from each of rev2 - rev4 and rev2Score\n- rev4Score to their new locations then add the new data.', 'One better way to handle this would be to allow the renaming of parameters.', 'Either in the ""options"" section or by right clicking on the parameter name.', 'This is likely to affect other templates too.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+254292,VisualEditor: Let users relabel (or renumber if auto-numbered) parameters in the transclusion dialog,*** Bug 51558 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51558 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52247,VisualEditor: User personal links appear above VE dialogs,"**Author:** `rachelqa99`
+
+**Description:**
+This it the top level links English, Talk, Preferences, Watchlist etc appearing on top of references window
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: User personal links appear above VE dialogs\n\n**Author:** CODE\n\n**Description:**\nThis it the top level links English, Talk, Preferences, Watchlist etc appearing on top of references window\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor']",['BUG REPRODUCTION']
+253215,VisualEditor: User personal links appear above VE dialogs,This was fixed in the deployment earlier this week.,task_subcomment,['This was fixed in the deployment earlier this week.'],['BUG REPRODUCTION']
+253212,VisualEditor: User personal links appear above VE dialogs,Confirmed in Chrome/Mac; this looks like a general issue with z-indexes. Thanks for the catch!,task_subcomment,"['Confirmed in Chrome/Mac; this looks like a general issue with z-indexes.', 'Thanks for the catch!']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+253208,VisualEditor: User personal links appear above VE dialogs,"Created attachment 12650
+Screenshot showing issue (extracted from Word docx file)
+
+**Attached**: {F11829}",task_subcomment,['Created attachment 12650\nScreenshot showing issue (extracted from Word docx file)\n\n**Attached**: {F11829}'],['ATTACHMENT']
+253200,VisualEditor: User personal links appear above VE dialogs,"**rachelqa99** wrote:
+
+screenshot
+
+//attachment screenshotve.docx ignored as obsolete//",task_subcomment,['**rachelqa99** wrote:\n\nscreenshot\n\n//attachment screenshotve.docx ignored as obsolete//'],['OBSERVED BUG BEHAVIOR']
+52240,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","Totally a nice-to-have; it'd be good if the link inspector could inform users that they're linking through to a DAB page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50160
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59208
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49502",task_description,"[""VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link\n\nTotally a nice-to-have; it'd be good if the link inspector could inform users that they're linking through to a DAB page."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+252858,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","Change 110654 merged by jenkins-bot:
+Mark disambiguation and redirect pages in the link inspector
+
+https://gerrit.wikimedia.org/r/110654",task_subcomment,['Change 110654 merged by jenkins-bot:\nMark disambiguation and redirect pages in the link inspector\n\nGERRIT_URL'],['ACTION ON ISSUE']
+252855,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","Change 110654 had a related patch set uploaded by Alex Monk:
+Mark disambiguation and redirect pages in the link inspector
+
+https://gerrit.wikimedia.org/r/110654",task_subcomment,['Change 110654 had a related patch set uploaded by Alex Monk:\nMark disambiguation and redirect pages in the link inspector\n\nGERRIT_URL'],['ACTION ON ISSUE']
+252851,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link",Hint: Links to disambig pages can now be easily checked with the isDisambiguationPage() function introduced with Gerrit 100413.,task_subcomment,['Hint: Links to disambig pages can now be easily checked with the isDisambiguationPage() function introduced with Gerrit 100413.'],['INVESTIGATION AND EXPLORATION']
+252844,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","Can we also ask that VE warns about ""auto-links"", which is, links in the article pointing to the article itself? https://bugzilla.wikimedia.org/show_bug.cgi?id=50497 explains why those links can happen, but that is true for templates, I can't recall real reasons for wanting that to happen in the article body as well.
+So [[user:Fram]] suggested that a warning would be useful in that case.",task_subcomment,"['Can we also ask that VE warns about ""auto-links"", which is, links in the article pointing to the article itself?', ""URL explains why those links can happen, but that is true for templates, I can't recall real reasons for wanting that to happen in the article body as well."", 'So [[user:Fram]] suggested that a warning would be useful in that case.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+252839,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","**Saehrimnirwikipedia** wrote:
+
+Hi is anyone working on this since it is now deployed on more wikipedias this will become a bigger and bigger problem? Before VE people were checking if the Link was going to the right target more often because it was possible to have typos but with a drop down list they are bound to rely that what they pick will work as intended.",task_subcomment,"['**Saehrimnirwikipedia** wrote:\n\nHi is anyone working on this since it is now deployed on more wikipedias this will become a bigger and bigger problem?', 'Before VE people were checking if the Link was going to the right target more often because it was possible to have typos but with a drop down list they are bound to rely that what they pick will work as intended.']","['BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION']"
+252836,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link",*** Bug 51524 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51524 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252834,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link",The current code related to this functionality is in VisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWLinkTargetInputWidget.js if anyone wants to take a shot at it.,task_subcomment,['The current code related to this functionality is in VisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWLinkTargetInputWidget.js if anyone wants to take a shot at it.'],['SOLUTION DISCUSSION']
+252831,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","This has come up in a discussion about surging numbers of dablinks being noticed by the dab project.  If VE is the source for this uptick, we should think about getting this fix in sooner rather than later. 
+
+Discussion on en.:
+http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28miscellaneous%29#Disambiguation_in_crisis",task_subcomment,"['This has come up in a discussion about surging numbers of dablinks being noticed by the dab project.', 'If VE is the source for this uptick, we should think about getting this fix in sooner rather than later.', 'Discussion on en.', ':\nURL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+252827,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link",This has been implemented in the old editor (WikiEditor). See https://gerrit.wikimedia.org/r/#/c/70564/ for the implementation details. It should be easy to add this feature to VisualEditor as well.,task_subcomment,"['This has been implemented in the old editor (WikiEditor).', 'See URL for the implementation details.', 'It should be easy to add this feature to VisualEditor as well.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+252823,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link",*** Bug 50986 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50986 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+252818,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","Sure; I don't think we're saying it shouldn't /let/ the user, merely that it should inform the user.",task_subcomment,"[""Sure; I don't think we're saying it shouldn't /let/ the user, merely that it should inform the user.""]",['SOLUTION DISCUSSION']
+252811,"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link","I agree for disambiguation pages.
+
+But I believe creating a wikilink to a redirect page is OK. For instance linking to ""HTC Super3"" even though it is actually a redirect to ""HTC Super"".",task_subcomment,"['I agree for disambiguation pages.', 'But I believe creating a wikilink to a redirect page is OK. For instance linking to ""HTC Super3"" even though it is actually a redirect to ""HTC Super"".']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52231,Jenkins: migrate qunit jobs from master to gallium,"The Qunit jobs are currently running on the master, they need to be moved to
+gallium slave nodes.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",task_description,"['Jenkins: migrate qunit jobs from master to gallium\n\nThe Qunit jobs are currently running on the master, they need to be moved to\ngallium slave nodes.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+252258,Jenkins: migrate qunit jobs from master to gallium,I have updated some files ownerships manually and validated qunit tests jobs are passing for MediaWiki core and VisualEditor.,task_subcomment,['I have updated some files ownerships manually and validated qunit tests jobs are passing for MediaWiki core and VisualEditor.'],['OBSERVED BUG BEHAVIOR']
+252255,Jenkins: migrate qunit jobs from master to gallium,"Change 72083 merged by Hashar:
+tie qunit jobs to slaves
+
+https://gerrit.wikimedia.org/r/72083",task_subcomment,['Change 72083 merged by Hashar:\ntie qunit jobs to slaves\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+252252,Jenkins: migrate qunit jobs from master to gallium,"Change 72086 merged by coren:
+contint: file perms for qunit jobs
+
+https://gerrit.wikimedia.org/r/72086",task_subcomment,['Change 72086 merged by coren:\ncontint: file perms for qunit jobs\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+252247,Jenkins: migrate qunit jobs from master to gallium,"Change 72086 had a related patch set uploaded by Hashar:
+contint: migrate qunit jobs to Jenkins slaves
+
+https://gerrit.wikimedia.org/r/72086",task_subcomment,['Change 72086 had a related patch set uploaded by Hashar:\ncontint: migrate qunit jobs to Jenkins slaves\n\nGERRIT_URL'],['ACTION ON ISSUE']
+252243,Jenkins: migrate qunit jobs from master to gallium,"Change 72083 had a related patch set uploaded by Hashar:
+tie qunit jobs to slaves
+
+https://gerrit.wikimedia.org/r/72083",task_subcomment,['Change 72083 had a related patch set uploaded by Hashar:\ntie qunit jobs to slaves\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+52225,"VisualEditor: Non-primary edit tab 
  •  should have class=""collapsible""","Screenshot: Narrow window
+
+When space is scarce (for example at high zoom, or when the window is very narrow), the ""View history"" tab is moved to the drop-down menu (that also includes ""Delete"", ""Move"", etc.) so that the action remains accessible.
+
+The ""Edit"" and ""Edit source"" tabs don't seem to do the same; they stay where they are, which prevents them from being used in similar situations (see attached screenshots).
+
+It would imho make sense to migrate both tabs to the drop-down menu as well when there isn't enough space to display them at their usual location, so that users can still access the edit modes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11766}",task_description,"['VisualEditor: Non-primary edit tab 
  •  should have class=""collapsible""\n\nScreenshot: Narrow window\n\nWhen space is scarce (for example at high zoom, or when the window is very narrow), the ""View history"" tab is moved to the drop-down menu (that also includes ""Delete"", ""Move"", etc.)', 'so that the action remains accessible.', 'The ""Edit"" and ""Edit source"" tabs don\'t seem to do the same; they stay where they are, which prevents them from being used in similar situations (see attached screenshots).', ""It would imho make sense to migrate both tabs to the drop-down menu as well when there isn't enough space to display them at their usual location, so that users can still access the edit modes."", '--------------------------\n**Version**: unspecified\n**Severity**: minor\n\n**Attached**: {F11766}']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+251918,"VisualEditor: Non-primary edit tab 
  •  should have class=""collapsible""","Change 123503 merged by jenkins-bot:
+Give the edit tab 
  •  closest to the collapsed tabs menu class=collapsible
+
+https://gerrit.wikimedia.org/r/123503",task_subcomment,['Change 123503 merged by jenkins-bot:\nGive the edit tab 
  •  closest to the collapsed tabs menu class=collapsible\n\nGERRIT_URL'],['ACTION ON ISSUE']
+251911,"VisualEditor: Non-primary edit tab 
  •  should have class=""collapsible""","Change 123503 had a related patch set uploaded by Alex Monk:
+Give the edit tab 
  •  closest to the collapsed tabs menu class=collapsible
+
+https://gerrit.wikimedia.org/r/123503",task_subcomment,['Change 123503 had a related patch set uploaded by Alex Monk:\nGive the edit tab 
  •  closest to the collapsed tabs menu class=collapsible\n\nGERRIT_URL'],['ACTION ON ISSUE']
+251902,"VisualEditor: Non-primary edit tab 
  •  should have class=""collapsible""","(In reply to comment #0)
+> It would imho make sense to migrate both tabs to the drop-down menu as well
+> when there isn't enough space to display them at their usual location, so
+> that
+> users can still access the edit modes.
+
+""Edit"" is not normally collapsed, but it would make sense for ""Edit source"". You'd just add class=""collapsible"" on the 
  •  and it will magically work.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n""Edit"" is not normally collapsed, but it would make sense for ""Edit source"".', 'You\'d just add class=""collapsible"" on the 
  •  and it will magically work.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251895,"VisualEditor: Non-primary edit tab 
  •  should have class=""collapsible""","Created attachment 12643
+Screenshot: High zoom
+
+**Attached**: {F11767}",task_subcomment,['Created attachment 12643\nScreenshot: High zoom\n\n**Attached**: {F11767}'],['ATTACHMENT']
+52216,VisualEditor: Middle-clicking/Ctrl+clicking on wikilinks fails when using full index.php URL,"1. Go to http://en.wikipedia.org/w/index.php?title=Black&veaction=edit
+2. Middle-click or ctrl+click on any wikilink
+
+You get a 404 page, e.g. http://en.wikipedia.org/w/Outer_space
+
+VE should use fully qualified hrefs (/wiki/foo), just as MW always does.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Middle-clicking/Ctrl+clicking on wikilinks fails when using full index.php URL\n\n1.', 'Go to URL\n2.', 'Middle-click or ctrl+click on any wikilink\n\nYou get a 404 page, e.g.', 'URL\n\nVE should use fully qualified hrefs (/wiki/foo), just as MW always does.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251419,VisualEditor: Middle-clicking/Ctrl+clicking on wikilinks fails when using full index.php URL,"I think this is a duplicate of 48915, which clearly we should fix right now.
+
+*** This bug has been marked as a duplicate of bug 48915 ***",task_subcomment,"['I think this is a duplicate of 48915, which clearly we should fix right now.', '*** This bug has been marked as a duplicate of bug 48915 ***']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+52208,VisualEditor: Possible to have links nested inside links,"(Sorry for carelessly filing a dupe before (bug 50207) - I have checked this one, but if it is a dupe, you are most welcome to trout me for wasting your time!)
+
+1. Edit [[testwiki:VisualEditor:Links]] in VE
+2. Make a selection like
+
+     Golden Gate National Recreation [Area is the] best
+
+   (partly inside the link, partly outside it)
+3. Click the ""Link"" toolbar button and make a link to any page
+4. Click in the word ""Area"" to move the cursor there
+
+Two link icons appear in the floating toolbar.
+
+5. Save page > Review changes
+
+Wikitext output has two links side-by-side, pointing to the same target.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Possible to have links nested inside links\n\n(Sorry for carelessly filing a dupe before (bug 50207) - I have checked this one, but if it is a dupe, you are most welcome to trout me for wasting your time!)', '1.', 'Edit [[testwiki:VisualEditor:Links]] in VE\n2.', 'Make a selection like\n\n     Golden Gate National Recreation [Area is the] best\n\n   (partly inside the link, partly outside it)\n3.', 'Click the ""Link"" toolbar button and make a link to any page\n4.', 'Click in the word ""Area"" to move the cursor there\n\nTwo link icons appear in the floating toolbar.', '5.', 'Save page > Review changes\n\nWikitext output has two links side-by-side, pointing to the same target.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250969,VisualEditor: Possible to have links nested inside links,Merged and we'll push this to production in the next hour or so.,task_subcomment,"[""Merged and we'll push this to production in the next hour or so.""]",['SOLUTION USAGE']
+250958,VisualEditor: Possible to have links nested inside links,Related URL: https://gerrit.wikimedia.org/r/70644 (Gerrit Change I1cab7f3cc4fc9589eced01ad38c59fe5b9622a57),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I1cab7f3cc4fc9589eced01ad38c59fe5b9622a57)'],['OBSERVED BUG BEHAVIOR']
+250949,VisualEditor: Possible to have links nested inside links,"(In reply to comment #0)
+> (Sorry for carelessly filing a dupe before (bug 50207) - I have checked this
+> one, but if it is a dupe, you are most welcome to trout me for wasting your
+> time!)
+
+Ha, no worries; dupe's aren't in any way useless (it reminds us that it's a real problem we need to fix really soon!). It's mostly just that it's a waste of your time. :-(
+
+> 
+> 1. Edit [[testwiki:VisualEditor:Links]] in VE
+> 2. Make a selection like
+> 
+>      Golden Gate National Recreation [Area is the] best
+> 
+>    (partly inside the link, partly outside it)
+> 3. Click the ""Link"" toolbar button and make a link to any page
+> 4. Click in the word ""Area"" to move the cursor there
+> 
+> Two link icons appear in the floating toolbar.
+> 
+> 5. Save page > Review changes
+> 
+> Wikitext output has two links side-by-side, pointing to the same target.
+
+Yeah, this is definitely a fail on our part (and a regression!). Thanks for the spot; assigning to Ed.",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nHa, no worries; dupe's aren't in any way useless (it reminds us that it's a real problem we need to fix really soon!)."", ""It's mostly just that it's a waste of your time."", ':-(\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah, this is definitely a fail on our part (and a regression!).', 'Thanks for the spot; assigning to Ed.']","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'ACTION ON ISSUE']"
+52197,VisualEditor: Make ve.ui.PopupWidget#display signature not insane,"3 parameters is the limit, 6 is crazy.
+
+ve.ui.PopupWidget.prototype.display = function ( x, y, width, height, transition, embedded ) {
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Make ve.ui.PopupWidget#display signature not insane\n\n3 parameters is the limit, 6 is crazy.', 've.ui.PopupWidget.prototype.display = function ( x, y, width, height, transition, embedded ) {\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+250314,VisualEditor: Make ve.ui.PopupWidget#display signature not insane,"Looking pretty good. It's been separated and the method itself (OO.ui.PopupWidget#display) no longer exists.
+
+https://github.com/wikimedia/oojs-ui/blob/e43584b420/src/widgets/PopupWidget.js",task_subcomment,"['Looking pretty good.', ""It's been separated and the method itself (OO.ui.PopupWidget#display) no longer exists."", 'URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52182,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","screenshot of nested templates in VisualEditor
+
+Templates are sometimes nested into one another. For example, https://en.wikipedia.org/wiki/Template:Chembox relies on sub-templates like https://en.wikipedia.org/wiki/Template:Chembox_Properties , which itself relies on other templates etc.
+
+VisualEditor currently doesn't seem to handle these sub-templates. It shows a nice interface for the top-level template, then shows wikitext for the others (see screenshot).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11704}",task_description,"['VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g.', 'infoboxes)\n\nscreenshot of nested templates in VisualEditor\n\nTemplates are sometimes nested into one another.', 'For example, URL relies on sub-templates like URL , which itself relies on other templates etc.', ""VisualEditor currently doesn't seem to handle these sub-templates."", 'It shows a nice interface for the top-level template, then shows wikitext for the others (see screenshot).', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n\n**Attached**: {F11704}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+1624617,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)",https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Automatic_visual_editing_of_spanned_templates,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+1198565,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","This could be particularly helpful for common inline templates, such as the {{lang}} templates.  When readers see this:
+
+```
+Alaska (/əˈlæskə/ (listen); Aleut: Alax̂sxax̂; Inupiaq: Alaskaq; Russian: Аляска, translit. Alyaska) is a U.S. state in the northwest extremity of North America. 
+```
+
+the wikitext is this:
+
+```
+'''Alaska''' ({{IPAc-en|audio=en-us-Alaska.ogg|ə|ˈ|l|æ|s|k|ə}}; {{lang-ale|Alax̂sxax̂}}; {{Lang-ik|Alaskaq}}; {{Lang-ru|Аляска|translit=Alyaska}}) is a [[U.S. state]] in the northwest extremity of [[North America]]. 
+```
+
+and the editor in the visual editor sees four templates.  It would be much nicer if you could just stick your cursor in the middle of ""Aleut: Alax̂sxax̂"" and change that without having to open any dialog boxes at all.",task_subcomment,"['This could be particularly helpful for common inline templates, such as the {{lang}} templates.', 'When readers see this:\n\n``CODE`CODE`CODE``\n\nand the editor in the visual editor sees four templates.', 'It would be much nicer if you could just stick your cursor in the middle of ""Aleut: Alax̂sxax̂"" and change that without having to open any dialog boxes at all.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+754131,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","Hey Riccardo, will try and find an answer for you.",task_subcomment,"['Hey Riccardo, will try and find an answer for you.']",['INVESTIGATION AND EXPLORATION']
+747843,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","Hello, Riccardo from WikiToLearn here.
+
+We use a lot of templates in our books, and, especially for maths, we would love to have visual editing of templates. I have seen that in T53374 the type for coherent wikitext was added. We would love to implement a solution similar to what has been done for the ""Insert Media"" dialog where there is a lighter VisualEditor is present when the user edits the caption. Our desired behiavor is to have the same editor show up when the type associated with the parameter is of type `content`.
+
+However, we would only do this if you think it is a good idea, and ideally will accept the patch, to avoid forking an extension as big as VisualEditor. Is it something that would be interesting?",task_subcomment,"['Hello, Riccardo from WikiToLearn here.', 'We use a lot of templates in our books, and, especially for maths, we would love to have visual editing of templates.', 'I have seen that in T53374 the type for coherent wikitext was added.', 'We would love to implement a solution similar to what has been done for the ""Insert Media"" dialog where there is a lighter VisualEditor is present when the user edits the caption.', 'Our desired behiavor is to have the same editor show up when the type associated with the parameter is of type CODE.', 'However, we would only do this if you think it is a good idea, and ideally will accept the patch, to avoid forking an extension as big as VisualEditor.', 'Is it something that would be interesting?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+249561,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)",*** Bug 52786 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52786 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249557,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","(In reply to comment #10)
+> In reply to Gabriel Wicke, substing {{subst:div col}} would give 
     class=""mw-columns-2""> .. 
    . This would work fine for all subsequent
+> edits
+> with VE, but not for editors using wikitext.
+
+I don't see a big difference between a div start / end tag and {{div col}} / {{div col end}} template pairs. Both are disconnected and of roughly the same text length.",task_subcomment,"[""(In reply to comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't see a big difference between a div start / end tag and {{div col}} / {{div col end}} template pairs."", 'Both are disconnected and of roughly the same text length.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+249554,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","This has come up a few times at 
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#a_sensible_way_to_edit_.7B.7Bdiv_col.7D.7D_sections
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Bulleted_lists
+
+In reply to Gabriel Wicke, substing {{subst:div col}} would give 
     .. 
    . This would work fine for all subsequent edits with VE, but not for editors using wikitext.
+
+Ideally list in {{div col}} blocks would be edited in place. Just as if it was a normal list. 
+
+I think this points to a wider question: that some templates are going to need special ways of editing them. You might be able to add a field to the template data, say, ""type"":""wikitext-block"" indicating its a block which should be edited in place. Some sort of extension mechanism could be used, say with an associated  lua module providing hints to VE on how to edit the data.",task_subcomment,"['This has come up a few times at \nURL\nURL\n\nIn reply to Gabriel Wicke, substing {{subst:div col}} would give 
     .. 
    .', 'This would work fine for all subsequent edits with VE, but not for editors using wikitext.', 'Ideally list in {{div col}} blocks would be edited in place.', 'Just as if it was a normal list.', 'I think this points to a wider question: that some templates are going to need special ways of editing them.', 'You might be able to add a field to the template data, say, ""type"":""wikitext-block"" indicating its a block which should be edited in place.', 'Some sort of extension mechanism could be used, say with an associated  lua module providing hints to VE on how to edit the data.']","['WORKAROUNDS', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+249550,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)",*** Bug 51485 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51485 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249545,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","We also need to be able to add the template {{tl|multiple issues}} around existing tags: when editing [[Dadloi]] I wanted to add a second maintenance tag and then tidy them up into {{tl|mi}}, but of course had to do the latter in Edit Source after my VE edit.",task_subcomment,"['We also need to be able to add the template {{tl|multiple issues}} around existing tags: when editing [[Dadloi]] I wanted to add a second maintenance tag and then tidy them up into {{tl|mi}}, but of course had to do the latter in Edit Source after my VE edit.']",['SOLUTION DISCUSSION']
+249538,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","**kwwilliams** wrote:
+
+I'm seeing a few comments that imply that nested templates are somehow the result of a poorly thought out design: I take issue with that. Take {{BillboardURLbyName}}, for example: it's got a very simple job: give it the name of a musical artist, and it will return the URL to the Billboard page for that artist's charts or biography. Billboard loves to redesign its site periodically and builds the URL based on six digit numbers, so we really don't want URL hardcoding going on. 
+
+It would be a very poor design if we required every template that could accept a URL to understand how to translate an artist name into a URL. It's much better to do it the way we do: pass {{BillboardURLbyName|artist name}} as an argument to templates that require URLs, and let each template do its own job.",task_subcomment,"[""**kwwilliams** wrote:\n\nI'm seeing a few comments that imply that nested templates are somehow the result of a poorly thought out design: I take issue with that."", ""Take {{BillboardURLbyName}}, for example: it's got a very simple job: give it the name of a musical artist, and it will return the URL to the Billboard page for that artist's charts or biography."", ""Billboard loves to redesign its site periodically and builds the URL based on six digit numbers, so we really don't want URL hardcoding going on."", 'It would be a very poor design if we required every template that could accept a URL to understand how to translate an artist name into a URL.', ""It's much better to do it the way we do: pass {{BillboardURLbyName|artist name}} as an argument to templates that require URLs, and let each template do its own job.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+249530,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","Adding keywords to summary to make this searchable.
+
+As noted in bug 50595, this bug prevents copy-pasting formatted text from the main document into a template.",task_subcomment,"['Adding keywords to summary to make this searchable.', 'As noted in bug 50595, this bug prevents copy-pasting formatted text from the main document into a template.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+249521,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)",*** Bug 50595 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50595 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249509,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","Something like 
     .. 
     with the proper class definition in common.css would work better for editing in VE, as the wrapper won't be template-generated then.
+
+Generally visual editing works best if a template produces a self-contained part of a page ('properly nested') rather than cut-up start / content / end templates.",task_subcomment,"['Something like 
     .. 
     with the proper class definition in common.css would work better for editing in VE, as the wrapper won\'t be template-generated then.', ""Generally visual editing works best if a template produces a self-contained part of a page ('properly nested') rather than cut-up start / content / end templates.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+249500,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","This bug affects all attempts to edit items in lists which are set out in columns using {{tl|div col}} or {{tl|colbegin}}, so is going to disconcert a lot of editors. I hope it's near the top of the ""to-do list"":  see [[Wikipedia:VisualEditor/Feedback#Editing_within_a_multi-column_list_.28ie_between_.7B.7Bcolbegin.7D.7D_and_.7B.7Bcolend.7D.7D.29]]",task_subcomment,"['This bug affects all attempts to edit items in lists which are set out in columns using {{tl|div col}} or {{tl|colbegin}}, so is going to disconcert a lot of editors.', 'I hope it\'s near the top of the ""to-do list"":  see [[Wikipedia:VisualEditor/Feedback#Editing_within_a_multi-column_list_.28ie_between_.7B.7Bcolbegin.7D.7D_and_.7B.7Bcolend.7D.7D.29]]']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+249491,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)",*** Bug 50355 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50355 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249486,"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","These are currently supported, just as wikitext. :-)
+
+It depends on some changes in Parsoid (which they've put on ice during deployment), and some tweaks in VisualEditor, but this should be relatively do-able.",task_subcomment,"['These are currently supported, just as wikitext.', "":-)\n\nIt depends on some changes in Parsoid (which they've put on ice during deployment), and some tweaks in VisualEditor, but this should be relatively do-able.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+52172,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,"See https://en.wikipedia.org/wiki/Template:Userspace draft - when rendered in the VE it displays the mainspace appropriate text regardless of what namespace it is in.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"[""VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in\n\nSee URL draft - when rendered in the VE it displays the mainspace appropriate text regardless of what namespace it is in."", '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['BUG REPRODUCTION', 'BUG REPRODUCTION']"
+249036,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,I think this was resolved in Gerrit change 127388,task_subcomment,['I think this was resolved in Gerrit change 127388'],['SOLUTION DISCUSSION']
+249033,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,"Is this fixed?
+
+When I look at this page which uses [[template:userspace draft]]:
+
+https://en.wikipedia.org/wiki/User:JohnArmagh/Heads_of_Government_of_the_State_of_Victoria,_Australia?veaction=edit
+
+The appropriate message is shown.
+
+However part of that box should render as
+""This draft was last edited 13 months ago""
+but in VE is renders as
+This draft was last edited 1 second's time""
+
+which means {{REVISIONTIMESTAMP}} isnt expanding correctly as, based on the future tense, it is giving a value that is CURRENTTIME+1..?",task_subcomment,"['Is this fixed?', 'When I look at this page which uses [[template:userspace draft]]:\n\nURL\n\nThe appropriate message is shown.', 'However part of that box should render as\n""This draft was last edited 13 months ago""\nbut in VE is renders as\nThis draft was last edited 1 second\'s time""\n\nwhich means {{REVISIONTIMESTAMP}} isnt expanding correctly as, based on the future tense, it is giving a value that is CURRENTTIME+1..?']","['BUG REPRODUCTION', 'SOLUTION USAGE', 'BUG REPRODUCTION']"
+249028,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,*** Bug 50582 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50582 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249024,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,"This was originally about the Parsoid issue, which is now fixed, but re-purposing to be about the DM re-render to PHP parser issue.",task_subcomment,"['This was originally about the Parsoid issue, which is now fixed, but re-purposing to be about the DM re-render to PHP parser issue.']",['BUG REPRODUCTION']
+249018,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,"I'm guessing this is actually about newly inserted {{NAMESPACE}} calls:
+
+http://www.mediawiki.org/wiki/User:GWicke/TestNamespace?veaction=edit
+
+Reassigning to VE.",task_subcomment,"[""I'm guessing this is actually about newly inserted {{NAMESPACE}} calls:\n\nURL\n\nReassigning to VE.""]",['ACTION ON ISSUE']
+249013,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,"We pass in the title to the PHP preprocessor, so namespace-dependent parserfunctions should work as expected. Are you talking about Parsoid rendering or the VE's preview rendering after inserting a new template?",task_subcomment,"['We pass in the title to the PHP preprocessor, so namespace-dependent parserfunctions should work as expected.', ""Are you talking about Parsoid rendering or the VE's preview rendering after inserting a new template?""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+249005,VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,"By the time we get the template, the evaluation of the parser functions - in this case, {{NAMESPACE}} - has already been done (by Parsoid). In general, I believe that most parser functions are just ""return true"" at this point, and will be coming in future.",task_subcomment,"['By the time we get the template, the evaluation of the parser functions - in this case, {{NAMESPACE}} - has already been done (by Parsoid).', 'In general, I believe that most parser functions are just ""return true"" at this point, and will be coming in future.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+52171,VisualEditor: Re-label the group UI element in the reference dialog to explain what it does,"In the Reference editor we have two fields:
+
+""Re-use by this name""
+""Use this group""
+
+These names are useless for new editors (too cryptic and unclear - what is ""re-use""? a verb? referring to what?) and also unhelpful for established users (they need to know that these are totally identical to the name="""" and group="""" attributes). It is also not clear that they are only occasionally needed.
+
+Something simpler, like ""Reference name (optional)"" and ""Reference group (optional)"" could be better. 
+
+Same in the Reference list editor:
+
+""Use this group"" -> ""Display references belonging to this group (optional)""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Re-label the group UI element in the reference dialog to explain what it does\n\nIn the Reference editor we have two fields:\n\n""Re-use by this name""\n""Use this group""\n\nThese names are useless for new editors (too cryptic and unclear - what is ""re-use""?', 'a verb?', 'referring to what?)', 'and also unhelpful for established users (they need to know that these are totally identical to the name="""" and group="""" attributes).', 'It is also not clear that they are only occasionally needed.', 'Something simpler, like ""Reference name (optional)"" and ""Reference group (optional)"" could be better.', 'Same in the Reference list editor:\n\n""Use this group"" -> ""Display references belonging to this group (optional)""\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+248960,VisualEditor: Re-label the group UI element in the reference dialog to explain what it does,"(In reply to comment #1)
+> There is also a request in that discussion about whether ""Transclusion"" could
+> be renamed to something in plain English, like ""Templates"".
+
+The problem is that they aren't just templates - there are also magic words and parser functions as well, like Wikidata invocations or other oddities that MediaWiki supports. Lumping them all in as templates makes things much harder to explain in documentation.",task_subcomment,"[""(In reply to comment #1)\nQUOTE\nQUOTE\n\nThe problem is that they aren't just templates - there are also magic words and parser functions as well, like Wikidata invocations or other oddities that MediaWiki supports."", 'Lumping them all in as templates makes things much harder to explain in documentation.']","['MOTIVATION', 'SOLUTION DISCUSSION']"
+248955,VisualEditor: Re-label the group UI element in the reference dialog to explain what it does,"There is also a request in that discussion about whether ""Transclusion"" could be renamed to something in plain English, like ""Templates"".",task_subcomment,"['There is also a request in that discussion about whether ""Transclusion"" could be renamed to something in plain English, like ""Templates"".']",['INVESTIGATION AND EXPLORATION']
+52167,VisualEditor: Support unicode equivalence for client side text searches,"Planned features, such as searching for an existing reference by content, will require us to implement some http://en.wikipedia.org/wiki/Unicode_equivalence .
+
+We will probably want to use NFKD (""Characters are decomposed by compatibility, and multiple combining characters are arranged in a specific order."") to catch cases such as 'ff' === 'ff', and we will probably want to strip combining characters (i.e. all accents), so that 'Amelie' === 'Amélie'.
+
+https://github.com/walling/unorm looks like a good library for the job. We may want to fork it into UnicodeJS.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Support unicode equivalence for client side text searches\n\nPlanned features, such as searching for an existing reference by content, will require us to implement some URL .', 'We will probably want to use NFKD (""Characters are decomposed by compatibility, and multiple combining characters are arranged in a specific order."")', ""to catch cases such as 'ff' === 'ff', and we will probably want to strip combining characters (i.e."", ""all accents), so that 'Amelie' === 'Amélie'."", 'URL looks like a good library for the job.', 'We may want to fork it into UnicodeJS.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+248733,VisualEditor: Support unicode equivalence for client side text searches,"So, if I'm understanding correctly, when the user starts a search we want to generate a normalised copy of the entire document in NFKD. (Otherwise we've got a problem keeping two copies in sync). Is this acceptable efficiency-wise?
+
+Could we force the characters in the document model to be in NFC? Could Parsoid provide the article text in NFC? (This is partially off-topic, but we probably want to consider different normalisation issues together).",task_subcomment,"[""So, if I'm understanding correctly, when the user starts a search we want to generate a normalised copy of the entire document in NFKD."", ""(Otherwise we've got a problem keeping two copies in sync)."", 'Is this acceptable efficiency-wise?', 'Could we force the characters in the document model to be in NFC?', 'Could Parsoid provide the article text in NFC?', '(This is partially off-topic, but we probably want to consider different normalisation issues together).']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+248728,VisualEditor: Support unicode equivalence for client side text searches,Agreed. You're likely to do that naturally when displaying search results but it would be a consideration if you try to highlight the matching substring in the result (a non-trivial problem when normalisation is involved),task_subcomment,"['Agreed.', ""You're likely to do that naturally when displaying search results but it would be a consideration if you try to highlight the matching substring in the result (a non-trivial problem when normalisation is involved)""]","['EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION']"
+248723,VisualEditor: Support unicode equivalence for client side text searches,"It's worth noting that in most software, many common grapheme clusters are displayed more correctly when encoded as a single unicode character than when encoded with combining characters. For example, 'sgrîn' (""sgr\u00EEn"") displays correctly in my version of Firefox on Linux, but the equivalent decomposed string 'sgrîn' (""sgri\u0302n"") shows up with the dot still on the i and the accent in the wrong place (either uncentered over the i, or over the n, depending on the font).
+
+Therefore, while we may want to search and process text using decomposed forms, we should probably use the composed forms for display.",task_subcomment,"[""It's worth noting that in most software, many common grapheme clusters are displayed more correctly when encoded as a single unicode character than when encoded with combining characters."", 'For example, \'sgrîn\' (""sgr\\u00EEn"") displays correctly in my version of Firefox on Linux, but the equivalent decomposed string \'sgrîn\' (""sgri\\u0302n"") shows up with the dot still on the i and the accent in the wrong place (either uncentered over the i, or over the n, depending on the font).', 'Therefore, while we may want to search and process text using decomposed forms, we should probably use the composed forms for display.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+248718,VisualEditor: Support unicode equivalence for client side text searches,"I don't see why not. We may want to add things like 'ß' => 'ss' in German, or final vs. non-final sigma in Greek (https://en.wikipedia.org/wiki/Sigma#Character_Encodings)",task_subcomment,"[""I don't see why not."", ""We may want to add things like 'ß' => 'ss' in German, or final vs. non-final sigma in Greek (URL""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+248713,VisualEditor: Support unicode equivalence for client side text searches,"We probably shouldn't strip down beyond NFKD. For some languages, 'ä' should be equivalent to 'a'; for others, it shouldn't be equivalent to anything; for still others, it should be equivalent to 'ae'.
+
+Will it be feasible to implement language-specific search on top of this?",task_subcomment,"[""We probably shouldn't strip down beyond NFKD."", ""For some languages, 'ä' should be equivalent to 'a'; for others, it shouldn't be equivalent to anything; for still others, it should be equivalent to 'ae'."", 'Will it be feasible to implement language-specific search on top of this?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+52126,VisualEditor: Can't copy/paste header from start of document without losing formatting,"See https://en.wikipedia.org/w/index.php?title=User:JohnCD/VEtest&diff=prev&oldid=561397375 - the header is de-headered, and a spurious nowiki tag added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Can't copy/paste header from start of document without losing formatting\n\nSee URL - the header is de-headered, and a spurious nowiki tag added."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+1038472,VisualEditor: Can't copy/paste header from start of document without losing formatting,"I peeked at the revision:
+
+```name=Before
+==L2 Header==
+===L3 header===
+Some text including '''bold '''and ''italic ''and '''''both '''''at once
+[..]
+==Fourth L2 header==
+```
+
+```name=After saving
+==L2 Header==
+===L3 header===
+Some text including '''bold '''and ''italic ''and '''''both '''''at once
+[..]
+==Fourth L2 header==
+L2 Header
+===L3 header===
+Some text including '''bold '''and ''italic ''and '''''both ''at once
+===Another L3 header===
+This line includes a [[Wikipedia:Wikilinks|wikilink]] as a sample
+====
+```
+
+I presume the edit was to select from start (""L2 Header"") until end of first sentence, copy that, and paste at the end. Nothing the bugs: 1) `L2 Header` didn't become a heading, and 2) odd `` in a heading at the end. I could not reproduce this on testwiki today. Closing as resolved.",task_subcomment,"['I peeked at the revision:\n\n``CODE`CODE`CODE`CODEL2 HeaderCODE` in a heading at the end.', 'I could not reproduce this on testwiki today.', 'Closing as resolved.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+1038391,VisualEditor: Can't copy/paste header from start of document without losing formatting,"I can't reproduce this. I'm not sure what the original issue was, given the missing reproduction page, but a heading at the beginning doesn't seem to behave in any way differently than other headings.
+
+To copy a heading along with the formatting, you have to select it together with the closing tag, which is a bit awkward and not obvious, but it's the same for all headings.",task_subcomment,"[""I can't reproduce this."", ""I'm not sure what the original issue was, given the missing reproduction page, but a heading at the beginning doesn't seem to behave in any way differently than other headings."", ""To copy a heading along with the formatting, you have to select it together with the closing tag, which is a bit awkward and not obvious, but it's the same for all headings.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+1038389,VisualEditor: Can't copy/paste header from start of document without losing formatting,"> See https://en.wikipedia.org/w/index.php?title=User:JohnCD/VEtest&diff=prev&oldid=561397375 - the header is de-headered, and a spurious nowiki tag added.
+
+This link is dead, it seems the page was deleted.",task_subcomment,"['QUOTE\n\nThis link is dead, it seems the page was deleted.']",['OBSERVED BUG BEHAVIOR']
+533273,VisualEditor: Can't copy/paste header from start of document without losing formatting,"It doesn't really matter if the header is the first one, and also happens when the entire section is selected.",task_subcomment,"[""It doesn't really matter if the header is the first one, and also happens when the entire section is selected.""]",['OBSERVED BUG BEHAVIOR']
+246345,VisualEditor: Can't copy/paste header from start of document without losing formatting,*** Bug 54728 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54728 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+246337,VisualEditor: Can't copy/paste header from start of document without losing formatting,"Can't reproduce the last heading nowiki-ing, but the first of a document appears to be unable to copy with formatting.",task_subcomment,"[""Can't reproduce the last heading nowiki-ing, but the first of a document appears to be unable to copy with formatting.""]",['OBSERVED BUG BEHAVIOR']
+52113,VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption,"See https://en.wikipedia.org/wiki/Chloroplast?veaction=edit for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption\n\nSee URL for example."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245424,VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption,Gerrit 70336 is a quick hack to fix this in VisualEditor. Parsoid bug for a proper fix (longer-term) is bug 50142.,task_subcomment,"['Gerrit 70336 is a quick hack to fix this in VisualEditor.', 'Parsoid bug for a proper fix (longer-term) is bug 50142.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+245416,VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption,https://gerrit.wikimedia.org/r/70336 (Gerrit Change I24491979bc7a27d2380924e48cb677b01e9f8f9b) | change APPROVED and MERGED [by jenkins-bot],task_subcomment,['GERRIT_URL (Gerrit Change I24491979bc7a27d2380924e48cb677b01e9f8f9b) | change APPROVED and MERGED [by jenkins-bot]'],['OBSERVED BUG BEHAVIOR']
+245409,VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption,Related URL: https://gerrit.wikimedia.org/r/70336 (Gerrit Change I24491979bc7a27d2380924e48cb677b01e9f8f9b),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I24491979bc7a27d2380924e48cb677b01e9f8f9b)'],['OBSERVED BUG BEHAVIOR']
+245404,VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption,"It looks like this is [[File:…|right|«alt text»]] is getting wrongly interpreted by Parsoid as a thumb image as opposed to a block image (which doesn't have a caption):
+
+[[File:{{Remove file prefix|{{{1|{{{image|Example.svg}}}}}}}}|right|{{Str number/trim|{{{3|{{{width|250px}}}}}}}}px|{{{2|{{{caption|Caption goes here.}}}}}}]]
+
+->
+
+
    
+  
+  
    Structure of a typical higher-plant chloroplast
    
+
    
+
+(The 
     shouldn't be set, and also there should be an alt="""" set.)",task_subcomment,"['It looks like this is [[File:…|right|«alt text»]] is getting wrongly interpreted by Parsoid as a thumb image as opposed to a block image (which doesn\'t have a caption):\n\n[[File:{{Remove file prefix|{{{1|{{{image|Example.svg}}}}}}}}|right|{{Str number/trim|{{{3|{{{width|250px}}}}}}}}px|{{{2|{{{caption|Caption goes here.}}}}}}]]\n\n->\n\n
    \n  \n  
    Structure of a typical higher-plant chloroplast
    \n
    \n\n(The 
     shouldn\'t be set, and also there should be an alt="""" set.)']",['OBSERVED BUG BEHAVIOR']
+245397,VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption,"First image, top right; I suspect stupidity in the {{Plain image}} template.",task_subcomment,"['First image, top right; I suspect stupidity in the {{Plain image}} template.']",['OBSERVED BUG BEHAVIOR']
+245391,VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption,"(In reply to comment #0)
+> See https://en.wikipedia.org/wiki/Chloroplast?veaction=edit for example.
+
+Can you say where? There's 27 images on that page and 15 of them are non-captioned images, but I don't see the alt-text coming through for them.",task_subcomment,"['(In reply to comment #0)\nQUOTE\n\nCan you say where?', ""There's 27 images on that page and 15 of them are non-captioned images, but I don't see the alt-text coming through for them.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52100,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","https://en.wikipedia.org/w/index.php?title=AES11&diff=prev&oldid=561340674
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T57769}
+{T61647}",task_description,"['VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\n{T57769}\n{T61647}']",['OBSERVED BUG BEHAVIOR']
+445461,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",Split that into {T96395} as it's mobile-specific.,task_subcomment,"[""Split that into {T96395} as it's mobile-specific.""]",['SOLUTION DISCUSSION']
+439847,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",It looks like this is still happening: https://en.wikipedia.org/w/index.php?diff=655361654,task_subcomment,['It looks like this is still happening: URL'],['OBSERVED BUG BEHAVIOR']
+436280,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",Indeed.,task_subcomment,['Indeed.'],['OBSERVED BUG BEHAVIOR']
+435947,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","If I understand correctly, the fix was deployed as part of version 1.25wmf23, which hasn't arrived to Wikipedias yet. It'll be deployed there tomorrow (April 1).",task_subcomment,"[""If I understand correctly, the fix was deployed as part of version 1.25wmf23, which hasn't arrived to Wikipedias yet."", ""It'll be deployed there tomorrow (April 1).""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+435922,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",See [[https://tt.wikipedia.org/w/index.php?title=%D0%9F%D1%81%D0%BA%D0%BE%D0%B2_%D3%A9%D0%BB%D0%BA%D3%99%D1%81%D0%B5&diff=prev&oldid=2056059|here]] though?,task_subcomment,['See [[URL though?'],['URL']
+431384,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",The same fix as for T51452 - verified in beta.,task_subcomment,['The same fix as for T51452 - verified in beta.'],['BUG REPRODUCTION']
+430147,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output 
     instead of 
+
+[[https://gerrit.wikimedia.org/r/162310]]",task_subcomment,"['Change 162310 merged by jenkins-bot:\nFor empty / whitespace-only headings, output 
     instead of \n\n[[GERRIT_URL]]']",['GERRIT_URL']
+412855,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","Change 162310 had a related patch set uploaded (by Jforrester):
+MWHeading: Don't put self in output if contents are blank or whitespace
+
+[[https://gerrit.wikimedia.org/r/162310]]
+
+#patch-for-review",task_subcomment,"[""Change 162310 had a related patch set uploaded (by Jforrester):\nMWHeading: Don't put self in output if contents are blank or whitespace\n\n[[GERRIT_URL]]\n\n#patch-for-review""]",['GERRIT_URL']
+244604,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","Change 162310 had a related patch set uploaded by Jforrester:
+MWHeading: Don't put self in output if contents are blank or whitespace
+
+https://gerrit.wikimedia.org/r/162310",task_subcomment,"[""Change 162310 had a related patch set uploaded by Jforrester:\nMWHeading: Don't put self in output if contents are blank or whitespace\n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+244600,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","en.wp user 28bytes comments:
+There was an unneeded section, so I selected the section, pressed ""delete"" and saved. VE did this [1]; I expected it to do this. [2]
+
+1: https://en.wikipedia.org/w/index.php?title=Degeneracy&diff=prev&oldid=569795975
+2: https://en.wikipedia.org/w/index.php?title=Degeneracy&diff=569796007&oldid=567105149",task_subcomment,"['en.wp user 28bytes comments:\nThere was an unneeded section, so I selected the section, pressed ""delete"" and saved.', 'VE did this [1]; I expected it to do this.', '[2]\n\n1: URL\n2: URL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', '2: URL']"
+244596,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",This editor http://en.wikipedia.org/w/index.php?title=Pound_%28mass%29&diff=569770089&oldid=569255959 removed the whole section.  It could not possibly have been their intention to leave behind an empty heading line.,task_subcomment,"['This editor URL removed the whole section.', 'It could not possibly have been their intention to leave behind an empty heading line.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244593,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","<< Often, when an editor tries to remove (or accidentally removes) a section header, the result in VE is something like this: http://en.wikipedia.org/w/index.php?title=%C3%87ank%C4%B1r%C4%B1_Province&diff=567375871&oldid=542107518 . This is seldom (if ever) the intention, can VE be coded to simply remove the section header in these cases? Fram (talk) 09:32, 6 August 2013 (UTC) >>",task_subcomment,"['<< Often, when an editor tries to remove (or accidentally removes) a section header, the result in VE is something like this: URL .', 'This is seldom (if ever) the intention, can VE be coded to simply remove the section header in these cases?', 'Fram (talk) 09:32, 6 August 2013 (UTC) >>']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+244587,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","Since 51829 is now marked as a dupe, 
+should we also discuss here an issue that Dan reported as well - VE turning the next paragraph into a heading,
+or that ""when pressing delete on an empty heading line, if there is a template such as {{main}} on the next line, it is unexpectedly deleted"", as user:WS states on enwp?",task_subcomment,"['Since 51829 is now marked as a dupe, \nshould we also discuss here an issue that Dan reported as well - VE turning the next paragraph into a heading,\nor that ""when pressing delete on an empty heading line, if there is a template such as {{main}} on the next line, it is unexpectedly deleted"", as user:WS states on enwp?']",['SOLUTION DISCUSSION']
+244580,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","Speaking as an end-user, I spent quite some time trying to figure out how to delete a heading. It was quite confusing. Bug 51829 (marked as a duplicate) describes my attempts.
+
+VE's behavior in this regard is the opposite of (say) MS Word's.  In Word, if you highlight one character beyond the heading and press Delete, you remove the heading. In VE, you have to highlight an invisible area *preceding* the heading. This is not intuitive.",task_subcomment,"['Speaking as an end-user, I spent quite some time trying to figure out how to delete a heading.', 'It was quite confusing.', 'Bug 51829 (marked as a duplicate) describes my attempts.', ""VE's behavior in this regard is the opposite of (say) MS Word's."", 'In Word, if you highlight one character beyond the heading and press Delete, you remove the heading.', 'In VE, you have to highlight an invisible area *preceding* the heading.', 'This is not intuitive.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+244573,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",*** Bug 51829 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51829 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+244566,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","""Encourage"" yes...",task_subcomment,"['""Encourage"" yes...']",['SOLUTION DISCUSSION']
+244556,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","(In reply to comment #3)
+> I'm not sure we should be deleting empty headings. The user may want to
+> delete all the contents of a heading and replace it (or select-all then type,
+> which would perform the same operations internally).
+
+Oh, yes, this was meant to be on save, rather than as they edit.
+
+> Perhaps a solution would be for Parsoid to strip empty blocks (provided they
+> weren't that way to begin with)?
+
+That could also work, but feels a bit clunky; I think Parsoid should expect users to send it the HTML they actually want saved, and that it's up to clients to encourage users to indeed create such HTML.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nOh, yes, this was meant to be on save, rather than as they edit.', ""QUOTE\nQUOTE\n\nThat could also work, but feels a bit clunky; I think Parsoid should expect users to send it the HTML they actually want saved, and that it's up to clients to encourage users to indeed create such HTML.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244549,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","Or we have a system for flagging up formatting irregularities (e.g. markers in the margin), which could also flag up other violations of formatting conventions (e.g. double linebreaks).",task_subcomment,"['Or we have a system for flagging up formatting irregularities (e.g.', 'markers in the margin), which could also flag up other violations of formatting conventions (e.g.', 'double linebreaks).']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+244540,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""","I'm not sure we should be deleting empty headings. The user may want to delete all the contents of a heading and replace it (or select-all then type, which would perform the same operations internally).
+
+More generally we don't delete paragraphs when they are empty, unless the user presses backspace again, so doing so for just headings would be a confusing user experience.
+
+Perhaps a solution would be for Parsoid to strip empty blocks (provided they weren't that way to begin with)?",task_subcomment,"[""I'm not sure we should be deleting empty headings."", 'The user may want to delete all the contents of a heading and replace it (or select-all then type, which would perform the same operations internally).', ""More generally we don't delete paragraphs when they are empty, unless the user presses backspace again, so doing so for just headings would be a confusing user experience."", ""Perhaps a solution would be for Parsoid to strip empty blocks (provided they weren't that way to begin with)?""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244531,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",%%%*** Bug 51417 has been marked as a duplicate of this bug. ***%%%,task_subcomment,"['%%%*** Bug 51417 has been marked as a duplicate of this bug.', '***%%%']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+244523,"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""====""",*** Bug 50313 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50313 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52093,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"Some experienced editors are complaining that writing in VE is slower for them now, because they have to use the toolbar. They are requesting to be able to use wikicode from within the VE.
+
+Instead of fully introducing wikicode into the edit mode as some people have requested, I have a different idea. What if we use [[ and {{ as hotkeys to open the insert link and insert template dialogs ? When detecting this combination, the editor could automatically remove this characters from the editsurface and present the dialog to the user. Then the user can keep typing, greatly speeding up the time to author a sentence.
+
+These are by far the most used insertions I presume. File and external links are much less common, and I don't see how you could easily have a hotkey like supo
+
+I think that would solve much of the concerns that have been mentioned.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog\n\nSome experienced editors are complaining that writing in VE is slower for them now, because they have to use the toolbar."", 'They are requesting to be able to use wikicode from within the VE.', 'Instead of fully introducing wikicode into the edit mode as some people have requested, I have a different idea.', 'What if we use [[ and {{ as hotkeys to open the insert link and insert template dialogs ?', 'When detecting this combination, the editor could automatically remove this characters from the editsurface and present the dialog to the user.', 'Then the user can keep typing, greatly speeding up the time to author a sentence.', 'These are by far the most used insertions I presume.', ""File and external links are much less common, and I don't see how you could easily have a hotkey like supo\n\nI think that would solve much of the concerns that have been mentioned."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+339567,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"'[[' triggers Link insertion; '{{' - inserts Template.
+
+Verified in beta/test2/production",task_subcomment,"[""'[[' triggers Link insertion; '{{' - inserts Template."", 'Verified in beta/test2/production']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+337424,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,ZOMG!,task_subcomment,['ZOMG!'],['OBSERVED BUG BEHAVIOR']
+333294,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"Change 175910 merged by jenkins-bot:
+Provide '[[' and '{{' to trigger the appropriate window open actions
+
+[[https://gerrit.wikimedia.org/r/175910]]",task_subcomment,"[""Change 175910 merged by jenkins-bot:\nProvide '[[' and '{{' to trigger the appropriate window open actions\n\n[[GERRIT_URL]]""]",['GERRIT_URL']
+333277,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"Change 175910 had a related patch set uploaded (by Jforrester):
+Provide '[[' and '{{' to trigger the appropriate window open actions
+
+[[https://gerrit.wikimedia.org/r/175910]]
+
+#patch-for-review",task_subcomment,"[""Change 175910 had a related patch set uploaded (by Jforrester):\nProvide '[[' and '{{' to trigger the appropriate window open actions\n\n[[GERRIT_URL]]\n\n#patch-for-review""]",['GERRIT_URL']
+333250,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,This is no longer catastrophically expensive to do. Yay.,task_subcomment,"['This is no longer catastrophically expensive to do.', 'Yay.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+244117,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"I think in general this is a bad idea to do inside VisualEditor, as Brion's comments expand quite nicely. Consequently, I'm marking this as a WONTFIX.
+
+However, yes, of course communities should feel free to write a gadget to do such a thing if you think helpful - but working with us to make VisualEditor better (rather than adding hacks) sounds like a better use of people's time.",task_subcomment,"[""I think in general this is a bad idea to do inside VisualEditor, as Brion's comments expand quite nicely."", ""Consequently, I'm marking this as a WONTFIX."", ""However, yes, of course communities should feel free to write a gadget to do such a thing if you think helpful - but working with us to make VisualEditor better (rather than adding hacks) sounds like a better use of people's time.""]","['INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+244108,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"Typing in the VE should .... just type. ""Markup"" that gets input should just be treated as text, just like when we type """" into a Bugzilla bug title and expect it to say """" on the other side.
+
+Of course a gadget that listens for ""[["" and triggers the dialog might be spiffy for power users who just like brackets :), but I wouldn't recommend building it in.",task_subcomment,"['Typing in the VE should .... just type.', '""Markup"" that gets input should just be treated as text, just like when we type """" into a Bugzilla bug title and expect it to say """" on the other side.', 'Of course a gadget that listens for ""[["" and triggers the dialog might be spiffy for power users who just like brackets :), but I wouldn\'t recommend building it in.']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+244100,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,I think this is a wider issue of how the VE treats people trying to put markup in.,task_subcomment,['I think this is a wider issue of how the VE treats people trying to put markup in.'],['SOLUTION DISCUSSION']
+244096,Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"It's not required for new users to use the toolbar.  In VE, there is a concept of  hotkeys.  For creating a link use command+k (mac) or control+k (pc)",task_subcomment,"[""It's not required for new users to use the toolbar."", 'In VE, there is a concept of  hotkeys.', 'For creating a link use command+k (mac) or control+k (pc)']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+52075,VisualEditor: Reflist columns parameter getting ignored/changed for display,"Compare the number of columns in https://en.wikipedia.org/wiki/Kartik_Poornima in read and VEdit mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Reflist columns parameter getting ignored/changed for display\n\nCompare the number of columns in URL in read and VEdit mode.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+243034,VisualEditor: Reflist columns parameter getting ignored/changed for display,This was probably fixed by the suite of changes in CE's munging of CSS two weeks ago.,task_subcomment,"[""This was probably fixed by the suite of changes in CE's munging of CSS two weeks ago.""]",['OBSERVED BUG BEHAVIOR']
+243030,VisualEditor: Reflist columns parameter getting ignored/changed for display,"Me neither.
+https://en.wikipedia.org/wiki/Kartik_Poornima?veaction=edit
+https://en.wikipedia.org/wiki/Kartik_Poornima?action=edit&preview=yes",task_subcomment,"['Me neither.', 'URL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243027,VisualEditor: Reflist columns parameter getting ignored/changed for display,Can't reproduce (not anymore at least). Can you?,task_subcomment,"[""Can't reproduce (not anymore at least)."", 'Can you?']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+52074,VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing,"Screenshot
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49818
+
+**Attached**: {F11448}",task_description,"['VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing\n\nScreenshot\n\nSee screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL\n\n**Attached**: {F11448}']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+242983,VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing,*** Bug 49768 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49768 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242976,VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing,"
+
+%%%*** This bug has been marked as a duplicate of bug 49818 ***%%%",task_subcomment,['\n\n%%%*** This bug has been marked as a duplicate of bug 49818 ***%%%'],['ACTION ON ISSUE']
+52069,VisualEditor: Unreferenced section template not displaying properly,"See screenshot; problem with the template or with the parsing of it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Unreferenced section template not displaying properly\n\nSee screenshot; problem with the template or with the parsing of it?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242696,VisualEditor: Unreferenced section template not displaying properly,"This turned out to be a problem with the template which we fixed by editing said template. See bug 44452 for more details.
+
+*** This bug has been marked as a duplicate of bug 44452 ***",task_subcomment,"['This turned out to be a problem with the template which we fixed by editing said template.', 'See bug 44452 for more details.', '*** This bug has been marked as a duplicate of bug 44452 ***']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+242690,VisualEditor: Unreferenced section template not displaying properly,"(In reply to comment #3)
+> Try https://en.wikipedia.org/wiki/Riddler#Fictional_character_biography
+
+Seems to be a problem with {{unreferenced section}}; {{unreferenced|section}} works just fine. Can't work out why, though.",task_subcomment,"['(In reply to comment #3)\nQUOTE\n\nSeems to be a problem with {{unreferenced section}}; {{unreferenced|section}} works just fine.', ""Can't work out why, though.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+242684,VisualEditor: Unreferenced section template not displaying properly,Try https://en.wikipedia.org/wiki/Riddler#Fictional_character_biography,task_subcomment,['Try URL'],['OBSERVED BUG BEHAVIOR']
+242678,VisualEditor: Unreferenced section template not displaying properly,"I can't reproduce this - what page did it appear on (or was it all of them?).
+
+Example URLs that work for me:
+
+https://en.wikipedia.org/wiki/4th_Cinemalaya_Independent_Film_Festival?veaction=edit (page)
+
+https://en.wikipedia.org/wiki/User:Jdforrester_(WMF)/Sandbox?veaction=edit (section)",task_subcomment,"[""I can't reproduce this - what page did it appear on (or was it all of them?)."", 'Example URLs that work for me:\n\nURL (page)\n\nURL (section)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242674,VisualEditor: Unreferenced section template not displaying properly,"Screenshot
+
+Moron features forgot to attach the screenshot.
+
+...he has now remembered to attach the screenshot.
+
+Have a screenshot.
+
+**Attached**: {F11438}",task_subcomment,"['Screenshot\n\nMoron features forgot to attach the screenshot.', '...he has now remembered to attach the screenshot.', 'Have a screenshot.', '**Attached**: {F11438}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+52052,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","...and quite dramatically - take a look at https://en.wikipedia.org/w/index.php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+T50830",task_description,"['VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff\n\n...and quite dramatically - take a look at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nT50830']",['OBSERVED BUG BEHAVIOR']
+1845921,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.",task_subcomment,"['Parsoid\'s ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit.', 'Please re-open if you run into similar dirty diffs that happened within the last year or so.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+241737,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0)
+> ...and quite dramatically - take a look at
+> https://en.wikipedia.org/w/index.
+> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133
+
+Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement.
+
+Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-(
+
+Punting to Roan for thoughts, but I think this is probably a lost cause.
+
+(In reply to comment #1)
+> Brad also has a suggestion (along with a bug report) for a workflow to make
+> these easier to identify:
+
+That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']","['SOCIAL CONVERSATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+241733,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify:
+
+""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",task_subcomment,"['Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify:\n\n""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff.', ""If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team."", '(Please don\'t try to use this idea as an error concealment technique: these errors shouldn\'t occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+52040,Set $wgWellFormedXml = false by default,"The main reason for this still being true was screen-scraping bots (together with $wgHtml5).
+
+For some reason when $wgHtml5 was finally enabled we forgot to also get rid of wgWellFormedXml=true.
+
+We should disable it by default for the same reason we now enable wgHtml5 by default.
+
+This is mainly bugging because of the ""&&"" sign we have as of recently in the default html output, which, due to wgWellFormedXml, causes an ugly CDATA section.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",task_description,"['Set $wgWellFormedXml = false by default\n\nThe main reason for this still being true was screen-scraping bots (together with $wgHtml5).', 'For some reason when $wgHtml5 was finally enabled we forgot to also get rid of wgWellFormedXml=true.', 'We should disable it by default for the same reason we now enable wgHtml5 by default.', 'This is mainly bugging because of the ""&&"" sign we have as of recently in the default html output, which, due to wgWellFormedXml, causes an ugly CDATA section.', '--------------------------\n**Version**: 1.22.0\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241013,Set $wgWellFormedXml = false by default,"Change 70036 abandoned by Krinkle:
+Set $wgWellFormedXml to false by default
+
+Reason:
+Agreed, per bug.
+
+https://gerrit.wikimedia.org/r/70036",task_subcomment,"['Change 70036 abandoned by Krinkle:\nSet $wgWellFormedXml to false by default\n\nReason:\nAgreed, per bug.', 'GERRIT_URL']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+241006,Set $wgWellFormedXml = false by default,I note btw that the tidy config is also set to produce XHTML.,task_subcomment,['I note btw that the tidy config is also set to produce XHTML.'],['OBSERVED BUG BEHAVIOR']
+241000,Set $wgWellFormedXml = false by default,"I've decided that I don't think this should be done, now or in the future. I think the general idea behind HTML's original SGML -> XML migration, i.e. to make parsers easier to write at the expense of brevity, continues to be sound and useful. The benefits of a reversion to SGML are small, and the costs can be expected to mirror bug 52253.",task_subcomment,"[""I've decided that I don't think this should be done, now or in the future."", ""I think the general idea behind HTML's original SGML -> XML migration, i.e."", 'to make parsers easier to write at the expense of brevity, continues to be sound and useful.', 'The benefits of a reversion to SGML are small, and the costs can be expected to mirror bug 52253.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+240995,Set $wgWellFormedXml = false by default,"(In reply to comment #2)
+> You could just use , it would be
+> shorter than what you have currently: 
+
+, rather. The ""window."" is important here, as we want to keep going even if jQuery is not loaded and thus its variable is not defined.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\n, rather.', 'The ""window.""', 'is important here, as we want to keep going even if jQuery is not loaded and thus its variable is not defined.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+240990,Set $wgWellFormedXml = false by default,"You could just use , it would be shorter than what you have currently: 
+
+In any case, I don't think that CDATA is a particularly inefficient or ugly part of our HTML output, compared to, say,
+
+mw.loader.implement(""user.options"",function(){mw.user.options.set({""ccmeonemails"":0,""cols"":80,""date"":""default"",""diffonly"":0,""disablemail"":0,""disablesuggest"":0,""editfont"":""default"",""editondblclick"":0,""editsection"":1,""editsectiononrightclick"":0,""enotifminoredits"":0,""enotifrevealaddr"":0,""enotifusertalkpages"":1,""enotifwatchlistpages"":0,""extendwatchlist"":0,""fancysig"":0,""forceeditsummary"":0,""gender"":""unknown"",""hideminor"":0,""hidepatrolled"":0,""imagesize"":2,""justify"":0,""math"":0,""minordefault"":0,""newpageshidepatrolled"":0,""nocache"":0,""noconvertlink"":0,""norollbackdiff"":0,""numberheadings"":0,""previewonfirst"":0,""previewontop"":1,""rcdays"":7,""rclimit"":50,""rememberpassword"":0,""rows"":25,""searchlimit"":20,""showhiddencats"":false,""showjumplinks"":1,""shownumberswatching"":1,""showtoc"":1,""showtoolbar"":1,""skin"":""vector"",""stubthreshold"":0,""thumbsize"":4,""underline"":2,""uselivepreview"":0,""usenewrc"":0,""watchcreations"":1,""watchdefault"":0,""watchdeletion"":0,""watchlistdays"":3,""watchlisthideanons"":0,""watchlisthidebots"":0,
+""watchlisthideliu"":0,""watchlisthideminor"":0,""watchlisthideown"":0,""watchlisthidepatrolled"":0,""watchmoves"":0,""wllimit"":250,""useeditwarning"":1,""flaggedrevssimpleui"":1,""flaggedrevsstable"":0,""flaggedrevseditdiffs"":true,""flaggedrevsviewdiffs"":false,""vector-simplesearch"":1,""vector-collapsiblenav"":1,""usebetatoolbar"":1,""usebetatoolbar-cgd"":1,""aftv5-last-filter"":null,""visualeditor-enable"":1,""wikilove-enabled"":1,""echo-subscriptions-web-page-review"":true,""echo-subscriptions-email-page-review"":false,""ep_showtoplink"":false,""ep_bulkdelorgs"":false,""ep_bulkdelcourses"":true,""ep_showdyk"":true,""echo-notify-show-link"":true,""echo-show-alert"":true,""echo-email-frequency"":0,""echo-subscriptions-email-system"":true,""echo-subscriptions-web-system"":true,""echo-subscriptions-email-other"":false,""echo-subscriptions-web-other"":true,""echo-subscriptions-email-edit-user-talk"":false,""echo-subscriptions-web-edit-user-talk"":true,""echo-subscriptions-email-reverted"":false,""echo-subscriptions-web-reverted"":true,
+""echo-subscriptions-email-article-linked"":false,""echo-subscriptions-web-article-linked"":false,""echo-subscriptions-email-mention"":false,""echo-subscriptions-web-mention"":true,""echo-subscriptions-web-edit-thank"":true,""echo-subscriptions-email-edit-thank"":false,""gettingstarted-task-toolbar-show-intro"":true,""variant"":""en"",""language"":""en"",""searchNs0"":true,""searchNs1"":false,""searchNs2"":false,""searchNs3"":false,""searchNs4"":false,""searchNs5"":false,""searchNs6"":false,""searchNs7"":false,""searchNs8"":false,""searchNs9"":false,""searchNs10"":false,""searchNs11"":false,""searchNs12"":false,""searchNs13"":false,""searchNs14"":false,""searchNs15"":false,""searchNs100"":false,""searchNs101"":false,""searchNs108"":false,""searchNs109"":false,""searchNs446"":false,""searchNs447"":false,""searchNs710"":false,""searchNs711"":false,""searchNs828"":false,""searchNs829"":false,""gadget-teahouse"":1,""gadget-ReferenceTooltips"":1,""gadget-DRN-wizard"":1,""gadget-charinsert"":1,""gadget-mySandbox"":1});},{},{});mw.loader.implement(""user.tokens"",function(){mw
+.user.tokens.set({""editToken"":""+\\"",""patrolToken"":false,""watchToken"":false});},{},{});
+
+which is sent out with every anonymous page view.",task_subcomment,"['You could just use , it would be shorter than what you have currently: \n\nIn any case, I don\'t think that CDATA is a particularly inefficient or ugly part of our HTML output, compared to, say,\n\nmw.loader.implement(""user.options"",function(){mw.user.options.set({""ccmeonemails"":0,""cols"":80,""date"":""default"",""diffonly"":0,""disablemail"":0,""disablesuggest"":0,""editfont"":""default"",""editondblclick"":0,""editsection"":1,""editsectiononrightclick"":0,""enotifminoredits"":0,""enotifrevealaddr"":0,""enotifusertalkpages"":1,""enotifwatchlistpages"":0,""extendwatchlist"":0,""fancysig"":0,""forceeditsummary"":0,""gender"":""unknown"",""hideminor"":0,""hidepatrolled"":0,""imagesize"":2,""justify"":0,""math"":0,""minordefault"":0,""newpageshidepatrolled"":0,""nocache"":0,""noconvertlink"":0,""norollbackdiff"":0,""numberheadings"":0,""previewonfirst"":0,""previewontop"":1,""rcdays"":7,""rclimit"":50,""rememberpassword"":0,""rows"":25,""searchlimit"":20,""showhiddencats"":false,""showjumplinks"":1,""shownumberswatching"":1,""showtoc"":1,""showtoolbar"":1,""skin"":""vector"",""stubthreshold"":0,""thumbsize"":4,""underline"":2,""uselivepreview"":0,""usenewrc"":0,""watchcreations"":1,""watchdefault"":0,""watchdeletion"":0,""watchlistdays"":3,""watchlisthideanons"":0,""watchlisthidebots"":0,\n""watchlisthideliu"":0,""watchlisthideminor"":0,""watchlisthideown"":0,""watchlisthidepatrolled"":0,""watchmoves"":0,""wllimit"":250,""useeditwarning"":1,""flaggedrevssimpleui"":1,""flaggedrevsstable"":0,""flaggedrevseditdiffs"":true,""flaggedrevsviewdiffs"":false,""vector-simplesearch"":1,""vector-collapsiblenav"":1,""usebetatoolbar"":1,""usebetatoolbar-cgd"":1,""aftv5-last-filter"":null,""visualeditor-enable"":1,""wikilove-enabled"":1,""echo-subscriptions-web-page-review"":true,""echo-subscriptions-email-page-review"":false,""ep_showtoplink"":false,""ep_bulkdelorgs"":false,""ep_bulkdelcourses"":true,""ep_showdyk"":true,""echo-notify-show-link"":true,""echo-show-alert"":true,""echo-email-frequency"":0,""echo-subscriptions-email-system"":true,""echo-subscriptions-web-system"":true,""echo-subscriptions-email-other"":false,""echo-subscriptions-web-other"":true,""echo-subscriptions-email-edit-user-talk"":false,""echo-subscriptions-web-edit-user-talk"":true,""echo-subscriptions-email-reverted"":false,""echo-subscriptions-web-reverted"":true,\n""echo-subscriptions-email-article-linked"":false,""echo-subscriptions-web-article-linked"":false,""echo-subscriptions-email-mention"":false,""echo-subscriptions-web-mention"":true,""echo-subscriptions-web-edit-thank"":true,""echo-subscriptions-email-edit-thank"":false,""gettingstarted-task-toolbar-show-intro"":true,""variant"":""en"",""language"":""en"",""searchNs0"":true,""searchNs1"":false,""searchNs2"":false,""searchNs3"":false,""searchNs4"":false,""searchNs5"":false,""searchNs6"":false,""searchNs7"":false,""searchNs8"":false,""searchNs9"":false,""searchNs10"":false,""searchNs11"":false,""searchNs12"":false,""searchNs13"":false,""searchNs14"":false,""searchNs15"":false,""searchNs100"":false,""searchNs101"":false,""searchNs108"":false,""searchNs109"":false,""searchNs446"":false,""searchNs447"":false,""searchNs710"":false,""searchNs711"":false,""searchNs828"":false,""searchNs829"":false,""gadget-teahouse"":1,""gadget-ReferenceTooltips"":1,""gadget-DRN-wizard"":1,""gadget-charinsert"":1,""gadget-mySandbox"":1});},{},{});mw.loader.implement(""user.tokens"",function(){mw\n.user.tokens.set({""editToken"":""+\\\\"",""patrolToken"":false,""watchToken"":false});},{},{});\n\nwhich is sent out with every anonymous page view.']",['BUG REPRODUCTION']
+240984,Set $wgWellFormedXml = false by default,Related URL: https://gerrit.wikimedia.org/r/70036 (Gerrit Change I4155c74042d22527dc5c9460a4af8b7b1adb36cc),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I4155c74042d22527dc5c9460a4af8b7b1adb36cc)'],['OBSERVED BUG BEHAVIOR']
+52014,VisualEditor: cannot reposition typing cursor using the mouse in edit summary,"Self-explanatory, albeit poorly worded; if you type something out in the edit summary box, and then click on a point in that text to move your typing cursor....no luck. This is going to be a total pain for things as simple as tyop corrections.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: cannot reposition typing cursor using the mouse in edit summary\n\nSelf-explanatory, albeit poorly worded; if you type something out in the edit summary box, and then click on a point in that text to move your typing cursor....no luck.', 'This is going to be a total pain for things as simple as tyop corrections.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+239584,VisualEditor: cannot reposition typing cursor using the mouse in edit summary,Fixed and deployed; sorry for this.,task_subcomment,['Fixed and deployed; sorry for this.'],['SOLUTION USAGE']
+239576,VisualEditor: cannot reposition typing cursor using the mouse in edit summary,A fix to bug 49927 might also fix this.,task_subcomment,['A fix to bug 49927 might also fix this.'],['BUG REPRODUCTION']
+52002,"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder","From [[Wikipedia:VisualEditor/Feedback#Editing_Defaultsort]]:
+
+> The Page Settings box displays the article title as a default ""Defaultsort"". But it doesn't seem possible to edit it: typing any letters removes the whole existing text, while trying to delete a few characters has no effect. Where the sort key is not identical to the article title it's usually a variation of it - delete a leading ""The "", or move the given name from start to end. It's a waste to have to retype it all: we ought to be able to edit that box.
+> 
+> This is because the default defaultsort value (article title) is implemented as ""placeholder"" text. Instead, it should be normal editable text.
+> 
+> Upon closing the page settings dialog, the logic should be, ""if defaultsort != article title, add a {{DEFAULTSORT:}} magic word, else remove existing {{DEFAULTSORT:}} if present"".",task_description,"['VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder\n\nFrom [[Wikipedia:VisualEditor/Feedback#Editing_Defaultsort]]:\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE']",['SOLUTION DISCUSSION']
+238946,"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder","(In reply to pamdavies7 from comment #3)
+> Thanks for the explanation! So it remains a bug - and distinctly irritating,
+> for someone who adds a lot of DEFAULTSORTs to articles. 
+> 
+> That said, I suppose it doesn't actually create any more work for the editor
+> than adding the DEFAULTSORT in the old edit system: the value would always
+> have had to be typed in from scratch.
+
+But in the old system one could copy and paste the title from some part of the record, edit as needed (move ""The"" to end, replace an accented letter by plain), highlight, click on ""DEFAULTSORT"" from the editing menu below the edit box, and that was that. Having to retype is more work; having to retype when you can't see the original to copy from is sometimes impossible.",task_subcomment,"['(In reply to pamdavies7 from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBut in the old system one could copy and paste the title from some part of the record, edit as needed (move ""The"" to end, replace an accented letter by plain), highlight, click on ""DEFAULTSORT"" from the editing menu below the edit box, and that was that.', ""Having to retype is more work; having to retype when you can't see the original to copy from is sometimes impossible.""]","['MOTIVATION', 'INVESTIGATION AND EXPLORATION']"
+238941,"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder",*** Bug 69568 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 69568 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+238936,"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder","What if the article ""Abc"" has a DEFAULTSORT set to ""Alphabet"", but is then renamed to ""Alphabet"", making the DEFAULTSORT and article title the same. Then someone opens the category editor, upon save we see that DEFAULTSORT and the article title are the same and remove it. Now you have a dirty diff.
+
+So, we see that separating the default value of the actual value is... well, valuable.
+
+The UX issue is that we force the user to start from scratch when editing the field. The real cause of all this is that we are using the value of text input widget to not only detect a change, but also whether to set or not.
+
+We may consider doing something else, like having a tick to explicitly override the sorting key, and separately have a text input widget which, as requested, is populated with the default or current value.
+
+There are a few things I'm not happy with here, however.
+
+* What happens when DEFAULTSORT is set to empty string?
+* It feels like we are adding too much complexity
+* If the user unticks override, does the text input widget's value get set to the deafult value, or just get grayed out (either has it's downfalls)",task_subcomment,"['What if the article ""Abc"" has a DEFAULTSORT set to ""Alphabet"", but is then renamed to ""Alphabet"", making the DEFAULTSORT and article title the same.', 'Then someone opens the category editor, upon save we see that DEFAULTSORT and the article title are the same and remove it.', 'Now you have a dirty diff.', 'So, we see that separating the default value of the actual value is... well, valuable.', 'The UX issue is that we force the user to start from scratch when editing the field.', 'The real cause of all this is that we are using the value of text input widget to not only detect a change, but also whether to set or not.', 'We may consider doing something else, like having a tick to explicitly override the sorting key, and separately have a text input widget which, as requested, is populated with the default or current value.', ""There are a few things I'm not happy with here, however."", '* What happens when DEFAULTSORT is set to empty string?', ""* It feels like we are adding too much complexity\n* If the user unticks override, does the text input widget's value get set to the deafult value, or just get grayed out (either has it's downfalls)""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238931,"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder","Thanks for the explanation! So it remains a bug - and distinctly irritating, for someone who adds a lot of DEFAULTSORTs to articles. 
+
+That said, I suppose it doesn't actually create any more work for the editor than adding the DEFAULTSORT in the old edit system: the value would always have had to be typed in from scratch.",task_subcomment,"['Thanks for the explanation!', 'So it remains a bug - and distinctly irritating, for someone who adds a lot of DEFAULTSORTs to articles.', ""That said, I suppose it doesn't actually create any more work for the editor than adding the DEFAULTSORT in the old edit system: the value would always have had to be typed in from scratch.""]","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+238927,"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder","(In reply to comment #1)
+> This seemed yesterday to be fixed (I managed to edit the DEFAULTSORT of [[The
+> New Elizabethans]] by removing ""The "" and retyping it at the end), but today
+> - both this morning and just now - the problem is still/again there: to edit
+> the DEFAULTSORT of [[Alexander Gilkes]] I had to retype it all.
+
+We've not touched this code in the past two weeks; what you saw was the effect of someone setting the DEFAULTSORT actively to ""The New Elizabethans"" - see the diff on your edit: https://en.wikipedia.org/w/index.php?title=The_New_Elizabethans&diff=562509771&oldid=562443570",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWe\'ve not touched this code in the past two weeks; what you saw was the effect of someone setting the DEFAULTSORT actively to ""The New Elizabethans"" - see the diff on your edit: URL']",['MOTIVATION']
+238924,"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder","This seemed yesterday to be fixed (I managed to edit the DEFAULTSORT of [[The New Elizabethans]] by removing ""The "" and retyping it at the end), but today - both this morning and just now - the problem is still/again there: to edit the DEFAULTSORT of [[Alexander Gilkes]] I had to retype it all. ~~~~",task_subcomment,"['This seemed yesterday to be fixed (I managed to edit the DEFAULTSORT of [[The New Elizabethans]] by removing ""The "" and retyping it at the end), but today - both this morning and just now - the problem is still/again there: to edit the DEFAULTSORT of [[Alexander Gilkes]] I had to retype it all.', '~~~~']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+51981,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it","More general bug, following on from bug 41150 - this is for text selections, for other generated content blocks, ? others.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50643",task_description,"['VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it\n\nMore general bug, following on from bug 41150 - this is for text selections, for other generated content blocks, ?', 'others.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION USAGE']"
+237746,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it","Change 140103 merged by jenkins-bot:
+Drag and drop of arbitrary selections
+
+https://gerrit.wikimedia.org/r/140103",task_subcomment,['Change 140103 merged by jenkins-bot:\nDrag and drop of arbitrary selections\n\nGERRIT_URL'],['ACTION ON ISSUE']
+237742,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it","Change 140103 had a related patch set uploaded by Esanders:
+Drag and drop of arbitrary selections
+
+https://gerrit.wikimedia.org/r/140103",task_subcomment,['Change 140103 had a related patch set uploaded by Esanders:\nDrag and drop of arbitrary selections\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+237737,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 49486 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49486 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237732,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",fwiw I believe this bug has been mentioned at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_weekly_update_-_2013-09-26_.28MW_1.22wmf19.29 - being the doubt whether reflists can be now dragged or not.,task_subcomment,['fwiw I believe this bug has been mentioned at URL - being the doubt whether reflists can be now dragged or not.'],['OBSERVED BUG BEHAVIOR']
+237726,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it","As an update, if you select a reference or non-floated template you can now move these too; however, floated templates and text can't be moved with drag-and-drop yet.",task_subcomment,"[""As an update, if you select a reference or non-floated template you can now move these too; however, floated templates and text can't be moved with drag-and-drop yet.""]",['SOLUTION USAGE']
+237719,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 52364 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52364 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237711,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 50359 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50359 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237703,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",Adding a link to https://bugzilla.wikimedia.org/show_bug.cgi?id=50359 which is related.,task_subcomment,['Adding a link to URL which is related.'],['INVESTIGATION AND EXPLORATION']
+237696,"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 50183 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50183 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51977,VisualEditor: Closing a dialog scrolls you up to the top of the document,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,['VisualEditor: Closing a dialog scrolls you up to the top of the document\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor'],['OBSERVED BUG BEHAVIOR']
+237537,VisualEditor: Closing a dialog scrolls you up to the top of the document,Fixed and being deployed right now.,task_subcomment,['Fixed and being deployed right now.'],['ACTION ON ISSUE']
+237530,VisualEditor: Closing a dialog scrolls you up to the top of the document,Related URL: https://gerrit.wikimedia.org/r/70614 (Gerrit Change I8cc12ba7845eebc6199fbcd2d355bf0d5f38264b),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I8cc12ba7845eebc6199fbcd2d355bf0d5f38264b)'],['OBSERVED BUG BEHAVIOR']
+237525,VisualEditor: Closing a dialog scrolls you up to the top of the document,"Ignore that, the selection is still working after Roan rolled back newFromDocumentInsertion, but scroll is still a problem.",task_subcomment,"['Ignore that, the selection is still working after Roan rolled back newFromDocumentInsertion, but scroll is still a problem.']",['OBSERVED BUG BEHAVIOR']
+237518,VisualEditor: Closing a dialog scrolls you up to the top of the document,This is a regression because I fixed dialog close re-focusing.,task_subcomment,['This is a regression because I fixed dialog close re-focusing.'],['OBSERVED BUG BEHAVIOR']
+51968,VisualEditor: VE not detecting colour/boxing around multiple issues template,"See https://en.wikipedia.org/wiki/Virivilai for example - bug with the VE or bug with the template?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: VE not detecting colour/boxing around multiple issues template\n\nSee URL for example - bug with the VE or bug with the template?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236877,VisualEditor: VE not detecting colour/boxing around multiple issues template,"We've fixed this, somehow, since it was filed; sorry for not being able to be more precise as to whether the fix was in Parsoid or VisualEditor (it definitely wasn't the template, as that's not been changed in > a month).",task_subcomment,"[""We've fixed this, somehow, since it was filed; sorry for not being able to be more precise as to whether the fix was in Parsoid or VisualEditor (it definitely wasn't the template, as that's not been changed in > a month).""]",['ACTION ON ISSUE']
+51964,VisualEditor: Saving or closing the editing pane does not restore the default view of the article,"The VisualEditor isn't perfectly rendering markup yet (which is understandable), and even when it does it'll look slightly different from read mode in a lot of ways. The problem is that cancelling the VE editing interface, or saving, loads a VE-rendered article view rather than what the article actually looks like.
+
+(sorry if this sounds nonsensical; it's difficult to explain at this end).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Saving or closing the editing pane does not restore the default view of the article\n\nThe VisualEditor isn't perfectly rendering markup yet (which is understandable), and even when it does it'll look slightly different from read mode in a lot of ways."", 'The problem is that cancelling the VE editing interface, or saving, loads a VE-rendered article view rather than what the article actually looks like.', ""(sorry if this sounds nonsensical; it's difficult to explain at this end)."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236532,VisualEditor: Saving or closing the editing pane does not restore the default view of the article,I believe all of the changes for this has been merged and fixed some months ago; please correct if there are still issues.,task_subcomment,['I believe all of the changes for this has been merged and fixed some months ago; please correct if there are still issues.'],['SOLUTION DISCUSSION']
+236527,VisualEditor: Saving or closing the editing pane does not restore the default view of the article,"The example given at the enwiki feedback page was [[scaphoid fracture]]. Observe the spacing of infobox content, then enter and leave VE mode and notice the alteration.",task_subcomment,"['The example given at the enwiki feedback page was [[scaphoid fracture]].', 'Observe the spacing of infobox content, then enter and leave VE mode and notice the alteration.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51954,"Provide a neater way to edit transclusions that do not take a pipe (e.g. {{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})","If I try to edit a number in a {{formatnum:…}}, the VisualEditor displays the template’s edition window, saying it is (for example) the 'formatnum:959719' template, without any parameter. So if I want to change the number, I need to remove the 'template' and then to add a new one, for example 'formatnum:958719'.
+
+The editor should allow changing the number without having to remove the 'template'.
+",task_description,"['Provide a neater way to edit transclusions that do not take a pipe (e.g.', ""{{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})\n\nIf I try to edit a number in a {{formatnum:…}}, the VisualEditor displays the template’s edition window, saying it is (for example) the 'formatnum:959719' template, without any parameter."", ""So if I want to change the number, I need to remove the 'template' and then to add a new one, for example 'formatnum:958719'."", ""The editor should allow changing the number without having to remove the 'template'.""]","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+2269276,"Provide a neater way to edit transclusions that do not take a pipe (e.g. {{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})","Is there any way to put this on the agenda? This bug is already 10 years old. In the Norwegian Bokmål Wikipedia, we use `{{formatnum:}}` even in normal text in articles, and like Danmichaelo said above, the only way to edit such numbers in Visual Editor is to delete the number and insert the new number (and then it won't have the proper formatting).",task_subcomment,"['Is there any way to put this on the agenda?', 'This bug is already 10 years old.', ""In the Norwegian Bokmål Wikipedia, we use CODE even in normal text in articles, and like Danmichaelo said above, the only way to edit such numbers in Visual Editor is to delete the number and insert the new number (and then it won't have the proper formatting).""]","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+1568872,"Provide a neater way to edit transclusions that do not take a pipe (e.g. {{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})","Related: {T204370} and {T204371}, although VE would probably still have to know enough to translate the 'old style' syntax into the newer uniform syntax.",task_subcomment,"[""Related: {T204370} and {T204371}, although VE would probably still have to know enough to translate the 'old style' syntax into the newer uniform syntax.""]",['INVESTIGATION AND EXPLORATION']
+884671,"Provide a neater way to edit transclusions that do not take a pipe (e.g. {{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})",">>! In T51954#3388374, @Danmichaelo wrote:
+> Was hit by this limitation when I was editing an article now. Couldn't find any way to edit the number except to delete it, so I changed the title to reflect that.
+
+Thanks for the input, but please don't make bugs less general. You can add further examples of how they affect you, but that should be as a comment or in the description, not removing other things that are already covered by this task. For instance, this also applies to the `#dateformat`, `lc`, and `int` transclusion objects.",task_subcomment,"[""QUOTE\nQUOTE\n\nThanks for the input, but please don't make bugs less general."", 'You can add further examples of how they affect you, but that should be as a comment or in the description, not removing other things that are already covered by this task.', 'For instance, this also applies to the CODE, CODE, and CODE transclusion objects.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+884165,"Provide a neater way to edit transclusions that do not take a pipe (e.g. {{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})","Was hit by this limitation when I was editing an article now. Couldn't find any way to edit the number except to delete it, so I changed the title to reflect that.",task_subcomment,"['Was hit by this limitation when I was editing an article now.', ""Couldn't find any way to edit the number except to delete it, so I changed the title to reflect that.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+235790,"Provide a neater way to edit transclusions that do not take a pipe (e.g. {{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})","""{{formatnum:…}} is not a template"" - true
+
+For this, Parsoid takes wikitext like:
+
+  This was {{formatnum:1234567890}} years ago.
+
+… and gives us HTML of:
+
+
    This was 1,234,567,890 years ago.
    
+
+… so maybe we'd want to special-case on 'function':'formatnum' so that they're easier to edit?",task_subcomment,"['""{{formatnum:…}} is not a template"" - true\n\nFor this, Parsoid takes wikitext like:\n\n  This was {{formatnum:1234567890}} years ago.', '… and gives us HTML of:\n\n
    This was 1,234,567,890 years ago.
    \n\n… so maybe we\'d want to special-case on \'function\':\'formatnum\' so that they\'re easier to edit?']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+51951,"Window title for ""Creating"" should support parser functions","The browser window title is changed to ""Parse error at position 0 in input {{""}}{{{1|$1}}}{{""}}"" when editing an article with the VisualEditor on dewp. Reproducible in many articles and at least Firefox and Chromium.
+",task_description,"['Window title for ""Creating"" should support parser functions\n\nThe browser window title is changed to ""Parse error at position 0 in input {{""}}{{{1|$1}}}{{""}}"" when editing an article with the VisualEditor on dewp.', 'Reproducible in many articles and at least Firefox and Chromium.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+443120,"Window title for ""Creating"" should support parser functions","(If they're wontfix, then let's decline them.)",task_subcomment,"[""(If they're wontfix, then let's decline them.)""]",['ACTION ON ISSUE']
+442066,"Window title for ""Creating"" should support parser functions","This and T95711 are wontfix. These localisation messages should not use parser functions. This was never intentionally supported and whatever localisation needs exist in German that need this should be filed as a separate task against MediaWiki core to find a way to support that.
+
+Complex parser functions will not be supported in this interface message. ",task_subcomment,"['This and T95711 are wontfix.', 'These localisation messages should not use parser functions.', 'This was never intentionally supported and whatever localisation needs exist in German that need this should be filed as a separate task against MediaWiki core to find a way to support that.', 'Complex parser functions will not be supported in this interface message.']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+441979,"Window title for ""Creating"" should support parser functions","(No ""Parse error at position 0"" since T54479 was fixed.)",task_subcomment,"['(No ""Parse error at position 0"" since T54479 was fixed.)']",['OBSERVED BUG BEHAVIOR']
+441974,"Window title for ""Creating"" should support parser functions","This is still a problem, currently only visible when creating a new page because https://de.wikipedia.org/w/index.php?title=MediaWiki:Editing&action=edit no longer has the templates, but https://de.wikipedia.org/w/index.php?title=MediaWiki:Creating&action=edit still does. T95711 is the same bug for MediaWiki's live preview feature.",task_subcomment,"['This is still a problem, currently only visible when creating a new page because URL no longer has the templates, but URL still does.', ""T95711 is the same bug for MediaWiki's live preview feature.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+235683,"Window title for ""Creating"" should support parser functions","This is still an issue. I've restored MediaWiki:Editing on testwiki for demonstration purposes.
+
+Krinkle has stated ""Don't use wikitext in this message"" (MediaWiki:Editing), but he didn't give a reason. Since parser functions, etc. work fine in this message in MediaWiki core, I think we should expect VE to handle them too, or else it should use a different message that specifically does not support fancy stuff.",task_subcomment,"['This is still an issue.', ""I've restored MediaWiki:Editing on testwiki for demonstration purposes."", 'Krinkle has stated ""Don\'t use wikitext in this message"" (MediaWiki:Editing), but he didn\'t give a reason.', 'Since parser functions, etc.', 'work fine in this message in MediaWiki core, I think we should expect VE to handle them too, or else it should use a different message that specifically does not support fancy stuff.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235680,"Window title for ""Creating"" should support parser functions",This seems solved now on dewp. Good to close from my side.,task_subcomment,"['This seems solved now on dewp.', 'Good to close from my side.']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+235677,"Window title for ""Creating"" should support parser functions","This seems to be caused by the templates in [[de:MediaWiki:Editing]]. 
+
+Can be seen on testwiki as well, where parser functions are the cause ([[testwiki:MediaWiki:Editing]]).",task_subcomment,"['This seems to be caused by the templates in [[de:MediaWiki:Editing]].', 'Can be seen on testwiki as well, where parser functions are the cause ([[testwiki:MediaWiki:Editing]]).']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+51943,"VisualEditor: ""Edit"" should load the latest version without hardcoding the ""current"" revision id (due to race condition and cache)","Steps to reproduce:
+1. open article in browser window
+2. open same article in another browser window, edit, save changes
+3. edit with VE in first window
+
+Expected result: VE show some sort of warning, and loads the newest version of the article (or maybe refuses to edit it at all).
+
+Actual result: VE happily edits the old revision, and shows [[MediaWiki:Editingold]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: ""Edit"" should load the latest version without hardcoding the ""current"" revision id (due to race condition and cache)\n\nSteps to reproduce:\n1. open article in browser window\n2. open same article in another browser window, edit, save changes\n3. edit with VE in first window\n\nExpected result: VE show some sort of warning, and loads the newest version of the article (or maybe refuses to edit it at all).', 'Actual result: VE happily edits the old revision, and shows [[MediaWiki:Editingold]].', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+235288,"VisualEditor: ""Edit"" should load the latest version without hardcoding the ""current"" revision id (due to race condition and cache)","This is now deployed and appears to be working as expected in production, according to my testing. Marking as fixed. Please re-open if you find otherwise.",task_subcomment,"['This is now deployed and appears to be working as expected in production, according to my testing.', 'Marking as fixed.', 'Please re-open if you find otherwise.']","['SOLUTION USAGE', 'ACTION ON ISSUE', 'ACTION ON ISSUE']"
+235278,"VisualEditor: ""Edit"" should load the latest version without hardcoding the ""current"" revision id (due to race condition and cache)","Change 72070 merged by jenkins-bot:
+mw.ViewPageTarget: Fix incorrect retention of the wrong oldid
+
+https://gerrit.wikimedia.org/r/72070",task_subcomment,['Change 72070 merged by jenkins-bot:\nmw.ViewPageTarget: Fix incorrect retention of the wrong oldid\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+235270,"VisualEditor: ""Edit"" should load the latest version without hardcoding the ""current"" revision id (due to race condition and cache)","Change 72070 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Fix incorrect retention of the wrong oldid
+
+https://gerrit.wikimedia.org/r/72070",task_subcomment,['Change 72070 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget: Fix incorrect retention of the wrong oldid\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+51926,Parsoid not correctly rendering bold/italic text,"See, for example, the lead of https://en.wikipedia.org/wiki/Flaming_Pie in the VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Parsoid not correctly rendering bold/italic text\n\nSee, for example, the lead of URL in the VisualEditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233872,Parsoid not correctly rendering bold/italic text,"Verified that [[Flaming Pie]], [[Dictionary]], [[Moon]], [[Metallica_(album)]], and [[User:Kww/italictest3]] are rendered correctly in the deployed Parsoid/Visual Editor. Closing as fixed.",task_subcomment,"['Verified that [[Flaming Pie]], [[Dictionary]], [[Moon]], [[Metallica_(album)]], and [[User:Kww/italictest3]] are rendered correctly in the deployed Parsoid/Visual Editor.', 'Closing as fixed.']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+233866,Parsoid not correctly rendering bold/italic text,"Change 79925 merged by jenkins-bot:
+Tweak QuoteTransformer to more closely match PHP doQuotes.
+
+https://gerrit.wikimedia.org/r/79925",task_subcomment,"['Change 79925 merged by jenkins-bot:\nTweak QuoteTransformer to more closely match PHP doQuotes.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233862,Parsoid not correctly rendering bold/italic text,"Change 79925 had a related patch set uploaded by Cscott:
+WIP: Tweak QuoteTransformer to more closely match PHP doQuotes.
+
+https://gerrit.wikimedia.org/r/79925",task_subcomment,"['Change 79925 had a related patch set uploaded by Cscott:\nWIP: Tweak QuoteTransformer to more closely match PHP doQuotes.', 'GERRIT_URL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233858,Parsoid not correctly rendering bold/italic text,"Change 79343 merged by jenkins-bot:
+Add parserTests for the interaction of italics and possessives.
+
+https://gerrit.wikimedia.org/r/79343",task_subcomment,"['Change 79343 merged by jenkins-bot:\nAdd parserTests for the interaction of italics and possessives.', 'GERRIT_URL']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+233853,Parsoid not correctly rendering bold/italic text,"Change 79343 had a related patch set uploaded by Cscott:
+Add parserTests for the interaction of italics and possessives.
+
+https://gerrit.wikimedia.org/r/79343",task_subcomment,"['Change 79343 had a related patch set uploaded by Cscott:\nAdd parserTests for the interaction of italics and possessives.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+233844,Parsoid not correctly rendering bold/italic text,*** Bug 52254 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52254 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233838,Parsoid not correctly rendering bold/italic text,See also bug 47326.,task_subcomment,['See also bug 47326.'],['MOTIVATION']
+233833,Parsoid not correctly rendering bold/italic text,Just dropping this in for cross-referencing: bug 13227 (this bug made me remember that one).,task_subcomment,['Just dropping this in for cross-referencing: bug 13227 (this bug made me remember that one).'],['OBSERVED BUG BEHAVIOR']
+233826,Parsoid not correctly rendering bold/italic text,"Taking this one, on subbu's suggestion.",task_subcomment,"[""Taking this one, on subbu's suggestion.""]",['SOLUTION DISCUSSION']
+233819,Parsoid not correctly rendering bold/italic text,"This is still appearing, this time in https://en.wikipedia.org/w/index.php?title=Dictionary&oldid=563086179&veaction=edit - start at "" Sebastián Covarrubias""",task_subcomment,"['This is still appearing, this time in URL - start at "" Sebastián Covarrubias""']",['OBSERVED BUG BEHAVIOR']
+51924,VisualEditor: Refactor dialog to not need hardcoded padding for each subclass,"e.g. I don't want to see this:
+
+.ve-ui-mwReferenceDialog-body {
+  padding: 2em;
+}
+
+and have to apply that to each dialog that doesn't have panels.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Refactor dialog to not need hardcoded padding for each subclass\n\ne.g.', ""I don't want to see this:\n\n.ve-ui-mwReferenceDialog-body {\n  padding: 2em;\n}\n\nand have to apply that to each dialog that doesn't have panels."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+1099386,VisualEditor: Refactor dialog to not need hardcoded padding for each subclass,Closing vague idea from past me. Looks like this may've been an issue in what's now become OOUI.,task_subcomment,"['Closing vague idea from past me.', ""Looks like this may've been an issue in what's now become OOUI.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+51923,"VisualEditor: Rename internal use of ""Reference list"" to ""References list""","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Rename internal use of ""Reference list"" to ""References list""\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",['SOLUTION DISCUSSION']
+233594,"VisualEditor: Rename internal use of ""Reference list"" to ""References list""","Change 155091 merged by jenkins-bot:
+Rename ""reference list"" to ""references list"" internally
+
+https://gerrit.wikimedia.org/r/155091",task_subcomment,"['Change 155091 merged by jenkins-bot:\nRename ""reference list"" to ""references list"" internally\n\nGERRIT_URL']",['ACTION ON ISSUE']
+233590,"VisualEditor: Rename internal use of ""Reference list"" to ""References list""","Change 155091 had a related patch set uploaded by Jforrester:
+Rename ""reference list"" to ""references list"" internally
+
+https://gerrit.wikimedia.org/r/155091",task_subcomment,"['Change 155091 had a related patch set uploaded by Jforrester:\nRename ""reference list"" to ""references list"" internally\n\nGERRIT_URL']",['ACTION ON ISSUE']
+51906,monitor mediawiki extensions superproject misconfiguration,"The beta cluster rely on the super project mediawiki/extensions.git to deploy extensions automatically.  Sometime an extension would be misconfigured, a recent example is VisualEditor which got stuck for a few weeks to an old version (bug 49846).
+
+It would be nice to run a SQL query daily that would mail gerritadmin about any misconfiguration.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",task_description,"['monitor mediawiki extensions superproject misconfiguration\n\nThe beta cluster rely on the super project mediawiki/extensions.git to deploy extensions automatically.', 'Sometime an extension would be misconfigured, a recent example is VisualEditor which got stuck for a few weeks to an old version (bug 49846).', 'It would be nice to run a SQL query daily that would mail gerritadmin about any misconfiguration.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+232687,monitor mediawiki extensions superproject misconfiguration,"I have filled that bug to monitor mediawiki/extensions.git being badly configured (for bug 49846).  Instead of using Gerrit maintained mediawiki/extensions.git, I will write a script that list all extensions, register them on beta and then do the submodule update.",task_subcomment,"['I have filled that bug to monitor mediawiki/extensions.git being badly configured (for bug 49846).', 'Instead of using Gerrit maintained mediawiki/extensions.git, I will write a script that list all extensions, register them on beta and then do the submodule update.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+232684,monitor mediawiki extensions superproject misconfiguration,"(In reply to comment #6)
+> So now ""all"" that is needed is to have this in a cronjob that mails the
+> output to...?
+
+I have no clue where it could be send. Nor do I have any idea where such a script should be run.
+
+Possibly, we could run it once a few times per day as a Jenkins job and make that job alert back on IRC and/or to the Gerrit admin mail alias.",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\n\nI have no clue where it could be send.', 'Nor do I have any idea where such a script should be run.', 'Possibly, we could run it once a few times per day as a Jenkins job and make that job alert back on IRC and/or to the Gerrit admin mail alias.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+232681,monitor mediawiki extensions superproject misconfiguration,"(In reply to comment #7)
+> Greg: Was that a question to hashar?
+
+Yeah, rhetorical mostly, but he's the one that can answer it ;)",task_subcomment,"[""(In reply to comment #7)\nQUOTE\n\nYeah, rhetorical mostly, but he's the one that can answer it ;)""]",['ACTION ON ISSUE']
+232676,monitor mediawiki extensions superproject misconfiguration,Greg: Was that a question to hashar?,task_subcomment,['Greg: Was that a question to hashar?'],['OBSERVED BUG BEHAVIOR']
+232670,monitor mediawiki extensions superproject misconfiguration,"So now ""all"" that is needed is to have this in a cronjob that mails the output to...?",task_subcomment,"['So now ""all"" that is needed is to have this in a cronjob that mails the output to...?']",['SOLUTION DISCUSSION']
+232662,monitor mediawiki extensions superproject misconfiguration,https://gerrit.wikimedia.org/r/#/c/70836/ adds a script to verify the extensions syncronization.,task_subcomment,['URL adds a script to verify the extensions syncronization.'],['INVESTIGATION AND EXPLORATION']
+232653,monitor mediawiki extensions superproject misconfiguration,"A slightly better version being run on mediawiki/extensions.git at d0680b9
+
+
+$ git submodule --quiet foreach 'test ""$(git rev-list HEAD..origin/master --count)"" = ""0"" || echo ""ERROR! $path is lagging behind.""'ERROR! AutoCreateCategoryPages is lagging behind.
+ERROR! Bootstrap is lagging behind.
+ERROR! Campaigns is lagging behind.
+ERROR! CirrusSearch is lagging behind.
+ERROR! CommunityTwitter is lagging behind.
+ERROR! CoreEvents is lagging behind.
+ERROR! EImage is lagging behind.
+ERROR! JsonData is lagging behind.
+ERROR! Less is lagging behind.
+ERROR! OpenStreetMapSlippyMap is lagging behind.
+ERROR! PerPageLicense is lagging behind.
+ERROR! QuickResponse is lagging behind.
+ERROR! TimelineTable is lagging behind.
+ERROR! VisualEditor is lagging behind.
+ERROR! WikibaseDataModel is lagging behind.
+ERROR! WikibaseQueryEngine is lagging behind.
+$",task_subcomment,"['A slightly better version being run on mediawiki/extensions.git at d0680b9\n\n\n$ git submodule --quiet foreach \'test ""$(git rev-list HEAD..origin/master --count)"" = ""0"" || echo ""ERROR!', '$path is lagging behind.""\'ERROR!', 'AutoCreateCategoryPages is lagging behind.', 'ERROR!', 'Bootstrap is lagging behind.', 'ERROR!', 'Campaigns is lagging behind.', 'ERROR!', 'CirrusSearch is lagging behind.', 'ERROR!', 'CommunityTwitter is lagging behind.', 'ERROR!', 'CoreEvents is lagging behind.', 'ERROR!', 'EImage is lagging behind.', 'ERROR!', 'JsonData is lagging behind.', 'ERROR!', 'Less is lagging behind.', 'ERROR!', 'OpenStreetMapSlippyMap is lagging behind.', 'ERROR!', 'PerPageLicense is lagging behind.', 'ERROR!', 'QuickResponse is lagging behind.', 'ERROR!', 'TimelineTable is lagging behind.', 'ERROR!', 'VisualEditor is lagging behind.', 'ERROR!', 'WikibaseDataModel is lagging behind.', 'ERROR!', 'WikibaseQueryEngine is lagging behind.', '$']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+232645,monitor mediawiki extensions superproject misconfiguration,"So to find out what is not up to date:
+
+Fetch the extensions:
+
+ git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions.git 
+ cd extensions
+ git submodule update --init
+
+Then for each submodules look at the number of commits between HEAD (the currently checked out version locally) and origin/master (the version in gerrit):
+
+ git submodule foreach 'test ""$(git rev-list HEAD..origin/master --count)"" = ""0""  && echo ""Up to date."" || echo ""ERROR!""'
+
+Gives out something like:
+
+ ...
+ Entering 'AuthorProtect'
+ Up to date.
+ Entering 'AutoCreateCategoryPages'
+ ERROR!
+
+That extension is indeed lagging:
+
+hashar:~/extensions/AutoCreateCategoryPages$ git log --oneline --decorate  --all -n4
+14a097d (origin/master, origin/HEAD, master) Localisation updates from http://translatewiki.net.
+981a381 (HEAD) Localisation updates from http://translatewiki.net.
+e01f64e Add .gitreview and .gitignore
+7ae6dd3 (origin/REL1_21) Localisation updates from http://translatewiki.net.",task_subcomment,"['So to find out what is not up to date:\n\nFetch the extensions:\n\n git clone URL \n cd extensions\n git submodule update --init\n\nThen for each submodules look at the number of commits between HEAD (the currently checked out version locally) and origin/master (the version in gerrit):\n\n git submodule foreach \'test ""$(git rev-list HEAD..origin/master --count)"" = ""0""  && echo ""Up to date.""', '|| echo ""ERROR!""\'', 'Gives out something like:\n\n ...', ""Entering 'AuthorProtect'\n Up to date."", ""Entering 'AutoCreateCategoryPages'\n ERROR!"", 'That extension is indeed lagging:\n\nhashar:~/extensions/AutoCreateCategoryPages$ git log --oneline --decorate  --all -n4\n14a097d (origin/master, origin/HEAD, master) Localisation updates from URL\n981a381 (HEAD) Localisation updates from URL\ne01f64e Add .gitreview and .gitignore\n7ae6dd3 (origin/REL1_21) Localisation updates from URL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+232637,monitor mediawiki extensions superproject misconfiguration,"Campaigns not updating, bug 50261",task_subcomment,"['Campaigns not updating, bug 50261']",['OBSERVED BUG BEHAVIOR']
+232633,monitor mediawiki extensions superproject misconfiguration,"Vector was not updated either, might have caused bug 49911",task_subcomment,"['Vector was not updated either, might have caused bug 49911']",['OBSERVED BUG BEHAVIOR']
+51901,"Parsoid should have template parameter key/value whitespace of "" = "" not ""=""","In edits like https://fr.wikipedia.org/w/index.php?diff=94100781 , the whitespaces between the equal sign of a template parameter and the value of that parameter are removed. This causes confusing diffs since the user didn't make that change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Parsoid should have template parameter key/value whitespace of "" = "" not ""=""\n\nIn edits like URL , the whitespaces between the equal sign of a template parameter and the value of that parameter are removed.', ""This causes confusing diffs since the user didn't make that change."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232275,"Parsoid should have template parameter key/value whitespace of "" = "" not ""=""",This has now been done in Parsoid.,task_subcomment,['This has now been done in Parsoid.'],['SOLUTION DISCUSSION']
+232264,"Parsoid should have template parameter key/value whitespace of "" = "" not ""=""","That said, we are considering changing the default for edited templates where we normalize to a single space around the '=' sign.  This will still affect other templates where there was no space around them before, but in general, the change might be a better default.
+
+This will still not fix the problem when HTML isn't preserved (either due to Parsoid or VE bugs) in its original form (as noted by Gabriel).  But, changing the default whitespace around '=' for template transclusions should make this look a little better.",task_subcomment,"[""That said, we are considering changing the default for edited templates where we normalize to a single space around the '=' sign."", 'This will still affect other templates where there was no space around them before, but in general, the change might be a better default.', ""This will still not fix the problem when HTML isn't preserved (either due to Parsoid or VE bugs) in its original form (as noted by Gabriel)."", ""But, changing the default whitespace around '=' for template transclusions should make this look a little better.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+232257,"Parsoid should have template parameter key/value whitespace of "" = "" not ""=""","If the user edited the transclusion, then normalization of spaces is to be expected, as remembering every purely syntactical variation would add way too much complexity and slow down processing.
+
+If the user did not touch the transclusion, then you should not see any diff in the template. If you are still seeing a diff, then it is pretty likely that this is a VisualEditor issue. There were some issues in the preservation of HTML for templates when passed through VisualEditor, which can cause the template to appear edited when we get the HTML back.",task_subcomment,"['If the user edited the transclusion, then normalization of spaces is to be expected, as remembering every purely syntactical variation would add way too much complexity and slow down processing.', 'If the user did not touch the transclusion, then you should not see any diff in the template.', 'If you are still seeing a diff, then it is pretty likely that this is a VisualEditor issue.', 'There were some issues in the preservation of HTML for templates when passed through VisualEditor, which can cause the template to appear edited when we get the HTML back.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51866,"VisualEditor: Transclusion editor shows empty ""content"" sections for newlines","1. Go to [[Ahab]] and edit in VE
+2. Select the succession box at the bottom and edit with transclusion editor
+3. Observe that ""content"" sections are present that look blank, but on closer inspection, contain only a newline
+
+Some templates (like succession boxes) unfortunately need to be on separate lines in the wikitext :( But the current UI for this is non-obvious and could be made better.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Transclusion editor shows empty ""content"" sections for newlines\n\n1.', 'Go to [[Ahab]] and edit in VE\n2.', 'Select the succession box at the bottom and edit with transclusion editor\n3.', 'Observe that ""content"" sections are present that look blank, but on closer inspection, contain only a newline\n\nSome templates (like succession boxes) unfortunately need to be on separate lines in the wikitext :( But the current UI for this is non-obvious and could be made better.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+255915,"VisualEditor: Transclusion editor shows empty ""content"" sections for newlines","The work-around that Parsoid did to hide these means that these don't appear unless it's mis-matched, which is reasonable enough that I'm going to flag as WORKSFORME.",task_subcomment,"[""The work-around that Parsoid did to hide these means that these don't appear unless it's mis-matched, which is reasonable enough that I'm going to flag as WORKSFORME.""]",['WORKAROUNDS']
+255908,"VisualEditor: Transclusion editor shows empty ""content"" sections for newlines","This is the exact wikitext that is interspersed between template calls, so follows our DOM spec (see http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Template_content). 
+
+The decision whether that should be presented in the UI is one for the VisualEditor team to make. Non-whitespace content like '|-' for a new table row is probably important to show, while pure ws could also be hidden from view.",task_subcomment,"['This is the exact wikitext that is interspersed between template calls, so follows our DOM spec (see URL \n\nThe decision whether that should be presented in the UI is one for the VisualEditor team to make.', ""Non-whitespace content like '|-' for a new table row is probably important to show, while pure ws could also be hidden from view.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+255903,"VisualEditor: Transclusion editor shows empty ""content"" sections for newlines","Yeah, this is a bit of a mess. We could get Parsoid to /always/ do a newline between templates of the same generated block, I suppose? Gabriel, thoughts?",task_subcomment,"['Yeah, this is a bit of a mess.', 'We could get Parsoid to /always/ do a newline between templates of the same generated block, I suppose?', 'Gabriel, thoughts?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+51844,Images: New images get a link=… set whether or not they need it,"Follow-on from bug 49596.
+
+The insertion of a new image adds link=… whether or not it's been actively set away from the default.
+
+Thus (in the example in bug 49596 comment 0) we get:
+
+[[File:CV.03326.jpg|link=https://commons.wikimedia.org/wiki/File:CV.03326.jpg|right|framed|424x275px]]
+
+… instead of:
+
+[[File:CV.03326.jpg|right|framed|424x275px]]
+
+… which is bad in terms of wikitext-user utility.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['Images: New images get a link=… set whether or not they need it\n\nFollow-on from bug 49596.', ""The insertion of a new image adds link=… whether or not it's been actively set away from the default."", 'Thus (in the example in bug 49596 comment 0) we get:\n\n[[File:CV.03326.jpg|link=URL\n\n… instead of:\n\n[[File:CV.03326.jpg|right|framed|424x275px]]\n\n… which is bad in terms of wikitext-user utility.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+253999,Images: New images get a link=… set whether or not they need it,"Change 119087 merged by jenkins-bot:
+Clarified the default link for image insertion.
+
+https://gerrit.wikimedia.org/r/119087",task_subcomment,"['Change 119087 merged by jenkins-bot:\nClarified the default link for image insertion.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+253995,Images: New images get a link=… set whether or not they need it,"Change 119087 had a related patch set uploaded by Cscott:
+Clarified the default link for image insertion.
+
+https://gerrit.wikimedia.org/r/119087",task_subcomment,"['Change 119087 had a related patch set uploaded by Cscott:\nClarified the default link for image insertion.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+253992,Images: New images get a link=… set whether or not they need it,"Clarified the spec: https://www.mediawiki.org/w/index.php?title=Parsoid%2FMediaWiki_DOM_spec&diff=931265&oldid=931084
+I believe Parsoid's behavior is correct.",task_subcomment,"[""Clarified the spec: URL\nI believe Parsoid's behavior is correct.""]",['OBSERVED BUG BEHAVIOR']
+253987,Images: New images get a link=… set whether or not they need it,"mooeypoo and I tried to reproduce without success.  the code looks correct: the link option is suppressed iff a[href] == img[resource].   Both of these should be local relative URLs, since the only way external images can be referenced is via instacommons (which provides local URLs for the image).",task_subcomment,"['mooeypoo and I tried to reproduce without success.', 'the code looks correct: the link option is suppressed iff a[href] == img[resource].', 'Both of these should be local relative URLs, since the only way external images can be referenced is via instacommons (which provides local URLs for the image).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+253982,Images: New images get a link=… set whether or not they need it,"Ok, from looking at the code I can confirm that the link= attribute should be suppressed iff the img[resource] attribute is equal to the a[href].  I'm guessing that autocommons is screwing with this?",task_subcomment,"['Ok, from looking at the code I can confirm that the link= attribute should be suppressed iff the img[resource] attribute is equal to the a[href].', ""I'm guessing that autocommons is screwing with this?""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+253976,Images: New images get a link=… set whether or not they need it,"Hm, I note that the DOM spec describes ""resource attribute on image"" this way:
+
+> link to image resource page. TODO: what to use for images from commons?
+
+I'm guessing this is the root of the problem.  What is VE currently setting the resource attribute to, for images from commons?",task_subcomment,"['Hm, I note that the DOM spec describes ""resource attribute on image"" this way:\n\nQUOTE\n\nI\'m guessing this is the root of the problem.', 'What is VE currently setting the resource attribute to, for images from commons?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253967,Images: New images get a link=… set whether or not they need it,"Hm, maybe this only occurs with images from commons now?  Can you confirm that, James?  It would be helpful to see exactly what VE is giving to Parsoid for new images, and how you are indicating that the link is the default.",task_subcomment,"['Hm, maybe this only occurs with images from commons now?', 'Can you confirm that, James?', 'It would be helpful to see exactly what VE is giving to Parsoid for new images, and how you are indicating that the link is the default.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION']"
+253957,Images: New images get a link=… set whether or not they need it,"Still appears to be happening now that the workaround is removed:
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=81525&oldid=81245",task_subcomment,['Still appears to be happening now that the workaround is removed:\n\nURL'],['OBSERVED BUG BEHAVIOR']
+253950,Images: New images get a link=… set whether or not they need it,This bug is fixed; opened bug 61560 for the VE team to revert their workaround hack.,task_subcomment,['This bug is fixed; opened bug 61560 for the VE team to revert their workaround hack.'],['BUG REPRODUCTION']
+253944,Images: New images get a link=… set whether or not they need it,This should be fixed by https://gerrit.wikimedia.org/r/103082 (if it wasn't already fixed).  Should be verified fixed by the VE team once this lands (and their local workaround reverted?).,task_subcomment,"[""This should be fixed by GERRIT_URL (if it wasn't already fixed)."", 'Should be verified fixed by the VE team once this lands (and their local workaround reverted?', ').']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+253939,Images: New images get a link=… set whether or not they need it,"I cannot reproduce this on latest master.
+
+[subbu@earth lib] cat /tmp/img.html
+
+[subbu@earth lib] node parse --html2wt < /tmp/img.html
+[[File:VisualEditor-logo.svg|300x300px]]",task_subcomment,"['I cannot reproduce this on latest master.', '[subbu@earth lib] cat /tmp/img.html\n\n[subbu@earth lib] node parse --html2wt < /tmp/img.html\n[[File:VisualEditor-logo.svg|300x300px]]']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+253933,Images: New images get a link=… set whether or not they need it,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+253926,Images: New images get a link=… set whether or not they need it,"This is worked around (albeit with potentially a bit of a hack) in VisualEditor, so not so important now from VisualEditor's POV.",task_subcomment,"[""This is worked around (albeit with potentially a bit of a hack) in VisualEditor, so not so important now from VisualEditor's POV.""]",['SOLUTION DISCUSSION']
+253920,Images: New images get a link=… set whether or not they need it,*** Bug 49848 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49848 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+253916,Images: New images get a link=… set whether or not they need it,Related URL: https://gerrit.wikimedia.org/r/70551 (Gerrit Change I75dbbfdd248a6f5696252ef3a2d7ca6ede0fa156),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I75dbbfdd248a6f5696252ef3a2d7ca6ede0fa156)'],['OBSERVED BUG BEHAVIOR']
+253912,Images: New images get a link=… set whether or not they need it,"
+
+serialises to:
+
+[[File:VisualEditor-logo.svg|300x105px]]
+
+Whereas
+
+
+
+(removed data-parsoid from  tag)
+
+serialises to:
+
+[[File:VisualEditor-logo.svg|link=File:VisualEditor-logo.svg|300x105px]]",task_subcomment,"['\n\nserialises to:\n\n[[File:VisualEditor-logo.svg|300x105px]]\n\nWhereas\n\n\n\n(removed data-parsoid from  tag)\n\nserialises to:\n\n[[File:VisualEditor-logo.svg|link=File:VisualEditor-logo.svg|300x105px]]']",['SOLUTION DISCUSSION']
+253906,Images: New images get a link=… set whether or not they need it,This looks like a Parsoid issue:,task_subcomment,['This looks like a Parsoid issue:'],['OBSERVED BUG BEHAVIOR']
+51833,VisualEditor: Quick transclusion dialog UX improvements,"Template overall:
+* Template panel should have a link to the template's definition page (if it's a real template)
+* Template panel should have a link to the relevant MW Manual page (if it's a parser function)
+
+Parameters:
+* Label for parameter should use the ""label"" from TemplateData, not the wt name
+* Label panel should use the ""description"" from TemplateData above the content box
+* Label panel should indicate if a parameter is ""mandatory"" from TemplateData
+* Label panel should show the ""default"" from TemplateData
+* Label panel should indicate if a parameter is ""deprecated"" from TemplateData
+
+Adding parameters:
+* Template panel should show available unused parameters and way to add them
+* Template panel should highlight available unused parameters that are mandatory
+* Template panel should highlight available unused parameters that are in sets
+* Insertion of a template with TemplateData should auto-insert the mandatory parameters
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52576",task_description,"['VisualEditor: Quick transclusion dialog UX improvements\n\nTemplate overall:\n* Template panel should have a link to the template\'s definition page (if it\'s a real template)\n* Template panel should have a link to the relevant MW Manual page (if it\'s a parser function)\n\nParameters:\n* Label for parameter should use the ""label"" from TemplateData, not the wt name\n* Label panel should use the ""description"" from TemplateData above the content box\n* Label panel should indicate if a parameter is ""mandatory"" from TemplateData\n* Label panel should show the ""default"" from TemplateData\n* Label panel should indicate if a parameter is ""deprecated"" from TemplateData\n\nAdding parameters:\n* Template panel should show available unused parameters and way to add them\n* Template panel should highlight available unused parameters that are mandatory\n* Template panel should highlight available unused parameters that are in sets\n* Insertion of a template with TemplateData should auto-insert the mandatory parameters\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",['ISSUE CONTENT MANAGEMENT']
+253343,VisualEditor: Quick transclusion dialog UX improvements,"… of the remaining items, I've split them out into:
+
+(In reply to comment #2)
+> Template panel:
+> * Link to the template page (if it's a transclusion from a MediaWiki page)
+> * Link to the MediaWiki.org Manual (if it's a parser function)
+
+Collectively https://bugzilla.wikimedia.org/show_bug.cgi?id=49772
+
+> * Use ""Param#required"" data to prioritise/encourage use of those parameters
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50747
+
+> * Use ""Root#sets"" data to allow addition and/or completion of parameter
+> sets
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53609
+
+> * Cursor keys can let you select parameters in the search results off the
+> screen and the dialog doesn’t scroll
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53610
+
+> * Checkbox (?) to substitute a template on save, rather than leave as
+> transclusion 
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49904
+
+> Parameter panel:
+> * Use ""Param#required"" from TemplateData
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53611
+
+> * Use ""Param#default"" from TemplateData
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52753
+
+> * Use ""Param#deprecated"" from TemplateData
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53612
+
+> * Use ""Param#type"" from TemplateData
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53613
+
+So, closing as INVALID.",task_subcomment,"[""… of the remaining items, I've split them out into:\n\n(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nCollectively URL\n\nQUOTE\n\nURL\n\nQUOTE\nQUOTE\n\nURL\n\nQUOTE\nQUOTE\n\nURL\n\nQUOTE\nQUOTE\n\nURL\n\nQUOTE\nQUOTE\n\nURL\n\nQUOTE\n\nURL\n\nQUOTE\n\nURL\n\nQUOTE\n\nURL\n\nSo, closing as INVALID.""]",['ACTION ON ISSUE']
+253336,VisualEditor: Quick transclusion dialog UX improvements,Have un-trackered-this;,task_subcomment,['Have un-trackered-this;'],['OBSERVED BUG BEHAVIOR']
+253328,VisualEditor: Quick transclusion dialog UX improvements,"UX items at this point:
+
+| Template panel:
+| * Move “add parameter” button to alongside the search field, not below the results list, so it can be found
+| * Link to the template page (if it's a transclusion from a MediaWiki page)
+| * Link to the MediaWiki.org Manual (if it's a parser function)
+| * Use ""Param#required"" data to prioritise/encourage use of those parameters
+| * Use ""Root#sets"" data to allow addition and/or completion of parameter sets
+| * Auto-add required parameters when creating a new Template transclusion
+| * Double-click on a parameter in the selection menu should insert it
+| * Up/down keys work in the parameter search field results, but not left/right, even though it’s not just a vertical list
+| * Cursor keys can let you select parameters in the search results off the screen and the dialog doesn’t scroll
+| * When adding a template, auto-add all mandatory parameters
+| * Checkbox (?) to substitute a template on save, rather than leave as transclusion 
+| 
+| Parameter panel:
+| * Use ""Param#required"" from TemplateData
+| * Use ""Param#default"" from TemplateData
+| * Use ""Param#deprecated"" from TemplateData
+| * Use ""Param#type"" from TemplateData",task_subcomment,"['UX items at this point:\n\n| Template panel:\n| * Move “add parameter” button to alongside the search field, not below the results list, so it can be found\n| * Link to the template page (if it\'s a transclusion from a MediaWiki page)\n| * Link to the MediaWiki.org Manual (if it\'s a parser function)\n| * Use ""Param#required"" data to prioritise/encourage use of those parameters\n| * Use ""Root#sets"" data to allow addition and/or completion of parameter sets\n| * Auto-add required parameters when creating a new Template transclusion\n| * Double-click on a parameter in the selection menu should insert it\n| * Up/down keys work in the parameter search field results, but not left/right, even though it’s not just a vertical list\n| * Cursor keys can let you select parameters in the search results off the screen and the dialog doesn’t scroll\n| * When adding a template, auto-add all mandatory parameters\n| * Checkbox (?)', 'to substitute a template on save, rather than leave as transclusion \n| \n| Parameter panel:\n| * Use ""Param#required"" from TemplateData\n| * Use ""Param#default"" from TemplateData\n| * Use ""Param#deprecated"" from TemplateData\n| * Use ""Param#type"" from TemplateData']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+253322,VisualEditor: Quick transclusion dialog UX improvements,"updated:
+
+Template panel:
+* Link to the template page (if it's a transclusion from a MediaWiki page)
+* Link to the MediaWiki.org Manual (if it's a parser function)
+* Use ""Root#description"" from TemplateData: Done.
+
+Parameter panel:
+* Use ""Param#label"" from TemplateData: Done.
+* Use ""Param#description"" from TemplateData: Done.
+* Use ""Param#required"" from TemplateData: TODO.
+* Use ""Param#default"" from TemplateData: TODO.
+* Use ""Param#deprecated"" from TemplateData: TODO.
+* Use ""Param#type"" from TemplateData: TODO.
+
+""Add parameter"" panel:
+* Show available (unused) parameters
+* Use ""Param#required"" data to prioritise/encourage use of those parameters
+* Use ""Root#sets"" data to allow addition and/or completion of parameter sets
+* Creating a new Template transclusion should start with all required parameters auto-inserted (instead of requiring the user to add them one-by-one).",task_subcomment,"['updated:\n\nTemplate panel:\n* Link to the template page (if it\'s a transclusion from a MediaWiki page)\n* Link to the MediaWiki.org Manual (if it\'s a parser function)\n* Use ""Root#description"" from TemplateData: Done.', 'Parameter panel:\n* Use ""Param#label"" from TemplateData: Done.', '* Use ""Param#description"" from TemplateData: Done.', '* Use ""Param#required"" from TemplateData: TODO.', '* Use ""Param#default"" from TemplateData: TODO.', '* Use ""Param#deprecated"" from TemplateData: TODO.', '* Use ""Param#type"" from TemplateData: TODO.', '""Add parameter"" panel:\n* Show available (unused) parameters\n* Use ""Param#required"" data to prioritise/encourage use of those parameters\n* Use ""Root#sets"" data to allow addition and/or completion of parameter sets\n* Creating a new Template transclusion should start with all required parameters auto-inserted (instead of requiring the user to add them one-by-one).']","['SOLUTION USAGE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+51823,Infobox is duplicated and duplicate is substed,"In these two edits made with VisualEditor, the infobox was duplicated on save and the duplicate was actually subst'd into the infobox's table:
+https://fr.wikipedia.org/w/index.php?diff=94112508
+https://fr.wikipedia.org/w/index.php?diff=94163787
+
+The behavior seems to be inconsistent since in the first case, the duplicate was inserted right after the infobox, and in the second case, it was inserted after the first paragraph
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",task_description,"[""Infobox is duplicated and duplicate is substed\n\nIn these two edits made with VisualEditor, the infobox was duplicated on save and the duplicate was actually subst'd into the infobox's table:\nURL\nURL\n\nThe behavior seems to be inconsistent since in the first case, the duplicate was inserted right after the infobox, and in the second case, it was inserted after the first paragraph\n\n--------------------------\n**Version**: unspecified\n**Severity**: major""]",['OBSERVED BUG BEHAVIOR']
+252816,Infobox is duplicated and duplicate is substed,We believe that these cases have now been fixed (though we may be wrong). Please re-open if so.,task_subcomment,"['We believe that these cases have now been fixed (though we may be wrong).', 'Please re-open if so.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+252809,Infobox is duplicated and duplicate is substed,"Another infobox duplicated while the editor is touching something else (not the infobox):
+
+https://ca.wikipedia.org/w/index.php?title=Hurac%C3%A0_de_Cuba_de_1910&diff=11973992&oldid=11973843
+
+Duplication of infoboxes is a big deal, very visible and annoying for editors that have to go and change back. Defining importance just in case this report was unnoticed, although of course this is a call for JamesF.  :)",task_subcomment,"['Another infobox duplicated while the editor is touching something else (not the infobox):\n\nURL\n\nDuplication of infoboxes is a big deal, very visible and annoying for editors that have to go and change back.', 'Defining importance just in case this report was unnoticed, although of course this is a call for JamesF.', ':)']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+51806,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Hidden templates, like Template:Use British English, are displaying as carriage returns. These are pretty easy to mistakenly identify as typos or errors and delete. We need a better way of displaying those within the VE, or (as a long-term goal) a better way of surfacing metadata, a la the ""page settings"" page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49603
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53659",task_description,"['Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g.', 'a puzzle piece?)', 'Hidden templates, like Template:Use British English, are displaying as carriage returns.', 'These are pretty easy to mistakenly identify as typos or errors and delete.', 'We need a better way of displaying those within the VE, or (as a long-term goal) a better way of surfacing metadata, a la the ""page settings"" page.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+425589,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"There is a curious case of the template: https://test2.wikipedia.org/wiki/Template:No_spam  {{@}}. 
+Inserting {{@}}  will display the icon, just as for the hidden template: 'Use British English'. 
+
+Is it intentional? 
+",task_subcomment,"['There is a curious case of the template: URL  {{@}}.', ""Inserting {{@}}  will display the icon, just as for the hidden template: 'Use British English'."", 'Is it intentional?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+424617,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"After a page is Saved, and then switch to Edit mode - the icon for Hidden template is not displayed. Saw it in Chrome.",task_subcomment,"['After a page is Saved, and then switch to Edit mode - the icon for Hidden template is not displayed.', 'Saw it in Chrome.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+422065,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),{F56750}?,task_subcomment,['{F56750}?'],['SOLUTION DISCUSSION']
+421849,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Change 193975 merged by jenkins-bot:
+Add an icon to hidden templates
+
+[[https://gerrit.wikimedia.org/r/193975]]",task_subcomment,['Change 193975 merged by jenkins-bot:\nAdd an icon to hidden templates\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+419580,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"We have a general ""template"" icon, adding @violetto to point to the right asset. ",task_subcomment,"['We have a general ""template"" icon, addingSCREEN_NAME to point to the right asset.']",['SOLUTION DISCUSSION']
+419570,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Change 193975 had a related patch set uploaded (by Mooeypoo):
+Add an icon to hidden templates
+
+[[https://gerrit.wikimedia.org/r/193975]]
+",task_subcomment,['Change 193975 had a related patch set uploaded (by Mooeypoo):\nAdd an icon to hidden templates\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+251654,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),*** Bug 72963 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 72963 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251648,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"As an additional item (from bug 51978 comment 6):
+
+> Using the {{כ}} template works correctly while editing articles, and the
+> original test page https://he.wikipedia.org/wiki/User:Amire80/ve-rlm shows
+> everything correctly.
+>
+> That said, there are issues with handling this template after it's inserted:
+> * The bubble that shows its name appears in a wrong location.
+
+This is related to this bug – the context seems to find the nearest thing that actually displays and attaches to that. When we display a place for the context to show, it will presumably show there. :-)",task_subcomment,"['As an additional item (from bug 51978 comment 6):\n\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis is related to this bug – the context seems to find the nearest thing that actually displays and attaches to that.', 'When we display a place for the context to show, it will presumably show there.', ':-)']","['MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251641,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Hi James. Thanks for the explanation. Today I learned the word ""slugs"". To me they are sufficiently clear that those aren't white space but something different. Some vocal users on nl.wp portray slugs as ""ugly white rows"" and fear accidental deletion, the examples provided that would be images. I will continue discussion on bug 47790 and bug 55336 about accidental deletion of FocusableNodes. I've seen a live case in which slugs cannot be deleted. However the cases mentioned above can be.",task_subcomment,"['Hi James.', 'Thanks for the explanation.', 'Today I learned the word ""slugs"".', ""To me they are sufficiently clear that those aren't white space but something different."", 'Some vocal users on nl.wp portray slugs as ""ugly white rows"" and fear accidental deletion, the examples provided that would be images.', 'I will continue discussion on bug 47790 and bug 55336 about accidental deletion of FocusableNodes.', ""I've seen a live case in which slugs cannot be deleted."", 'However the cases mentioned above can be.']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251633,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"(In reply to Ad Huikeshoven from comment #23)
+> Ok to take the conversation there. I've read through bug 47790 and the
+> reported issues are more or less the same. Bug 47790 is solved. What is the
+> timeline of deployment?
+
+It's already deployed.
+
+It was deployed to MediaWiki.org on 6 March 2014 (see the ""Milestone"" field), so it would have reached the Dutch Wikipedia a week later, on 13 March 2014.
+
+That's what I meant by ""This feels like you don't think the resolution to bug 47790 in March was sufficient"". :-)",task_subcomment,"[""(In reply to Ad Huikeshoven from comment #23)\nQUOTE\nQUOTE\nQUOTE\n\nIt's already deployed."", 'It was deployed to MediaWiki.org on 6 March 2014 (see the ""Milestone"" field), so it would have reached the Dutch Wikipedia a week later, on 13 March 2014.', 'That\'s what I meant by ""This feels like you don\'t think the resolution to bug 47790 in March was sufficient"".', ':-)']","['SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+251626,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),Ok to take the conversation there. I've read through bug 47790 and the reported issues are more or less the same. Bug 47790 is solved. What is the timeline of deployment?,task_subcomment,"['Ok to take the conversation there.', ""I've read through bug 47790 and the reported issues are more or less the same."", 'Bug 47790 is solved.', 'What is the timeline of deployment?']","['ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'WORKAROUNDS']"
+251620,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"(In reply to Ad Huikeshoven from comment #21)
+> On nl.wp a discussion has started to turn on VE. In the process feedback has
+> been collected on VE. Some users commented on ""white lines"" as a blocking
+> issue for turning VE on as default. 
+> On top of pages like:
+> * https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit
+> * https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit
+> * https://nl.wikipedia.org/wiki/Rijn?veaction=edit
+> * https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit
+> * https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit
+> as well as on other places on the page ""white lines"" or carriage returns
+> appear in VE edit mode which do not appear in read mode. On mouse over the
+> white line turns blue. 
+> 
+> Some users fear that newcomers others will delete those white lines and
+> carriage returns. However, after deletion of those lines images are
+> accidently deleted from the page.
+> 
+> (Deleting white space at the bottom of a page might also delete accidently
+> categories and other metadata.)
+> 
+> How can I help to resolve this 'bug'?
+
+This feels like you don't think the resolution to bug 47790 in March was sufficient; I'm not sure that this has anything to do with this bug, however. Take the conversation there?",task_subcomment,"[""(In reply to Ad Huikeshoven from comment #21)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis feels like you don't think the resolution to bug 47790 in March was sufficient; I'm not sure that this has anything to do with this bug, however."", 'Take the conversation there?']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+251614,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. 
+On top of pages like:
+* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit
+* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit
+* https://nl.wikipedia.org/wiki/Rijn?veaction=edit
+* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit
+* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit
+as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. 
+
+Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page.
+
+(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)
+
+How can I help to resolve this 'bug'?",task_subcomment,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'CONTRIBUTION AND COMMITMENT']"
+251609,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),*** Bug 52551 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52551 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251603,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),*** Bug 60830 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 60830 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251597,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"> > A work around for this allowing you to add and not delete stuff you've added
+> > would be to make their removal undoable. Not ideal but better than nothing.
+> 
+> Though the problem is that you don't know you've removed them until you
+> realise
+> on saving the page that something you thought you'd added isn't there! A
+> message like ""removing invisible template: are you sure?"" would be helpful.
+
+Yes. Although reading comment 15 again I meant to say ""make their addition undoable."" (not removal). Sorry for the confusion.",task_subcomment,"['QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYes.', 'Although reading comment 15 again I meant to say ""make their addition undoable.""', '(not removal).', 'Sorry for the confusion.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+251591,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),*** Bug 52658 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52658 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251585,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"> 
+> A work around for this allowing you to add and not delete stuff you've added
+> would be to make their removal undoable. Not ideal but better than nothing.
+
+Though the problem is that you don't know you've removed them until you realise on saving the page that something you thought you'd added isn't there! A message like ""removing invisible template: are you sure?"" would be helpful.",task_subcomment,"[""QUOTE\nQUOTE\nQUOTE\n\nThough the problem is that you don't know you've removed them until you realise on saving the page that something you thought you'd added isn't there!"", 'A message like ""removing invisible template: are you sure?""', 'would be helpful.']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+251579,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"PamD at en.wp complains that:
+""[When] I add invisible matter to an article (eg {{coord missing}}), it's too easy to delete it later in the same edit while ""tidying up"" blank lines etc.""
+
+Suggestions have been made above about how to deal with this in advance of working out how to display hidden templates, e.g. in comment 9. 
+
+Alternatively invisible templates could just be declared not deletable in VE (i.e. just treat them like nowikis). It will occasionally leave unnecessary templates in but that is going to be far rarer than deleting them without meaning or even knowledge as happens now.
+
+A work around for this allowing you to add and not delete stuff you've added would be to make their removal undoable. Not ideal but better than nothing.",task_subcomment,"['PamD at en.wp complains that:\n""[When] I add invisible matter to an article (eg {{coord missing}}), it\'s too easy to delete it later in the same edit while ""tidying up"" blank lines etc.""', 'Suggestions have been made above about how to deal with this in advance of working out how to display hidden templates, e.g.', 'in comment 9.', 'Alternatively invisible templates could just be declared not deletable in VE (i.e.', 'just treat them like nowikis).', 'It will occasionally leave unnecessary templates in but that is going to be far rarer than deleting them without meaning or even knowledge as happens now.', ""A work around for this allowing you to add and not delete stuff you've added would be to make their removal undoable."", 'Not ideal but better than nothing.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251573,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Regarding the English language variable templates specifically, it would be great if these were handled by pushing it into a meta tag (bug 52166) and incorporate it into page settings.
+
+Regarding top icons, there is a core enhancement for a pre-defined area for these icons (bug 23796), and a VE enhancement request to do the same (bug 51420).
+
+Regarding others, a puzzle piece sounds like a great UI for it.  Or a custom icon defined in TemplateData?",task_subcomment,"['Regarding the English language variable templates specifically, it would be great if these were handled by pushing it into a meta tag (bug 52166) and incorporate it into page settings.', 'Regarding top icons, there is a core enhancement for a pre-defined area for these icons (bug 23796), and a VE enhancement request to do the same (bug 51420).', 'Regarding others, a puzzle piece sounds like a great UI for it.', 'Or a custom icon defined in TemplateData?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251567,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),*** Bug 51322 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51322 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251560,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),Whatever solution is here should also apply to templates that normally produce text but have been created empty for whatever reason. For example it is possible to add a {{small}} template with no text to display.,task_subcomment,"['Whatever solution is here should also apply to templates that normally produce text but have been created empty for whatever reason.', 'For example it is possible to add a {{small}} template with no text to display.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251553,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),FYI: I count 3 reports in the last 10 posts on WP:VP/T today related to accidental 'hidden' or 'floating' templates deletion.,task_subcomment,"[""FYI: I count 3 reports in the last 10 posts on WP:VP/T today related to accidental 'hidden' or 'floating' templates deletion.""]",['OBSERVED BUG BEHAVIOR']
+251547,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),*** Bug 49633 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49633 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251540,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Why not allowing deletion of a template by keyboard only if the template is selected, not just if the cursor if just before or after the template ?
+I don't know if it's difficult to implement, but that would help preventing accidental deletions.",task_subcomment,"['Why not allowing deletion of a template by keyboard only if the template is selected, not just if the cursor if just before or after the template ?', ""I don't know if it's difficult to implement, but that would help preventing accidental deletions.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251532,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"I've seen it a couple of times so far, but not that often. Having said that, we haven't been actively patrolling recentchanges in a while. I'd personally like some kind of resolution pre-IP rollout, because even if it's relatively rare we're throwing sheer numbers at every bug.",task_subcomment,"[""I've seen it a couple of times so far, but not that often."", ""Having said that, we haven't been actively patrolling recentchanges in a while."", ""I'd personally like some kind of resolution pre-IP rollout, because even if it's relatively rare we're throwing sheer numbers at every bug.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251526,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Oliver and others watching this bug, what's your sense from reviewing changes how often this (accidental deletion of hidden templates) is currently occurring in practice? Knowing this (even if it's anecdata) would help setting priority for this bug.",task_subcomment,"[""Oliver and others watching this bug, what's your sense from reviewing changes how often this (accidental deletion of hidden templates) is currently occurring in practice?"", ""Knowing this (even if it's anecdata) would help setting priority for this bug.""]","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION']"
+251520,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"How about this: If the cursor is before or straight after a template, pop the 'puzzle' indicator into view.
+
+You could make it float above the current line, with a droplet (as a sort of cursor) downward pointing at the position where there is a template that is invisible or floating. When you click the icon, move the cursor to be on 'template', blue highlighting the template content if it is not hidden (this will help direct the users eye from cursor position to content) and directly open the template editor.",task_subcomment,"[""How about this: If the cursor is before or straight after a template, pop the 'puzzle' indicator into view."", 'You could make it float above the current line, with a droplet (as a sort of cursor) downward pointing at the position where there is a template that is invisible or floating.', ""When you click the icon, move the cursor to be on 'template', blue highlighting the template content if it is not hidden (this will help direct the users eye from cursor position to content) and directly open the template editor.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251514,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Even with non-hidden, but floating templates it can be confusing. To quote a user:
+
+http://en.wikipedia.org/w/index.php?title=Peach_Springs_Trading_Post&oldid=563257259
+
+I place the cursor to the left of the line that begins ""The Peach Springs Trad...."", just after the malformed comment, then press backspace, in the hopes of starting to delete said malformed content, the entire infobox disappears.  This is quite startling.
+
+Perhaps a warning is required for the short term ? ""Are you sure you want to delete template... ?""",task_subcomment,"['Even with non-hidden, but floating templates it can be confusing.', 'To quote a user:\n\nURL\n\nI place the cursor to the left of the line that begins ""The Peach Springs Trad...."", just after the malformed comment, then press backspace, in the hopes of starting to delete said malformed content, the entire infobox disappears.', 'This is quite startling.', 'Perhaps a warning is required for the short term ?', '""Are you sure you want to delete template...', '?""']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251508,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),I have no idea if there /is/ a standard. A good illustration is https://en.wikipedia.org/w/index.php?title=Template:Persondata&action=edit,task_subcomment,"['I have no idea if there /is/ a standard.', 'A good illustration is URL']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+251501,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"btw What's the standard of ""hidden templates"". Are templates generating 
    something
     hidden, or what about 
    something
     when [[MediaWiki:Common.css]] contains .hidden{display:none;} ?",task_subcomment,"['btw What\'s the standard of ""hidden templates"".', 'Are templates generating 
    something
     hidden, or what about 
    something
     when [[MediaWiki:Common.css]] contains .hidden{display:none;} ?']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+251495,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"A side-effect of this is that it's impossible to maintain good formatting (keep a blank line between metadata and article text, for example) because the content does not exist from an editor's perspective.",task_subcomment,"[""A side-effect of this is that it's impossible to maintain good formatting (keep a blank line between metadata and article text, for example) because the content does not exist from an editor's perspective.""]",['SOLUTION DISCUSSION']
+251491,Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),"Template:Clear is also a good example of this. Although it doesn't even display as a carriage return. You can insert the template, and then it complete disappears.",task_subcomment,"['Template:Clear is also a good example of this.', ""Although it doesn't even display as a carriage return."", 'You can insert the template, and then it complete disappears.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51784,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,"Especially important for newly inserted ones, as at the moment we have no idea what they are going to be so we just assume inline.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update\n\nEspecially important for newly inserted ones, as at the moment we have no idea what they are going to be so we just assume inline.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+662704,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,"Change 288813 merged by jenkins-bot:
+[BREAKING CHANGE] Evalute block/inline state when inserting a transclusion node
+
+[[https://gerrit.wikimedia.org/r/288813]]",task_subcomment,['Change 288813 merged by jenkins-bot:\n[BREAKING CHANGE] Evalute block/inline state when inserting a transclusion node\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+662528,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,"Change 288813 had a related patch set uploaded (by Esanders):
+[BREAKING CHANGE] Evalute block/inline state when inserting a transclusion node
+
+[[https://gerrit.wikimedia.org/r/288813]]
+",task_subcomment,['Change 288813 had a related patch set uploaded (by Esanders):\n[BREAKING CHANGE] Evalute block/inline state when inserting a transclusion node\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+250142,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 72045 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 72045 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250138,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,"Inez talked to me about this long-standing problem today. He worked on a solution that involves waiting for the preview to come back before inserting the template, displaying a spinner in the meantime. His code is at https://github.com/Wikia/app/pull/4932/files . It looks a bit rough and it only deals with insertion, but I think the general approach could work out pretty well. If nothing else, it could be a stop-gap until we have collaborative editing and having a transclusion reevaluate its type asynchronously would not be a big deal.",task_subcomment,"['Inez talked to me about this long-standing problem today.', 'He worked on a solution that involves waiting for the preview to come back before inserting the template, displaying a spinner in the meantime.', 'His code is at URL .', 'It looks a bit rough and it only deals with insertion, but I think the general approach could work out pretty well.', 'If nothing else, it could be a stop-gap until we have collaborative editing and having a transclusion reevaluate its type asynchronously would not be a big deal.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250134,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 52032 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52032 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250130,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,"(In reply to comment #5)
+> Parsoid says they now have a public wt2html API that we can use instead of
+> action=parse. That would at least allow use to let Parsoid determine whether
+> it
+> is inline or block (instead of sniffing the html result, though that's fairly
+> trivial, just  vs. everything else, right? Maybe a few other inline
+> elements nodes that we use, or do we wrap them all?)
+> 
+> However we still need to then find a way to swap the data model node instance
+> in that case. (..)
+
+From ve.dm.MWTransclusionBlockNode to ve.dm.MWTransclusionInlineNode or visa versa.",task_subcomment,['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nFrom ve.dm.MWTransclusionBlockNode to ve.dm.MWTransclusionInlineNode or visa versa.'],['MOTIVATION']
+250124,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,"Parsoid says they now have a public wt2html API that we can use instead of action=parse. That would at least allow use to let Parsoid determine whether it is inline or block (instead of sniffing the html result, though that's fairly trivial, just  vs. everything else, right? Maybe a few other inline elements nodes that we use, or do we wrap them all?)
+
+However we still need to then find a way to swap the data model node instance in that case. Having 1 datamodel type would be nice indeed. We could make it similar to extension tags in that templates have their own class, but it wouldn't be specific to an element type, we can still swap it dynamically (just like we can change lists from UL to OL).",task_subcomment,"['Parsoid says they now have a public wt2html API that we can use instead of action=parse.', ""That would at least allow use to let Parsoid determine whether it is inline or block (instead of sniffing the html result, though that's fairly trivial, just  vs. everything else, right?"", 'Maybe a few other inline elements nodes that we use, or do we wrap them all?)', 'However we still need to then find a way to swap the data model node instance in that case.', 'Having 1 datamodel type would be nice indeed.', ""We could make it similar to extension tags in that templates have their own class, but it wouldn't be specific to an element type, we can still swap it dynamically (just like we can change lists from UL to OL).""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+250117,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 50610 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50610 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250109,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 54893 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 54893 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250099,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,%%%*** Bug 50363 has been marked as a duplicate of this bug. ***%%%,task_subcomment,"['%%%*** Bug 50363 has been marked as a duplicate of this bug.', '***%%%']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+250089,VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,"Possible solution may involve removing distinction between block & inline transclusion types in the DM, replacing with hybrid type, and have CE work out how to render it properly.",task_subcomment,"['Possible solution may involve removing distinction between block & inline transclusion types in the DM, replacing with hybrid type, and have CE work out how to render it properly.']",['SOLUTION DISCUSSION']
+51778,VisualEditor: Template dialog should look up TemplateData for newly-added templates,"Currently in the template dialog when you insert a new template (or other transclusion) it doesn't look up TemplateData for said template (but re-uses if available). It should.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: Template dialog should look up TemplateData for newly-added templates\n\nCurrently in the template dialog when you insert a new template (or other transclusion) it doesn't look up TemplateData for said template (but re-uses if available)."", 'It should.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+249765,VisualEditor: Template dialog should look up TemplateData for newly-added templates,"Seems to have been some cache issues, because it seems to be fine now",task_subcomment,"['Seems to have been some cache issues, because it seems to be fine now']",['OBSERVED BUG BEHAVIOR']
+249758,VisualEditor: Template dialog should look up TemplateData for newly-added templates,"(In reply to comment #5)
+> Testing on beta, which is using 1.22alpha (3c4aac9) the issue seems to
+
+This is mediawiki-core. VisualEditor at beta.wmflabs should be currently at f8d2f14 (latest; including merged commit) after Reedy manually updated it (again).",task_subcomment,"['(In reply to comment #5)\nQUOTE\n\nThis is mediawiki-core.', 'VisualEditor at beta.wmflabs should be currently at f8d2f14 (latest; including merged commit) after Reedy manually updated it (again).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249750,VisualEditor: Template dialog should look up TemplateData for newly-added templates,"Testing on beta, which is using 1.22alpha (3c4aac9) the issue seems to persist:
+
+First I make a new template instance and file one parameter:
+http://i.imgur.com/69K7IcD.png
+
+Notice the lack of information
+
+Next I apply changes, and open the template dialog again, and following is shown:
+http://i.imgur.com/hV8rqag.png",task_subcomment,"['Testing on beta, which is using 1.22alpha (3c4aac9) the issue seems to persist:\n\nFirst I make a new template instance and file one parameter:\nURL\n\nNotice the lack of information\n\nNext I apply changes, and open the template dialog again, and following is shown:\nURL']",['BUG REPRODUCTION']
+249745,VisualEditor: Template dialog should look up TemplateData for newly-added templates,Done in the above commit.,task_subcomment,['Done in the above commit.'],['SOLUTION DISCUSSION']
+249740,VisualEditor: Template dialog should look up TemplateData for newly-added templates,"Change 71132 merged by jenkins-bot:
+Use template data for new templates and fix alias bug
+
+https://gerrit.wikimedia.org/r/71132",task_subcomment,['Change 71132 merged by jenkins-bot:\nUse template data for new templates and fix alias bug\n\nGERRIT_URL'],['ACTION ON ISSUE']
+249735,VisualEditor: Template dialog should look up TemplateData for newly-added templates,"Change 71132 had a related patch set uploaded by Trevor Parscal:
+Use template data for new templates
+
+https://gerrit.wikimedia.org/r/71132",task_subcomment,['Change 71132 had a related patch set uploaded by Trevor Parscal:\nUse template data for new templates\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+249729,VisualEditor: Template dialog should look up TemplateData for newly-added templates,"Any movement on this? I note the milestone was yesterday's deploy (if it went out but got reverted with the wmf7 problems, ignore me).",task_subcomment,"['Any movement on this?', ""I note the milestone was yesterday's deploy (if it went out but got reverted with the wmf7 problems, ignore me).""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+51767,"VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements","Screenshot
+
+See associated screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11694}",task_description,"['VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements\n\nScreenshot\n\nSee associated screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11694}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+249229,"VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements","Now fixed, I believe.",task_subcomment,"['Now fixed, I believe.']",['SOLUTION DISCUSSION']
+51761,VisualEditor: Provide an easy way to sanity-check VE input / output behavior,"In the investigation of most round-tripping bugs we need to figure out if VE modified the DOM in unexpected ways or Parsoid had issues in handling an unmodified DOM. 
+
+We need an easy way to display both the original HTML string retrieved by VE and a serialization of the modified HTML the VE sends out, possibly popped up in two textareas on some keybinding for easy copying.
+
+This would at least allow basic manual debugging.
+
+Optionally, as a time saver, it would be nice if you could also output a DOM diff that makes it easy to spot DOM differences. You could probably base this on the Parsoid DOMDiff module. This DOM diff can also be used in sanity checks to automatically detect VE round-trip issues.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Provide an easy way to sanity-check VE input / output behavior\n\nIn the investigation of most round-tripping bugs we need to figure out if VE modified the DOM in unexpected ways or Parsoid had issues in handling an unmodified DOM.', 'We need an easy way to display both the original HTML string retrieved by VE and a serialization of the modified HTML the VE sends out, possibly popped up in two textareas on some keybinding for easy copying.', 'This would at least allow basic manual debugging.', 'Optionally, as a time saver, it would be nice if you could also output a DOM diff that makes it easy to spot DOM differences.', 'You could probably base this on the Parsoid DOMDiff module.', 'This DOM diff can also be used in sanity checks to automatically detect VE round-trip issues.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+51754,VisualEditor: Rename [big|small]Stack variables in ve.dm.Surface,"To something which describes their function, not form.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Rename [big|small]Stack variables in ve.dm.Surface\n\nTo something which describes their function, not form.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+248379,VisualEditor: Rename [big|small]Stack variables in ve.dm.Surface,"Change 100313 merged by jenkins-bot:
+Rename big/small stack to undoStack & newTransactions
+
+https://gerrit.wikimedia.org/r/100313",task_subcomment,['Change 100313 merged by jenkins-bot:\nRename big/small stack to undoStack & newTransactions\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+248370,VisualEditor: Rename [big|small]Stack variables in ve.dm.Surface,"Change 100313 had a related patch set uploaded by Esanders:
+Rename big/small stack to undoStack & newTransactions
+
+https://gerrit.wikimedia.org/r/100313",task_subcomment,['Change 100313 had a related patch set uploaded by Esanders:\nRename big/small stack to undoStack & newTransactions\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+51725,VisualEditor: You can't select text in the save dialog,"You really should be able to. I mean, the cursor pointer triggers and everything. Tsk.
+
+(Actually, it's ignoring all clicks that aren't on the buttons, or so it seems.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"[""VisualEditor: You can't select text in the save dialog\n\nYou really should be able to."", 'I mean, the cursor pointer triggers and everything.', 'Tsk.', ""(Actually, it's ignoring all clicks that aren't on the buttons, or so it seems.)"", '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+246790,VisualEditor: You can't select text in the save dialog,This was fixed in wmf8.,task_subcomment,['This was fixed in wmf8.'],['BUG REPRODUCTION']
+51682,VisualEditor: Link duplicated,"Screenshot
+
+See associated screenshot, from the page https://en.wikipedia.org/wiki/Henkle_v._Gregory
+
+Reproduced in Chrome, Safari and Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11483}",task_description,"['VisualEditor: Link duplicated\n\nScreenshot\n\nSee associated screenshot, from the page URL\n\nReproduced in Chrome, Safari and Firefox.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11483}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+243824,VisualEditor: Link duplicated,"Not the same issue; user clearly managed to add a linked space after the italics, which is a UX issue we need to fix generally.",task_subcomment,"['Not the same issue; user clearly managed to add a linked space after the italics, which is a UX issue we need to fix generally.']",['INVESTIGATION AND EXPLORATION']
+243819,VisualEditor: Link duplicated,"I haven't been able to, but then this kind of thing is pretty difficult to duplicate (unless you want me spending 40 minutes basically doing my damnedest to break linking and looking at what happens each time).",task_subcomment,"[""I haven't been able to, but then this kind of thing is pretty difficult to duplicate (unless you want me spending 40 minutes basically doing my damnedest to break linking and looking at what happens each time).""]",['OBSERVED BUG BEHAVIOR']
+243815,VisualEditor: Link duplicated,This isn't necessarily the same issue. Is it reproduceable?,task_subcomment,"[""This isn't necessarily the same issue."", 'Is it reproduceable?']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+243812,VisualEditor: Link duplicated,It seems not - https://en.wikipedia.org/w/index.php?title=List_of_television_series_canceled_after_one_episode&curid=30873088&diff=562679038&oldid=562678963,task_subcomment,['It seems not - URL'],['OBSERVED BUG BEHAVIOR']
+243810,VisualEditor: Link duplicated,"We fixed this as part of the DM tweaks, I believe.",task_subcomment,"['We fixed this as part of the DM tweaks, I believe.']",['SOLUTION DISCUSSION']
+51645,VisualEditor: Deleting the slug a floated image appears in deletes the image… but retains the caption as a paragraph,"Deleting leading newline destroys [[File:....]]
+
+Steps to reproduce:
+
+1. Open a page with [[File:...]] as first line
+
+2. VE adds a leading newline into the edit window
+
+3. Delete this leading newline because for experienced editor it looks superfluous
+
+4. Save
+
+Result: [[File:...]] syntax is destroyed, only the caption is left.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://test.wikipedia.org/w/index.php?title=User:Raymond/image&diff=174494&oldid=174493",task_description,"['VisualEditor: Deleting the slug a floated image appears in deletes the image… but retains the caption as a paragraph\n\nDeleting leading newline destroys [[File:....]]\n\nSteps to reproduce:\n\n1.', 'Open a page with [[File:...]] as first line\n\n2.', 'VE adds a leading newline into the edit window\n\n3.', 'Delete this leading newline because for experienced editor it looks superfluous\n\n4.', 'Save\n\nResult: [[File:...]] syntax is destroyed, only the caption is left.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+241688,VisualEditor: Deleting the slug a floated image appears in deletes the image… but retains the caption as a paragraph,Backdating to when I *think* we fixed this.,task_subcomment,['Backdating to when I *think* we fixed this.'],['SOLUTION DISCUSSION']
+241682,VisualEditor: Deleting the slug a floated image appears in deletes the image… but retains the caption as a paragraph,"I cannot reproduce it now. Looks like it got fixed. Therefore, changing the status to resolved-fixed .
+Reopen it if you think it still exists.",task_subcomment,"['I cannot reproduce it now.', 'Looks like it got fixed.', 'Therefore, changing the status to resolved-fixed .', 'Reopen it if you think it still exists.']","['BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION USAGE', 'ACTION ON ISSUE']"
+241679,VisualEditor: Deleting the slug a floated image appears in deletes the image… but retains the caption as a paragraph,"Deleting the slug a floated item is locked into is ""designed"" to delete the item, so this is expected behaviour. See bug 43026 for a wider discussion - we need a better UX concept around here, I feel.
+
+However, leaving the caption there is... not meant to happen. Re-purposing.",task_subcomment,"['Deleting the slug a floated item is locked into is ""designed"" to delete the item, so this is expected behaviour.', 'See bug 43026 for a wider discussion - we need a better UX concept around here, I feel.', 'However, leaving the caption there is... not meant to happen.', 'Re-purposing.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+51622,Add support for (the equivalent of?) editintro and preload,"In VE, new users may use tutorials/wizards which use [[ https://en.wikinews.org/wiki/Help:Creating_and_using_editintro_and_preload_templates | editintro/preload ]] features, which aren't supported by the visual editor yet.
+",task_description,"['Add support for (the equivalent of?)', ""editintro and preload\n\nIn VE, new users may use tutorials/wizards which use [[ URL | editintro/preload ]] features, which aren't supported by the visual editor yet.""]","['SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+936116,Add support for (the equivalent of?) editintro and preload,"Change 380530 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Api: include preload content when section=new
+
+[[https://gerrit.wikimedia.org/r/380530]]
+",task_subcomment,['Change 380530 merged by jenkins-bot:\n[mediawiki/extensions/VisualEditor@master] Api: include preload content when section=new\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+936091,Add support for (the equivalent of?) editintro and preload,"Change 380530 had a related patch set uploaded (by DLynch; owner: DLynch):
+[mediawiki/extensions/VisualEditor@master] Api: include preload content when section=new
+
+[[https://gerrit.wikimedia.org/r/380530]]
+",task_subcomment,['Change 380530 had a related patch set uploaded (by DLynch; owner: DLynch):\n[mediawiki/extensions/VisualEditor@master] Api: include preload content when section=new\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+935959,Add support for (the equivalent of?) editintro and preload,Adding the tag per https://www.mediawiki.org/w/index.php?title=Topic:Tys3st4u4fbxis43 .,task_subcomment,['Adding the tag per URL .'],['INVESTIGATION AND EXPLORATION']
+933926,Add support for (the equivalent of?) editintro and preload,"Just to confirm, now that patch has made its way to the beta cluster, the inputbox button works and gets us this:
+
+{F9677679}",task_subcomment,"['Just to confirm, now that patch has made its way to the beta cluster, the inputbox button works and gets us this:\n\n{F9677679}']",['INVESTIGATION AND EXPLORATION']
+933676,Add support for (the equivalent of?) editintro and preload,"Change 379246 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Hooks: remove preloadtitle from unsupported list
+
+[[https://gerrit.wikimedia.org/r/379246]]
+",task_subcomment,['Change 379246 merged by jenkins-bot:\n[mediawiki/extensions/VisualEditor@master] Hooks: remove preloadtitle from unsupported list\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+933665,Add support for (the equivalent of?) editintro and preload,"Change 379246 had a related patch set uploaded (by DLynch; owner: DLynch):
+[mediawiki/extensions/VisualEditor@master] Hooks: remove preloadtitle from unsupported list
+
+[[https://gerrit.wikimedia.org/r/379246]]
+",task_subcomment,['Change 379246 had a related patch set uploaded (by DLynch; owner: DLynch):\n[mediawiki/extensions/VisualEditor@master] Hooks: remove preloadtitle from unsupported list\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+933667,Add support for (the equivalent of?) editintro and preload,"Ah, that's because I didn't remove `preloadtitle` from the `unsupportedEditParams` list.
+
+Note that if you edit the URL to removes just that parameter, it gets the expected result: https://en.wikipedia.beta.wmflabs.org/w/index.php?title=Template_talk:Submit_an_edit_request&action=edit&preload=Template%3ASubmit_an_edit_request%2Fpreload&editintro=Template%3AEdit_protected%2Feditintro&preloadparams%5B%5D=&preloadparams%5B%5D=Template%3ASubmit_an_edit_request§ion=new",task_subcomment,"[""Ah, that's because I didn't remove CODE from the CODE list."", 'Note that if you edit the URL to removes just that parameter, it gets the expected result: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+933662,Add support for (the equivalent of?) editintro and preload,"Ah, that's because I didn't remove `preloadtitle` from the `unsupportedEditParams` list.
+
+Note that if you edit the URL to removes just that parameted, it gets the expected result: https://en.wikipedia.beta.wmflabs.org/w/index.php?title=Template_talk:Submit_an_edit_request&action=edit&preload=Template%3ASubmit_an_edit_request%2Fpreload&editintro=Template%3AEdit_protected%2Feditintro&preloadparams%5B%5D=&preloadparams%5B%5D=Template%3ASubmit_an_edit_request§ion=new",task_subcomment,"[""Ah, that's because I didn't remove CODE from the CODE list."", 'Note that if you edit the URL to removes just that parameted, it gets the expected result: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+933498,Add support for (the equivalent of?) editintro and preload,"What is the best way to test this?
+
+I tried using [[https://en.wikipedia.beta.wmflabs.org/wiki/Template:Submit_an_edit_request|Template:Submit an edit request]] on the beta cluster, which appears to use preloading, but it kicked me straight in to the 2010 editor even though I've got the 2017 editor beta feature enabled. I don't even know where I'd begin to test it in the visual editor.",task_subcomment,"['What is the best way to test this?', ""I tried using [[URL an edit request]] on the beta cluster, which appears to use preloading, but it kicked me straight in to the 2010 editor even though I've got the 2017 editor beta feature enabled."", ""I don't even know where I'd begin to test it in the visual editor.""]","['TESTING', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+932399,Add support for (the equivalent of?) editintro and preload,"Change 378343 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Enable preload in VisualEditor
+
+[[https://gerrit.wikimedia.org/r/378343]]
+",task_subcomment,['Change 378343 merged by jenkins-bot:\n[mediawiki/extensions/VisualEditor@master] Enable preload in VisualEditor\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+932160,Add support for (the equivalent of?) editintro and preload,"Change 378726 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget: Support preloadtitle in source mode
+
+[[https://gerrit.wikimedia.org/r/378726]]
+",task_subcomment,['Change 378726 merged by jenkins-bot:\n[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget: Support preloadtitle in source mode\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+932137,Add support for (the equivalent of?) editintro and preload,"Change 378726 had a related patch set uploaded (by DLynch; owner: DLynch):
+[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget: Support preloadtitle in source mode
+
+[[https://gerrit.wikimedia.org/r/378726]]
+",task_subcomment,['Change 378726 had a related patch set uploaded (by DLynch; owner: DLynch):\n[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget: Support preloadtitle in source mode\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+931356,Add support for (the equivalent of?) editintro and preload,"That patch is very much the ""better than nothing"" version James suggested. It pulls the article, substitutes in the parameters, and then if it's in visual mode it runs it through Parsoid. It should be functionally-equivalent for the 2017 wikitext editor, though, since that doesn't rely on always containing valid documents.",task_subcomment,"['That patch is very much the ""better than nothing"" version James suggested.', ""It pulls the article, substitutes in the parameters, and then if it's in visual mode it runs it through Parsoid."", ""It should be functionally-equivalent for the 2017 wikitext editor, though, since that doesn't rely on always containing valid documents.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+931353,Add support for (the equivalent of?) editintro and preload,"Change 378343 had a related patch set uploaded (by DLynch; owner: DLynch):
+[mediawiki/extensions/VisualEditor@master] Enable preload in VisualEditor
+
+[[https://gerrit.wikimedia.org/r/378343]]
+",task_subcomment,['Change 378343 had a related patch set uploaded (by DLynch; owner: DLynch):\n[mediawiki/extensions/VisualEditor@master] Enable preload in VisualEditor\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+888417,Add support for (the equivalent of?) editintro and preload,This would be very useful for the [[ https://en.wikiversity.org/wiki/Wikidebate | Wikidebate ]] project at Wikiversity.,task_subcomment,['This would be very useful for the [[ URL | Wikidebate ]] project at Wikiversity.'],['SOLUTION DISCUSSION']
+786447,Add support for (the equivalent of?) editintro and preload,"Change 329796 merged by jenkins-bot:
+Add editintro to notices
+
+[[https://gerrit.wikimedia.org/r/329796]]",task_subcomment,['Change 329796 merged by jenkins-bot:\nAdd editintro to notices\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+785360,Add support for (the equivalent of?) editintro and preload,"Change 329796 had a related patch set uploaded (by Esanders):
+Add editintro to notices
+
+[[https://gerrit.wikimedia.org/r/329796]]
+",task_subcomment,['Change 329796 had a related patch set uploaded (by Esanders):\nAdd editintro to notices\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+774711,Add support for (the equivalent of?) editintro and preload,"VisualEditor having preload support for page creation would be nice. Preload is used in article wizards (e.g. [[ https://en.wikipedia.org/wiki/Wikipedia:Article_wizard/Ready_for_submission | en-wp ]], [[ https://ru.wikipedia.org/wiki/Шаблон:Article_wizard/create | ru-wp ]]).",task_subcomment,"['VisualEditor having preload support for page creation would be nice.', 'Preload is used in article wizards (e.g.', '[[ URL | en-wp ]], [[ URL | ru-wp ]]).']","['SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+773271,Add support for (the equivalent of?) editintro and preload,"It looks like there are similar problems on Mobile view, which may be of interest to anyone who is relying on preload:  {T126190}",task_subcomment,"['It looks like there are similar problems on Mobile view, which may be of interest to anyone who is relying on preload:  {T126190}']",['OBSERVED BUG BEHAVIOR']
+684079,Add support for (the equivalent of?) editintro and preload,ProofreadPage needs support of the  EditFormPreloadText hook instead of editinfo/preload parameters. Tracked by task T138588,task_subcomment,"['ProofreadPage needs support of the  EditFormPreloadText hook instead of editinfo/preload parameters.', 'Tracked by task T138588']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+683673,Add support for (the equivalent of?) editintro and preload,"Thomas's suggestion is that if the article is a 404 (non-extant), we sling the contents of `preload` parameter's indicated article's Parsoid blob as the initial version of the article, and if that's not balanced wikitext (and so not the desired HTML) ""oh well"", at least it's better than nothing. Thoughts?",task_subcomment,"['Thomas\'s suggestion is that if the article is a 404 (non-extant), we sling the contents of CODE parameter\'s indicated article\'s Parsoid blob as the initial version of the article, and if that\'s not balanced wikitext (and so not the desired HTML) ""oh well"", at least it\'s better than nothing.', 'Thoughts?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+683670,Add support for (the equivalent of?) editintro and preload,A note from @tpt that this is pretty important for successful #proofreadpage integration.,task_subcomment,['A note fromSCREEN_NAME that this is pretty important for successful #proofreadpage integration.'],['SOLUTION DISCUSSION']
+479089,Add support for (the equivalent of?) editintro and preload,"These tasks *really* shouldn't have been merged, despite being about 'the same' area of code (one is about important functionality half done through on-wiki hacky JavaScript, the other is about modifying a fundamental user pattern in core to work with VisualEditor); un-merging.",task_subcomment,"[""These tasks *really* shouldn't have been merged, despite being about 'the same' area of code (one is about important functionality half done through on-wiki hacky JavaScript, the other is about modifying a fundamental user pattern in core to work with VisualEditor); un-merging.""]",['ACTION ON ISSUE']
+479087,Add support for (the equivalent of?) editintro and preload,"These tasks *really* shouldn't have been merged, despite being about 'the same' extension (one is about important functionality half done through on-wiki hacky JavaScript, the other is about modifying an extension to work with VisualEditor); un0merging.",task_subcomment,"[""These tasks *really* shouldn't have been merged, despite being about 'the same' extension (one is about important functionality half done through on-wiki hacky JavaScript, the other is about modifying an extension to work with VisualEditor); un0merging.""]",['ACTION ON ISSUE']
+478923,Add support for (the equivalent of?) editintro and preload,"We've encountered this issue too on a private MediaWiki. 
+Would be really great to have this supported - this would make the VE more versatile in some use cases!
+
+Thanks!",task_subcomment,"[""We've encountered this issue too on a private MediaWiki."", 'Would be really great to have this supported - this would make the VE more versatile in some use cases!', 'Thanks!']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+478609,Add support for (the equivalent of?) editintro and preload,"nominating this as Q1 blocker, since this is closely tied to the current BLP practices on english wikipedia, a very visible and sensitive part of our policies.",task_subcomment,"['nominating this as Q1 blocker, since this is closely tied to the current BLP practices on english wikipedia, a very visible and sensitive part of our policies.']",['EXPECTED BEHAVIOR']
+478589,Add support for (the equivalent of?) editintro and preload,"I've merged the above, and copied the details into the description above.",task_subcomment,"[""I've merged the above, and copied the details into the description above.""]",['ACTION ON ISSUE']
+411903,Add support for (the equivalent of?) editintro and preload,"Editintro and preload are parameters supported by the core, but it is ""hidden feature"", which is exposed natively by InputBox extension (on non native - using external link)",task_subcomment,"['Editintro and preload are parameters supported by the core, but it is ""hidden feature"", which is exposed natively by InputBox extension (on non native - using external link)']",['SOLUTION DISCUSSION']
+411836,Add support for (the equivalent of?) editintro and preload,Editintro/preloud are parts of inputbox extension? Or how it is related?,task_subcomment,"['Editintro/preloud are parts of inputbox extension?', 'Or how it is related?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+402213,Add support for (the equivalent of?) editintro and preload,Indeed.,task_subcomment,['Indeed.'],['OBSERVED BUG BEHAVIOR']
+393115,Add support for (the equivalent of?) editintro and preload,"I think editintro/preload would be very useful not just for new users, but for many kinds of repetitive administration tasks/queries for which preloads are now used. Having TemplateData integrated (I guess), users could be presented the fields they have to fill in the visual way, avoiding errors and fully controlling the input.",task_subcomment,"['I think editintro/preload would be very useful not just for new users, but for many kinds of repetitive administration tasks/queries for which preloads are now used.', 'Having TemplateData integrated (I guess), users could be presented the fields they have to fill in the visual way, avoiding errors and fully controlling the input.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+51620,VisualEditor: Section edit links opens the source editor after saving the section using the visual editor,"To reproduce:
+
+1. Open a page with several sections.
+2. Scroll to the second section and press the ""edit"" link near the heading. The Visual Editor opens. Make a change in the text and save the edit.
+3. Press the same ""edit"" link again.
+
+Observed: The source editor opens.
+
+Expected: The visual editor opens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Section edit links opens the source editor after saving the section using the visual editor\n\nTo reproduce:\n\n1.', 'Open a page with several sections.', '2.', 'Scroll to the second section and press the ""edit"" link near the heading.', 'The Visual Editor opens.', 'Make a change in the text and save the edit.', '3.', 'Press the same ""edit"" link again.', 'Observed: The source editor opens.', 'Expected: The visual editor opens.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION USAGE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+240282,VisualEditor: Section edit links opens the source editor after saving the section using the visual editor,*** Bug 50181 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50181 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240274,VisualEditor: Section edit links opens the source editor after saving the section using the visual editor,Merged. Will go out on Thursday or beforehand if we push.,task_subcomment,"['Merged.', 'Will go out on Thursday or beforehand if we push.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+240270,VisualEditor: Section edit links opens the source editor after saving the section using the visual editor,Related URL: https://gerrit.wikimedia.org/r/70324 (Gerrit Change Idf938c0dc8535c30ce63a05d56abeee210a67380),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change Idf938c0dc8535c30ce63a05d56abeee210a67380)'],['OBSERVED BUG BEHAVIOR']
+51618,"""View source"" is missing on protected LQT pages","As indicated on
+[[mw:Thread:VisualEditor/Feedback/source code?]]
+the page
+https://www.mediawiki.org/wiki/VisualEditor/Feedback
+which was protected recently has no ""View source"" link to see the content of the header. There should be one, pointing to
+https://www.mediawiki.org/wiki/VisualEditor/Feedback?action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['""View source"" is missing on protected LQT pages\n\nAs indicated on\n[[mw:Thread:VisualEditor/Feedback/source code?]]', 'the page\nURL\nwhich was protected recently has no ""View source"" link to see the content of the header.', 'There should be one, pointing to\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+240225,"""View source"" is missing on protected LQT pages","Change 68860 merged by jenkins-bot:
+Show an edit link for discussion page headers even if the user can't edit it
+
+https://gerrit.wikimedia.org/r/68860",task_subcomment,"[""Change 68860 merged by jenkins-bot:\nShow an edit link for discussion page headers even if the user can't edit it\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+240220,"""View source"" is missing on protected LQT pages",Related URL: https://gerrit.wikimedia.org/r/68860 (Gerrit Change I99c17acea0be7b0ef650959e5e280ca5e9154b2a),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I99c17acea0be7b0ef650959e5e280ca5e9154b2a)'],['OBSERVED BUG BEHAVIOR']
+51617,"VisualEditor: Visually discourage use of ""legal"" but unwanted structures in sub-editors (e.g. lists in references)","In VE, click the ""Reference"" toolbar icon. According to the toolbar icons in the ""Content"" section, it is possible to insert lists, headings and images within the text of a reference.
+
+This is a nonsensical capability. The only required formatting here is bold, italic and wikilink, if that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52646",task_description,"['VisualEditor: Visually discourage use of ""legal"" but unwanted structures in sub-editors (e.g.', 'lists in references)\n\nIn VE, click the ""Reference"" toolbar icon.', 'According to the toolbar icons in the ""Content"" section, it is possible to insert lists, headings and images within the text of a reference.', 'This is a nonsensical capability.', 'The only required formatting here is bold, italic and wikilink, if that.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']","['SOLUTION DISCUSSION', 'SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+240190,"VisualEditor: Visually discourage use of ""legal"" but unwanted structures in sub-editors (e.g. lists in references)","(In reply to comment #3)
+> (In reply to comment #2)
+> > Maybe we can discourage users from doing these things in some way, but we
+> > can't
+> > just not support this, as users have to be able to edit these back into a
+> > more
+> > rational use.
+> 
+> On enwiki there is never any good reason to have headings or images in
+> references. In the 0.000001% of cases where it is actually wanted, it can
+> just be done using the wikitext source editor, I think.
+
+The objective of VE is for even power users to never need to enter the wikitext editor. Fixing broken usage would be an example of a use case that we'd want to support.
+
+> However, I can understand that other wikis might want this functionality in
+> VE for some reason, so I suppose enwiki could hide the relevant functionality
+> via CSS or something like that if you think it would be better.
+
+I was thinking of having such tools hidden under an ""advanced tools"" collapsed block in the toolbar, but we should properly look at this rather than just commit to the way to do it in a Bugzilla thread. :-) Ideally we'd rather not have individual wikis trying to come up with local-only ""solutions"" to this.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe objective of VE is for even power users to never need to enter the wikitext editor.', ""Fixing broken usage would be an example of a use case that we'd want to support."", 'QUOTE\nQUOTE\nQUOTE\n\nI was thinking of having such tools hidden under an ""advanced tools"" collapsed block in the toolbar, but we should properly look at this rather than just commit to the way to do it in a Bugzilla thread.', ':-) Ideally we\'d rather not have individual wikis trying to come up with local-only ""solutions"" to this.']","['MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN']"
+240182,"VisualEditor: Visually discourage use of ""legal"" but unwanted structures in sub-editors (e.g. lists in references)","(In reply to comment #2)
+> Maybe we can discourage users from doing these things in some way, but we
+> can't
+> just not support this, as users have to be able to edit these back into a
+> more
+> rational use.
+
+On enwiki there is never any good reason to have headings or images in references. In the 0.000001% of cases where it is actually wanted, it can just be done using the wikitext source editor, I think.
+
+However, I can understand that other wikis might want this functionality in VE for some reason, so I suppose enwiki could hide the relevant functionality via CSS or something like that if you think it would be better.",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nOn enwiki there is never any good reason to have headings or images in references.', 'In the 0.000001% of cases where it is actually wanted, it can just be done using the wikitext source editor, I think.', 'However, I can understand that other wikis might want this functionality in VE for some reason, so I suppose enwiki could hide the relevant functionality via CSS or something like that if you think it would be better.']","['EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+240177,"VisualEditor: Visually discourage use of ""legal"" but unwanted structures in sub-editors (e.g. lists in references)","(In reply to comment #1)
+> (In reply to comment #0)
+> > lists, headings and images
+> 
+> Sorry, the list functionality has been correctly removed from this view. It
+> is only headings and images that need to be hidden.
+
+
+Regrettably, wikitext does actually pretty much everything inside references except other references (though some, ahem, ""enterprising"" users have found a way around that intentional limit). Examples:
+
+  https://www.mediawiki.org/wiki/VisualEditor:TestReferenceContents
+
+Maybe we can discourage users from doing these things in some way, but we can't just not support this, as users have to be able to edit these back into a more rational use.
+
+(The reason that these were removed are that you're not allowed lists in image captions; we're clearly going to have to split what things the sub-editors can allow by type. Created that as bug 49657.)",task_subcomment,"['(In reply to comment #1)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n\nRegrettably, wikitext does actually pretty much everything inside references except other references (though some, ahem, ""enterprising"" users have found a way around that intentional limit).', ""Examples:\n\n  URL\n\nMaybe we can discourage users from doing these things in some way, but we can't just not support this, as users have to be able to edit these back into a more rational use."", ""(The reason that these were removed are that you're not allowed lists in image captions; we're clearly going to have to split what things the sub-editors can allow by type."", 'Created that as bug 49657.)']","['MOTIVATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+240173,"VisualEditor: Visually discourage use of ""legal"" but unwanted structures in sub-editors (e.g. lists in references)","(In reply to comment #0)
+> lists, headings and images
+
+Sorry, the list functionality has been correctly removed from this view. It is only headings and images that need to be hidden.",task_subcomment,"['(In reply to comment #0)\nQUOTE\n\nSorry, the list functionality has been correctly removed from this view.', 'It is only headings and images that need to be hidden.']","['WORKAROUNDS', 'OBSERVED BUG BEHAVIOR']"
+51604,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"This is to run from 19 June (end on with the Notifications split test, so we don't much their data up).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/70737
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49727",task_description,"[""Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts\n\nThis is to run from 19 June (end on with the Notifications split test, so we don't much their data up)."", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**URL**: URL\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+239450,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,https://en.wikipedia.org/w/index.php?title=Humanoid&diff=prev&oldid=561404936,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+239444,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,https://en.wikipedia.org/w/index.php?title=2013_CONCACAF_Gold_Cup&diff=561404682&oldid=561374126,task_subcomment,['URL'],['SOLUTION DISCUSSION']
+239439,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"https://en.wikipedia.org/w/index.php?title=Minnesota&curid=19590&diff=561394244&oldid=561292962
+
+Dirty diff, HTML comments being stripped, etc.
+
+Will the VisualEditor team be cleaning up these edits?",task_subcomment,"['URL\n\nDirty diff, HTML comments being stripped, etc.', 'Will the VisualEditor team be cleaning up these edits?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+239437,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,This is now deployed and will run for a week or so to help advise on whether the main switch should be thrown for all users. Data to be published as we get it.,task_subcomment,"['This is now deployed and will run for a week or so to help advise on whether the main switch should be thrown for all users.', 'Data to be published as we get it.']","['SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION']"
+239435,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"From :
+
+---
+Hey all. We're going to postpone the A/B test for several days; I'll post more details as I get them, but I understand it's largely down to known bugs with the existing software - bugs that you reported, and bugs that were crucial in making a go/no go decision. Thank you to everyone for all your hard work poking at the VE, and for all your reports thus far; it's much appreciated :). Okeyes (WMF) (talk) 19:25, 18 June 2013 (UTC)
+---
+
+Thanks to Legoktm for pointing this out to me, otherwise I likely never would've seen it.",task_subcomment,"['From  This is to run from 19 June (end on with the Notifications split test, so we
+> don't much their data up).
+
+June 19 is a few days away. Given some of the recent feedback at [[Wikipedia:VisualEditor/Feedback]] regarding severe bugs in VisualEditor, it doesn't seem like VisualEditor is ready to be deployed more widely.",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\n\nJune 19 is a few days away.', ""Given some of the recent feedback at [[Wikipedia:VisualEditor/Feedback]] regarding severe bugs in VisualEditor, it doesn't seem like VisualEditor is ready to be deployed more widely.""]","['WORKAROUNDS', 'FUTURE PLAN']"
+239423,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"It seems like auto-opting in a user also requires an auto-opt out mechanism. Otherwise, this is a dramatic departure from user expectations. As I understand it, anonymous users currently get the wikitext editor. Nearly every MediaWiki installation, including the one the user was just using use the standard wikitext editor, so suddenly changing that needs to be done cautiously.
+
+Is there currently an auto-opt mechanism? If not, I consider that a blocker to this bug being resolved.
+
+While I think it's ethically questionable to run experiments on users in this manner, one safeguard is ensuring that it's as easy as possible for users to _escape_ such experiments. Within the VisualEditor interface (and possibly elsewhere in the user interface), there should be one-click ""I didn't ask for this"" option to disable VisualEditor. In addition to an option on the editor itself, other areas of the site (such as the post-login screen) could be modified. ""Welcome to Wikipedia! You've been selected to test our beta software. [opt out]"" or similar.",task_subcomment,"['It seems like auto-opting in a user also requires an auto-opt out mechanism.', 'Otherwise, this is a dramatic departure from user expectations.', 'As I understand it, anonymous users currently get the wikitext editor.', 'Nearly every MediaWiki installation, including the one the user was just using use the standard wikitext editor, so suddenly changing that needs to be done cautiously.', 'Is there currently an auto-opt mechanism?', 'If not, I consider that a blocker to this bug being resolved.', ""While I think it's ethically questionable to run experiments on users in this manner, one safeguard is ensuring that it's as easy as possible for users to _escape_ such experiments."", 'Within the VisualEditor interface (and possibly elsewhere in the user interface), there should be one-click ""I didn\'t ask for this"" option to disable VisualEditor.', 'In addition to an option on the editor itself, other areas of the site (such as the post-login screen) could be modified.', '""Welcome to Wikipedia!', ""You've been selected to test our beta software."", '[opt out]"" or similar.']","['SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+239419,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"(In reply to comment #2)
+> Has en.wikipedia been notified?
+
+This would be good.
+
+From what I can tell, this test only applies to new users, though it's difficult to figure that out based on the current Bugzilla subject text or the related commit. It currently reads as though this will be an A/B on all users, not just new users.",task_subcomment,"['(In reply to comment #2)\nQUOTE\n\nThis would be good.', ""From what I can tell, this test only applies to new users, though it's difficult to figure that out based on the current Bugzilla subject text or the related commit."", 'It currently reads as though this will be an A/B on all users, not just new users.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+239415,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,Related URL: https://gerrit.wikimedia.org/r/68846 (Gerrit Change I94d74fd8abeba465f1f9463890541e8c8f786a43),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I94d74fd8abeba465f1f9463890541e8c8f786a43)'],['OBSERVED BUG BEHAVIOR']
+239411,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,Has en.wikipedia been notified?,task_subcomment,['Has en.wikipedia been notified?'],['ACTION ON ISSUE']
+239407,Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,Related URL: https://gerrit.wikimedia.org/r/68845 (Gerrit Change I5c603ece309d61641d32ccc9eff5ea2890d5b816),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I5c603ece309d61641d32ccc9eff5ea2890d5b816)'],['OBSERVED BUG BEHAVIOR']
+51602,VisualEditor: Show VisualEditor tag in diffs,"The VisualEditor edit tag (Tag: VisualEditor) should show on diffs, too.  This will probably require a core change.  However, I'm filing it here, both so you're aware of it, and because it might need to be configurable (it might be we don't want all tags, such as AbuseFilter, etc. to show on diffs).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Show VisualEditor tag in diffs\n\nThe VisualEditor edit tag (Tag: VisualEditor) should show on diffs, too.', 'This will probably require a core change.', ""However, I'm filing it here, both so you're aware of it, and because it might need to be configurable (it might be we don't want all tags, such as AbuseFilter, etc."", 'to show on diffs).', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+239174,VisualEditor: Show VisualEditor tag in diffs,"Change 73004 merged by jenkins-bot:
+Remove ""Tag: "" prefix, now that they're in MW core
+
+https://gerrit.wikimedia.org/r/73004",task_subcomment,"['Change 73004 merged by jenkins-bot:\nRemove ""Tag: "" prefix, now that they\'re in MW core\n\nGERRIT_URL']",['ACTION ON ISSUE']
+239171,VisualEditor: Show VisualEditor tag in diffs,"The core change is done in MW master, and will be part of wmf10; as such, marking this as fixed.",task_subcomment,"['The core change is done in MW master, and will be part of wmf10; as such, marking this as fixed.']",['SOLUTION DISCUSSION']
+239167,VisualEditor: Show VisualEditor tag in diffs,"Change 72317 merged by jenkins-bot:
+Show change tags on diffs
+
+https://gerrit.wikimedia.org/r/72317",task_subcomment,['Change 72317 merged by jenkins-bot:\nShow change tags on diffs\n\nGERRIT_URL'],['ACTION ON ISSUE']
+239163,VisualEditor: Show VisualEditor tag in diffs,"(In reply to comment #5)
+> Because revision tagging is really incomplete, as I recall, lacking
+> the ability to do all the things you might want to do with revision
+> tags (like manually adding one, removing an incorrect one, renaming
+> one, etc.).
+
+File a bug :) Change I8ace1d47 (now abandoned) attempted to add an API
+module for this, it could be used as a starting point.
+
+
+(In reply to comment #5)
+> Matthew also brings up another major point in comment 4.
+> Historically revision tags have been added with AbuseFilter filters
+> (Andrew G. wrote both the AbuseFilter extension and the core
+> revision tagging feature, as I remember it). Consequently, making
+> ""possible libel"" or other similar tags more visible in the user
+> interface may not be a great idea until revision tagging is further
+> developed.
+
+They are not really *that* visible, they're displayed just like edit
+summaries, but without the italics. (Of course wiki admins can make
+them show up all uppercase, bold and on neon-yellow background.)",task_subcomment,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nFile a bug :) Change I8ace1d47 (now abandoned) attempted to add an API\nmodule for this, it could be used as a starting point.', ""(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThey are not really *that* visible, they're displayed just like edit\nsummaries, but without the italics."", '(Of course wiki admins can make\nthem show up all uppercase, bold and on neon-yellow background.)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239156,VisualEditor: Show VisualEditor tag in diffs,"(In reply to comment #3)
+> Personally I see no reason to show any tag in history view, but keep it
+> hidden on diff view. What would be the use case?
+
+Because revision tagging is really incomplete, as I recall, lacking the ability to do all the things you might want to do with revision tags (like manually adding one, removing an incorrect one, renaming one, etc.).
+
+Matthew also brings up another major point in comment 4. Historically revision tags have been added with AbuseFilter filters (Andrew G. wrote both the AbuseFilter extension and the core revision tagging feature, as I remember it). Consequently, making ""possible libel"" or other similar tags more visible in the user interface may not be a great idea until revision tagging is further developed.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\n\nBecause revision tagging is really incomplete, as I recall, lacking the ability to do all the things you might want to do with revision tags (like manually adding one, removing an incorrect one, renaming one, etc.).', 'Matthew also brings up another major point in comment 4.', 'Historically revision tags have been added with AbuseFilter filters (Andrew G. wrote both the AbuseFilter extension and the core revision tagging feature, as I remember it).', 'Consequently, making ""possible libel"" or other similar tags more visible in the user interface may not be a great idea until revision tagging is further developed.']","['INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+239150,VisualEditor: Show VisualEditor tag in diffs,"(In reply to comment #3)
+> Personally I see no reason to show any tag in history view, but keep it
+> hidden on diff view. What would be the use case?
+
+It might be annoying to have AbuseFilter tags exposed on the diff UI, since they are known to sometimes be inaccurate (like any automatic classification).  When you're looking at the diff, you see the full change, so automatic classifications are less necessary.
+
+However, I think it's reasonable to just show all the tags for now, and revisit if it turns out to be an issue in practice.",task_subcomment,"['(In reply to comment #3)\nQUOTE\nQUOTE\n\nIt might be annoying to have AbuseFilter tags exposed on the diff UI, since they are known to sometimes be inaccurate (like any automatic classification).', ""When you're looking at the diff, you see the full change, so automatic classifications are less necessary."", ""However, I think it's reasonable to just show all the tags for now, and revisit if it turns out to be an issue in practice.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239146,VisualEditor: Show VisualEditor tag in diffs,"(In reply to comment #0)
+> because it might need to be configurable (it might be
+> we don't want all tags, such as AbuseFilter, etc. to show on diffs).
+
+Personally I see no reason to show any tag in history view, but keep it hidden on diff view. What would be the use case?",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\n\nPersonally I see no reason to show any tag in history view, but keep it hidden on diff view.', 'What would be the use case?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+239142,VisualEditor: Show VisualEditor tag in diffs,"Change 72317 had a related patch set uploaded by Matmarex:
+Show change tags on diffs
+
+https://gerrit.wikimedia.org/r/72317",task_subcomment,['Change 72317 had a related patch set uploaded by Matmarex:\nShow change tags on diffs\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+239139,VisualEditor: Show VisualEditor tag in diffs,"Core change request created as bug 49656. Until that's done this is a ""later"", sadly.",task_subcomment,"['Core change request created as bug 49656.', 'Until that\'s done this is a ""later"", sadly.']","['MOTIVATION', 'SOLUTION DISCUSSION']"
+51569,Make ULS input methods work in content editable divs of VisualEditor,"ULS IME not working with Visual Editor fields
+
+--------------------------
+**Version**: master
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50722
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53700
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53701
+https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/3493",task_description,['Make ULS input methods work in content editable divs of VisualEditor\n\nULS IME not working with Visual Editor fields\n\n--------------------------\n**Version**: master\n**Severity**: major\n**See Also**:\nURL\nURL\nURL\nURL'],['BUG REPRODUCTION']
+596676,Make ULS input methods work in content editable divs of VisualEditor,"As of https://gerrit.wikimedia.org/r/#/c/264577/ in #jquery.ime this should now be resolved and working for all users, and will be part of the wmf.12 release starting tomorrow.",task_subcomment,"['As of URL in #jquery.ime this should now be resolved and working for all users, and will be part of the wmf.12 release starting tomorrow.']",['SOLUTION USAGE']
+237041,Make ULS input methods work in content editable divs of VisualEditor,*** Bug 58662 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 58662 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237035,Make ULS input methods work in content editable divs of VisualEditor,Please use bugzilla as the single place o make issues known that are relevant for developers. References to lists of issues on wiki pages will not do.,task_subcomment,"['Please use bugzilla as the single place o make issues known that are relevant for developers.', 'References to lists of issues on wiki pages will not do.']","['ISSUE CONTENT MANAGEMENT', 'BUG REPRODUCTION']"
+237031,Make ULS input methods work in content editable divs of VisualEditor,"(In reply to comment #13)
+@ Santhosh Thottingal  Please have a look at [https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_.2B_ULS_unicode_Devnagari_Script_input_issues].I have added a table of known issues today.
+
+Rgds",task_subcomment,"['(In reply to comment #13)\n@ Santhosh Thottingal  Please have a look at [URL have added a table of known issues today.', 'Rgds']","['WORKAROUNDS', 'SOLUTION DISCUSSION']"
+237028,Make ULS input methods work in content editable divs of VisualEditor,"With https://gerrit.wikimedia.org/r/#/c/79755/ jquery.ime start working in visual editor. The UI is not integrated well with the VE UI. And there are VE specific bugs related to cursor handling and text selection, that are applicable to all IMEs or non latin text.",task_subcomment,"['With URL jquery.ime start working in visual editor.', 'The UI is not integrated well with the VE UI.', 'And there are VE specific bugs related to cursor handling and text selection, that are applicable to all IMEs or non latin text.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+237024,Make ULS input methods work in content editable divs of VisualEditor,"Hi, 
+
+Thanks for your reply,I know in any case you will be doing your best to make both extensions compatible.What will be likely situation during the time gap,so please let we know if you can think of any easy time gap solution can be made available.Other wise even while ULS is with us, we will be back to square one. 
+
+
+
+
+Warm Regards",task_subcomment,"['Hi, \n\nThanks for your reply,I know in any case you will be doing your best to make both extensions compatible.What will be likely situation during the time gap,so please let we know if you can think of any easy time gap solution can be made available.Other wise even while ULS is with us, we will be back to square one.', 'Warm Regards']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+237020,Make ULS input methods work in content editable divs of VisualEditor,"It's probably important to manage expectations here.
+
+Tl;dr: it's not realistic to assess that ULS/jQuery.IME input methods will work in VE before the end of July 2013. At this time, no reliable estimate can be made when this is to be expected. Working towards getting this issue resolved has a high priority in the VE and LE teams.
+
+Input methods for many scripts, either natively supported by an operating system, by an application, or by JavaScript, are currently incompatible or at least lead to unexpcted behavior when using VisualEditor.
+
+Possible ways that will allow this to be resolved are currently being explored. I expect that by the end of next week, The VisualEditor and Language Engineering team will have an understanding that will allow them to estimate how much time is needed to make native input possible in most, if not all scripts, when using VE. Once that is done, further exploration is needed to assess the effort needed to make input methods work correctly, including the input methods of ULS/jQuery.IME.
+
+See bug 33077 for more details. In the near future, I expect we will be able to identify issues that need to be resolved before we can work on this issue specifically in the field ""depends on"".",task_subcomment,"[""It's probably important to manage expectations here."", ""Tl;dr: it's not realistic to assess that ULS/jQuery.IME input methods will work in VE before the end of July 2013."", 'At this time, no reliable estimate can be made when this is to be expected.', 'Working towards getting this issue resolved has a high priority in the VE and LE teams.', 'Input methods for many scripts, either natively supported by an operating system, by an application, or by JavaScript, are currently incompatible or at least lead to unexpcted behavior when using VisualEditor.', 'Possible ways that will allow this to be resolved are currently being explored.', 'I expect that by the end of next week, The VisualEditor and Language Engineering team will have an understanding that will allow them to estimate how much time is needed to make native input possible in most, if not all scripts, when using VE.', 'Once that is done, further exploration is needed to assess the effort needed to make input methods work correctly, including the input methods of ULS/jQuery.IME.', 'See bug 33077 for more details.', 'In the near future, I expect we will be able to identify issues that need to be resolved before we can work on this issue specifically in the field ""depends on"".']","['SOLUTION DISCUSSION', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'EXPECTED BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'EXPECTED BEHAVIOR']"
+237016,Make ULS input methods work in content editable divs of VisualEditor,"Hi,
+
+Waiting for this to be available for test,if possible  couple of days before VE to be launched on vernacular wikis which are dependent on ULS. Time table for hi and few other wikis is expected to be 22nd July 2013.
+
+
+Thanks and Warm Regards",task_subcomment,"['Hi,\n\nWaiting for this to be available for test,if possible  couple of days before VE to be launched on vernacular wikis which are dependent on ULS.', 'Time table for hi and few other wikis is expected to be 22nd July 2013.', 'Thanks and Warm Regards']","['FUTURE PLAN', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+237012,Make ULS input methods work in content editable divs of VisualEditor,*** Bug 51354 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51354 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+237006,Make ULS input methods work in content editable divs of VisualEditor,"**ansumang** wrote:
+
+Santhosh, I think by changing the summary, we could avoid the duplicates?
+
+(In reply to comment #7)
+%%%> *** Bug 50345 has been marked as a duplicate of this bug. ***%%%",task_subcomment,"['**ansumang** wrote:\n\nSanthosh, I think by changing the summary, we could avoid the duplicates?', '(In reply to comment #7)\n%%%> *** Bug 50345 has been marked as a duplicate of this bug.', '***%%%']","['INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE', 'OBSERVED BUG BEHAVIOR']"
+236999,Make ULS input methods work in content editable divs of VisualEditor,*** Bug 50345 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50345 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236989,Make ULS input methods work in content editable divs of VisualEditor,"Making this a bug instead of a feature, as we would expect the key mappings to work on any input field that is more or less supported for well supported and stable MediaWiki extensions, including VisualEditor.
+
+Set to highest priority. Tracked on Wikimedia Language Engineering team as https://mingle.corp.wikimedia.org/projects/internationalization/cards/3493
+
+If anyone is working on this and expects to be done before 2013-07-07, please let us know and we'll wait. Otherwise, I expect we will have development capacity to take this up and get it delivered by 2013-07-09.",task_subcomment,"['Making this a bug instead of a feature, as we would expect the key mappings to work on any input field that is more or less supported for well supported and stable MediaWiki extensions, including VisualEditor.', 'Set to highest priority.', ""Tracked on Wikimedia Language Engineering team as URL\n\nIf anyone is working on this and expects to be done before 2013-07-07, please let us know and we'll wait."", 'Otherwise, I expect we will have development capacity to take this up and get it delivered by 2013-07-09.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'FUTURE PLAN']"
+236982,Make ULS input methods work in content editable divs of VisualEditor,*** Bug 50293 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50293 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236975,Make ULS input methods work in content editable divs of VisualEditor,*** Bug 49704 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49704 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236969,Make ULS input methods work in content editable divs of VisualEditor,CCing Moriel who's working for GSoC2013 on VisualEditor issues around i18n and in particular RTL; she may have some thoughts. :-),task_subcomment,"[""CCing Moriel who's working for GSoC2013 on VisualEditor issues around i18n and in particular RTL; she may have some thoughts."", ':-)']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+236965,Make ULS input methods work in content editable divs of VisualEditor,*** Bug 49643 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49643 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236959,Make ULS input methods work in content editable divs of VisualEditor,This is part of a GSOC2013 project and tracked here https://github.com/wikimedia/jquery.ime/issues/136,task_subcomment,['This is part of a GSOC2013 project and tracked here URL'],['OBSERVED BUG BEHAVIOR']
+51564,VisualEditor: Review behaviour in CE with 

    s,"Need to review and get working so we can ask Parsoid to re-enable these (stop them being wrapped as s) - bug 47403 comment 3.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",task_description,"['VisualEditor: Review behaviour in CE with 

    s\n\nNeed to review and get working so we can ask Parsoid to re-enable these (stop them being wrapped as s) - bug 47403 comment 3.', '--------------------------\n**Version**: unspecified\n**Severity**: minor']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+51552,VisualEditor: UI loading should trigger events that other tools can listen for,"I'm thinking something like:
+
+start loading VE
+done loading VE UI
+start rendering VE content
+done rendering VE content
+done loading VE
+
+These would make it easier for other scripts to hook into what is going on. We could use it for instance to add the BLP/disambig editnotice to the actual edit notices on the english wikipedia. https://en.wikipedia.org/wiki/Wikipedia:Editnotice#Edit_intros
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: UI loading should trigger events that other tools can listen for\n\nI'm thinking something like:\n\nstart loading VE\ndone loading VE UI\nstart rendering VE content\ndone rendering VE content\ndone loading VE\n\nThese would make it easier for other scripts to hook into what is going on."", 'We could use it for instance to add the BLP/disambig editnotice to the actual edit notices on the english wikipedia.', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+235880,VisualEditor: UI loading should trigger events that other tools can listen for,"We should probably have a proper discussion about events and integration with external tools, rather than doing spike solutions; punting to Trevor to discuss (post-July).",task_subcomment,"['We should probably have a proper discussion about events and integration with external tools, rather than doing spike solutions; punting to Trevor to discuss (post-July).']",['FUTURE PLAN']
+51551,VisualEditor: Can't paste into a selection covering the end of the document,"1. Copy some plain text
+2. Make a selection in the document up to the end of it (e.g. select all)
+3. Paste
+4. Exception time!
+
+Problem is in ve.dm.Surface line 376:
+
+rightAnnotations = dataModelData.getAnnotationsFromOffset( right );
+
+with right = -1 (out of bounds)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"[""VisualEditor: Can't paste into a selection covering the end of the document\n\n1."", 'Copy some plain text\n2.', 'Make a selection in the document up to the end of it (e.g.', 'select all)\n3.', 'Paste\n4.', 'Exception time!', 'Problem is in ve.dm.Surface line 376:\n\nrightAnnotations = dataModelData.getAnnotationsFromOffset( right );\n\nwith right = -1 (out of bounds)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+470735,VisualEditor: Can't paste into a selection covering the end of the document,"Change 131717 had a related patch set uploaded (by Liangent):
+LanguageConverter fix of empty and numeric strings
+
+[[https://gerrit.wikimedia.org/r/131717]]
+",task_subcomment,['Change 131717 had a related patch set uploaded (by Liangent):\nLanguageConverter fix of empty and numeric strings\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+235841,VisualEditor: Can't paste into a selection covering the end of the document,Merged and will go out with wmf8 from Thursday 20 June.,task_subcomment,['Merged and will go out with wmf8 from Thursday 20 June.'],['SOLUTION USAGE']
+235836,VisualEditor: Can't paste into a selection covering the end of the document,Related URL: https://gerrit.wikimedia.org/r/68629 (Gerrit Change I7497b5195961e46718c7382409a66b7eec1162a9),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I7497b5195961e46718c7382409a66b7eec1162a9)'],['OBSERVED BUG BEHAVIOR']
+51549,"VisualEditor: Dialogs are quite big, maybe they could be smaller","It should allow the editor to see the page content while specifying a reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49969
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755",task_description,"['VisualEditor: Dialogs are quite big, maybe they could be smaller\n\nIt should allow the editor to see the page content while specifying a reference.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL\nURL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+235768,"VisualEditor: Dialogs are quite big, maybe they could be smaller",We changed the sizes of dialogs a few months ago.,task_subcomment,['We changed the sizes of dialogs a few months ago.'],['OBSERVED BUG BEHAVIOR']
+235766,"VisualEditor: Dialogs are quite big, maybe they could be smaller","(In reply to comment #2)
+> I think the user needs to be able to see the page text, but the current modal
+> window takes too much space in the screen. If it wasn't modal, the user could
+> at least drag it to the side to see the text.
+
+Hmm... It seems a dialog can be modal while still being draggable:
+http://jqueryui.com/dialog/#modal-confirmation",task_subcomment,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nHmm...', 'It seems a dialog can be modal while still being draggable:\nURL']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+235761,"VisualEditor: Dialogs are quite big, maybe they could be smaller","(In reply to comment #3)
+> Compare this with WikiEditor's dialog (which can be moved on the screen, and
+> do not forget what the user typed)
+
+and is smaller...",task_subcomment,['(In reply to comment #3)\nQUOTE\nQUOTE\n\nand is smaller...'],['SOLUTION DISCUSSION']
+235755,"VisualEditor: Dialogs are quite big, maybe they could be smaller","Notice that if I type some text in the window and then close it for a moment, to take a look in the text, it forgets what I typed once I open the window again.
+
+Compare this with WikiEditor's dialog (which can be moved on the screen, and do not forget what the user typed)",task_subcomment,"['Notice that if I type some text in the window and then close it for a moment, to take a look in the text, it forgets what I typed once I open the window again.', ""Compare this with WikiEditor's dialog (which can be moved on the screen, and do not forget what the user typed)""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+235750,"VisualEditor: Dialogs are quite big, maybe they could be smaller","I think the user needs to be able to see the page text, but the current modal window takes too much space in the screen. If it wasn't modal, the user could at least drag it to the side to see the text.",task_subcomment,"['I think the user needs to be able to see the page text, but the current modal window takes too much space in the screen.', ""If it wasn't modal, the user could at least drag it to the side to see the text.""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION']"
+235744,"VisualEditor: Dialogs are quite big, maybe they could be smaller","(In reply to comment #0)
+> It should allow the editor to see the page content while specifying a
+> reference.
+
+I'm a bit confused by your title - are you saying that you expect modal items to take up less screen estate? All modal items in VE (dialogs) are the same, standard size.",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\n\nI'm a bit confused by your title - are you saying that you expect modal items to take up less screen estate?"", 'All modal items in VE (dialogs) are the same, standard size.']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+51514,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),"Right now the z-index for .ve-ui-surface-overlay is set to 1000, which is way higher than pretty much anything else in MediaWiki. This makes it float above lots of things it shouldn't float above, like the header drop-down menu in the visual editor, the Echo notifications dropdown, etc. The z-index for the Echo notifications dropdown is 100 (so that it is higher than the close buttons in SiteNotices which are 99).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway)\n\nRight now the z-index for .ve-ui-surface-overlay is set to 1000, which is way higher than pretty much anything else in MediaWiki."", ""This makes it float above lots of things it shouldn't float above, like the header drop-down menu in the visual editor, the Echo notifications dropdown, etc."", 'The z-index for the Echo notifications dropdown is 100 (so that it is higher than the close buttons in SiteNotices which are 99).', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+233699,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),"(In reply to Alex Monk from comment #6)
+> Wasn't this fixed by Gerrit change #70572?
+
+Yes.",task_subcomment,['(In reply to Alex Monk from comment #6)\nQUOTE\n\nYes.'],['SOLUTION DISCUSSION']
+233692,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),Wasn't this fixed by Gerrit change 70572?,task_subcomment,"[""Wasn't this fixed by Gerrit change 70572?""]",['MOTIVATION']
+233686,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),Marking as tech-debt and pulling from beta per discussion.,task_subcomment,['Marking as tech-debt and pulling from beta per discussion.'],['ACTION ON ISSUE']
+233678,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),"The z-index isn't too high, the reason the overlays are on top of the save dialog is because they are in a further relative subtree of the DOM. Whether it is z-index -999, 0 or 100000 won't matter.
+
+The actual issue described here is bug 49275.
+
+The overlay using z-index is a separate issue that is otherwise harmless. I'd recommend we:
+* Mark as invalid (z-index isn't a problem).
+* or; Turn this into a technical debt ""clean up"" reminder to get rid of the z-index (they're no longer needed afaik, because we moved overlays to be a proper relative subtree overlay instead of siblings with higher z-index).
+* or; Mark as duplicate of bug 49275.",task_subcomment,"[""The z-index isn't too high, the reason the overlays are on top of the save dialog is because they are in a further relative subtree of the DOM."", ""Whether it is z-index -999, 0 or 100000 won't matter."", 'The actual issue described here is bug 49275.', 'The overlay using z-index is a separate issue that is otherwise harmless.', ""I'd recommend we:\n* Mark as invalid (z-index isn't a problem)."", '* or; Turn this into a technical debt ""clean up"" reminder to get rid of the z-index (they\'re no longer needed afaik, because we moved overlays to be a proper relative subtree overlay instead of siblings with higher z-index).', '* or; Mark as duplicate of bug 49275.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+233673,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),"(In reply to comment #0)
+> Right now the z-index for .ve-ui-surface-overlay is set to 1000, which is way
+> higher than pretty much anything else in MediaWiki. This makes it float above
+> lots of things it shouldn't float above, like the header drop-down menu in
+> the
+> visual editor, the Echo notifications dropdown, etc. The z-index for the Echo
+> notifications dropdown is 100 (so that it is higher than the close buttons in
+> SiteNotices which are 99).
+
+Yes, this was deliberate; you may recall the arms race with Echo where you kept breaking VE with your z-index changes for three weeks, hence this setting whilst we waited for Echo to stop changing. :-)
+
+(In reply to comment #2)
+> Created attachment 12545 [details]
+> Blue overlay
+> 
+> Is this screenshot related to this bug or another effect/issue?
+
+That's specifically bug 49275, but yes, that is related to this. The ""proper"" solution to this is putting the entire save dialog in its own iframe (like all the dialogs we've created since the new dialog system was built), but it's too close to deployment to do major changes like that.
+
+**Attached**: {F11114}",task_subcomment,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYes, this was deliberate; you may recall the arms race with Echo where you kept breaking VE with your z-index changes for three weeks, hence this setting whilst we waited for Echo to stop changing.', "":-)\n\n(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's specifically bug 49275, but yes, that is related to this."", 'The ""proper"" solution to this is putting the entire save dialog in its own iframe (like all the dialogs we\'ve created since the new dialog system was built), but it\'s too close to deployment to do major changes like that.', '**Attached**: {F11114}']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+233664,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),"Created attachment 12545
+Blue overlay
+
+Is this screenshot related to this bug or another effect/issue?
+
+**Attached**: {F11114}",task_subcomment,"['Created attachment 12545\nBlue overlay\n\nIs this screenshot related to this bug or another effect/issue?', '**Attached**: {F11114}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+233657,VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway),"The VisualEditor's save dialog has a z-index of 3, so perhaps you'll want to use something like 2 for ve-ui-surface-overlay rather than 1000.",task_subcomment,"[""The VisualEditor's save dialog has a z-index of 3, so perhaps you'll want to use something like 2 for ve-ui-surface-overlay rather than 1000.""]",['SOLUTION DISCUSSION']
+51491,VisualEditor: Transclusion dialog for objects without params should give you some clue as to what to do,"Screenshot
+
+An example is https://www.mediawiki.org/wiki/Template:Extension_code_in_wiki which can be seen at https://www.mediawiki.org/wiki/Extension:Syntax_Highlighting
+
+If opened in the inspector menu it displays pretty much nothing (screenshot attached) because there aren't any modifiable parameters. It comes off looking like it broke ;p.
+
+It would be good if, instead of displaying the title, the inspector menu could display a slug that reads something like ""This template has no editable elements"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11046}",task_description,"[""VisualEditor: Transclusion dialog for objects without params should give you some clue as to what to do\n\nScreenshot\n\nAn example is URL which can be seen at URL\n\nIf opened in the inspector menu it displays pretty much nothing (screenshot attached) because there aren't any modifiable parameters."", 'It comes off looking like it broke ;p.\n\nIt would be good if, instead of displaying the title, the inspector menu could display a slug that reads something like ""This template has no editable elements"".', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11046}']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+232199,VisualEditor: Transclusion dialog for objects without params should give you some clue as to what to do,"This is already fixed in master, and will go out in wmf8; our apologies for it looking so denuded in that version!",task_subcomment,"['This is already fixed in master, and will go out in wmf8; our apologies for it looking so denuded in that version!']",['SOLUTION USAGE']
+51452,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"When an editor tried to remove a heading, the following empty h3 tag seems to have been left behind:  
    
+
+Serializes to ====== and the user complained about it.
+
+From the bug report: /mng/bugs/en.2013-06-10T16:41:02.032Z-Lightning_(software) on parsoid.wmflabs.org
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs\n\nWhen an editor tried to remove a heading, the following empty h3 tag seems to have been left behind:  
    \n\nSerializes to ====== and the user complained about it.', 'From the bug report: /mng/bugs/en.2013-06-10T16:41:02.032Z-Lightning_(software) on parsoid.wmflabs.org\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+442609,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,These look like cached code issues. Closing absent further issues.,task_subcomment,"['These look like cached code issues.', 'Closing absent further issues.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+437791,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Found an other one, edit time is about 12 hours after the first example
+https://fr.wikipedia.org/w/index.php?title=Nahhalin&diff=prev&oldid=113480458",task_subcomment,"['Found an other one, edit time is about 12 hours after the first example\nURL']",['OBSERVED BUG BEHAVIOR']
+437631,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"I checked again on production - including checking on the exactly same section layout on which the bug was reported: 
+{F108277}
+
+
+
+",task_subcomment,['I checked again on production - including checking on the exactly same section layout on which the bug was reported: \n{F108277}'],['OBSERVED BUG BEHAVIOR']
+437566,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"No other edits with `====` for the moment, I will send an other comment if I see one",task_subcomment,"['No other edits with CODE for the moment, I will send an other comment if I see one']",['OBSERVED BUG BEHAVIOR']
+437395,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,">>! In T51452#1174343, @NicoV wrote:
+> It doesn't seem to be fixed in 1.25wmf23.
+> Edit from 17 hours ago on frwiki (Version page reports 1.25wmf23) with the same kind of problems :
+> https://fr.wikipedia.org/w/index.php?title=Tour_d%27Alg%C3%A9rie_1952&diff=prev&oldid=113472247
+
+Yesterday's deployment happened late, so maybe this happened just before or just after the deployment and the user's browser was still running the old code? I tried to create an empty heading or a whitespace-only heading in VE on frwiki and I couldn't. Are there any other edits adding `====` that are more recent?",task_subcomment,"[""QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYesterday's deployment happened late, so maybe this happened just before or just after the deployment and the user's browser was still running the old code?"", ""I tried to create an empty heading or a whitespace-only heading in VE on frwiki and I couldn't."", 'Are there any other edits adding CODE that are more recent?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+437341,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"It doesn't seem to be fixed in 1.25wmf23.
+Edit from 17 hours ago on frwiki (Version page reports 1.25wmf23) with the same kind of problems :
+https://fr.wikipedia.org/w/index.php?title=Tour_d%27Alg%C3%A9rie_1952&diff=prev&oldid=113472247",task_subcomment,"[""It doesn't seem to be fixed in 1.25wmf23."", 'Edit from 17 hours ago on frwiki (Version page reports 1.25wmf23) with the same kind of problems :\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+431381,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Deleting headings is clean now
+
+Beta {F103264}
+vs
+current production(wmf22)
+{F103266}",task_subcomment,['Deleting headings is clean now\n\nBeta {F103264}\nvs\ncurrent production(wmf22)\n{F103266}'],['OBSERVED BUG BEHAVIOR']
+430149,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output 
     instead of 
+
+[[https://gerrit.wikimedia.org/r/162310]]",task_subcomment,"['Change 162310 merged by jenkins-bot:\nFor empty / whitespace-only headings, output 
     instead of \n\n[[GERRIT_URL]]']",['GERRIT_URL']
+412857,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Change 162310 had a related patch set uploaded (by Jforrester):
+MWHeading: Don't put self in output if contents are blank or whitespace
+
+[[https://gerrit.wikimedia.org/r/162310]]
+
+#patch-for-review",task_subcomment,"[""Change 162310 had a related patch set uploaded (by Jforrester):\nMWHeading: Don't put self in output if contents are blank or whitespace\n\n[[GERRIT_URL]]\n\n#patch-for-review""]",['GERRIT_URL']
+229854,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,*** Bug 70368 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 70368 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+229850,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Change 162310 had a related patch set uploaded by Jforrester:
+MWHeading: Don't put self in output if contents are blank or whitespace
+
+https://gerrit.wikimedia.org/r/162310",task_subcomment,"[""Change 162310 had a related patch set uploaded by Jforrester:\nMWHeading: Don't put self in output if contents are blank or whitespace\n\nGERRIT_URL""]",['INVESTIGATION AND EXPLORATION']
+229843,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,/mnt/bugs/2013-06-10T13:57:10.670Z-%25E8%25A5%25BF%25E7%2593%259C%25E6%25B3%25A2 (chinese wikipedia) has an empty heading tag left behind as well (probably inserted when the user added a heading and then deleted it).,task_subcomment,['/mnt/bugs/2013-06-10T13:57:10.670Z-%25E8%25A5%25BF%25E7%2593%259C%25E6%25B3%25A2 (chinese wikipedia) has an empty heading tag left behind as well (probably inserted when the user added a heading and then deleted it).'],['OBSERVED BUG BEHAVIOR']
+229837,VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"/mnt/bugs/2013-06-09T22%3A08%3A31.223Z-Sapo-comum (ptwiki) reports an empty heading left behind ""== =="" when the user actually meant to delete it (and I presume thought it gone after the non-whitespace text was deleted).",task_subcomment,"['/mnt/bugs/2013-06-09T22%3A08%3A31.223Z-Sapo-comum (ptwiki) reports an empty heading left behind ""== =="" when the user actually meant to delete it (and I presume thought it gone after the non-whitespace text was deleted).']",['OBSERVED BUG BEHAVIOR']
+51431,VisualEditor: Grunt leaves behind temporary html file if tests fail,"modules/ve/test/index-phantomjs-tmp.html is not deleted if the tests fail.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",task_description,"['VisualEditor: Grunt leaves behind temporary html file if tests fail\n\nmodules/ve/test/index-phantomjs-tmp.html is not deleted if the tests fail.', '--------------------------\n**Version**: unspecified\n**Severity**: trivial']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+253197,VisualEditor: Grunt leaves behind temporary html file if tests fail,Related URL: https://gerrit.wikimedia.org/r/68631 (Gerrit Change I5079d00a63d43276a12dd78c306bb3819470631d),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I5079d00a63d43276a12dd78c306bb3819470631d)'],['OBSERVED BUG BEHAVIOR']
+51429,VisualEditor: Adding a new heading should add a newline before the heading too,"I think it is standard in in (all?) Wikipedias to add a newline before adding a new heading.
+
+This is currently not done by the VisualEditor, see URL.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://de.wikipedia.org/w/index.php?title=Benutzer:Raymond/heading&diff=119444892&oldid=119444326",task_description,"['VisualEditor: Adding a new heading should add a newline before the heading too\n\nI think it is standard in in (all?)', 'Wikipedias to add a newline before adding a new heading.', 'This is currently not done by the VisualEditor, see URL.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**URL**: URL']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'ISSUE CONTENT MANAGEMENT']"
+253137,VisualEditor: Adding a new heading should add a newline before the heading too,"Roan - I guess we could do this at our end, or as a ""default whitespace"" rule in Parsoid. Which do you think makes most sense?",task_subcomment,"['Roan - I guess we could do this at our end, or as a ""default whitespace"" rule in Parsoid.', 'Which do you think makes most sense?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+51428,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)","Steps to reproduce:
+
+1. Go into a heading
+
+2. Change heading level from 2 to 3 (i.e.)
+
+Expected output: Only the number of = should change
+
+Actual output: Number of = is changed correctly but the newline before the heading is moved under the heading now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://de.wikipedia.org/w/index.php?title=Benutzer:Raymond/heading&diff=119444161&oldid=119444142",task_description,"['Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)\n\nSteps to reproduce:\n\n1.', 'Go into a heading\n\n2.', 'Change heading level from 2 to 3 (i.e.)', 'Expected output: Only the number of = should change\n\nActual output: Number of = is changed correctly but the newline before the heading is moved under the heading now.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'ISSUE CONTENT MANAGEMENT']"
+253086,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)",Fix deployed.,task_subcomment,['Fix deployed.'],['ACTION ON ISSUE']
+253081,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)",https://gerrit.wikimedia.org/r/70214 (Gerrit Change Id8e5b87602e3ba0f0e1cf6b5c6e03f4949e7d053) | change APPROVED and MERGED [by jenkins-bot],task_subcomment,['GERRIT_URL (Gerrit Change Id8e5b87602e3ba0f0e1cf6b5c6e03f4949e7d053) | change APPROVED and MERGED [by jenkins-bot]'],['OBSERVED BUG BEHAVIOR']
+253077,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)",Related URL: https://gerrit.wikimedia.org/r/70214 (Gerrit Change Id8e5b87602e3ba0f0e1cf6b5c6e03f4949e7d053),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change Id8e5b87602e3ba0f0e1cf6b5c6e03f4949e7d053)'],['OBSERVED BUG BEHAVIOR']
+253072,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)","(In reply to comment #3)
+> I believe they have a default whitespace setting that could fix this so this
+> could be raised as a Parsoid bug.
+
+Marking as such.",task_subcomment,['(In reply to comment #3)\nQUOTE\nQUOTE\n\nMarking as such.'],['ACTION ON ISSUE']
+253067,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)","On a separate note, the standard spacing around headings (on en.wiki at least) appears to be:
+
+Foo
+
+==Bar==
+Baz
+
+Where Parsoid renders:
+
+Foo
+==Bar==
+Baz
+
+I believe they have a default whitespace setting that could fix this so this could be raised as a Parsoid bug.",task_subcomment,"['On a separate note, the standard spacing around headings (on en.wiki at least) appears to be:\n\nFoo\n\n==Bar==\nBaz\n\nWhere Parsoid renders:\n\nFoo\n==Bar==\nBaz\n\nI believe they have a default whitespace setting that could fix this so this could be raised as a Parsoid bug.']",['INVESTIGATION AND EXPLORATION']
+253063,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)","Replacing a heading is the same a removing the old one and inserting a new one (transactionally speaking), so all the (non visible) whitespace information will be lost.
+
+The output on the right is what you'd get if you created the document from scratch and as you are making structural changes, rather than changes within a paragraph, it is arguably by design that we throw away any old quirks in the wikitext for that section.",task_subcomment,"['Replacing a heading is the same a removing the old one and inserting a new one (transactionally speaking), so all the (non visible) whitespace information will be lost.', ""The output on the right is what you'd get if you created the document from scratch and as you are making structural changes, rather than changes within a paragraph, it is arguably by design that we throw away any old quirks in the wikitext for that section.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+253060,"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)","Indeed; a newline above or below a heading will be trimmed when the heading is changed in some manner. Is this Parsoid's behaviour?
+
+https://www.mediawiki.org/w/index.php?title=VisualEditor:Bug_49428&diff=715815&oldid=715814",task_subcomment,"['Indeed; a newline above or below a heading will be trimmed when the heading is changed in some manner.', ""Is this Parsoid's behaviour?"", 'URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+51420,VisualEditor: Rendering of categories fails on first load sometimes in Chrome (Webkit?),"Instead of ""Foo v"" you get ""Foo
+v"" - dialog contents render before they're styled because the CSS is slow in coming in (per Roan).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Rendering of categories fails on first load sometimes in Chrome (Webkit?)', 'Instead of ""Foo v"" you get ""Foo\nv"" - dialog contents render before they\'re styled because the CSS is slow in coming in (per Roan).', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+852196,VisualEditor: Rendering of categories fails on first load sometimes in Chrome (Webkit?),"The code to which this refers has been since adjusted, and I think this is now long-fixed.",task_subcomment,"['The code to which this refers has been since adjusted, and I think this is now long-fixed.']",['OBSERVED BUG BEHAVIOR']
+252567,VisualEditor: Rendering of categories fails on first load sometimes in Chrome (Webkit?),"Per Timo:
+
+| Most likely cause of meta dialog's flash of unstyled content:
+|
+| ve.ui.Dialog.js:
+|   ""ve.ui.Dialog.static.addLocalStylesheets( [ 've.ui.Dialog.css' ] );""",task_subcomment,"['Per Timo:\n\n| Most likely cause of meta dialog\'s flash of unstyled content:\n|\n| ve.ui.Dialog.js:\n|   ""ve.ui.Dialog.static.addLocalStylesheets( [ \'ve.ui.Dialog.css\' ] );""']",['INVESTIGATION AND EXPLORATION']
+252564,VisualEditor: Rendering of categories fails on first load sometimes in Chrome (Webkit?),"So there are two somewhat separate (but possibly connected issues) here. One is that, when you load the category dialog on a cold cache (try incognito window) in Chrome, the dialog contents are displayed before they're styled. I can reproduce this on mw.org but not on localhost, presumably because localhost delivers the CSS really fast.
+
+The rendering bug that James is talking about, with the arrow appearing on the next line, only happens in Chrome and only when the flash of unstyled content also happens.
+
+It would be nice if we could block showing the dialog on the CSS loading. The way we load CSS into the dialog iframes should probably be reconsidered anyway.",task_subcomment,"['So there are two somewhat separate (but possibly connected issues) here.', ""One is that, when you load the category dialog on a cold cache (try incognito window) in Chrome, the dialog contents are displayed before they're styled."", 'I can reproduce this on mw.org but not on localhost, presumably because localhost delivers the CSS really fast.', 'The rendering bug that James is talking about, with the arrow appearing on the next line, only happens in Chrome and only when the flash of unstyled content also happens.', 'It would be nice if we could block showing the dialog on the CSS loading.', 'The way we load CSS into the dialog iframes should probably be reconsidered anyway.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+51400,Images: Handle templated image options containing pipes,"Some perverse templates such as {{Largethumb}} return a string with several options separated by pipes (""thumb|px""). In the PHP parser those pipes are then picked up by the link regexp, so result in the regular image options.
+
+In our attribute handling we expand attributes separately, so can end up with strings like the above in a single attribute value. In [[:de:Portal:Thüringen]] for example that is the case for the href attribute, which then caused a crash after retrieving image properties.
+
+We will likely need to handle expanded attributes containing a pipe properly by re-parsing their string representation. This will be difficult to map onto our current template-affected attribute handling.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Images: Handle templated image options containing pipes\n\nSome perverse templates such as {{Largethumb}} return a string with several options separated by pipes (""thumb|px"").', 'In the PHP parser those pipes are then picked up by the link regexp, so result in the regular image options.', 'In our attribute handling we expand attributes separately, so can end up with strings like the above in a single attribute value.', 'In [[:de:Portal:Thüringen]] for example that is the case for the href attribute, which then caused a crash after retrieving image properties.', 'We will likely need to handle expanded attributes containing a pipe properly by re-parsing their string representation.', 'This will be difficult to map onto our current template-affected attribute handling.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+1482590,Images: Handle templated image options containing pipes,"Parsoid supports templated image options. Editability in VE of these is not a Parsoid issue. But, since then, the largethumb issues have been resolved differently and VE has been enabled on nlwiki. 
+Other missing functionality is tracked in their own bugs (ex: T88040). So, resolving this.
+",task_subcomment,"['Parsoid supports templated image options.', 'Editability in VE of these is not a Parsoid issue.', 'But, since then, the largethumb issues have been resolved differently and VE has been enabled on nlwiki.', 'Other missing functionality is tracked in their own bugs (ex: T88040).', 'So, resolving this.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+569742,Images: Handle templated image options containing pipes,"The current name of this ticket ""Images: Handle templated image options containing pipes"" suggests that handling templated image options or image options without pipes would work. They don't. Consider renaming to ""Images: Handle templated image options"".
+
+On nl.wp largethumb==""260px|thumb"". Creating a single option template like large==""260px"" would change [[file.foo.jpg|{{largethumb}}]] into [[file.foo.jpg|{{large}}|thumb]]. The first isn't editable in VE. The latter isn't editable in VE either, though the template contains only  a single attribute, and does not contain pipes. ",task_subcomment,"['The current name of this ticket ""Images: Handle templated image options containing pipes"" suggests that handling templated image options or image options without pipes would work.', ""They don't."", 'Consider renaming to ""Images: Handle templated image options"".', 'On nl.wp largethumb==""260px|thumb"".', 'Creating a single option template like large==""260px"" would change [[file.foo.jpg|{{largethumb}}]] into [[file.foo.jpg|{{large}}|thumb]].', ""The first isn't editable in VE."", ""The latter isn't editable in VE either, though the template contains only  a single attribute, and does not contain pipes.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+548278,Images: Handle templated image options containing pipes,"As stated in T51400#579910, Parsoid has implemented solution 1 which has been live in production since February 2014. This prevents largethumb images from being edited in VisualEditor and also ensures that those images roundtrip correctly.
+
+If {T88040} is resolved, we could potentially unblock the editing support for these images -- to be investigated.  Other possibilities for dealing with largethumb have been discussed in comments above (T51400#579925, T51400#1071119). In addition, as far as I know, VE does not yet support editing of templated-affected attributes. So, that editing support would have to be added to VE before these images with template-generated attributes can be edited.
+
+So, TL:DR; is that the status quo seems fine for enabling VE, i.e .this task should no longer be a blocker. It prevents editing of these largethumb-marked images in VE, but it shouldn't corrupt those pages either, nor should it block editing of other parts of the page.",task_subcomment,"['As stated in T51400#579910, Parsoid has implemented solution 1 which has been live in production since February 2014.', 'This prevents largethumb images from being edited in VisualEditor and also ensures that those images roundtrip correctly.', 'If {T88040} is resolved, we could potentially unblock the editing support for these images -- to be investigated.', 'Other possibilities for dealing with largethumb have been discussed in comments above (T51400#579925, T51400#1071119).', 'In addition, as far as I know, VE does not yet support editing of templated-affected attributes.', 'So, that editing support would have to be added to VE before these images with template-generated attributes can be edited.', 'So, TL:DR; is that the status quo seems fine for enabling VE, i.e .this task should no longer be a blocker.', ""It prevents editing of these largethumb-marked images in VE, but it shouldn't corrupt those pages either, nor should it block editing of other parts of the page.""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+426040,Images: Handle templated image options containing pipes,"Nothing to be here for this quarter .. So, I am removing the VE Q3 blocker part.",task_subcomment,"['Nothing to be here for this quarter ..', 'So, I am removing the VE Q3 blocker part.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+417902,Images: Handle templated image options containing pipes,"The solution to this bug is probably something like ""largethumb"" in core or T90914.  But we could also create a {{largethumb2|File:Foo.jpg|some|options|caption}} template which expanded to a complete 
     tag; that would allow pages which use {{largethumb2}} to be edited in VE.  Ideally we'd use something like wikilint to automatically apply the {{largethumb2}} template.",task_subcomment,"['The solution to this bug is probably something like ""largethumb"" in core or T90914.', 'But we could also create a {{largethumb2|File:Foo.jpg|some|options|caption}} template which expanded to a complete 
     tag; that would allow pages which use {{largethumb2}} to be edited in VE.', ""Ideally we'd use something like wikilint to automatically apply the {{largethumb2}} template.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+405126,Images: Handle templated image options containing pipes,"We need to figure out what else to do with it as far as editing goes. As it stands, Parsoid supports rendering and roundtripping for these templates.",task_subcomment,"['We need to figure out what else to do with it as far as editing goes.', 'As it stands, Parsoid supports rendering and roundtripping for these templates.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251344,Images: Handle templated image options containing pipes,All patches merged; resetting bug status,task_subcomment,['All patches merged; resetting bug status'],['ACTION ON ISSUE']
+251339,Images: Handle templated image options containing pipes,This problem exists because nl.wp wants two thumb sizes. Why not add 'largethumb' as a core part of syntax? i.e. Has that approach been explored and rejected?,task_subcomment,"['This problem exists because nl.wp wants two thumb sizes.', ""Why not add 'largethumb' as a core part of syntax?"", 'i.e.', 'Has that approach been explored and rejected?']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+251334,Images: Handle templated image options containing pipes,"Change 110095 merged by jenkins-bot:
+Set up data-mw for all templated image attributes.
+
+https://gerrit.wikimedia.org/r/110095",task_subcomment,"['Change 110095 merged by jenkins-bot:\nSet up data-mw for all templated image attributes.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+251330,Images: Handle templated image options containing pipes,"Here is the latest on this. 
+
+https://gerrit.wikimedia.org/r/#/c/110095/ provides support for templated image options. It identifies individual image options that came from a template and provides VE sufficient information to make them editable. Parsoid can then serialize the edited attributes back to transclusions. See https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Transclusion-affected_attributes for how Parsoid conveys this information to clients (VE).
+
+However, {{largethumb}} is still a special case. That gerrit patch also adds support for parsing largethumb as two image options. However, Parsoid cannot provide editing support for it, i.e. we cannot mark up both ""thumb"" and ""261px"" as coming from templates, that they are connected, and that VE cannot edit them individually. As you can see from the DOM spec (linked above), the spec is already fairly complex and we do not want to complicate the spec further to support this edge case. This is not just a complication for Parsoid, but for VE, and any other clients that need to deal with this spec.
+
+That said, there are two options for how we can move forward.
+
+1. Parsoid can mark images from {{largethumb}} uneditable so that VE doesn't attempt to deal with that template. This also means that the wikitext for these images will always be preserved and can only be edited in wikitext mode.
+
+2. Parsoid makes the image editable. When the page is edited in VE, Parsoid preserves the image including {{largethumb}} transclusion when the image itself is not edited (even if other parts of the page are edited - which should be the vast majority of edits). But, if the image itself is edited, the {{largethumb}} template will effectively be subst-ed because Parsoid flattens out {{largethumb}} to regular options: ""thumb"" and ""261px"".
+
+As of now, gerrit patch 110095 implements solution 1. as an initial step. However, in the long run, we feel solution 2 is a better solution that  provides editing support and also gradually moves towards reduced largethumb usage (by subst-ing largethumb images edited in VE). John Vandenburg has suggested in comment 3 (#c3 above) that if nlwiki set 261px as the default thumbnail size, editors could simply use |thumb instead of |{{largethumb}} and get the same effect. Not sure if that is viable, but collating all suggestions here in one place.
+
+It would be good to get some input on these options.",task_subcomment,"['Here is the latest on this.', 'URL provides support for templated image options.', 'It identifies individual image options that came from a template and provides VE sufficient information to make them editable.', 'Parsoid can then serialize the edited attributes back to transclusions.', 'See URL for how Parsoid conveys this information to clients (VE).', 'However, {{largethumb}} is still a special case.', 'That gerrit patch also adds support for parsing largethumb as two image options.', 'However, Parsoid cannot provide editing support for it, i.e.', 'we cannot mark up both ""thumb"" and ""261px"" as coming from templates, that they are connected, and that VE cannot edit them individually.', 'As you can see from the DOM spec (linked above), the spec is already fairly complex and we do not want to complicate the spec further to support this edge case.', 'This is not just a complication for Parsoid, but for VE, and any other clients that need to deal with this spec.', 'That said, there are two options for how we can move forward.', '1.', ""Parsoid can mark images from {{largethumb}} uneditable so that VE doesn't attempt to deal with that template."", 'This also means that the wikitext for these images will always be preserved and can only be edited in wikitext mode.', '2.', 'Parsoid makes the image editable.', 'When the page is edited in VE, Parsoid preserves the image including {{largethumb}} transclusion when the image itself is not edited (even if other parts of the page are edited - which should be the vast majority of edits).', 'But, if the image itself is edited, the {{largethumb}} template will effectively be subst-ed because Parsoid flattens out {{largethumb}} to regular options: ""thumb"" and ""261px"".', 'As of now, gerrit patch 110095 implements solution 1. as an initial step.', 'However, in the long run, we feel solution 2 is a better solution that  provides editing support and also gradually moves towards reduced largethumb usage (by subst-ing largethumb images edited in VE).', 'John Vandenburg has suggested in comment 3 (#c3 above) that if nlwiki set 261px as the default thumbnail size, editors could simply use |thumb instead of |{{largethumb}} and get the same effect.', 'Not sure if that is viable, but collating all suggestions here in one place.', 'It would be good to get some input on these options.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+251326,Images: Handle templated image options containing pipes,"Change 110095 had a related patch set uploaded by Subramanya Sastry:
+WIP: Set up data-mw for all templated image attributes.
+
+https://gerrit.wikimedia.org/r/110095",task_subcomment,"['Change 110095 had a related patch set uploaded by Subramanya Sastry:\nWIP: Set up data-mw for all templated image attributes.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+251321,Images: Handle templated image options containing pipes,"Change 76821 merged by jenkins-bot:
+Add new parserTests for image attributes coming from templates.
+
+https://gerrit.wikimedia.org/r/76821",task_subcomment,"['Change 76821 merged by jenkins-bot:\nAdd new parserTests for image attributes coming from templates.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+251315,Images: Handle templated image options containing pipes,"Change 76821 had a related patch set uploaded by Cscott:
+Add new parserTests for image attributes coming from templates.
+
+https://gerrit.wikimedia.org/r/76821",task_subcomment,"['Change 76821 had a related patch set uploaded by Cscott:\nAdd new parserTests for image attributes coming from templates.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+251309,Images: Handle templated image options containing pipes,"There are two independent issues here, it appears.
+
+1. Image attributes that are template-affected are not properly marked up during parse and hence doesn't rt back to its original form.  This is an issue independent of {{largethumb}} usage.  Once we fix this, even if the {{largethumb}} template doesn't parse correctly, it will RT correctly. This may be easier to fix.  Will create a separate bug report for it.
+
+[subbu@earth tests] echo '[[File:Telephone exchange 1.svg|thumb|{{echo|261px}}]]' | node parse --wt2wt
+[[File:Telephone exchange 1.svg|thumb|261px]]
+
+2. Proper rendering of the image in VE depends on us correctly handling the largethumb template (and other such templated image options containing pipes).",task_subcomment,"['There are two independent issues here, it appears.', '1.', ""Image attributes that are template-affected are not properly marked up during parse and hence doesn't rt back to its original form."", 'This is an issue independent of {{largethumb}} usage.', ""Once we fix this, even if the {{largethumb}} template doesn't parse correctly, it will RT correctly."", 'This may be easier to fix.', 'Will create a separate bug report for it.', ""[subbu@earth tests] echo '[[File:Telephone exchange 1.svg|thumb|{{echo|261px}}]]' | node parse --wt2wt\n[[File:Telephone exchange 1.svg|thumb|261px]]\n\n2."", 'Proper rendering of the image in VE depends on us correctly handling the largethumb template (and other such templated image options containing pipes).']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION']"
+251301,Images: Handle templated image options containing pipes,~ 1 in 225 nlwp articles (0.45%) have this bug.  This bug affects the whole page.,task_subcomment,"['~ 1 in 225 nlwp articles (0.45%) have this bug.', 'This bug affects the whole page.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+251294,Images: Handle templated image options containing pipes,"Except for eight cases, the parser fails for nl.wp pages at http://parsoid.wmflabs.org:8001/topfails all contain '{{largethumb}}'.",task_subcomment,"[""Except for eight cases, the parser fails for nl.wp pages at URL all contain '{{largethumb}}'.""]",['BUG REPRODUCTION']
+251289,Images: Handle templated image options containing pipes,"Ugh, I guess we have to get to this sooner than later then and find a reasonable solution.",task_subcomment,"['Ugh, I guess we have to get to this sooner than later then and find a reasonable solution.']",['SOLUTION DISCUSSION']
+251284,Images: Handle templated image options containing pipes,"There are around 110 uses on enwp
+https://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Template:Largethumb&limit=110
+They are all in the article, and most of them are [[491]]-[[635]] (years).  I'm guessing they can be subst'd without much concern, to converted to normal thumbs.
+
+On nlwp, it is way over 5000 uses
+https://nl.wikipedia.org/w/index.php?title=Speciaal:VerwijzingenNaarHier/Sjabloon:Largethumb&limit=5000
+
+They are in the pages; not in a template, and nlwp doesnt appear keen to subst: them.  Has anyone proposed that their default thumbnail be set to this value?
+
+only four uses here:
+https://nds-nl.wikipedia.org/wiki/Spesiaal:Verwiezingen_naor_disse_pagina/Mal:Largethumb",task_subcomment,"['There are around 110 uses on enwp\nURL\nThey are all in the article, and most of them are [[491]]-[[635]] (years).', ""I'm guessing they can be subst'd without much concern, to converted to normal thumbs."", 'On nlwp, it is way over 5000 uses\nURL\n\nThey are in the pages; not in a template, and nlwp doesnt appear keen to subst: them.', 'Has anyone proposed that their default thumbnail be set to this value?', 'only four uses here:\nURL']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+251279,Images: Handle templated image options containing pipes,https://gerrit.wikimedia.org/r/67853 (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173) | change APPROVED and MERGED [by jenkins-bot],task_subcomment,['GERRIT_URL (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173) | change APPROVED and MERGED [by jenkins-bot]'],['OBSERVED BUG BEHAVIOR']
+251273,Images: Handle templated image options containing pipes,Related URL: https://gerrit.wikimedia.org/r/67853 (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173)'],['OBSERVED BUG BEHAVIOR']
+51394,VisualEditor: Misc. issues,"https://en.wikipedia.org/w/index.php?title=Mavericks_(location)&diff=559262706&oldid=559261658
+
+There are a few issues here:
+
+* the diff presented to the user prior to save didn't include any of these extraneous changes (or I obviously wouldn't have saved the edit);
+
+* there's  markup being inserted throughout the page, breaking a number of links; and
+
+* there's spacing normalization being done to template parameters, resulting in an even dirtier diff.
+
+I'm not sure how these issues should be split out or if there are existing bug reports for all three of these issues.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=visualeditor",task_description,"['VisualEditor: Misc.', ""issues\n\nURL\n\nThere are a few issues here:\n\n* the diff presented to the user prior to save didn't include any of these extraneous changes (or I obviously wouldn't have saved the edit);\n\n* there's  markup being inserted throughout the page, breaking a number of links; and\n\n* there's spacing normalization being done to template parameters, resulting in an even dirtier diff."", ""I'm not sure how these issues should be split out or if there are existing bug reports for all three of these issues."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+250788,VisualEditor: Misc. issues,Marking as such.,task_subcomment,['Marking as such.'],['OBSERVED BUG BEHAVIOR']
+250779,VisualEditor: Misc. issues,"The  tags in Cite transclusions (and other tpl transclusions, if they showed up) should be fixed.  My suggestion is to close this bug now since the VE heading bug is tracked separately, and as for user entering wikitext, well, that could be a feature request for VE alerting the user when (s)he enters wikitext, or maybe a FAQ entry or something. 
+
+In all cases, this bug wont be much useful beyond this point.",task_subcomment,"['The  tags in Cite transclusions (and other tpl transclusions, if they showed up) should be fixed.', 'My suggestion is to close this bug now since the VE heading bug is tracked separately, and as for user entering wikitext, well, that could be a feature request for VE alerting the user when (s)he enters wikitext, or maybe a FAQ entry or something.', 'In all cases, this bug wont be much useful beyond this point.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+250771,VisualEditor: Misc. issues,"MZMcBride: For future reference, only one single bug per report please. Also see https://www.mediawiki.org/wiki/How_to_report_a_bug . I'd normally close such tickets as INVALID and ask the reporter to file separate tickets.",task_subcomment,"['MZMcBride: For future reference, only one single bug per report please.', 'Also see URL .', ""I'd normally close such tickets as INVALID and ask the reporter to file separate tickets.""]","['ISSUE CONTENT MANAGEMENT', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+250765,VisualEditor: Misc. issues,"The  tags in Cite transclusions in ref tags is a Parsoid bug.  I have that on my radar -- will look into that next possibly.
+
+As for  tags in other places, looking at bug reports on parsoid.wmflabs.org, there are three different reasons
+
+* due to the bug in ref-tags I mentioned above
+
+* user entering wikitext in the visual editor (Ex: ==See also==* [[Tomato (company)]] in https://en.wikipedia.org/w/index.php?title=Underworld_(band)&diff=prev&oldid=559255806 based on looking at the HTML sent to Parsoid).  I've seen wikitext entered via VE in a few bug reports -- all such wikitext will be nowiki escaped by Parsoid
+
+* Empty heading left behind in the visual editor (tracked in Bug 49452)",task_subcomment,"['The  tags in Cite transclusions in ref tags is a Parsoid bug.', 'I have that on my radar -- will look into that next possibly.', 'As for  tags in other places, looking at bug reports on parsoid.wmflabs.org, there are three different reasons\n\n* due to the bug in ref-tags I mentioned above\n\n* user entering wikitext in the visual editor (Ex: ==See also==* [[Tomato (company)]] in URL based on looking at the HTML sent to Parsoid).', ""I've seen wikitext entered via VE in a few bug reports -- all such wikitext will be nowiki escaped by Parsoid\n\n* Empty heading left behind in the visual editor (tracked in Bug 49452)""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+250760,VisualEditor: Misc. issues,"Expansion wtf (warning: large diff):
+
+https://en.wikipedia.org/w/index.php?title=Breast_cancer&diff=558696523&oldid=558695500",task_subcomment,['Expansion wtf (warning: large diff):\n\nURL'],['OBSERVED BUG BEHAVIOR']
+250754,VisualEditor: Misc. issues,"(In reply to comment #3)
+> Misspelling trap:
+> 
+> https://en.wikipedia.org/w/index.
+> php?title=Pepsi_Next&curid=35519554&diff=559230837&oldid=559223494
+That one isn't a serialization or round-tripping bug. The user edited the text of the link, but didn't edit the target.
+
+Arguably, links where the text equals the target should have the target track the text when the user edits them. Or maybe they shouldn't. James?
+
+(In reply to comment #2)
+>  funkiness:
+> 
+> https://en.wikipedia.org/w/index.
+> php?title=British_Rail_Class_50&curid=1448622&diff=559199747&oldid=558786539
+Probably a Parsoid bug due to Gallery being capitalized. CCing Gabriel.
+
+The nowiki issues also look like Parsoid serialization bugs to me.",task_subcomment,"[""(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nThat one isn't a serialization or round-tripping bug."", ""The user edited the text of the link, but didn't edit the target."", 'Arguably, links where the text equals the target should have the target track the text when the user edits them.', ""Or maybe they shouldn't."", 'James?', '(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nProbably a Parsoid bug due to Gallery being capitalized.', 'CCing Gabriel.', 'The nowiki issues also look like Parsoid serialization bugs to me.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+250749,VisualEditor: Misc. issues," funkiness:
+
+https://en.wikipedia.org/w/index.php?title=Louis-J%C3%A9r%C3%B4me_Gohier&curid=2785680&diff=558445883&oldid=542944471",task_subcomment,[' funkiness:\n\nURL'],['OBSERVED BUG BEHAVIOR']
+250743,VisualEditor: Misc. issues,"Misspelling trap:
+
+https://en.wikipedia.org/w/index.php?title=Pepsi_Next&curid=35519554&diff=559230837&oldid=559223494",task_subcomment,['Misspelling trap:\n\nURL'],['OBSERVED BUG BEHAVIOR']
+250737,VisualEditor: Misc. issues," funkiness:
+
+https://en.wikipedia.org/w/index.php?title=British_Rail_Class_50&curid=1448622&diff=559199747&oldid=558786539",task_subcomment,[' funkiness:\n\nURL'],['OBSERVED BUG BEHAVIOR']
+250731,VisualEditor: Misc. issues,"This bug is probably a wash in terms of being an actionable report, so I'll just use it to log other diffs I'm coming across via .
+
+
+ corruption:
+
+https://en.wikipedia.org/w/index.php?title=Black_Country_Communion&curid=25818560&diff=559205644&oldid=547680063
+
+
+ weirdness:
+
+https://en.wikipedia.org/w/index.php?title=Lightning_(software)&diff=prev&oldid=559252596
+
+
+Possible unintentional HTML comment removal;  corruption:
+
+https://en.wikipedia.org/w/index.php?title=Underworld_(band)&diff=prev&oldid=559255806",task_subcomment,"[""This bug is probably a wash in terms of being an actionable report, so I'll just use it to log other diffs I'm coming across via  corruption:\n\nURL\n\n\n weirdness:\n\nURL\n\n\nPossible unintentional HTML comment removal;  corruption:\n\nURL""]",['OBSERVED BUG BEHAVIOR']
+51346,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)","There are a couple of ways to configure references to display differently:
+http://www.mediawiki.org/wiki/Extension:Cite/Cite.php#Set_references_to_use_.5E_and_letters_like_Wikipedia
+we should access these so the rendering in edit mode is consistent with the that in read mode.
+",task_description,"['Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g.', '1.0, 1.1 / a,b,c, removing brackets, etc.)', 'There are a couple of ways to configure references to display differently:\nURL\nwe should access these so the rendering in edit mode is consistent with the that in read mode.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+639683,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)",">>! In T51346#2174472, @Trizek-WMF wrote:
+>>>! In T51346#2173928, @Jdforrester-WMF wrote:
+>> This requires changes to Common.css (or some other site-level styling script) to change the rendering. However, I'd invite wikis to seriously consider whether they really want to vary from every other wiki's rendering.
+> 
+> On the reverse order, what prevents you to use the Common.css as it is? I mean, on a WYSIWYG system, you expect to have the same rendering both on reading and editing, which is what has been defined in the Common.css or in website settings.
+
+Because Cite doesn't yet use these styles in read mode (that's {T104927}, which is in fact blocked by doing this). :-)",task_subcomment,"[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBecause Cite doesn't yet use these styles in read mode (that's {T104927}, which is in fact blocked by doing this)."", ':-)']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+639673,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)",">>! In T51346#2173928, @Jdforrester-WMF wrote:
+> This requires changes to Common.css (or some other site-level styling script) to change the rendering. However, I'd invite wikis to seriously consider whether they really want to vary from every other wiki's rendering.
+
+On the reverse order, what prevents you to use the Common.css as it is? I mean, on a WYSIWYG system, you expect to have the same rendering both on reading and editing, which is what has been defined in the Common.css or in website settings.
+
+Thank you for the fix, by the way. ",task_subcomment,"['QUOTE\nQUOTE\n\nOn the reverse order, what prevents you to use the Common.css as it is?', 'I mean, on a WYSIWYG system, you expect to have the same rendering both on reading and editing, which is what has been defined in the Common.css or in website settings.', 'Thank you for the fix, by the way.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE']"
+639607,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)","The change for frwiki to make it look like their current local customisation is roughly: 
+``` lang=css
+/* French Wikipedia over-ride of styling for s */
+span.mw-ref a::after {
+  content: counter(mw-Ref,decimal);
+} 
+```",task_subcomment,['The change for frwiki to make it look like their current local customisation is roughly: \n``CODE``'],['INVESTIGATION AND EXPLORATION']
+639604,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)","This requires changes to Common.css (or some other site-level styling script) to change the rendering. However, I'd invite wikis to seriously consider whether they really want to vary from every other wiki's rendering.",task_subcomment,"['This requires changes to Common.css (or some other site-level styling script) to change the rendering.', ""However, I'd invite wikis to seriously consider whether they really want to vary from every other wiki's rendering.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+639597,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)","Got a feedback about it during a workshop: on fr.wp, footnotes are labelled as ""a, b, c""... in reading mode and ""3.0, 3.1, 3.2""... on edit mode. Plus, notes on the text don't have brackets on reading mode and have them on editing mode.",task_subcomment,"['Got a feedback about it during a workshop: on fr.wp, footnotes are labelled as ""a, b, c""... in reading mode and ""3.0, 3.1, 3.2""... on edit mode.', ""Plus, notes on the text don't have brackets on reading mode and have them on editing mode.""]","['MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+248012,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)",I74d4878 will let us fix this.,task_subcomment,['I74d4878 will let us fix this.'],['SOLUTION DISCUSSION']
+248005,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)","I think that this is the same problem:
+
+Footnotes created with the ref group  are displayed in the saved page as [a], [b], etc.  If you open them in VisualEditor, they display (while editing) as [lower-alpha 1], [lower-alpha 2], etc. instead of [a], [b], etc.",task_subcomment,"['I think that this is the same problem:\n\nFootnotes created with the ref group  are displayed in the saved page as [a], [b], etc.', 'If you open them in VisualEditor, they display (while editing) as [lower-alpha 1], [lower-alpha 2], etc.', 'instead of [a], [b], etc.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+247996,"Cite CSS should be adjusted by wikis to set a non-standard rendering style (e.g. 1.0, 1.1 / a,b,c, removing brackets, etc.)",*** Bug 51453 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51453 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51328,Create Wikipedia Tuvan,"The language committee and WMF Board have approved the creation of Wikipedia Tuvan.
+
+Language code: tyv
+Site URL: tyv.wikipedia.org
+Project name: Википедия
+Project namespace: Википедия
+Project talk namespace: Википедия дугайында сүмелел
+Project logo: http://commons.wikimedia.org/wiki/File:Wikipedia-logo-v2-tyv.png
+Timezone: Asia/Krasnoyarsk
+Language name: Тыва дыл
+Enable uploads: yes
+
+
+Thank you.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: //meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Tuvan",task_description,"['Create Wikipedia Tuvan\n\nThe language committee and WMF Board have approved the creation of Wikipedia Tuvan.', 'Language code: tyv\nSite URL: tyv.wikipedia.org\nProject name: Википедия\nProject namespace: Википедия\nProject talk namespace: Википедия дугайында сүмелел\nProject logo: URL\nTimezone: Asia/Krasnoyarsk\nLanguage name: Тыва дыл\nEnable uploads: yes\n\n\nThank you.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement\n**URL**: //meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Tuvan']","['FUTURE PLAN', 'SOLUTION USAGE', 'FUTURE PLAN']"
+247158,Create Wikipedia Tuvan,"(In reply to comment #28)
+> (In reply to comment #27)
+> > (In reply to comment #26)
+> > > RT ticket created for addition of lucene search indexes
+> > > https://rt.wikimedia.org/Ticket/Display.html?id=5588
+> > 
+> > But where's VisualEditor
+> 
+> Thank you very much for this reminder! I added it here (I think):
+> https://gerrit.wikimedia.org/r/#/c/79321/
+
+The VisualEditor can now be enabled in the preferences.",task_subcomment,['(In reply to comment #28)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe VisualEditor can now be enabled in the preferences.'],['SOLUTION DISCUSSION']
+247152,Create Wikipedia Tuvan,"Change 79321 merged by jenkins-bot:
+Add tyv.wikipedia to projects with visualeditor
+
+https://gerrit.wikimedia.org/r/79321",task_subcomment,['Change 79321 merged by jenkins-bot:\nAdd tyv.wikipedia to projects with visualeditor\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247145,Create Wikipedia Tuvan,"Change 79321 had a related patch set uploaded by Amire80:
+Add tyv.wikipedia to projects with visualeditor
+
+https://gerrit.wikimedia.org/r/79321",task_subcomment,['Change 79321 had a related patch set uploaded by Amire80:\nAdd tyv.wikipedia to projects with visualeditor\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247137,Create Wikipedia Tuvan,"(In reply to comment #27)
+> (In reply to comment #26)
+> > RT ticket created for addition of lucene search indexes
+> > https://rt.wikimedia.org/Ticket/Display.html?id=5588
+> 
+> But where's VisualEditor
+
+Thank you very much for this reminder! I added it here (I think):
+https://gerrit.wikimedia.org/r/#/c/79321/",task_subcomment,"['(In reply to comment #27)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThank you very much for this reminder!', 'I added it here (I think):\nURL']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+247128,Create Wikipedia Tuvan,"(In reply to comment #26)
+> RT ticket created for addition of lucene search indexes
+> https://rt.wikimedia.org/Ticket/Display.html?id=5588
+
+But where's VisualEditor",task_subcomment,"[""(In reply to comment #26)\nQUOTE\nQUOTE\n\nBut where's VisualEditor""]",['SOLUTION DISCUSSION']
+247120,Create Wikipedia Tuvan,RT ticket created for addition of lucene search indexes https://rt.wikimedia.org/Ticket/Display.html?id=5588,task_subcomment,['RT ticket created for addition of lucene search indexes URL'],['OBSERVED BUG BEHAVIOR']
+247115,Create Wikipedia Tuvan,Done!,task_subcomment,['Done!'],['SOLUTION DISCUSSION']
+247109,Create Wikipedia Tuvan,"Change 68188 merged by jenkins-bot:
+(bug 49328) Create Wikipedia in Tyvan language
+
+https://gerrit.wikimedia.org/r/68188",task_subcomment,['Change 68188 merged by jenkins-bot:\n(bug 49328) Create Wikipedia in Tyvan language\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+247103,Create Wikipedia Tuvan,*** Bug 52691 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52691 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+247097,Create Wikipedia Tuvan,"Change 78332 merged by jenkins-bot:
+Add tyv to langlist
+
+https://gerrit.wikimedia.org/r/78332",task_subcomment,['Change 78332 merged by jenkins-bot:\nAdd tyv to langlist\n\nGERRIT_URL'],['ACTION ON ISSUE']
+247091,Create Wikipedia Tuvan,"Change 78332 had a related patch set uploaded by Reedy:
+Add tyv to langlist
+
+https://gerrit.wikimedia.org/r/78332",task_subcomment,['Change 78332 had a related patch set uploaded by Reedy:\nAdd tyv to langlist\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+247084,Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #19)
+> It should not be chosen arbitrarily. It is chosen according to what was
+> requested on the Meta request, here
+> , by
+> Agilight even.
+> You do have discussions on the Incubator talk pages of some contributors like
+> Tamara Ustinova and Agilight but there is no discussion of everyone anywhere.
+> If you want the sitename to be different, please stop spamming this bug and
+> convince them to change the request on Meta. If you don't manage to do that,
+> shut up and stop delaying this request.
+
+""It should not be chosen arbitrarily."" - I agree!
+
+""It is chosen according to what was requested on the Meta request, here <...>, by Agilight even."" - not exactly. Agilight's comment is a completion of your comment in 06:42, 2 June 2013, in other words, he is personally helping you and showing his acquiescence about the name ""Википедия"", and that has nothing to do with ""Agilight chose the name Википедия"". If the local community had chosen the name ""Википедия"", I would NEVER disturb you here. 
+
+I had no discussion with Tamara Ustinova about the name (what I talk with her is about our *personal* opinion about indigenous peoples). I did discussed with Agilight, and as far as I know Agilight have no preference about the name ""Википедия"". Also there is discussion for everyone here  and everyone in the local community who joined the discussion likes to adopt a native name, although till now no one has completed a good name proposal (Agilight said in his talk page he'd like to ask some people to give an advice).
+
+If you deserve the sitename translation to be ""Википедия"", please stop advertise it here and convince some Tuvan speakers in the community to express their preference of ""Википедия"" to all other translation. If you don't manage to do that, shut up and stop promoting ""Википедия"" to this request.",task_subcomment,"['**polar_bear0901** wrote:\n\n(In reply to comment #19)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\n""It should not be chosen arbitrarily.""', '- I agree!', '""It is chosen according to what was requested on the Meta request, here <...>, by Agilight even.""', '- not exactly.', 'Agilight\'s comment is a completion of your comment in 06:42, 2 June 2013, in other words, he is personally helping you and showing his acquiescence about the name ""Википедия"", and that has nothing to do with ""Agilight chose the name Википедия"".', 'If the local community had chosen the name ""Википедия"", I would NEVER disturb you here.', 'I had no discussion with Tamara Ustinova about the name (what I talk with her is about our *personal* opinion about indigenous peoples).', 'I did discussed with Agilight, and as far as I know Agilight have no preference about the name ""Википедия"".', ""Also there is discussion for everyone here , by Agilight even.
+You do have discussions on the Incubator talk pages of some contributors like Tamara Ustinova and Agilight but there is no discussion of everyone anywhere. If you want the sitename to be different, please stop spamming this bug and convince them to change the request on Meta. If you don't manage to do that, shut up and stop delaying this request.",task_subcomment,"['It should not be chosen arbitrarily.', 'It is chosen according to what was requested on the Meta request, here  (In reply to comment #14)
+> > I have been looking at the discussion page for almost a year to see if 
+> > anyone in the local community have provided a localization of the name
+> > Wikipedia, but till now they're still working in progress. 
+> 
+> ""Work in progress"" and ""for almost a year"" sounds like a contradiction at
+> first, so I'd like to take a look myself.
+> 
+> > few will realize that it's still editable
+> 
+> People learn when they get things told. Every article on the wiki is
+> temporarily too by that definition, as it might be improved later on.
+
+Well, if the project namespace should be arbitrarily chosen since it's temporarily, why don't we choose it to be Видибилиином?",task_subcomment,"[""**polar_bear0901** wrote:\n\n(In reply to comment #15)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, if the project namespace should be arbitrarily chosen since it's temporarily, why don't we choose it to be Видибилиином?""]",['SOLUTION DISCUSSION']
+247065,Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #16)
+> Changing status to PATCH_TO_REVIEW because there actually is a patch on Gerrit
+Thank you for your progress!
+
+I'd like to mention that concerning the historical discussion, most user who have Tuvan language ability (such as Agilight and Sborsody) have shown a positive altitude about having a native Tuvan name for Tuvan Wikipedia, while those who considered a native name unnecessary or aspiration are mostly Europeans who can not speak Tuvan language (e.g. Kaganer and Tamara Ustinova; what have been labeled a ""community requesting"" were an request by Kaganer). 
+
+But I'm *not* critcise them, because they're *naturally* speaking in an European POV and that's totally fine. What I'm requesting is that the Tuvan name of Wikipedia should be decided by the native community, rather than by an edit commited by a editor who have few Tuvan knowledge. So there's *no* community-established name at all.
+
+That's also the reason why I say the ""Project namespace:"" should be temporarily ""Wikipedia"" rather than request it to be ""Видибилиином"".",task_subcomment,"['**polar_bear0901** wrote:\n\n(In reply to comment #16)\nQUOTE\nThank you for your progress!', ""I'd like to mention that concerning the historical discussion, most user who have Tuvan language ability (such as Agilight and Sborsody) have shown a positive altitude about having a native Tuvan name for Tuvan Wikipedia, while those who considered a native name unnecessary or aspiration are mostly Europeans who can not speak Tuvan language (e.g."", 'Kaganer and Tamara Ustinova; what have been labeled a ""community requesting"" were an request by Kaganer).', ""But I'm *not* critcise them, because they're *naturally* speaking in an European POV and that's totally fine."", ""What I'm requesting is that the Tuvan name of Wikipedia should be decided by the native community, rather than by an edit commited by a editor who have few Tuvan knowledge."", ""So there's *no* community-established name at all."", 'That\'s also the reason why I say the ""Project namespace:"" should be temporarily ""Wikipedia"" rather than request it to be ""Видибилиином"".']","['SOLUTION DISCUSSION', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'SOCIAL CONVERSATION', 'POTENTIAL NEW ISSUES AND REQUESTS', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247056,Create Wikipedia Tuvan,"Changing status to PATCH_TO_REVIEW because there actually is a patch on Gerrit waiting to be reviewed & merged: https://gerrit.wikimedia.org/r/68188
+
+Assigning this bug to Sam because he's the one who's been creating new wikis lately.",task_subcomment,"[""Changing status to PATCH_TO_REVIEW because there actually is a patch on Gerrit waiting to be reviewed & merged: GERRIT_URL\n\nAssigning this bug to Sam because he's the one who's been creating new wikis lately.""]",['ACTION ON ISSUE']
+247049,Create Wikipedia Tuvan,"(In reply to comment #14)
+> I have been looking at the discussion page for almost a year to see if 
+> anyone in the local community have provided a localization of the name
+> Wikipedia, but till now they're still working in progress. 
+
+""Work in progress"" and ""for almost a year"" sounds like a contradiction at first, so I'd like to take a look myself.
+
+> few will realize that it's still editable
+
+People learn when they get things told. Every article on the wiki is temporarily too by that definition, as it might be improved later on.",task_subcomment,"['(In reply to comment #14)\nQUOTE\nQUOTE\nQUOTE\n\n""Work in progress"" and ""for almost a year"" sounds like a contradiction at first, so I\'d like to take a look myself.', 'QUOTE\n\nPeople learn when they get things told.', 'Every article on the wiki is temporarily too by that definition, as it might be improved later on.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247044,Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #13)
+> (In reply to comment #6)
+> > (In reply to comment #4)
+> > Yes. The community is choosing a name for Tuvan Wikipedia
+> 
+> Can you please provide a direct link to a *recent* discussion about this
+> topic,
+> on the wiki?
+Could you please first tell me why you want a *recent* discussion? I have been looking at the discussion page for almost a year to see if anyone in the local community have provided a localization of the name Wikipedia, but till now they're still working in progress. 
+> 
+> > So the information should be **temporarily**
+> 
+> If it makes you happier to call things ""temporarily"", all things are
+> temporarily up to some point. :) (Configuration settings can always be
+> changed
+> later.)
+Well, what you said is *technically* true, but remember once you establish a namespace Википедия few will realize that it's still editable (just as Ali said many Tuvans are not very good at Internet). What's more, once the term Википедия (which violate Tuvan vowel harmony by the last syllable ""я"") comes into a real Wikipedia, it will be used by some Tuvans, which makes it harder for the locals to choose a localized name.",task_subcomment,"['**polar_bear0901** wrote:\n\n(In reply to comment #13)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nCould you please first tell me why you want a *recent* discussion?', ""I have been looking at the discussion page for almost a year to see if anyone in the local community have provided a localization of the name Wikipedia, but till now they're still working in progress."", ""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nWell, what you said is *technically* true, but remember once you establish a namespace Википедия few will realize that it's still editable (just as Ali said many Tuvans are not very good at Internet)."", 'What\'s more, once the term Википедия (which violate Tuvan vowel harmony by the last syllable ""я"") comes into a real Wikipedia, it will be used by some Tuvans, which makes it harder for the locals to choose a localized name.']","['ACTION ON ISSUE', 'FUTURE PLAN', 'MOTIVATION', 'MOTIVATION']"
+247039,Create Wikipedia Tuvan,"(In reply to comment #6)
+> (In reply to comment #4)
+> Yes. The community is choosing a name for Tuvan Wikipedia
+
+Can you please provide a direct link to a *recent* discussion about this topic, on the wiki?
+
+> So the information should be **temporarily**
+
+If it makes you happier to call things ""temporarily"", all things are temporarily up to some point. :) (Configuration settings can always be changed later.)",task_subcomment,"['(In reply to comment #6)\nQUOTE\nQUOTE\n\nCan you please provide a direct link to a *recent* discussion about this topic, on the wiki?', 'QUOTE\n\nIf it makes you happier to call things ""temporarily"", all things are temporarily up to some point.', ':) (Configuration settings can always be changed later.)']","['ACTION ON ISSUE', 'SOCIAL CONVERSATION', 'SOLUTION DISCUSSION']"
+247034,Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #11)
+> That's nonsense. There is apparently no ""trying to establish a native name"",
+> because the discussion from Dec. 2012 fell asleep.
+> However, the Википедия name is surely 'established' in a certain way because
+> the community(!) requested it to be set as their sitename and used it also on
+> the Incubator pages. The community can use any name it wants, regardless of
+> whether that is ""European"" or ""native"" or not.
+
+That's not. Someone (not the community!) edit the info page/summary page of testwiki when the discussion still didn't go to an end, but this has nothing to do with what you claimed ""community requested it"". 
+
+So temporarily keep the computer internal name ""Wikipedia"" is good to our community becouse by doing that the local community can establish a Tuvan name of Wikipedia anytime.",task_subcomment,"[""**polar_bear0901** wrote:\n\n(In reply to comment #11)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's not."", 'Someone (not the community!)', 'edit the info page/summary page of testwiki when the discussion still didn\'t go to an end, but this has nothing to do with what you claimed ""community requested it"".', 'So temporarily keep the computer internal name ""Wikipedia"" is good to our community becouse by doing that the local community can establish a Tuvan name of Wikipedia anytime.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247028,Create Wikipedia Tuvan,"That's nonsense. There is apparently no ""trying to establish a native name"", because the discussion from Dec. 2012 fell asleep.
+However, the Википедия name is surely 'established' in a certain way because the community(!) requested it to be set as their sitename and used it also on the Incubator pages. The community can use any name it wants, regardless of whether that is ""European"" or ""native"" or not.",task_subcomment,"[""That's nonsense."", 'There is apparently no ""trying to establish a native name"", because the discussion from Dec. 2012 fell asleep.', ""However, the Википедия name is surely 'established' in a certain way because the community(!)"", 'requested it to be set as their sitename and used it also on the Incubator pages.', 'The community can use any name it wants, regardless of whether that is ""European"" or ""native"" or not.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+247022,Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #9)
+> Well, apparently polar_bear0901 (whom I do not know) opposes the translation
+> of
+> ""Wikipedia"" chosen by the test-community.
+> 
+> In his comment he refers to this discussion about the name from Dec 2012,
+> started by an IP (him?):
+>  %D0%9A%D0%BE%D0%BB_%D0%B0%D1%80%D1%8B%D0%BD#Localization>.
+> There was no conclusion.
+> 
+> See however https://meta.wikimedia.org/w/index.php?diff=5528227&oldid=5527996
+> and https://meta.wikimedia.org/w/index.php?diff=5529039&oldid=5528970 for the
+> community requesting the project & ns 4 name Википедия, upon which I based
+> comment 0.
+> Cf. also this recent ""editwarring"" on the Main Page:
+>  %D0%9A%D0%BE%D0%BB_%D0%B0%D1%80%D1%8B%D0%BD&action=history>
+> 
+> Unless the community itself decides to change the 'established' sitename, I'd
+> request the wiki configuration to be carried out as described in comment 0.
+
+But where did you show us an ""established"" sitename? I.e. did the community establish any site name? I didn't see any ""community requesting"" because the discussion didn't draw a conclution and the local community are still trying to establish a native name, and we should help them choosing a native name rather than apply an European name for them.",task_subcomment,"['**polar_bear0901** wrote:\n\n(In reply to comment #9)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBut where did you show us an ""established"" sitename?', 'I.e.', 'did the community establish any site name?', 'I didn\'t see any ""community requesting"" because the discussion didn\'t draw a conclution and the local community are still trying to establish a native name, and we should help them choosing a native name rather than apply an European name for them.']","['ACTION ON ISSUE', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+247016,Create Wikipedia Tuvan,"Well, apparently polar_bear0901 (whom I do not know) opposes the translation of ""Wikipedia"" chosen by the test-community.
+
+In his comment he refers to this discussion about the name from Dec 2012, started by an IP (him?): . There was no conclusion.
+
+See however https://meta.wikimedia.org/w/index.php?diff=5528227&oldid=5527996 and https://meta.wikimedia.org/w/index.php?diff=5529039&oldid=5528970 for the community requesting the project & ns 4 name Википедия, upon which I based comment 0.
+Cf. also this recent ""editwarring"" on the Main Page: 
+
+Unless the community itself decides to change the 'established' sitename, I'd request the wiki configuration to be carried out as described in comment 0.",task_subcomment,"['Well, apparently polar_bear0901 (whom I do not know) opposes the translation of ""Wikipedia"" chosen by the test-community.', 'In his comment he refers to this discussion about the name from Dec 2012, started by an IP (him?', '):  Waiting for Reedy to do some on-server magic.
+
+TEMPORARILY import an English name is important in that people will realize that the name is temporarily chosen and they still have rights to decide their localized name.",task_subcomment,['**polar_bear0901** wrote:\n\n(In reply to comment #5)\nQUOTE\n\nTEMPORARILY import an English name is important in that people will realize that the name is temporarily chosen and they still have rights to decide their localized name.'],['INVESTIGATION AND EXPLORATION']
+246991,Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #4)
+> Any problems with this request?
+
+Yes. The community is choosing a name for Tuvan Wikipedia (and someone are afraid whether they're granted the right to have a localised name of Wikipedia - see the talk page of the Main Page). 
+
+So the information should be **temporarily**
+
+Project name: Wikipedia
+Project namespace: Wikipedia
+Project talk namespace: Wikipedia дугайында сүмелел
+Project logo: http://commons.wikimedia.org/wiki/File:Wikipedia-logo-v2-en.png
+
+(I don't want to use the English name even temporarily but at least this may not result in many locals feel they're obliged to borrow the Russian name.)",task_subcomment,"['**polar_bear0901** wrote:\n\n(In reply to comment #4)\nQUOTE\n\nYes.', ""The community is choosing a name for Tuvan Wikipedia (and someone are afraid whether they're granted the right to have a localised name of Wikipedia - see the talk page of the Main Page)."", ""So the information should be **temporarily**\n\nProject name: Wikipedia\nProject namespace: Wikipedia\nProject talk namespace: Wikipedia дугайында сүмелел\nProject logo: URL\n\n(I don't want to use the English name even temporarily but at least this may not result in many locals feel they're obliged to borrow the Russian name.)""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+246982,Create Wikipedia Tuvan,Waiting for Reedy to do some on-server magic.,task_subcomment,['Waiting for Reedy to do some on-server magic.'],['ACTION ON ISSUE']
+246974,Create Wikipedia Tuvan,Any problems with this request?,task_subcomment,['Any problems with this request?'],['SOLUTION DISCUSSION']
+246967,Create Wikipedia Tuvan,Related URL: https://gerrit.wikimedia.org/r/68188 (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422)'],['OBSERVED BUG BEHAVIOR']
+246962,Create Wikipedia Tuvan,Related URL: https://gerrit.wikimedia.org/r/68188 (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422)'],['OBSERVED BUG BEHAVIOR']
+246958,Create Wikipedia Tuvan,[I guess that's more of a site request than a language setup bug? Also changing priority.],task_subcomment,"[""[I guess that's more of a site request than a language setup bug?"", 'Also changing priority.]']","['POTENTIAL NEW ISSUES AND REQUESTS', 'INVESTIGATION AND EXPLORATION']"
+51310,VisualEditor: Sometimes ignores changing a wikilink with an underscore to one with a space,"**Author:** `the.anonymouse.wikimedia`
+
+**Description:**
+I created a wikilink [https://en.wikipedia.org/w/index.php?title=User:The_Anonymouse/sandbox2&diff=558776770&oldid=548109401] as [[United_States]]. I then tried to use VisualEditor to change the underscore to a space ([[United States]]), but it said that my edit was ignored due to no changes. However, if I actually click the link button and click the United States link suggestion, it works as expected. That is how I eventually accomplished the edit with VisualEditor [https://en.wikipedia.org/w/index.php?title=User:The_Anonymouse/sandbox2&diff=558777422&oldid=558776770].
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42140",task_description,"['VisualEditor: Sometimes ignores changing a wikilink with an underscore to one with a space\n\n**Author:** CODE\n\n**Description:**\nI created a wikilink [URL as [[United_States]].', 'I then tried to use VisualEditor to change the underscore to a space ([[United States]]), but it said that my edit was ignored due to no changes.', 'However, if I actually click the link button and click the United States link suggestion, it works as expected.', 'That is how I eventually accomplished the edit with VisualEditor [URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: trivial\n**See Also**:\nURL']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+245921,VisualEditor: Sometimes ignores changing a wikilink with an underscore to one with a space,This got fixed a long time ago; sorry for the slow triage on your report.,task_subcomment,['This got fixed a long time ago; sorry for the slow triage on your report.'],['ACTION ON ISSUE']
+245912,VisualEditor: Sometimes ignores changing a wikilink with an underscore to one with a space,"Is this a Parsoid issue?
+
+
    Main page
    
+
+serialises to
+
+[[Main_page]]
+
+whereas
+
+
    Main page
    
+
+serialises to
+
+[[Main page]]
+
+which is what we want",task_subcomment,"['Is this a Parsoid issue?', '
    Main page
    \n\nserialises to\n\n[[Main_page]]\n\nwhereas\n\n
    Main page
    \n\nserialises to\n\n[[Main page]]\n\nwhich is what we want']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+51308,VisualEditor: Images' selection blocks can overlap the toolbar and prevent saving/etc.,"exemple in video
+
+When I add a picture and it gets behind the toolbar,
+This prevents the toolbar from be clicked
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11568}",task_description,"[""VisualEditor: Images' selection blocks can overlap the toolbar and prevent saving/etc."", 'exemple in video\n\nWhen I add a picture and it gets behind the toolbar,\nThis prevents the toolbar from be clicked\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11568}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+245808,VisualEditor: Images' selection blocks can overlap the toolbar and prevent saving/etc.,The problem seems to be fixed in the current version. Thank you!,task_subcomment,"['The problem seems to be fixed in the current version.', 'Thank you!']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+245804,VisualEditor: Images' selection blocks can overlap the toolbar and prevent saving/etc.,"(In reply to comment #0)
+> Created attachment 12495 [details]
+> exemple in video
+> 
+> When I add a picture and it gets behind the toolbar,
+> This prevents the toolbar from be clicked
+
+Thank you for the video; this is hugely helpful and very clear what's going wrong! Assigning.
+
+**Attached**: {F11568}",task_subcomment,"[""(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThank you for the video; this is hugely helpful and very clear what's going wrong!"", 'Assigning.', '**Attached**: {F11568}']","['SOLUTION USAGE', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+51257,VisualEditor: Provide full grapheme cluster boundary detection,"Per Ed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Provide full grapheme cluster boundary detection\n\nPer Ed.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+242564,VisualEditor: Provide full grapheme cluster boundary detection,"This was fixed by gerrit 68864; there are some edge cases which we may want to address in future (""three Korean Jamo and then a combining accent would split wrong""), but closing this as done.",task_subcomment,"['This was fixed by gerrit 68864; there are some edge cases which we may want to address in future (""three Korean Jamo and then a combining accent would split wrong""), but closing this as done.']",['BUG REPRODUCTION']
+242559,VisualEditor: Provide full grapheme cluster boundary detection,Related change: https://gerrit.wikimedia.org/r/#/c/68864/,task_subcomment,['Related change: URL'],['SOLUTION DISCUSSION']
+51147,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","Arrow shown in top-right, under search bar
+
+The Up-Arrow icon, at the top-right of the ""Review your changes"" dialog (which cancels the review window) needs a tooltip. 
+
+I suggest: ""Cancel review, go back to current edit"" or similar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11244}",task_description,"['VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?', 'Arrow shown in top-right, under search bar\n\nThe Up-Arrow icon, at the top-right of the ""Review your changes"" dialog (which cancels the review window) needs a tooltip.', 'I suggest: ""Cancel review, go back to current edit"" or similar.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n\n**Attached**: {F11244}']","['INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+236617,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","Yes, this was fixed ages ago. Apologies for not noting and closing then – thanks for the reminder!",task_subcomment,"['Yes, this was fixed ages ago.', 'Apologies for not noting and closing then – thanks for the reminder!']","['BUG REPRODUCTION', 'ACTION ON ISSUE']"
+236611,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","All left-arrows (except for the link-dialog?) appear to have been replaced with ""X"", and all ""X""s (plus the link-dialog arrow) have tooltips. 
+
+I think this can be closed-as-fixed, but I will leave it up to the product team in case I missed something that they're tracking with this.",task_subcomment,"['All left-arrows (except for the link-dialog?)', 'appear to have been replaced with ""X"", and all ""X""s (plus the link-dialog arrow) have tooltips.', ""I think this can be closed-as-fixed, but I will leave it up to the product team in case I missed something that they're tracking with this.""]","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+236603,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","**santosh.cool.reddy** wrote:
+
+""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?
+
+Look at the attached image,looks like this bug has been already solved. Arrow is replaced by an 'X'.
+
+**Attached**: {F11247}",task_subcomment,"['**santosh.cool.reddy** wrote:\n\n""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?', 'Look at the attached image,looks like this bug has been already solved.', ""Arrow is replaced by an 'X'."", '**Attached**: {F11247}']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236596,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","santosh reddy: I have no idea what you meant by ""cleared"". This bug report is still open and there is no patch mentioned. In case you meant that the bug is fixed for you, please provide a clear link where you see it fixed. Thanks.",task_subcomment,"['santosh reddy: I have no idea what you meant by ""cleared"".', 'This bug report is still open and there is no patch mentioned.', 'In case you meant that the bug is fixed for you, please provide a clear link where you see it fixed.', 'Thanks.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION']"
+236592,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","**santosh.cool.reddy** wrote:
+
+I see that this bug has been cleared. Please check the bug and close this bug.",task_subcomment,"['**santosh.cool.reddy** wrote:\n\nI see that this bug has been cleared.', 'Please check the bug and close this bug.']","['ACTION ON ISSUE', 'ACTION ON ISSUE']"
+236588,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","Argh, yes, Kaldari got his comment in before mine. :-)",task_subcomment,"['Argh, yes, Kaldari got his comment in before mine.', ':-)']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+236583,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","Also needed in ""Save your changes"" dialog for up and left arrows.",task_subcomment,"['Also needed in ""Save your changes"" dialog for up and left arrows.']",['OBSERVED BUG BEHAVIOR']
+236578,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?",*** Bug 49983 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49983 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+236573,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","Someone else commented on this today, and suggested that an [X] might be a better icon than a < or ^.
+
+See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Link_pop-up for further discussion.",task_subcomment,"['Someone else commented on this today, and suggested that an [X] might be a better icon than a < or ^.', 'See URL for further discussion.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+236568,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?",Thanks for the catch!,task_subcomment,['Thanks for the catch!'],['ACTION ON ISSUE']
+236565,"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","There's an Identical problem with the ""Report a problem"" dialog, in two places. 
+
+1) The left-arrow at the left-hand-side needs a tooltip. ""Cancel report, go back to Review"" or similar.
+
+2) The up-arrow at the top-right needs a different tooltip. ""Cancel report, go back to current edit"" or similar.
+
+(I'm not sure if you'd prefer this in the same bug, or split into 2 bugs, or even 3 bugs. Please let me know.)",task_subcomment,"['There\'s an Identical problem with the ""Report a problem"" dialog, in two places.', '1) The left-arrow at the left-hand-side needs a tooltip.', '""Cancel report, go back to Review"" or similar.', '2) The up-arrow at the top-right needs a different tooltip.', '""Cancel report, go back to current edit"" or similar.', ""(I'm not sure if you'd prefer this in the same bug, or split into 2 bugs, or even 3 bugs."", 'Please let me know.)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+51097,Use figure and figcaption HTML5 elements when possible,"Since MediaWiki allows images that are clearly separated out, we should see if we can use `
    ` and `
    `.  These tags are intended for ""//some flow content, optionally with a caption, that is self-contained and is typically referenced as a single unit from the main flow of the document.//""
+
+This would particularly make sense for thumb and frame where a caption is already shown.  However, figure can also be used without figcaption, which should simplify implementation.
+
+The main concern is backwards-compatibility with browsers that don't know about these tags. They're new to HTML5 (which is now always on in MediaWiki), but
+
+1. Older IE will not be able to style these elements from CSS
+2. Older IE will not be able to select these elements from JavaScript.  This can be worked around by calling `createElement(tagName)` once for each of the relevant tag names.
+
+For issue number 2, I think jQuery's internal `createSafeFragment` already takes care of old IE.  So only the styling issue remains.
+
+--------------------------
+See also: {T25932}",task_description,"['Use figure and figcaption HTML5 elements when possible\n\nSince MediaWiki allows images that are clearly separated out, we should see if we can use CODE and CODE.', 'These tags are intended for ""//some flow content, optionally with a caption, that is self-contained and is typically referenced as a single unit from the main flow of the document.//""\n\nThis would particularly make sense for thumb and frame where a caption is already shown.', 'However, figure can also be used without figcaption, which should simplify implementation.', ""The main concern is backwards-compatibility with browsers that don't know about these tags."", ""They're new to HTML5 (which is now always on in MediaWiki), but\n\n1."", 'Older IE will not be able to style these elements from CSS\n2.', 'Older IE will not be able to select these elements from JavaScript.', 'This can be worked around by calling CODE once for each of the relevant tag names.', ""For issue number 2, I think jQuery's internal CODE already takes care of old IE."", 'So only the styling issue remains.', '--------------------------\nSee also: {T25932}']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'MOTIVATION']"
+1820549,Use figure and figcaption HTML5 elements when possible,"Change 726645 **abandoned** by Arlolra:
+%%%[mediawiki/core@master] [WIP] Always ship content.media.less when content-media feature is requested%%%
+Reason:
+%%%%%%
+https://gerrit.wikimedia.org/r/726645",task_subcomment,['Change 726645 **abandoned** by Arlolra:\n%%%[mediawiki/core@master] [WIP] Always ship content.media.less when content-media feature is requested%%%\nReason:\n%%%%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1801744,Use figure and figcaption HTML5 elements when possible,"Change 730735 **merged** by C. Scott Ananian:
+%%%[mediawiki/core@REL1_37] RELEASE-NOTES-1.37: Add note about $wgParserEnableLegacyMediaDOM%%%
+https://gerrit.wikimedia.org/r/730735",task_subcomment,['Change 730735 **merged** by C. Scott Ananian:\n%%%[mediawiki/core@REL1_37] RELEASE-NOTES-1.37: Add note about $wgParserEnableLegacyMediaDOM%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1801007,Use figure and figcaption HTML5 elements when possible,"Change 725160 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Add $wgParserEnableLegacyMediaDOM to REL1-37 release notes%%%
+https://gerrit.wikimedia.org/r/725160",task_subcomment,['Change 725160 **merged** by jenkins-bot:\n%%%[mediawiki/core@master] Add $wgParserEnableLegacyMediaDOM to REL1-37 release notes%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1801000,Use figure and figcaption HTML5 elements when possible,"Change 730735 had a related patch set uploaded (by C. Scott Ananian; author: Arlolra):
+%%%[mediawiki/core@REL1_37] Add $wgParserEnableLegacyMediaDOM to REL1-37 release notes%%%
+https://gerrit.wikimedia.org/r/730735",task_subcomment,['Change 730735 had a related patch set uploaded (by C. Scott Ananian; author: Arlolra):\n%%%[mediawiki/core@REL1_37] Add $wgParserEnableLegacyMediaDOM to REL1-37 release notes%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1799058,Use figure and figcaption HTML5 elements when possible,">>! In T51097#7406103, @Tacsipacsi wrote:
+>>>! In T51097#7402844, @Legoktm wrote:
+>> How bad will it look if those styles aren't there?
+> Hopefully not that bad, at least in average. Images on Commons file description pages are usually inline (often transcluded in table cells), which don’t require much CSS. If you want to make sure, the necessary styles can be copied to (or `@import`ed from) [[https://commons.wikimedia.org/wiki/MediaWiki:Filepage.css|MediaWiki:Filepage.css]], which should be loaded on third-party wikis as well.
+
+That was the same conclusion that Arlo and I came to. I suggested that we make sure to backport the correct styles for the 1.35/1.36/1.37 branches, but not wait for a release before flipping the switch on Commons. If it turns out to be much worse than expected, we can ask Reedy to put out a MW maintenance release outside the normal cycle for this change.",task_subcomment,"['QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat was the same conclusion that Arlo and I came to.', 'I suggested that we make sure to backport the correct styles for the 1.35/1.36/1.37 branches, but not wait for a release before flipping the switch on Commons.', 'If it turns out to be much worse than expected, we can ask Reedy to put out a MW maintenance release outside the normal cycle for this change.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1796023,Use figure and figcaption HTML5 elements when possible,">>! In T51097#7402571, @Arlolra wrote:
+> If you can think of any other situation where there is similar cross wiki inclusion, please let me know
+
+Probably #mediawiki-extensions-doublewiki as well (used on Wikisources and a few other wikis). The transcluded pages often depend on their own wiki’s sitewide CSS and are thus already broken, breaking them a bit more doesn’t worsen the situation a lot…
+
+>>! In T51097#7402844, @Legoktm wrote:
+> How bad will it look if those styles aren't there?
+Hopefully not that bad, at least in average. Images on Commons file description pages are usually inline (often transcluded in table cells), which don’t require much CSS. If you want to make sure, the necessary styles can be copied to (or `@import`ed from) [[https://commons.wikimedia.org/wiki/MediaWiki:Filepage.css|MediaWiki:Filepage.css]], which should be loaded on third-party wikis as well.",task_subcomment,"['QUOTE\nQUOTE\n\nProbably #mediawiki-extensions-doublewiki as well (used on Wikisources and a few other wikis).', 'The transcluded pages often depend on their own wiki’s sitewide CSS and are thus already broken, breaking them a bit more doesn’t worsen the situation a lot…\n\nQUOTE\nQUOTE\nHopefully not that bad, at least in average.', 'Images on Commons file description pages are usually inline (often transcluded in table cells), which don’t require much CSS.', 'If you want to make sure, the necessary styles can be copied to (or CODEed from) [[URL which should be loaded on third-party wikis as well.']","['INVESTIGATION AND EXPLORATION', 'MOTIVATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+1795579,Use figure and figcaption HTML5 elements when possible,"Change 726643 **merged** by jenkins-bot:
+%%%[operations/mediawiki-config@master] Enable legacy media dom on metawiki%%%
+https://gerrit.wikimedia.org/r/726643",task_subcomment,['Change 726643 **merged** by jenkins-bot:\n%%%[operations/mediawiki-config@master] Enable legacy media dom on metawiki%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1795567,Use figure and figcaption HTML5 elements when possible,"Change 726707 **merged** by jenkins-bot:
+%%%[mediawiki/core@wmf/1.38.0-wmf.2] Add a separate config for content.media.less%%%
+https://gerrit.wikimedia.org/r/726707",task_subcomment,['Change 726707 **merged** by jenkins-bot:\n%%%[mediawiki/core@wmf/1.38.0-wmf.2] Add a separate config for content.media.less%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1795565,Use figure and figcaption HTML5 elements when possible,"Change 726709 **merged** by jenkins-bot:
+%%%[mediawiki/core@wmf/1.38.0-wmf.3] Add a separate config for content.media.less%%%
+https://gerrit.wikimedia.org/r/726709",task_subcomment,['Change 726709 **merged** by jenkins-bot:\n%%%[mediawiki/core@wmf/1.38.0-wmf.3] Add a separate config for content.media.less%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1795521,Use figure and figcaption HTML5 elements when possible,"Change 726697 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Add a separate config for content.media.less%%%
+https://gerrit.wikimedia.org/r/726697",task_subcomment,['Change 726697 **merged** by jenkins-bot:\n%%%[mediawiki/core@master] Add a separate config for content.media.less%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1795515,Use figure and figcaption HTML5 elements when possible,"Change 726709 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@wmf/1.38.0-wmf.3] Add a separate config for content.media.less%%%
+https://gerrit.wikimedia.org/r/726709",task_subcomment,['Change 726709 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[mediawiki/core@wmf/1.38.0-wmf.3] Add a separate config for content.media.less%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1795513,Use figure and figcaption HTML5 elements when possible,"Change 726707 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@wmf/1.38.0-wmf.2] Add a separate config for content.media.less%%%
+https://gerrit.wikimedia.org/r/726707",task_subcomment,['Change 726707 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[mediawiki/core@wmf/1.38.0-wmf.2] Add a separate config for content.media.less%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1795474,Use figure and figcaption HTML5 elements when possible,"Change 726697 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@master] Add a separate config for content.media.less%%%
+https://gerrit.wikimedia.org/r/726697",task_subcomment,['Change 726697 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[mediawiki/core@master] Add a separate config for content.media.less%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1795194,Use figure and figcaption HTML5 elements when possible,"I generally agree with the direction of the patch, if we can load the styles regardless of what the config flag is, we should.
+
+However, the situation for Commons is more tricky, because it's arbitrary MediaWiki installations requesting those pages...ideally we'd backport the styles for 1.35/1.36 if they're not there already. How bad will it look if those styles aren't there?",task_subcomment,"['I generally agree with the direction of the patch, if we can load the styles regardless of what the config flag is, we should.', ""However, the situation for Commons is more tricky, because it's arbitrary MediaWiki installations requesting those pages...ideally we'd backport the styles for 1.35/1.36 if they're not there already."", ""How bad will it look if those styles aren't there?""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1795164,Use figure and figcaption HTML5 elements when possible,"Change 726645 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@master] [WIP] Always ship content.media.less when content-media feature is requested%%%
+https://gerrit.wikimedia.org/r/726645",task_subcomment,['Change 726645 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[mediawiki/core@master] [WIP] Always ship content.media.less when content-media feature is requested%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1795160,Use figure and figcaption HTML5 elements when possible,"Change 726643 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[operations/mediawiki-config@master] [WIP] Enable legacy media dom on metawiki%%%
+https://gerrit.wikimedia.org/r/726643",task_subcomment,['Change 726643 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[operations/mediawiki-config@master] [WIP] Enable legacy media dom on metawiki%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1795149,Use figure and figcaption HTML5 elements when possible,"> Without any countermeasures, I’m pretty sure the same will happen on file description pages if Commons switches before other wikis
+
+Thanks.  If you can think of any other situation where there is similar cross wiki inclusion, please let me know",task_subcomment,"['QUOTE\n\nThanks.', 'If you can think of any other situation where there is similar cross wiki inclusion, please let me know']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1795139,Use figure and figcaption HTML5 elements when possible,"> Without any countermeasures, I’m pretty sure the same will happen on file description pages if Commons switches before other wikis
+
+Thanks.  If you can think of any of situation where there is similar cross wiki inclusion, please let me know",task_subcomment,"['QUOTE\n\nThanks.', 'If you can think of any of situation where there is similar cross wiki inclusion, please let me know']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1794932,Use figure and figcaption HTML5 elements when possible,"Deployment to Meta broke global user pages appearing on wikis that still use the legacy `
    `-based output, see T292498. Without any countermeasures, I’m pretty sure the same will happen on file description pages if Commons switches before other wikis.",task_subcomment,"['Deployment to Meta broke global user pages appearing on wikis that still use the legacy CODE-based output, see T292498.', 'Without any countermeasures, I’m pretty sure the same will happen on file description pages if Commons switches before other wikis.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+1794929,Use figure and figcaption HTML5 elements when possible,"Deployment to Meta broke global user pages appearing on wikis that still use the legacy `
    `-based output, see T292498.
+",task_subcomment,"['Deployment to Meta broke global user pages appearing on wikis that still use the legacy CODE-based output, see T292498.']",['OBSERVED BUG BEHAVIOR']
+1793345,Use figure and figcaption HTML5 elements when possible,"Change 725160 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@master] Add $wgParserEnableLegacyMediaDOM to REL1-37 release notes%%%
+https://gerrit.wikimedia.org/r/725160",task_subcomment,['Change 725160 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[mediawiki/core@master] Add $wgParserEnableLegacyMediaDOM to REL1-37 release notes%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1793029,Use figure and figcaption HTML5 elements when possible,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://sal.toolforge.org/log/yJ_wN3wB1jz_IcWuFNcF} [2021-09-30T18:20:53Z]  Synchronized wmf-config/InitialiseSettings.php: Config: [[gerrit:724861|Disable legacy media dom on a few more wikis (T51097)]] (duration: 01m 08s)",task_subcomment,"['{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=URL [2021-09-30T18:20:53Z]  Synchronized wmf-config/InitialiseSettings.php: Config: [[gerrit:724861|Disable legacy media dom on a few more wikis (T51097)]] (duration: 01m 08s)']",['INVESTIGATION AND EXPLORATION']
+1793024,Use figure and figcaption HTML5 elements when possible,"Change 724861 **merged** by jenkins-bot:
+%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%
+https://gerrit.wikimedia.org/r/724861",task_subcomment,['Change 724861 **merged** by jenkins-bot:\n%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1792511,Use figure and figcaption HTML5 elements when possible,"Change 724861 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%
+https://gerrit.wikimedia.org/r/724861",task_subcomment,['Change 724861 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1790311,Use figure and figcaption HTML5 elements when possible,"Shouldn't these changes have rolled out by now ? If so, why is the thumbnail on MediaWiki.org still jumping around after load ? (Ah, because I use Timeless and there is {T287965} )",task_subcomment,"[""Shouldn't these changes have rolled out by now ?"", 'If so, why is the thumbnail on MediaWiki.org still jumping around after load ?', '(Ah, because I use Timeless and there is {T287965} )']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+1790305,Use figure and figcaption HTML5 elements when possible,"Shouldn't these changes have rolled out by now ? If so, why is the thumbnail on MediaWiki.org still jumping around after load ?",task_subcomment,"[""Shouldn't these changes have rolled out by now ?"", 'If so, why is the thumbnail on MediaWiki.org still jumping around after load ?']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR']"
+1780534,Use figure and figcaption HTML5 elements when possible,"Change 719179 **merged** by jenkins-bot:
+%%%[mediawiki/core@REL1_36] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%
+https://gerrit.wikimedia.org/r/719179",task_subcomment,['Change 719179 **merged** by jenkins-bot:\n%%%[mediawiki/core@REL1_36] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1780533,Use figure and figcaption HTML5 elements when possible,"Change 719180 **merged** by jenkins-bot:
+%%%[mediawiki/core@REL1_35] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%
+https://gerrit.wikimedia.org/r/719180",task_subcomment,['Change 719180 **merged** by jenkins-bot:\n%%%[mediawiki/core@REL1_35] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1780524,Use figure and figcaption HTML5 elements when possible,"Change 719180 had a related patch set uploaded (by Krinkle; author: Arlolra):
+%%%[mediawiki/core@REL1_35] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%
+https://gerrit.wikimedia.org/r/719180",task_subcomment,['Change 719180 had a related patch set uploaded (by Krinkle; author: Arlolra):\n%%%[mediawiki/core@REL1_35] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1780523,Use figure and figcaption HTML5 elements when possible,"Change 719179 had a related patch set uploaded (by Krinkle; author: Arlolra):
+%%%[mediawiki/core@REL1_36] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%
+https://gerrit.wikimedia.org/r/719179",task_subcomment,['Change 719179 had a related patch set uploaded (by Krinkle; author: Arlolra):\n%%%[mediawiki/core@REL1_36] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1778354,Use figure and figcaption HTML5 elements when possible,"Change 714841 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%
+https://gerrit.wikimedia.org/r/714841",task_subcomment,['Change 714841 **merged** by jenkins-bot:\n%%%[mediawiki/core@master] resourceloader: Call getStyleFiles from FileModule::getFileHashes%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1775126,Use figure and figcaption HTML5 elements when possible,(Replied via a [[ https://gerrit.wikimedia.org/r/c/mediawiki/core/+/714841/2#message-e2a11b3e6f36e5f4561323aa91f6854567905332 | comment on Gerrit ]]),task_subcomment,['(Replied via a [[ URL | comment on Gerrit ]])'],['BUG REPRODUCTION']
+1775124,Use figure and figcaption HTML5 elements when possible,(Left a [[ https://gerrit.wikimedia.org/r/c/mediawiki/core/+/714841/2#message-e2a11b3e6f36e5f4561323aa91f6854567905332 | comment on Gerrit ]]),task_subcomment,['(Left a [[ URL | comment on Gerrit ]])'],['BUG REPRODUCTION']
+1775123,Use figure and figcaption HTML5 elements when possible,"It seems that SkinModule is completely missing any tracking of the feature files for versioning the module build hash. Thus, it would seem that even with this patch, we still don't get cache updates when the list of toggled features is changed, or worse, when deploying a change to any of the LESS files.
+
+I suggest we fix this by adding the relevant feature files to the list of files hashed. Either via getFileHashes/getStyleFiles without duplication, or via getFileDependencies with a small amount of duplication. Then the presence/absence of files for whatever reason is naturally taken care of as they would'be loaded and thus the array is naturally different. This is how FileModule works for other files.
+
+The simplest approach is probably to make use of getStyleFiles in the parent class, so that the override here is naturally taken into account instead of having to keep logic in sync.",task_subcomment,"['It seems that SkinModule is completely missing any tracking of the feature files for versioning the module build hash.', ""Thus, it would seem that even with this patch, we still don't get cache updates when the list of toggled features is changed, or worse, when deploying a change to any of the LESS files."", 'I suggest we fix this by adding the relevant feature files to the list of files hashed.', 'Either via getFileHashes/getStyleFiles without duplication, or via getFileDependencies with a small amount of duplication.', ""Then the presence/absence of files for whatever reason is naturally taken care of as they would'be loaded and thus the array is naturally different."", 'This is how FileModule works for other files.', 'The simplest approach is probably to make use of getStyleFiles in the parent class, so that the override here is naturally taken into account instead of having to keep logic in sync.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+1773933,Use figure and figcaption HTML5 elements when possible,"Change 714841 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@master] Alter the skin definition summary based on wgParserEnableLegacyMediaDOM%%%
+https://gerrit.wikimedia.org/r/714841",task_subcomment,['Change 714841 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[mediawiki/core@master] Alter the skin definition summary based on wgParserEnableLegacyMediaDOM%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1773880,Use figure and figcaption HTML5 elements when possible,"OK, I think this is related to caching (yes, @Arlolra was right). Specifically, the styles for this are loaded in an override of ResourceLoaderSkinModule::getStyleFiles():
+
+```
+				if ( $feature === 'content-media' && !$this->getConfig()->get( 'ParserEnableLegacyMediaDOM' ) ) {
+					$featureFilePaths['screen'][] = new ResourceLoaderFilePath(
+						'resources/src/mediawiki.skinning/content.media.less',
+						$defaultLocalBasePath,
+						$defaultRemoteBasePath
+					);
+				}
+```
+
+However, this new file path is not seen by ResourceLoaderModule::getDefinitionSummary() because it checks $this->styles. When $wgParserEnableLegacyMediaDOM was flipped, there was no cache invalidation since according to RL, the module and all its files were the same. 
+
+Quick fix: Add value of $wgParserEnableLegacyMediaDOM to ResourceLoaderSkinModule::getDefinitionSummary()
+
+I only did a quick skim, but it wasn't clear to me how the other feature changes experienced cache invalidation. Maybe a more detailed audit is necessary.",task_subcomment,"['OK, I think this is related to caching (yes,SCREEN_NAME was right).', 'Specifically, the styles for this are loaded in an override of ResourceLoaderSkinModule::getStyleFiles():\n\n``CODE``\n\nHowever, this new file path is not seen by ResourceLoaderModule::getDefinitionSummary() because it checks $this->styles.', 'When $wgParserEnableLegacyMediaDOM was flipped, there was no cache invalidation since according to RL, the module and all its files were the same.', ""Quick fix: Add value of $wgParserEnableLegacyMediaDOM to ResourceLoaderSkinModule::getDefinitionSummary()\n\nI only did a quick skim, but it wasn't clear to me how the other feature changes experienced cache invalidation."", 'Maybe a more detailed audit is necessary.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+1773870,Use figure and figcaption HTML5 elements when possible,"Correcting my previous comment, VisualEditor will load the styles via JS if you have it enabled, so you actually need to turn that off, and then you'll find that the photo no longer jumps and stays on the (wrong) left side, even with JS enabled. So the real problem is that the skin is not loading these styles.",task_subcomment,"[""Correcting my previous comment, VisualEditor will load the styles via JS if you have it enabled, so you actually need to turn that off, and then you'll find that the photo no longer jumps and stays on the (wrong) left side, even with JS enabled."", 'So the real problem is that the skin is not loading these styles.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+1773869,Use figure and figcaption HTML5 elements when possible,"~~When I load https://www.mediawiki.org/wiki/MediaWiki with JS disabled the image says on the left, which confirms @thedj's theory that the correct CSS is being loaded by JS (addModules) rather than properly with addModuleStyles.~~ However, I couldn't reproduce this on https://test.wikipedia.org/wiki/Image?useskin=vector&useskinversion=1 - not sure what's different really.
+
+As to why it's happening...I have no idea. My guess is that this is another regression from the skin refactoring, {T287410} which recently touched stuff like https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/skins/Vector/+/a50b1db7931610a038197b74ba798fe307e9055e
+
+Also for some reason Timeless has the ""content-media"" feature set to false, so it's just fully broken there AFAICT.",task_subcomment,"[""~~When I load URL with JS disabled the image says on the left, which confirmsSCREEN_NAME's theory that the correct CSS is being loaded by JS (addModules) rather than properly with addModuleStyles.~~ However, I couldn't reproduce this on URL - not sure what's different really."", ""As to why it's happening...I have no idea."", 'My guess is that this is another regression from the skin refactoring, {T287410} which recently touched stuff like URL\n\nAlso for some reason Timeless has the ""content-media"" feature set to false, so it\'s just fully broken there AFAICT.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+1773865,Use figure and figcaption HTML5 elements when possible,"When I load https://www.mediawiki.org/wiki/MediaWiki with JS disabled the image says on the left, which confirms @thedj's theory that the correct CSS is being loaded by JS (addModules) rather than properly with addModuleStyles. However, I couldn't reproduce this on https://test.wikipedia.org/wiki/Image?useskin=vector&useskinversion=1 - not sure what's different really.
+
+As to why it's happening...I have no idea. My guess is that this is another regression from the skin refactoring, {T287410} which recently touched stuff like https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/skins/Vector/+/a50b1db7931610a038197b74ba798fe307e9055e
+
+Also for some reason Timeless has the ""content-media"" feature set to false, so it's just fully broken there AFAICT.",task_subcomment,"[""When I load URL with JS disabled the image says on the left, which confirmsSCREEN_NAME's theory that the correct CSS is being loaded by JS (addModules) rather than properly with addModuleStyles."", ""However, I couldn't reproduce this on URL - not sure what's different really."", ""As to why it's happening...I have no idea."", 'My guess is that this is another regression from the skin refactoring, {T287410} which recently touched stuff like URL\n\nAlso for some reason Timeless has the ""content-media"" feature set to false, so it\'s just fully broken there AFAICT.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION']"
+1773857,Use figure and figcaption HTML5 elements when possible,"I could be wildly off base about caching ... suffice it to say, I'm looking into it",task_subcomment,"[""I could be wildly off base about caching ... suffice it to say, I'm looking into it""]",['SOLUTION DISCUSSION']
+1773843,Use figure and figcaption HTML5 elements when possible,I also see all the VE JS being loaded (with debug=true).. that's not normal.... ,task_subcomment,"[""I also see all the VE JS being loaded (with debug=true).. that's not normal....""]",['OBSERVED BUG BEHAVIOR']
+1773836,Use figure and figcaption HTML5 elements when possible,"@TheDJ Thanks for reporting
+
+It looks like the issue is with the cached stylesheet
+
+https://www.mediawiki.org/w/load.php?lang=en&modules=ext.discussionTools.init.styles%7Cext.echo.styles.badge%7Cext.uls.pt%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cmediawiki.ui.button%2Cicon%7Coojs-ui.styles.icons-alerts%7Cskins.vector.icons%2Cstyles&only=styles&skin=vector
+
+If I add `?debug=true` to it, I get results for ""mw:Image""
+
+The jump is probably because until the cache is purged, the styles don't kick in until VE or whathaveyou's styles are fetched by JS.
+
+Let me see about busting the cache",task_subcomment,"['SCREEN_NAME Thanks for reporting\n\nIt looks like the issue is with the cached stylesheet\n\nURL\n\nIf I add CODE to it, I get results for ""mw:Image""\n\nThe jump is probably because until the cache is purged, the styles don\'t kick in until VE or whathaveyou\'s styles are fetched by JS.', 'Let me see about busting the cache']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+1773784,Use figure and figcaption HTML5 elements when possible,"ok... now thumbframes on mediawiki.org are loading late.. seems like the parsoid CSS module is not added with addModuleStyles() to ensure its loaded before the page rendering starts ?
+
+See the image on https://www.mediawiki.org/wiki/MediaWiki jump from center to right as the page loads.
+Similar on https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021",task_subcomment,"['ok... now thumbframes on mediawiki.org are loading late.. seems like the parsoid CSS module is not added with addModuleStyles() to ensure its loaded before the page rendering starts ?', 'See the image on URL jump from center to right as the page loads.', 'Similar on URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+1773711,Use figure and figcaption HTML5 elements when possible,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://sal.toolforge.org/log/jyKHfnsB8Fs0LHO5Ao6j} [2021-08-25T18:16:22Z]  Synchronized wmf-config/InitialiseSettings.php: e6df0803e4eaca91bd725bcd376b260b97917de3: Disable legacy media dom on a few more wikis (T51097) (duration: 01m 05s)",task_subcomment,"['{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=URL [2021-08-25T18:16:22Z]  Synchronized wmf-config/InitialiseSettings.php: e6df0803e4eaca91bd725bcd376b260b97917de3: Disable legacy media dom on a few more wikis (T51097) (duration: 01m 05s)']",['SOLUTION USAGE']
+1773707,Use figure and figcaption HTML5 elements when possible,"Change 714635 **merged** by jenkins-bot:
+%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%
+https://gerrit.wikimedia.org/r/714635",task_subcomment,['Change 714635 **merged** by jenkins-bot:\n%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1773059,Use figure and figcaption HTML5 elements when possible,"Change 714635 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%
+https://gerrit.wikimedia.org/r/714635",task_subcomment,['Change 714635 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[operations/mediawiki-config@master] Disable legacy media dom on a few more wikis%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1762171,Use figure and figcaption HTML5 elements when possible,"@TheDJ thanks for filing those issue.  I've created or updated tasks where they can be discussed individually.
+",task_subcomment,"['SCREEN_NAME thanks for filing those issue.', ""I've created or updated tasks where they can be discussed individually.""]","['ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+1762111,Use figure and figcaption HTML5 elements when possible,"And I see a CSS reflow for videos on test.wikipedia.org. This is specifically with the videojs player, which is active on test.wp.org, not sure about the old Kaltura player.
+https://test.wikipedia.org/wiki/User:TheDJ/sandbox",task_subcomment,"['And I see a CSS reflow for videos on test.wikipedia.org.', 'This is specifically with the videojs player, which is active on test.wp.org, not sure about the old Kaltura player.', 'URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+1762107,Use figure and figcaption HTML5 elements when possible,"Also the following features broken alignment:
+- https://test.wikipedia.org/wiki/Rusa_test_page_2?useskin=timeless
+- https://test.wikipedia.org/wiki/Rusa_test_page_2?useskin=modern
+
+As well and most importantly and I think a blocker: printing in Vector is not aligning correctly. ",task_subcomment,['Also the following features broken alignment:\n- URL\n- URL\n\nAs well and most importantly and I think a blocker: printing in Vector is not aligning correctly.'],['BUG REPRODUCTION']
+1762106,Use figure and figcaption HTML5 elements when possible,"Also the following features broken alignment:
+- https://test.wikipedia.org/wiki/Rusa_test_page_2?useskin=timeless
+- https://test.wikipedia.org/wiki/Rusa_test_page_2?useskin=modern
+
+As well and most importantly, printing in Vector is not aligning correctly. ",task_subcomment,"['Also the following features broken alignment:\n- URL\n- URL\n\nAs well and most importantly, printing in Vector is not aligning correctly.']",['OBSERVED BUG BEHAVIOR']
+1762102,Use figure and figcaption HTML5 elements when possible,"I've noticed an important different between the two formats and it relates to where the emitted class is located. Before this class was applied directly to the img object, but now it seems this is on the wrapping class. While this is probably a rare use case, it's an important change and I know at least some image headers on mediawiki.org etc which likely will have to be adapted to take this into account.
+```
+[[File:Onion diagram.svg|thumb|right|300px|In this example onion, we test image placement.|class=djtest]]
+```
+```
+
    In this example onion, we test image placement.
    
+```
+
+```
+
      
    In this example onion, we test image placement.
    
+```",task_subcomment,"[""I've noticed an important different between the two formats and it relates to where the emitted class is located."", 'Before this class was applied directly to the img object, but now it seems this is on the wrapping class.', ""While this is probably a rare use case, it's an important change and I know at least some image headers on mediawiki.org etc which likely will have to be adapted to take this into account."", '``CODE`CODE`CODE`CODE`CODE``']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+1746248,Use figure and figcaption HTML5 elements when possible,"With the train going out to [[ https://wikitech.wikimedia.org/wiki/Deployments/Train#Group_0 | group 0 ]] today, we can look at two wikis which should be configured differently based on T51097#7182465,
+
+I verified that this is indeed running on testwiki.  For example, after an `?action=purge` on https://test.wikipedia.org/wiki/Rusa_test_page_2 I see,
+
+```
+
    In this example onion, we test image placement.
    
+```
+
+However, on mediawikiwiki, after similarly purging we get on https://www.mediawiki.org/wiki/Parsoid
+
+```
+
      
    Artist's impression of the Parsoid HTML5 + RDFa wiki runtime
    
+```",task_subcomment,"['With the train going out to [[ URL | group 0 ]] today, we can look at two wikis which should be configured differently based on T51097#7182465,\n\nI verified that this is indeed running on testwiki.', 'For example, after an CODE on URL I see,\n\n``CODE`CODE`CODE``']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+1745581,Use figure and figcaption HTML5 elements when possible,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://sal.toolforge.org/log/MmnfVHoB1jz_IcWuBfm2} [2021-06-28T23:05:39Z]  Synchronized wmf-config/InitialiseSettings.php: 5ec855d14b31a9392274c2bfe2e21e2ad44986bc: Enable Parsoid inspired media structure on test wikis (T51097) (duration: 00m 59s)",task_subcomment,"['{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=URL [2021-06-28T23:05:39Z]  Synchronized wmf-config/InitialiseSettings.php: 5ec855d14b31a9392274c2bfe2e21e2ad44986bc: Enable Parsoid inspired media structure on test wikis (T51097) (duration: 00m 59s)']",['SOLUTION USAGE']
+1745579,Use figure and figcaption HTML5 elements when possible,"Change 701612 **merged** by jenkins-bot:
+%%%[operations/mediawiki-config@master] Enable Parsoid inspired media structure on test wikis%%%
+https://gerrit.wikimedia.org/r/701612",task_subcomment,['Change 701612 **merged** by jenkins-bot:\n%%%[operations/mediawiki-config@master] Enable Parsoid inspired media structure on test wikis%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1744676,Use figure and figcaption HTML5 elements when possible,"Change 701612 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[operations/mediawiki-config@master] Disable legacy media structure on test wikis%%%
+https://gerrit.wikimedia.org/r/701612",task_subcomment,['Change 701612 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[operations/mediawiki-config@master] Disable legacy media structure on test wikis%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1744273,Use figure and figcaption HTML5 elements when possible,"Change 507512 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Emit media structure as piloted in Parsoid%%%
+https://gerrit.wikimedia.org/r/507512",task_subcomment,['Change 507512 **merged** by jenkins-bot:\n%%%[mediawiki/core@master] Emit media structure as piloted in Parsoid%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1744157,Use figure and figcaption HTML5 elements when possible,"Change 701449 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Add 
     to the never suppressing group in BlockLevelPass%%%
+https://gerrit.wikimedia.org/r/701449",task_subcomment,['Change 701449 **merged** by jenkins-bot:\n%%%[mediawiki/core@master] Add 
     to the never suppressing group in BlockLevelPass%%%\nGERRIT_URL'],['ACTION ON ISSUE']
+1744139,Use figure and figcaption HTML5 elements when possible,"Change 701449 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@master] Add 
     to the never suppressing group in BlockLevelPass%%%
+https://gerrit.wikimedia.org/r/701449",task_subcomment,['Change 701449 had a related patch set uploaded (by Arlolra; author: Arlolra):\n%%%[mediawiki/core@master] Add 
     to the never suppressing group in BlockLevelPass%%%\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1696981,Use figure and figcaption HTML5 elements when possible,https://gerrit.wikimedia.org/r/c/507512 is the only open patch remaining.,task_subcomment,['URL is the only open patch remaining.'],['SOLUTION DISCUSSION']
+1645454,Use figure and figcaption HTML5 elements when possible,"Change 647318 **abandoned** by Arlolra:
+[mediawiki/core@master] Update tests for $wgParserOutputLegacyMediaDOM
+
+Reason:
+These are now in I978187f9f6e9e0a105521ab3e26821e36a96b911
+
+https://gerrit.wikimedia.org/r/647318",task_subcomment,['Change 647318 **abandoned** by Arlolra:\n[mediawiki/core@master] Update tests for $wgParserOutputLegacyMediaDOM\n\nReason:\nThese are now in I978187f9f6e9e0a105521ab3e26821e36a96b911\n\nGERRIT_URL'],['ACTION ON ISSUE']
+1635100,Use figure and figcaption HTML5 elements when possible,"Change 647318 had a related patch set uploaded (by Arlolra; owner: Arlolra):
+[mediawiki/core@master] Update tests for $wgUseNewMediaStructure
+
+https://gerrit.wikimedia.org/r/647318",task_subcomment,['Change 647318 had a related patch set uploaded (by Arlolra; owner: Arlolra):\n[mediawiki/core@master] Update tests for $wgUseNewMediaStructure\n\nGERRIT_URL'],['BUG REPRODUCTION']
+1633208,Use figure and figcaption HTML5 elements when possible,"> But @Arlolra seems to have found the exception to that rule which we've all forgotten; I await with bated breath.
+
+My confusion was that `mw:Image(/Frameless)` aren't always inline, for example if they have explicit options like `|right`.  In which case, we'd emit a figure but hide the caption to match the output from the legacy parser.",task_subcomment,"[""QUOTE\n\nMy confusion was that CODE aren't always inline, for example if they have explicit options like CODE."", ""In which case, we'd emit a figure but hide the caption to match the output from the legacy parser.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+1633202,Use figure and figcaption HTML5 elements when possible,"From an accessibility standpoint, there may be reasons to emit a descriptive `
    ` even if it is not visible to a sighted user.
+
+That said, my understanding was that we couldn't actually do that because the figcaption could contain (eg) `
    ` tags that would break rendering in an inline context (where captions are normally hidden) and so we don't/can't actually emit the figcaption unless it is visible.  But @Arlolra seems to have found the exception to that rule which we've all forgotten; I await with bated breath.
+
+And (at the risk of continuing @ssastry's drift off-topic), in addition to fragmentation issues, improving the functionality of client-side gadgets is one reason to avoid unnecessary read-view transformations. (Ultimately, fast editing is also benefited if VE can operate with the rendered content instead of having to reload content at editor startup.  The idea is that VE only needs to load the (fairly small) data-mw associated w/ the region being edited at startup.)",task_subcomment,"['From an accessibility standpoint, there may be reasons to emit a descriptive CODE even if it is not visible to a sighted user.', ""That said, my understanding was that we couldn't actually do that because the figcaption could contain (eg) CODE tags that would break rendering in an inline context (where captions are normally hidden) and so we don't/can't actually emit the figcaption unless it is visible."", ""ButSCREEN_NAME seems to have found the exception to that rule which we've all forgotten; I await with bated breath."", ""And (at the risk of continuingSCREEN_NAME's drift off-topic), in addition to fragmentation issues, improving the functionality of client-side gadgets is one reason to avoid unnecessary read-view transformations."", '(Ultimately, fast editing is also benefited if VE can operate with the rendered content instead of having to reload content at editor startup.', 'The idea is that VE only needs to load the (fairly small) data-mw associated w/ the region being edited at startup.)']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1633196,Use figure and figcaption HTML5 elements when possible,"From an accessibility standpoint, there may be reasons to emit a descriptive `
    ` even if it is not visible to a sighted user.
+
+That said, my understanding was that we couldn't actually do that because the figcaption could contain (eg) `
    ` tags that would break rendering in an inline context (where captions are normally hidden) and so we don't/can't actually emit the figcaption unless it is visible.  But @Arlolra seems to have found the exception to that rule which we've all forgotten; I await with bated breath.",task_subcomment,"['From an accessibility standpoint, there may be reasons to emit a descriptive CODE even if it is not visible to a sighted user.', ""That said, my understanding was that we couldn't actually do that because the figcaption could contain (eg) CODE tags that would break rendering in an inline context (where captions are normally hidden) and so we don't/can't actually emit the figcaption unless it is visible."", ""ButSCREEN_NAME seems to have found the exception to that rule which we've all forgotten; I await with bated breath.""]","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+1633179,Use figure and figcaption HTML5 elements when possible,">>! In T51097#6690931, @Arlolra wrote:
+> I said this because I think the place where the stylesheet is saying to hide the figcaption is misleading.  Those are inline images where it isn't even emitted and the content is placed in the data-mw.
+
+Whoops, that's not true at all
+
+>>! In T51097#6690934, @ssastry wrote:
+> Are you saying I wasted my time there? :-) I should have stuck to my netflix movie instead of trying to check mail late in the evening.
+
+Only in so much as you wouldn't have goaded me into making blankly false statements",task_subcomment,"[""QUOTE\nQUOTE\n\nWhoops, that's not true at all\n\nQUOTE\nQUOTE\n\nOnly in so much as you wouldn't have goaded me into making blankly false statements""]",['MOTIVATION']
+1632855,Use figure and figcaption HTML5 elements when possible,">>! In T51097#6690931, @Arlolra wrote:
+> ... but just cautioning about using specific examples.
+
+Are you saying I wasted my time there? :-) I should have stuck to my netflix movie instead of trying to check mail late in the evening.",task_subcomment,"['QUOTE\nQUOTE\n\nAre you saying I wasted my time there?', ':-) I should have stuck to my netflix movie instead of trying to check mail late in the evening.']","['SOCIAL CONVERSATION', 'SOCIAL CONVERSATION']"
+1632853,Use figure and figcaption HTML5 elements when possible,"> I think we should file individual tasks for these things so they can be researched more thoroughly.
+
+I said this because I think the place where the stylesheet is saying to hide the figcaption is misleading.  Those are inline images where it isn't even emitted and the content is placed in the data-mw.  I'll submit a patch to delete it but just cautioning about using specific examples.",task_subcomment,"['QUOTE\n\nI said this because I think the place where the stylesheet is saying to hide the figcaption is misleading.', ""Those are inline images where it isn't even emitted and the content is placed in the data-mw."", ""I'll submit a patch to delete it but just cautioning about using specific examples.""]","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+1632841,Use figure and figcaption HTML5 elements when possible,">>! In T51097#6690317, @Krinkle wrote:
+>  I assumed that as part of moving toward Parsoid used natively, would be to (start) thinking about what a page-view worthy variant would look like in terms of lighter and more performant HTML/CSS. 
+
+I am going write a slightly broader (but tangential to this specific task) response here that we should pick up separately.
+
+Parsoid has very many clients: API consumers, editing clients, reading clients (mobile, desktop, apps), etc. Every client has slight different needs. Then, there are user-preferences. There is HTML regeneration on changes to things like red links. [ And, more broadly incremental parsing as a HTML -> HTML transformation on top of the previous version, but that is a different ball of wax we'll get to some day ] And, there is HTML adaptation for language variants, and so on.
+
+It is useful to look at all these requirements as broadly HTML -> HTML transformations of some canonical representation that Parsoid generates. Over time, HTML -> HTML transformations have been developed. over whatever Parsoid generates.: MCS / PCS / Kiwix, etc.  Mobile HTML will also adapt its HTML -> HTML layer for this as well (T269499).  And sometimes those transformations get upstreamed into Parsoid (ex: section wrapping). Separately, a related qn. we've been pondering is how all these various HTML -> HTML transformations should be developed / handled? Should they be API extensions of Parsoid? Should they live in Parsoid? Should they be separate (micro)services? Which of those services' output should be cached / stored, etc.?
+
+But, what your comment there gets at is this core question of** (a) what this canonical representation ought to be and (b) what client this ought to be tuned for.**
+
+Originally, this HTML was tuned for VisualEditor (for historical reasons). And, over time, we've started to move towards read views (hence T78676). So, from this POV, figcaptions will sometimes need to be hidden because in an editing client, the nature of the image might change and so a figcaption might go from being rendered to being hidden and vice versa. That observation basically generalizes to the principle that Parsoid's canonical output should expose all information there was in source (both syntactic and semantic). That is the core value of Parsoid's output and also what enables us to roundtrip wikitext without dirty diffs and lets us use the tagline: ""We deal with wikitext so you don't have to"".
+
+That said, this can lead to a lot of bloat. So, syntactic information is mostly hidden in data-parsoid and has been stripped from source from almost the very beginning. But, semantic information exists in data-mw and in other attributes that are dispersed in the DOM. For data-mw attribute, we have T78676.
+
+Given this baseline, the question is: do we need a HTML -> HTML layer for read views on top of Parsoid's canonical HTML output? We probably all have opinions. :-) On one extreme, we could strip all semantic information and all kinds of other attributes and information to reduce the network payload. But, we think that there is value in exposing some of the semantic information in Parsoid's output by default since we aren't convinced it bloats HTML payload significantly. I say that with the observation that the core parser's HTML output is somewhat of a historical (vs intentional) baseline (much like Parsoid's targeting of its HTML for VisualEditor is a similarly historical decision and not something that makes sense once we start targeting read views).
+
+But, anyway, as we talked back in July in our meeting and [[https://www.mediawiki.org/wiki/Parsing/Parser_Unification/Performance#HTML_output_size|captured in the notes]], we should collaborate and start evaluating Parsoid's HTML payload (after compression) and see what kind of change we are seeing and establish what kind of increase is acceptable. Before we do that, I feel trying to optimize media output to drop figcaptions, etc. is probably premature. I am not convinced the byte savings we gain from doing that on a typical page is worth the additional complexity of a HTML -> HTML transformation. Of course, we should still talk through what kind of fine-tuning we need for Parsoid's canonical output so that it is as close to being ready for read views without needing a HTML -> HTML transformation. But, we should do some baseline performance studies first before we dive into that kind of work.
+
+I know you are talking about performance more broadly including rendering time, etc, not just byte overhead and I defer to you, @Jdlrobson, @arlolra. But, thanks for starting this conversation going. It has helped me put down these notes coherently - something that has been bubbling up lately in bits and pieces in different conversations. Let us take this broader conversation to a separate ticket / meeting / gdoc.",task_subcomment,"['QUOTE\nQUOTE\n\nI am going write a slightly broader (but tangential to this specific task) response here that we should pick up separately.', 'Parsoid has very many clients: API consumers, editing clients, reading clients (mobile, desktop, apps), etc.', 'Every client has slight different needs.', 'Then, there are user-preferences.', 'There is HTML regeneration on changes to things like red links.', ""[ And, more broadly incremental parsing as a HTML -> HTML transformation on top of the previous version, but that is a different ball of wax we'll get to some day ] And, there is HTML adaptation for language variants, and so on."", 'It is useful to look at all these requirements as broadly HTML -> HTML transformations of some canonical representation that Parsoid generates.', 'Over time, HTML -> HTML transformations have been developed.', 'over whatever Parsoid generates.', ': MCS / PCS / Kiwix, etc.', 'Mobile HTML will also adapt its HTML -> HTML layer for this as well (T269499).', 'And sometimes those transformations get upstreamed into Parsoid (ex: section wrapping).', 'Separately, a related qn.', ""we've been pondering is how all these various HTML -> HTML transformations should be developed / handled?"", 'Should they be API extensions of Parsoid?', 'Should they live in Parsoid?', 'Should they be separate (micro)services?', ""Which of those services' output should be cached / stored, etc.?"", 'But, what your comment there gets at is this core question of** (a) what this canonical representation ought to be and (b) what client this ought to be tuned for.', '**\n\nOriginally, this HTML was tuned for VisualEditor (for historical reasons).', ""And, over time, we've started to move towards read views (hence T78676)."", 'So, from this POV, figcaptions will sometimes need to be hidden because in an editing client, the nature of the image might change and so a figcaption might go from being rendered to being hidden and vice versa.', ""That observation basically generalizes to the principle that Parsoid's canonical output should expose all information there was in source (both syntactic and semantic)."", 'That is the core value of Parsoid\'s output and also what enables us to roundtrip wikitext without dirty diffs and lets us use the tagline: ""We deal with wikitext so you don\'t have to"".', 'That said, this can lead to a lot of bloat.', 'So, syntactic information is mostly hidden in data-parsoid and has been stripped from source from almost the very beginning.', 'But, semantic information exists in data-mw and in other attributes that are dispersed in the DOM.', 'For data-mw attribute, we have T78676.', ""Given this baseline, the question is: do we need a HTML -> HTML layer for read views on top of Parsoid's canonical HTML output?"", 'We probably all have opinions.', ':-) On one extreme, we could strip all semantic information and all kinds of other attributes and information to reduce the network payload.', ""But, we think that there is value in exposing some of the semantic information in Parsoid's output by default since we aren't convinced it bloats HTML payload significantly."", ""I say that with the observation that the core parser's HTML output is somewhat of a historical (vs intentional) baseline (much like Parsoid's targeting of its HTML for VisualEditor is a similarly historical decision and not something that makes sense once we start targeting read views)."", ""But, anyway, as we talked back in July in our meeting and [[URL in the notes]], we should collaborate and start evaluating Parsoid's HTML payload (after compression) and see what kind of change we are seeing and establish what kind of increase is acceptable."", 'Before we do that, I feel trying to optimize media output to drop figcaptions, etc.', 'is probably premature.', 'I am not convinced the byte savings we gain from doing that on a typical page is worth the additional complexity of a HTML -> HTML transformation.', ""Of course, we should still talk through what kind of fine-tuning we need for Parsoid's canonical output so that it is as close to being ready for read views without needing a HTML -> HTML transformation."", 'But, we should do some baseline performance studies first before we dive into that kind of work.', 'I know you are talking about performance more broadly including rendering time, etc, not just byte overhead and I defer to you,SCREEN_NAME,SCREEN_NAME.', 'But, thanks for starting this conversation going.', 'It has helped me put down these notes coherently - something that has been bubbling up lately in bits and pieces in different conversations.', 'Let us take this broader conversation to a separate ticket / meeting / gdoc.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'ACTION ON ISSUE']"
+1632812,Use figure and figcaption HTML5 elements when possible,">>! In T51097#6690317, @Krinkle wrote:
+> @Arlolra @Jdlrobson The new selectors introduced here seem quite bad in terms of performance and stability. They seem very fragile, and I don't think we should use those on production page views.
+> 
+> Code in question at [mediawiki.skinning/content.media.less](https://gerrit.wikimedia.org/r/c/mediawiki/core/+/410362/19/resources/src/mediawiki.skinning/content.media.less).
+
+As Jon said, these are not new in the sense that they are factored out of `mediawiki.skinning.content.parsoid` so that they can be reused when the legacy parser starts emitting media structured as Parsoid would.
+
+See https://gerrit.wikimedia.org/r/c/mediawiki/core/+/507512 that implements that behind a flag, `$wgUseNewMediaStructure`
+
+See https://www.mediawiki.org/wiki/Specs/HTML/2.1.0#Media to get a sense of what the HTML looks like
+
+As explained on https://www.mediawiki.org/wiki/Parsing/Media_structure, we're trying to make these changes to the legacy parser before Parsoid starts being used for read views so that the changes there are staggered and less disruptive.
+
+> Also what are these styles based on?
+
+They're based on the definitions in `mediawiki.skinning.content` for thumbnails.  I guess the idea has been to come up with set of styles to apply to Parsoid's HTML so that it renders identically to what the legacy parser is giving us for read views.  Parsoid's current styles are the result of extensive visual diffing.
+
+See https://www.mediawiki.org/wiki/Parsing/Visual_Diff_Testing
+
+However, they evolved organically to meet the stated rendering goal and were likely blind to CSS performance and stability.
+
+> Is the plan to drop these styles in favour of the styles we have but with these new selectors as their target instead of the current ones?
+
+I would think the inverse, but see the caveats at https://gerrit.wikimedia.org/r/c/mediawiki/core/+/647333/12#message-6fed1f6653aadf34efbe76c0ae42117f7d41490d
+
+> I assumed that as part of moving toward Parsoid used natively, would be to (start) thinking about what a page-view worthy variant would look like in terms of lighter and more performant HTML/CSS.
+
+Looking at T258836, there's definitely been some consideration of the size of the HTML that we're shipping but I can't recall specific tasks about browser rendering time after the content is delivered.
+
+> I think part of that (might) have to be to encode these internal assumptions about structure so that only a simple and stable selector needs to be exposed to skins.
+
+I'm not sure exactly what you mean.  Parsoid's HTML is specified at the above link.
+
+> I also worry about some of the stylehacks in here perhaps exposing potential issues with the HTML itself. It is not clear to me why some of these workarounds are needed when the current HTML does not appear to need them. Such as hiding of `figcaption` elements (why are they in the HTML?), and the mapping of `mw-valign-middle` and similar classes (why does this exist?), and numerous reliance on wildcards like `*:first-child `. This seems very surprising and is imho a blocker to address before starting to rely on this from individual skins or page views.
+
+I think we should file individual tasks for these things so they can be researched more thoroughly.  I'm happy to work towards improving `content.media.less` and agree that both performance and stability should be addressed before it's used on production page views.
+
+Note that I may be making this worse with the patches for T269704",task_subcomment,"['QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAs Jon said, these are not new in the sense that they are factored out of CODE so that they can be reused when the legacy parser starts emitting media structured as Parsoid would.', ""See URL that implements that behind a flag, CODE\n\nSee URL to get a sense of what the HTML looks like\n\nAs explained on URL we're trying to make these changes to the legacy parser before Parsoid starts being used for read views so that the changes there are staggered and less disruptive."", ""QUOTE\n\nThey're based on the definitions in CODE for thumbnails."", ""I guess the idea has been to come up with set of styles to apply to Parsoid's HTML so that it renders identically to what the legacy parser is giving us for read views."", ""Parsoid's current styles are the result of extensive visual diffing."", 'See URL\n\nHowever, they evolved organically to meet the stated rendering goal and were likely blind to CSS performance and stability.', ""QUOTE\n\nI would think the inverse, but see the caveats at URL\n\nQUOTE\n\nLooking at T258836, there's definitely been some consideration of the size of the HTML that we're shipping but I can't recall specific tasks about browser rendering time after the content is delivered."", ""QUOTE\n\nI'm not sure exactly what you mean."", ""Parsoid's HTML is specified at the above link."", 'QUOTE\n\nI think we should file individual tasks for these things so they can be researched more thoroughly.', ""I'm happy to work towards improving CODE and agree that both performance and stability should be addressed before it's used on production page views."", 'Note that I may be making this worse with the patches for T269704']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+1632715,Use figure and figcaption HTML5 elements when possible,"The rules are currently disabled for all skins. For now, this is only refactoring and working towards deprecating the existing `mediawiki.skinning.content.parsoid` ResourceLoader module (please note these rules have been factored out of  the existing `mediawiki.skinning.content.parsoid` module https://gerrit.wikimedia.org/r/c/mediawiki/core/+/410362/19/resources/src/mediawiki.skinning/content.parsoid.less )
+
+
+My expectation is we are going to clean them up and consolidate the new `media` feature styles with `content` prior to deployment.
+",task_subcomment,"['The rules are currently disabled for all skins.', 'For now, this is only refactoring and working towards deprecating the existing CODE ResourceLoader module (please note these rules have been factored out of  the existing CODE module URL )\n\n\nMy expectation is we are going to clean them up and consolidate the new CODE feature styles with CODE prior to deployment.']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+1632709,Use figure and figcaption HTML5 elements when possible,"The rules are currently disabled for all skins. For now, this is only refactoring and working towards deprecating the existing `mediawiki.skinning.content.parsoid` ResourceLoader module
+
+My expectation is we are going to clean them up and consolidate the new `media` feature styles with `content` prior to deployment.
+",task_subcomment,"['The rules are currently disabled for all skins.', 'For now, this is only refactoring and working towards deprecating the existing CODE ResourceLoader module\n\nMy expectation is we are going to clean them up and consolidate the new CODE feature styles with CODE prior to deployment.']","['OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+1632706,Use figure and figcaption HTML5 elements when possible,"The rules are currently disabled for all skins. For now, this is only refactoring and working towards deprecating the existing mediawiki.skinning.content.parsoid.
+
+My expectation is we are going to clean them up and consolidate the new `media` feature styles with `content` prior to deployment.
+",task_subcomment,"['The rules are currently disabled for all skins.', 'For now, this is only refactoring and working towards deprecating the existing mediawiki.skinning.content.parsoid.', 'My expectation is we are going to clean them up and consolidate the new CODE feature styles with CODE prior to deployment.']","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'FUTURE PLAN']"
+1632689,Use figure and figcaption HTML5 elements when possible,"@Arlolra @Jdlrobson The new selectors introduced here seem quite bad in terms of performance and stability. They seem very fragile, and I don't think we should use those on production page views.
+
+Code in question at [mediawiki.skinning/content.media.less](https://gerrit.wikimedia.org/r/c/mediawiki/core/+/410362/19/resources/src/mediawiki.skinning/content.media.less).
+
+Also what are these styles based on? Is the plan to drop these styles in favour of the styles we have but with these new selectors as their target instead of the current ones? I assumed that as part of moving toward Parsoid used natively, would be to (start) thinking about what a page-view worthy variant would look like in terms of lighter and more performant HTML/CSS. I think part of that (might) have to be to encode these internal assumptions about structure so that only a simple and stable selector needs to be exposed to skins. I also worry about some of the stylehacks in here perhaps exposing potential issues with the HTML itself. It is not clear to me why some of these workarounds are needed when the current HTML does not appear to need them. Such as hiding of `figcaption` elements (why are they in the HTML?), and the mapping of `mw-valign-middle` and similar classes (why does this exist?), and numerous reliance on wildcards like `*:first-child `. This seems very surprising and is imho a blocker to address before starting to rely on this from individual skins or page views.",task_subcomment,"['SCREEN_NAMESCREEN_NAME The new selectors introduced here seem quite bad in terms of performance and stability.', ""They seem very fragile, and I don't think we should use those on production page views."", 'Code in question at [mediawiki.skinning/content.media.less](URL\n\nAlso what are these styles based on?', 'Is the plan to drop these styles in favour of the styles we have but with these new selectors as their target instead of the current ones?', 'I assumed that as part of moving toward Parsoid used natively, would be to (start) thinking about what a page-view worthy variant would look like in terms of lighter and more performant HTML/CSS.', 'I think part of that (might) have to be to encode these internal assumptions about structure so that only a simple and stable selector needs to be exposed to skins.', 'I also worry about some of the stylehacks in here perhaps exposing potential issues with the HTML itself.', 'It is not clear to me why some of these workarounds are needed when the current HTML does not appear to need them.', 'Such as hiding of CODE elements (why are they in the HTML?', '), and the mapping of CODE and similar classes (why does this exist?', '), and numerous reliance on wildcards like CODE.', 'This seems very surprising and is imho a blocker to address before starting to rely on this from individual skins or page views.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'MOTIVATION', 'OBSERVED BUG BEHAVIOR']"
+1631572,Use figure and figcaption HTML5 elements when possible,"Change 410362 **merged** by jenkins-bot:
+[mediawiki/core@master] Share Parsoid's media styling with content
+
+https://gerrit.wikimedia.org/r/410362",task_subcomment,"[""Change 410362 **merged** by jenkins-bot:\n[mediawiki/core@master] Share Parsoid's media styling with content\n\nGERRIT_URL""]",['ACTION ON ISSUE']
+1631539,Use figure and figcaption HTML5 elements when possible,"Change 647372 **merged** by jenkins-bot:
+[mediawiki/core@master] Add a feature flag to use the new media structure
+
+https://gerrit.wikimedia.org/r/647372",task_subcomment,['Change 647372 **merged** by jenkins-bot:\n[mediawiki/core@master] Add a feature flag to use the new media structure\n\nGERRIT_URL'],['ACTION ON ISSUE']
+1631451,Use figure and figcaption HTML5 elements when possible,"Change 647372 had a related patch set uploaded (by Arlolra; owner: Arlolra):
+[mediawiki/core@master] Add a feature flag to use the new media structure
+
+https://gerrit.wikimedia.org/r/647372",task_subcomment,['Change 647372 had a related patch set uploaded (by Arlolra; owner: Arlolra):\n[mediawiki/core@master] Add a feature flag to use the new media structure\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1631027,Use figure and figcaption HTML5 elements when possible,"Change 410362 had a related patch set uploaded (by Arlolra; owner: Arlolra):
+[mediawiki/core@master] Share Parsoid media styling with content
+
+https://gerrit.wikimedia.org/r/410362",task_subcomment,['Change 410362 had a related patch set uploaded (by Arlolra; owner: Arlolra):\n[mediawiki/core@master] Share Parsoid media styling with content\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+1273261,Use figure and figcaption HTML5 elements when possible,"Change 196532 abandoned by Arlolra:
+Use figure and figcaption HTML5 elements for media
+
+Reason:
+In favour of https://gerrit.wikimedia.org/r/c/mediawiki/core/ /507512
+
+[[https://gerrit.wikimedia.org/r/196532]]",task_subcomment,['Change 196532 abandoned by Arlolra:\nUse figure and figcaption HTML5 elements for media\n\nReason:\nIn favour of URL /507512\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+1273258,Use figure and figcaption HTML5 elements when possible,"Change 507512 had a related patch set uploaded (by Arlolra; owner: Arlolra):
+[mediawiki/core@master] Use figure and figcaption HTML5 elements for media
+
+[[https://gerrit.wikimedia.org/r/507512]]",task_subcomment,['Change 507512 had a related patch set uploaded (by Arlolra; owner: Arlolra):\n[mediawiki/core@master] Use figure and figcaption HTML5 elements for media\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+1271417,Use figure and figcaption HTML5 elements when possible,"Change 505645 **merged** by jenkins-bot:
+[mediawiki/core@master] Allow  attributes through Sanitizer
+
+[[https://gerrit.wikimedia.org/r/505645]]",task_subcomment,['Change 505645 **merged** by jenkins-bot:\n[mediawiki/core@master] Allow  attributes through Sanitizer\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+1268500,Use figure and figcaption HTML5 elements when possible,"Change 505645 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
+[mediawiki/core@master] Allow  attributes through Sanitizer
+
+[[https://gerrit.wikimedia.org/r/505645]]",task_subcomment,['Change 505645 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):\n[mediawiki/core@master] Allow  attributes through Sanitizer\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+967639,Use figure and figcaption HTML5 elements when possible,"Change 196533 abandoned by Umherirrender:
+Stop specifying element for thumbinner class
+
+Reason:
+See T178932
+
+[[https://gerrit.wikimedia.org/r/196533]]",task_subcomment,['Change 196533 abandoned by Umherirrender:\nStop specifying element for thumbinner class\n\nReason:\nSee T178932\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+785979,Use figure and figcaption HTML5 elements when possible,"I'm a little confused why this is in code review. The patch is over a year old and I'm unclear what the current state of this task is - have there been new developments? Has there been a request? I see some recent comments on the ticket from @ssastry:
+> No, not to be abandoned. We had an RFC hearing around this, and the block figure image usage had approval, but inline image markup was still to be resolved. Brion and Scott were going to do some follow up around that. Separately, we need to figure out transition plans for when we move to 
     markup since it will break user scripts, gadgets, etc. So, all those are blockers on getting this merged and deployed.
+
+Seems there is a lot more to work out here before we can help review this task?
+
+(Is someone more in the loop able to refresh the description so it does not date back to the Bugzilla days? :))",task_subcomment,"[""I'm a little confused why this is in code review."", ""The patch is over a year old and I'm unclear what the current state of this task is - have there been new developments?"", 'Has there been a request?', 'I see some recent comments on the ticket fromSCREEN_NAME:\nQUOTE\n\nSeems there is a lot more to work out here before we can help review this task?', '(Is someone more in the loop able to refresh the description so it does not date back to the Bugzilla days?', ':))']","['SOCIAL CONVERSATION', 'INVESTIGATION AND EXPLORATION', 'POTENTIAL NEW ISSUES AND REQUESTS', 'INVESTIGATION AND EXPLORATION', 'FUTURE PLAN', 'SOLUTION DISCUSSION']"
+785978,Use figure and figcaption HTML5 elements when possible,"I'm a little confused why this is in code review. The patch is over a year old and I'm unclear what the current state of this task is - have there been new developments? Has there been a request? I see some recent comments on the ticket from @ssastry:
+> No, not to be abandoned. We had an RFC hearing around this, and the block figure image usage had approval, but inline image markup was still to be resolved. Brion and Scott were going to do some follow up around that. Separately, we need to figure out transition plans for when we move to 
     markup since it will break user scripts, gadgets, etc. So, all those are blockers on getting this merged and deployed.
+
+Seems there is a lot more to work out here before we can help review this task?
+",task_subcomment,"[""I'm a little confused why this is in code review."", ""The patch is over a year old and I'm unclear what the current state of this task is - have there been new developments?"", 'Has there been a request?', 'I see some recent comments on the ticket fromSCREEN_NAME:\nQUOTE\n\nSeems there is a lot more to work out here before we can help review this task?']","['SOCIAL CONVERSATION', 'INVESTIGATION AND EXPLORATION', 'POTENTIAL NEW ISSUES AND REQUESTS', 'INVESTIGATION AND EXPLORATION']"
+573290,Use figure and figcaption HTML5 elements when possible,@niedzielski: cool.,task_subcomment,['SCREEN_NAME: cool.'],['SOLUTION DISCUSSION']
+573256,Use figure and figcaption HTML5 elements when possible,"@dr0ptp4kt, since this requires the Content Service to point at a local Vagrant instance, a local RESTBase and maybe also a local Parsoid install will be necessary. It'll take me a little while to get that configured. Unless this is urgent, let's see if @bearND can run this test.",task_subcomment,"['SCREEN_NAME, since this requires the Content Service to point at a local Vagrant instance, a local RESTBase and maybe also a local Parsoid install will be necessary.', ""It'll take me a little while to get that configured."", ""Unless this is urgent, let's see ifSCREEN_NAME can run this test.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+572809,Use figure and figcaption HTML5 elements when possible,"@mholloway and @niedzielski, are you able to verify no degradation of user experience with the Mobile Content Service in force with this patch, too? CC @bearND in case this task needs to wait until next week.",task_subcomment,"['SCREEN_NAME andSCREEN_NAME, are you able to verify no degradation of user experience with the Mobile Content Service in force with this patch, too?', 'CCSCREEN_NAME in case this task needs to wait until next week.']","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+572807,Use figure and figcaption HTML5 elements when possible,"Thanks, @niedzielski!",task_subcomment,"['Thanks,SCREEN_NAME!']",['ACTION ON ISSUE']
+572788,Use figure and figcaption HTML5 elements when possible,"@dr0ptp4kt, a quick follow up on gallery. The gallery images have their own request[0]. I also double checked functionally on a couple devices:
+
+## API 10 master and patch {F3046104} {F3046106}
+
+## API 23 master and patch {F3046116} {F3046118}
+
+For _even more_ thoroughness, here's link preview[1] which uses the same request as the gallery on master and its own request on Gingerbread:
+
+## API 10 master and patch {F3046108} {F3046110}
+
+## API 23 master and patch {F3046120} {F3046122}
+
+[0] https://phabricator.wikimedia.org/diffusion/APAW/browse/master/app/src/main/java/org/wikipedia/page/gallery/GalleryCollectionFetchTask.java
+[1] These look trash because I don't have all the extensions installed. The trash looks different on different APIs because the requests[2,3] and extract processing has changed since Gingerbread[4].
+[2] http://192.168.1.11:8080/w/api.php?action=query&format=json&titles=Thomas_Jefferson&continue=&prop=extracts%7Cpageimages%7Cpageterms&redirects=true&exchars=512&explaintext=true&piprop=thumbnail%7Cname&pithumbsize=320&wbptterms=description
+[3] http://192.168.1.11:8080/w/api.php?action=query&format=json&formatversion=2&prop=extracts%7Cpageimages&redirects=true&exsentences=5&explaintext=true&piprop=thumbnail%7Cname&pithumbsize=320&titles=Thomas_Jefferson
+[4] https://phabricator.wikimedia.org/rAPAWd945afc63d8025a2ae1198987f0b8cf95dc74efa#a0928e81",task_subcomment,"['SCREEN_NAME, a quick follow up on gallery.', 'The gallery images have their own request[0].', ""I also double checked functionally on a couple devices:\n\n## API 10 master and patch {F3046104} {F3046106}\n\n## API 23 master and patch {F3046116} {F3046118}\n\nFor _even more_ thoroughness, here's link preview[1] which uses the same request as the gallery on master and its own request on Gingerbread:\n\n## API 10 master and patch {F3046108} {F3046110}\n\n## API 23 master and patch {F3046120} {F3046122}\n\n[0] URL\n[1] These look trash because I don't have all the extensions installed."", 'The trash looks different on different APIs because the requests[2,3] and extract processing has changed since Gingerbread[4].', '[2] URL\n[3] URL\n[4] URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+572571,Use figure and figcaption HTML5 elements when possible,"## Results
+I877baf403088c716ad8e89752008b7a59b7e466c appears to work properly for the Android app, both master and the old deprecated Gingerbread version. I did not test the PhoneGap version. There are slight padding differences on some APIs but I think they're acceptable.
+
+## Setup
+I don't play with a local MW instance enough so please excuse the verbose notes for verification.
+
+I checked out master and made a page with some images. I checked out the patch and made another page with the same content. I can see that the master page has divs and the patch page has figures.
+
+I visited the two pages in the Android app (master and our old deprecated Gingerbread version-- not PhoneGap) on a number of devices.
+
+For posterity, some screen caps:
+
+## API 10 master and patch {F3045482} {F3045480}
+
+## API 19 master and patch {F3045484} {F3045486}
+
+## API 23 master and patch {F3045488} {F3045490}
+
+## Fire master and patch {F3045493} {F3045495}
+
+ ",task_subcomment,"['## Results\nI877baf403088c716ad8e89752008b7a59b7e466c appears to work properly for the Android app, both master and the old deprecated Gingerbread version.', 'I did not test the PhoneGap version.', ""There are slight padding differences on some APIs but I think they're acceptable."", ""## Setup\nI don't play with a local MW instance enough so please excuse the verbose notes for verification."", 'I checked out master and made a page with some images.', 'I checked out the patch and made another page with the same content.', 'I can see that the master page has divs and the patch page has figures.', 'I visited the two pages in the Android app (master and our old deprecated Gingerbread version-- not PhoneGap) on a number of devices.', 'For posterity, some screen caps:\n\n## API 10 master and patch {F3045482} {F3045480}\n\n## API 19 master and patch {F3045484} {F3045486}\n\n## API 23 master and patch {F3045488} {F3045490}\n\n## Fire master and patch {F3045493} {F3045495}']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+494576,Use figure and figcaption HTML5 elements when possible,"Change 196532 restored by Cscott:
+Use figure and figcaption HTML5 elements in Linker::makeThumbLink2
+
+Reason:
+I don't think abandoning this is helpful.  I'll put a -2 on it though to prevent premature commit.
+
+[[https://gerrit.wikimedia.org/r/196532]]",task_subcomment,"[""Change 196532 restored by Cscott:\nUse figure and figcaption HTML5 elements in Linker::makeThumbLink2\n\nReason:\nI don't think abandoning this is helpful."", ""I'll put a -2 on it though to prevent premature commit."", '[[GERRIT_URL]]']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+493821,Use figure and figcaption HTML5 elements when possible,"Change 196532 abandoned by Prtksxna:
+Use figure and figcaption HTML5 elements in Linker::makeThumbLink2
+
+Reason:
+Can be unabandoned whenever we're ready.
+
+[[https://gerrit.wikimedia.org/r/196532]]",task_subcomment,"[""Change 196532 abandoned by Prtksxna:\nUse figure and figcaption HTML5 elements in Linker::makeThumbLink2\n\nReason:\nCan be unabandoned whenever we're ready."", '[[GERRIT_URL]]']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+491971,Use figure and figcaption HTML5 elements when possible,I believe @TStarling and the parsing team have agreed on a long-term plan to make the PHP parser output and Parsoid output converge.,task_subcomment,['I believeSCREEN_NAME and the parsing team have agreed on a long-term plan to make the PHP parser output and Parsoid output converge.'],['FUTURE PLAN']
+483853,Use figure and figcaption HTML5 elements when possible,">>! In T51097#1157239, @matmarex wrote:
+>>>! In T51097#1155608, @Mattflaschen wrote:
+>> In what cases would someone need to explicitly use figcaption from wikitext (the main point is for people to use File tags, and the parser to generate them)?
+> 
+> https://en.wikipedia.org/wiki/Template:Multiple_image and other such templates need to replicate the HTML of the image thumbnails.
+
+I'm not opposing `
    ` in wikitext per se, but templates don't need it. They just have to look similar. There shouldn't be any styles specific to the figure elements in core. The classname on `
    ` will suffice and result in the same visual appearance and behaviour.
+
+Having said that, such templates shouldn't need to replicate the thumb HTML itself. We need to either support it by implementing the necessary bits in core (or an extension), or decide why it is undesired for some technical or UX reason and discourage its use.",task_subcomment,"[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI'm not opposing CODE in wikitext per se, but templates don't need it."", 'They just have to look similar.', ""There shouldn't be any styles specific to the figure elements in core."", 'The classname on CODE will suffice and result in the same visual appearance and behaviour.', ""Having said that, such templates shouldn't need to replicate the thumb HTML itself."", 'We need to either support it by implementing the necessary bits in core (or an extension), or decide why it is undesired for some technical or UX reason and discourage its use.']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+483852,Use figure and figcaption HTML5 elements when possible,">>! In T51097#1157239, @matmarex wrote:
+>>>! In T51097#1155608, @Mattflaschen wrote:
+>> In what cases would someone need to explicitly use figcaption from wikitext (the main point is for people to use File tags, and the parser to generate them)?
+> 
+> https://en.wikipedia.org/wiki/Template:Multiple_image and other such templates need to replicate the HTML of the image thumbnails.
+
+I'm not opposing `
    ` in wikitext per se, but templates don't need it. They just have to look similar. There shouldn't be any styles specific to the figure elements in core. The classname on `
    ` will suffice and result in the same visual appearance and behaviour.
+
+Having said that, such templates shouldn't need to exist. We need to either support it by implementing the necessary bits in core (or an extension), or decide why it is undesired for some technical or UX reason and discourage its use.",task_subcomment,"[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI'm not opposing CODE in wikitext per se, but templates don't need it."", 'They just have to look similar.', ""There shouldn't be any styles specific to the figure elements in core."", 'The classname on CODE will suffice and result in the same visual appearance and behaviour.', ""Having said that, such templates shouldn't need to exist."", 'We need to either support it by implementing the necessary bits in core (or an extension), or decide why it is undesired for some technical or UX reason and discourage its use.']","['MOTIVATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+434069,Use figure and figcaption HTML5 elements when possible,">>! In T51097#1155608, @Mattflaschen wrote:
+> In what cases would someone need to explicitly use figcaption from wikitext (the main point is for people to use File tags, and the parser to generate them)?
+
+https://en.wikipedia.org/wiki/Template:Multiple_image and other such templates need to replicate the HTML of the image thumbnails.",task_subcomment,['QUOTE\nQUOTE\n\nURL and other such templates need to replicate the HTML of the image thumbnails.'],['SOLUTION DISCUSSION']
+433725,Use figure and figcaption HTML5 elements when possible,">>! In T51097#1147961, @TheDJ wrote:
+> # Do we want users to use figcaption/figure from wikitext as well ? (I think this can be assessed at a later point in time).
+
+In what cases would someone need to explicitly use figcaption from wikitext (the main point is for people to use File tags, and the parser to generate them)?",task_subcomment,"['QUOTE\nQUOTE\n\nIn what cases would someone need to explicitly use figcaption from wikitext (the main point is for people to use File tags, and the parser to generate them)?']",['SOLUTION DISCUSSION']
+432192,Use figure and figcaption HTML5 elements when possible,"# Should be tested with the other skins.
+# It seems CSS or scripts for some people would break: https://en.wikipedia.org/w/index.php?title=Special:Search&limit=20&offset=20&profile=all&search=thumbinner Mostly this is style
+# MediaWiki:Gadget-ImageAnnotator.js would break and probably a few more",task_subcomment,"['# Should be tested with the other skins.', '# It seems CSS or scripts for some people would break: URL Mostly this is style\n# MediaWiki:Gadget-ImageAnnotator.js would break and probably a few more']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+432180,Use figure and figcaption HTML5 elements when possible,"As Brion said, be sure to validate against TimedMediaHandler, Mobile, WikiEditor and other extensions that depend on the current thumbnail layout.
+
+We will probably want to deploy the CSS changes before the element changes for cache reasons ?
+
+Also we have https://en.wikipedia.org/wiki/Category:Graphics_templates where I have two concerns:
+# How many of those templates will be affected
+# Do we want users to use figcaption/figure from wikitext as well ? (I think this can be assessed at a later point in time).",task_subcomment,"['As Brion said, be sure to validate against TimedMediaHandler, Mobile, WikiEditor and other extensions that depend on the current thumbnail layout.', 'We will probably want to deploy the CSS changes before the element changes for cache reasons ?', 'Also we have URL where I have two concerns:\n# How many of those templates will be affected\n# Do we want users to use figcaption/figure from wikitext as well ?', '(I think this can be assessed at a later point in time).']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+432078,Use figure and figcaption HTML5 elements when possible,Should be fine if the HTML5 shiv works properly.  No JS old IE is minimal per https://phabricator.wikimedia.org/T25932#851388 .  IE 8 ([last version](http://caniuse.com/#feat=html5semantic) not to support this out of the box) is EOL in January 2016 (less than 10 months away!),task_subcomment,"['Should be fine if the HTML5 shiv works properly.', 'No JS old IE is minimal per URL .', 'IE 8 ([last version](URL not to support this out of the box) is EOL in January 2016 (less than 10 months away!)']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'FUTURE PLAN']"
+425825,Use figure and figcaption HTML5 elements when possible,"Change 196533 had a related patch set uploaded (by Prtksxna):
+Stop specifying element for thumbinner class
+
+[[https://gerrit.wikimedia.org/r/196533]]
+",task_subcomment,['Change 196533 had a related patch set uploaded (by Prtksxna):\nStop specifying element for thumbinner class\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+425824,Use figure and figcaption HTML5 elements when possible,"Change 196532 had a related patch set uploaded (by Prtksxna):
+Use figure and figcaption HTML5 elements in Linker::makeThumbLink2
+
+[[https://gerrit.wikimedia.org/r/196532]]
+",task_subcomment,['Change 196532 had a related patch set uploaded (by Prtksxna):\nUse figure and figcaption HTML5 elements in Linker::makeThumbLink2\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+233759,Use figure and figcaption HTML5 elements when possible,"Docs on MDN for these elements:
+
+https://developer.mozilla.org/en-US/docs/Web/HTML/Element/figure
+
+https://developer.mozilla.org/en-US/docs/Web/HTML/Element/figcaption
+
+Core and mobile styles would have to be updated, and likely also some JS tools.
+
+Alternatively, 
     and 
     could be thrown in around the existing 
    s and s without changing the styles, assuming there's no default styles that override stuff.",task_subcomment,"['Docs on MDN for these elements:\n\nURL\n\nURL\n\nCore and mobile styles would have to be updated, and likely also some JS tools.', ""Alternatively, 
     and 
     could be thrown in around the existing 
    s and s without changing the styles, assuming there's no default styles that override stuff.""]","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+51092,VisualEditor: Reference lists should update more intelligently (i.e. less often),"Currently a reference list ( in wikitext) complete redraws every time an InternalItemNode is touched by a transaction. This is inefficient because:
+
+* Reference lists can be grouped, so a change to one InternalItemNode may not affect that reference list at all.
+* Changes to IternalItemNodes shouldn't change the ordering of the list, or any items not touched by the transaction, so we only need to selectively update the items in the list which have changed.",task_description,"['VisualEditor: Reference lists should update more intelligently (i.e.', 'less often)\n\nCurrently a reference list ( in wikitext) complete redraws every time an InternalItemNode is touched by a transaction.', 'This is inefficient because:\n\n* Reference lists can be grouped, so a change to one InternalItemNode may not affect that reference list at all.', ""* Changes to IternalItemNodes shouldn't change the ordering of the list, or any items not touched by the transaction, so we only need to selectively update the items in the list which have changed.""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+51089,Enable VisualEditor alpha on all Wikipedias,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,['Enable VisualEditor alpha on all Wikipedias\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'],['INVESTIGATION AND EXPLORATION']
+233287,Enable VisualEditor alpha on all Wikipedias,Done on 2013-06-06.,task_subcomment,['Done on 2013-06-06.'],['SOLUTION DISCUSSION']
+233281,Enable VisualEditor alpha on all Wikipedias,Related URL: https://gerrit.wikimedia.org/r/67151 (Gerrit Change I98eb9f4979ae8d1dc2fdca4d812feaee28672444),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I98eb9f4979ae8d1dc2fdca4d812feaee28672444)'],['OBSERVED BUG BEHAVIOR']
+51059,VisualEditor: Phantoms appear above edit notices,"Even though the edit notices appear above text, they don't appear above overlays, e.g. block phantoms.
+
+http://i.imgur.com/RAOdlIZ.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49361
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50096
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50545",task_description,"[""VisualEditor: Phantoms appear above edit notices\n\nEven though the edit notices appear above text, they don't appear above overlays, e.g."", 'block phantoms.', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL\nURL\nURL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+231284,VisualEditor: Phantoms appear above edit notices,"This has now been fixed by Rob; marking as such. I hope we can deploy this to production soon, possibly tomorrow.",task_subcomment,"['This has now been fixed by Rob; marking as such.', 'I hope we can deploy this to production soon, possibly tomorrow.']","['ACTION ON ISSUE', 'WORKAROUNDS']"
+231280,VisualEditor: Phantoms appear above edit notices,"See also bug 49275. The layer the phantoms are added too needs to be put below the layer of toolbar, edit notices and save dialog etc.",task_subcomment,"['See also bug 49275.', 'The layer the phantoms are added too needs to be put below the layer of toolbar, edit notices and save dialog etc.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+51034,Piping used unnecessarily when modifying an existing link,"I edited https://en.wikipedia.org/w/index.php?title=Eagle_Lake_%28Florida%29&oldid=557775556 which contained a piped link:
+
+[[Eagle Lake, Florida|Eagle Lake]]
+
+I used VisualEditor to change the anchor text to Eagle Lake, Florida.  That means piping is no longer necessary.  However, on the review changes screen, it showed:
+
+'''Eagle Lake''' is an elongated lake in shape located in the northern portion of [[Eagle Lake, Florida|Eagle Lake, Florida]].
+
+(irrelevant parts after omitted).
+
+It should just be:
+
+[[Eagle Lake, Florida]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Piping used unnecessarily when modifying an existing link\n\nI edited URL which contained a piped link:\n\n[[Eagle Lake, Florida|Eagle Lake]]\n\nI used VisualEditor to change the anchor text to Eagle Lake, Florida.', 'That means piping is no longer necessary.', ""However, on the review changes screen, it showed:\n\n'''Eagle Lake''' is an elongated lake in shape located in the northern portion of [[Eagle Lake, Florida|Eagle Lake, Florida]]."", '(irrelevant parts after omitted).', 'It should just be:\n\n[[Eagle Lake, Florida]]\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+229769,Piping used unnecessarily when modifying an existing link,Please note that this will be fixed on en-wp only after the latest version of parsoid is deployed.,task_subcomment,['Please note that this will be fixed on en-wp only after the latest version of parsoid is deployed.'],['WORKAROUNDS']
+229764,Piping used unnecessarily when modifying an existing link,https://gerrit.wikimedia.org/r/66880 (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28) | change APPROVED and MERGED [by jenkins-bot],task_subcomment,['GERRIT_URL (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28) | change APPROVED and MERGED [by jenkins-bot]'],['OBSERVED BUG BEHAVIOR']
+229758,Piping used unnecessarily when modifying an existing link,Related URL: https://gerrit.wikimedia.org/r/66880 (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28),task_subcomment,['Related URL: GERRIT_URL (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28)'],['OBSERVED BUG BEHAVIOR']
+229752,Piping used unnecessarily when modifying an existing link,"Never mind ... bad test case.  This behavior is correct since the second html snippet corresponds to parse output of ""[[Foo|Foo]]"" as wikitext input.
+
+The problem seems to be that the serializer doesn't exploit the information that the link target has been modified and that there is a diff-marker on the a-tag.",task_subcomment,"['Never mind ... bad test case.', 'This behavior is correct since the second html snippet corresponds to parse output of ""[[Foo|Foo]]"" as wikitext input.', ""The problem seems to be that the serializer doesn't exploit the information that the link target has been modified and that there is a diff-marker on the a-tag.""]","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+229745,Piping used unnecessarily when modifying an existing link,"Bug in LinkHandler in the serializer.  Our html2wt tests are lacking.
+
+[subbu@earth lib] cat /tmp/x
+Foo
+Foo
+[subbu@earth lib] node parse --html2wt < /tmp/x
+[[Foo]]
+[[Foo|Foo]]",task_subcomment,"['Bug in LinkHandler in the serializer.', 'Our html2wt tests are lacking.', '[subbu@earth lib] cat /tmp/x\nFoo\nFoo\n[subbu@earth lib] node parse --html2wt < /tmp/x\n[[Foo]]\n[[Foo|Foo]]']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+51000,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","When attempting to move a page where VisualEditor is enabled (take https://www.mediawiki.org/wiki/Special:MovePage/VisualEditor:Sandbox for an example), the tab ""Create source"" should be an ""Edit source"" tab instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66885",task_description,"['VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?', 'When attempting to move a page where VisualEditor is enabled (take URL for an example), the tab ""Create source"" should be an ""Edit source"" tab instead.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'BUG REPRODUCTION']"
+233059,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","(In reply to Alex Monk from comment #17)
+> Is there anything left to do here?
+
+This appears fixed for now (albeit as a hack).",task_subcomment,['(In reply to Alex Monk from comment #17)\nQUOTE\n\nThis appears fixed for now (albeit as a hack).'],['SOLUTION DISCUSSION']
+233049,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",Is there anything left to do here?,task_subcomment,['Is there anything left to do here?'],['SOLUTION DISCUSSION']
+233040,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Change 82744 merged by jenkins-bot:
+Reference core bug 53774 in bug 49000 comment
+
+https://gerrit.wikimedia.org/r/82744",task_subcomment,['Change 82744 merged by jenkins-bot:\nReference core bug 53774 in bug 49000 comment\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+233034,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Change 82744 had a related patch set uploaded by Jforrester:
+Reference core bug 53774 in bug 49000 comment
+
+https://gerrit.wikimedia.org/r/82744",task_subcomment,['Change 82744 had a related patch set uploaded by Jforrester:\nReference core bug 53774 in bug 49000 comment\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+233031,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","(In reply to comment #12)
+> I think I can still see this?
+> http://en.wikipedia.org/wiki/Special:WhatLinksHere/Esempio 
+> Thanks.
+
+This is caused by (core) bug 53774 which we will need to fix.",task_subcomment,['(In reply to comment #12)\nQUOTE\nQUOTE\nQUOTE\n\nThis is caused by (core) bug 53774 which we will need to fix.'],['OBSERVED BUG BEHAVIOR']
+233024,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","I mean, as the page does not exist, shouldn't that read Create source instead, as in http://en.wikipedia.org/wiki/Esempio ?",task_subcomment,"[""I mean, as the page does not exist, shouldn't that read Create source instead, as in URL ?""]",['OBSERVED BUG BEHAVIOR']
+233019,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","I think I can still see this? http://en.wikipedia.org/wiki/Special:WhatLinksHere/Esempio 
+Thanks.",task_subcomment,"['I think I can still see this?', 'URL \nThanks.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+233013,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",Now fixed and deployed.,task_subcomment,['Now fixed and deployed.'],['ACTION ON ISSUE']
+233005,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Change 77165 had a related patch set uploaded by Catrope:
+Move edit tab generation into PHP and make it more configurable
+
+https://gerrit.wikimedia.org/r/77165",task_subcomment,['Change 77165 had a related patch set uploaded by Catrope:\nMove edit tab generation into PHP and make it more configurable\n\nGERRIT_URL'],['ACTION ON ISSUE']
+232999,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Change 77253 merged by jenkins-bot:
+mw.ViewPageTarget.init: Fix pageExists/isViewPage behaviour
+
+https://gerrit.wikimedia.org/r/77253",task_subcomment,['Change 77253 merged by jenkins-bot:\nmw.ViewPageTarget.init: Fix pageExists/isViewPage behaviour\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+232993,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Change 77253 had a related patch set uploaded by Esanders:
+Fix pageExists/isViewPage behaviour
+
+https://gerrit.wikimedia.org/r/77253",task_subcomment,['Change 77253 had a related patch set uploaded by Esanders:\nFix pageExists/isViewPage behaviour\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+232986,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Change 77246 merged by jenkins-bot:
+Fix edit links on special pages
+
+https://gerrit.wikimedia.org/r/77246",task_subcomment,['Change 77246 merged by jenkins-bot:\nFix edit links on special pages\n\nGERRIT_URL'],['ACTION ON ISSUE']
+232979,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Change 77246 had a related patch set uploaded by Esanders:
+Fix edit links on special pages
+
+https://gerrit.wikimedia.org/r/77246",task_subcomment,['Change 77246 had a related patch set uploaded by Esanders:\nFix edit links on special pages\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+232971,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","More importantly, it lets you load VE dynamically, which it shouldn't.",task_subcomment,"[""More importantly, it lets you load VE dynamically, which it shouldn't.""]",['SOLUTION DISCUSSION']
+232965,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",Also show on Special:Whatlinkshere (e.g. https://it.wikipedia.org/wiki/Speciale:PuntanoQui/Wikipedia ),task_subcomment,"['Also show on Special:Whatlinkshere (e.g.', 'URL )']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+232960,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Also shown on Special:Undelete, after the page has been restored.
+
+i.e. ""User:John Vandenberg/test has been restored"" has tabs: Read | Edit | Create source | View history",task_subcomment,"['Also shown on Special:Undelete, after the page has been restored.', 'i.e.', '""User:John Vandenberg/test has been restored"" has tabs: Read | Edit | Create source | View history']","['SOLUTION USAGE', 'INVESTIGATION AND EXPLORATION', 'MOTIVATION']"
+232954,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?","Confirmed. It says ""Read | Edit | Create source | View history"".
+
+https://www.mediawiki.org/wiki/Special:MovePage/Sandbox",task_subcomment,"['Confirmed.', 'It says ""Read | Edit | Create source | View history"".', 'URL']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+232948,"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",--> VisualEditor,task_subcomment,['--> VisualEditor'],['INVESTIGATION AND EXPLORATION']
+50993,VisualEditor: Formatting styles drop down menu rendered behind the page title,"On http://www.mediawiki.org/wiki/VisualEditor:Test when clicking on the drop down menu for styles, the title of the page is still visible
+
+http://i.imgur.com/O3OvK3w.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Formatting styles drop down menu rendered behind the page title\n\nOn URL when clicking on the drop down menu for styles, the title of the page is still visible\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",['OBSERVED BUG BEHAVIOR']
+232546,VisualEditor: Formatting styles drop down menu rendered behind the page title,*** Bug 49430 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 49430 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+232542,VisualEditor: Formatting styles drop down menu rendered behind the page title,Thanks for the bug report; this is now fixed in wmf6 which was released yesterday to MediaWiki.org and will be available everywhere by the end of next week.,task_subcomment,['Thanks for the bug report; this is now fixed in wmf6 which was released yesterday to MediaWiki.org and will be available everywhere by the end of next week.'],['ACTION ON ISSUE']
+50974,VisualEditor: MWTemplateDialog should visually distinguish between wikitext and template name,"Screenshot while editing template with wikitext-generated target
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11029}",task_description,['VisualEditor: MWTemplateDialog should visually distinguish between wikitext and template name\n\nScreenshot while editing template with wikitext-generated target\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n\n**Attached**: {F11029}'],['OBSERVED BUG BEHAVIOR']
+231572,VisualEditor: MWTemplateDialog should visually distinguish between wikitext and template name,"A different icon seems somewhat undiscoverable, but not sure what better way to do this. Possibly call them ""Auto: "" rather than just """"? Making the name italics?",task_subcomment,"['A different icon seems somewhat undiscoverable, but not sure what better way to do this.', 'Possibly call them ""Auto: "" rather than just """"?', 'Making the name italics?']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+50960,VisualEditor: Cut-Paste of paragraphs seems broken in Firefox,"Problem 1:
+
+1. Open [[User:Ssastry]]
+2. Select Paragraph 3 completely.
+3. Ctrl-X
+4. Move to beginning of Paragraph 2.  Hit Enter.
+5. Ctrl-V on empty line
+
+The paragraph gets pasted on the same line as Paragraph 3.  
+
+Problem 2:
+
+Steps 1-3 and 5. are identical.  Step 4 is different:
+4. Move to end of Paragraph 1, hit enter key,
+
+The paragraph gets pasted *before* paragraph 1.  Additionally, on review-and-save, paragraph 1 is lost.  This is not a Parsoid issue -- the edited HTML is missing the paragraph.
+
+This problem seems specific to Firefox.  Cannot reproduce on Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Cut-Paste of paragraphs seems broken in Firefox\n\nProblem 1:\n\n1.', 'Open [[User:Ssastry]]\n2.', 'Select Paragraph 3 completely.', '3.', 'Ctrl-X\n4.', 'Move to beginning of Paragraph 2.', 'Hit Enter.', '5.', 'Ctrl-V on empty line\n\nThe paragraph gets pasted on the same line as Paragraph 3.', 'Problem 2:\n\nSteps 1-3 and 5. are identical.', 'Step 4 is different:\n4.', 'Move to end of Paragraph 1, hit enter key,\n\nThe paragraph gets pasted *before* paragraph 1.', 'Additionally, on review-and-save, paragraph 1 is lost.', 'This is not a Parsoid issue -- the edited HTML is missing the paragraph.', 'This problem seems specific to Firefox.', 'Cannot reproduce on Chrome.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+230654,VisualEditor: Cut-Paste of paragraphs seems broken in Firefox,This was fixed in the re-write of copy-and-paste; sorry we didn't update this bug until now.,task_subcomment,"[""This was fixed in the re-write of copy-and-paste; sorry we didn't update this bug until now.""]",['BUG REPRODUCTION']
+230651,VisualEditor: Cut-Paste of paragraphs seems broken in Firefox,Firefox 21.0,task_subcomment,['Firefox 21.0'],['OBSERVED BUG BEHAVIOR']
+230647,VisualEditor: Cut-Paste of paragraphs seems broken in Firefox,"(In reply to comment #0)
+> This problem seems specific to Firefox.  Cannot reproduce on Chrome.
+
+Version info always welcome, in general.",task_subcomment,"['(In reply to comment #0)\nQUOTE\n\nVersion info always welcome, in general.']",['SOLUTION DISCUSSION']
+50913,VisualEditor: Make ve.dm.Transaction chainable,"tx push
+tx push
+tx push
+tx push
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,['VisualEditor: Make ve.dm.Transaction chainable\n\ntx push\ntx push\ntx push\ntx push\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'],['INVESTIGATION AND EXPLORATION']
+50900,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"Image patch (https://gerrit.wikimedia.org/r/#/c/57817/) is missing error handling when the mw API is queried to get information about an image.
+
+Two kind of errors that handleResponse in LinkHandler.js has to deal with:
+
+(1) API error: Given that ApiRequest retries, an api error is an indication that the api may be temporarily down or that something else is wrong.  So, rather than continue, it is better to abort processing and return an error code to the clients so they can handle it however they want (ex: ve might tell the user that the page cannot be edited right now because of api/server issues).  This will require calling the error callback found in env.
+
+(2) Image missing: If the api comes back and tells us that the image is missing, we should handle this similar to how the PHP parser does it for missing images.
+- Maybe link to a special page/url that will let VE present an upload handler (check with VE folks as to what this url could be.  PHP parser behavior can be found by editing a page on wikipedia sandbox with a non-existent image)
+- Dont add a thumb.
+- Add a special rdf type on the image/wrapper tag: mw:Image/Missing maybe?
+
+EDIT: These properties should apply to missing templates as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw\n\nImage patch (URL is missing error handling when the mw API is queried to get information about an image.', 'Two kind of errors that handleResponse in LinkHandler.js has to deal with:\n\n(1) API error: Given that ApiRequest retries, an api error is an indication that the api may be temporarily down or that something else is wrong.', 'So, rather than continue, it is better to abort processing and return an error code to the clients so they can handle it however they want (ex: ve might tell the user that the page cannot be edited right now because of api/server issues).', 'This will require calling the error callback found in env.', '(2) Image missing: If the api comes back and tells us that the image is missing, we should handle this similar to how the PHP parser does it for missing images.', '- Maybe link to a special page/url that will let VE present an upload handler (check with VE folks as to what this url could be.', 'PHP parser behavior can be found by editing a page on wikipedia sandbox with a non-existent image)\n- Dont add a thumb.', '- Add a special rdf type on the image/wrapper tag: mw:Image/Missing maybe?', 'EDIT: These properties should apply to missing templates as well.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+815613,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"Change 339689 merged by jenkins-bot:
+T50900: Set mw:Error and provide error info in data-mw for ext/tpl
+
+[[https://gerrit.wikimedia.org/r/339689]]",task_subcomment,['Change 339689 merged by jenkins-bot:\nT50900: Set mw:Error and provide error info in data-mw for ext/tpl\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+815429,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"Change 339689 had a related patch set uploaded (by Arlolra):
+T50900: Set mw:Error and provide error info in data-mw for ext/tpl
+
+[[https://gerrit.wikimedia.org/r/339689]]
+",task_subcomment,['Change 339689 had a related patch set uploaded (by Arlolra):\nT50900: Set mw:Error and provide error info in data-mw for ext/tpl\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+509627,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"According to comments in ext.core.TemplateHandler.js, the data-mw update was supposed to apply to missing templates as well.  Re-opening and retitling to reflect work remaining, since there are already references in the source code to this bug #.",task_subcomment,"['According to comments in ext.core.TemplateHandler.js, the data-mw update was supposed to apply to missing templates as well.', 'Re-opening and retitling to reflect work remaining, since there are already references in the source code to this bug #.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+343581,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,This has been deployed.,task_subcomment,['This has been deployed.'],['SOLUTION USAGE']
+339921,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"Change 170455 merged by jenkins-bot:
+T50900: Add mw:Error   error info to data-mw for missing imgs
+
+[[https://gerrit.wikimedia.org/r/170455]]",task_subcomment,['Change 170455 merged by jenkins-bot:\nT50900: Add mw:Error   error info to data-mw for missing imgs\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+336370,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"Change 170455 had a related patch set uploaded (by Subramanya Sastry):
+T50900: Add mw:Error   error info to data-mw for missing imgs
+
+[[https://gerrit.wikimedia.org/r/170455]]
+
+#patch-for-review",task_subcomment,['Change 170455 had a related patch set uploaded (by Subramanya Sastry):\nT50900: Add mw:Error   error info to data-mw for missing imgs\n\n[[GERRIT_URL]]\n\n#patch-for-review'],['GERRIT_URL']
+226886,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"Change 170455 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 48900) Add mw:Error + error info to data-mw for missing imgs
+
+https://gerrit.wikimedia.org/r/170455",task_subcomment,['Change 170455 had a related patch set uploaded by Subramanya Sastry:\nWIP: (Bug 48900) Add mw:Error + error info to data-mw for missing imgs\n\nGERRIT_URL'],['BUG REPRODUCTION']
+226879,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,We should tackle this one soon since this blocks Flow from removing data-parsoid from their code. They use data-parsoid for missing images to render links. We currently emit a mw:Placeholder meta for it.,task_subcomment,"['We should tackle this one soon since this blocks Flow from removing data-parsoid from their code.', 'They use data-parsoid for missing images to render links.', 'We currently emit a mw:Placeholder meta for it.']","['FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+226873,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,*** Bug 51615 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51615 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+226871,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,Spec in development at http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Error_handling,task_subcomment,['Spec in development at URL'],['OBSERVED BUG BEHAVIOR']
+226868,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"We recently discussed this again. A possible solution might be to mark arbitrary elements as error-affected using an additional mw:Error typeof (or CSS class), plus error information in data-mw.error. This error information can be an object like this:
+
+{
+  key: ""missing-image"",
+  msg: ""This image did not exist""
+}
+ 
+The key can be used to retrieve localized messages. The msg just provides a non-localized fall-back. We could leave that out too if we are concerned about space.
+
+For images, we'd use the standard DOM structure as if the image existed, but point out the error with the typeof and data-mw so that the VE can help the user to fix the issue. Similarly, bots can look for errors and potentially fix them automatically.",task_subcomment,"['We recently discussed this again.', 'A possible solution might be to mark arbitrary elements as error-affected using an additional mw:Error typeof (or CSS class), plus error information in data-mw.error.', 'This error information can be an object like this:\n\n{\n  key: ""missing-image"",\n  msg: ""This image did not exist""\n}\n \nThe key can be used to retrieve localized messages.', 'The msg just provides a non-localized fall-back.', 'We could leave that out too if we are concerned about space.', ""For images, we'd use the standard DOM structure as if the image existed, but point out the error with the typeof and data-mw so that the VE can help the user to fix the issue."", 'Similarly, bots can look for errors and potentially fix them automatically.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+226863,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,*** Bug 51535 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51535 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+226859,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,*** Bug 50290 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50290 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+226852,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,Another example from bug 51244 - http://parsoid.wmflabs.org/pt/Usu%C3%A1rio:Helder.wiki/Testes?oldid=36380720,task_subcomment,['Another example from bug 51244 - URL'],['MOTIVATION']
+226845,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,*** Bug 51244 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51244 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+226839,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,*** Bug 51039 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 51039 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+226832,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],task_subcomment,"['[Parsoid component reorg by merging JS/General and General.', 'See bug 50685 for more information.', 'Filter bugmail on this comment.', 'parsoidreorg20130704]']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+226827,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,*** Bug 50035 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 50035 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+226822,Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,"Before merging Mark's image patch I added very basic error handling that at least round-trips the image in case something goes wrong. This uses a simple mw:Placeholder for now, but we should probably create a generic error RDFa type that lets us report localizable errors while still ensuring round-tripping.
+
+To let editors fix such an issue it might be useful to attach the regular DOM structure to the error wrapper. We'd also need to point out which property needs to be fixed, so that a client like the VisualEditor can provide a useful dialog.",task_subcomment,"[""Before merging Mark's image patch I added very basic error handling that at least round-trips the image in case something goes wrong."", 'This uses a simple mw:Placeholder for now, but we should probably create a generic error RDFa type that lets us report localizable errors while still ensuring round-tripping.', 'To let editors fix such an issue it might be useful to attach the regular DOM structure to the error wrapper.', ""We'd also need to point out which property needs to be fixed, so that a client like the VisualEditor can provide a useful dialog.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+50891,Parsoid should support  and  natively as they are not normal parser tags,"screenshot
+
+Example: https://www.mediawiki.org/wiki/Communication
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50284
+
+**Attached**: {F10855}",task_description,['Parsoid should support  and  natively as they are not normal parser tags\n\nscreenshot\n\nExample: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**URL**: URL\n**See Also**:\nURL\n\n**Attached**: {F10855}'],['BUG REPRODUCTION']
+585177,Parsoid should support  and  natively as they are not normal parser tags,"Parsoid will now wrap these appropriately with the proper typeof `mw:Extension/translate` and whatnot.
+
+Support for the Translate extension in VE is still needed, but a separate task.",task_subcomment,"['Parsoid will now wrap these appropriately with the proper typeof CODE and whatnot.', 'Support for the Translate extension in VE is still needed, but a separate task.']","['SOLUTION DISCUSSION', 'FUTURE PLAN']"
+585107,Parsoid should support  and  natively as they are not normal parser tags,"Change 261293 merged by jenkins-bot:
+T50891: Register  and  natively
+
+[[https://gerrit.wikimedia.org/r/261293]]",task_subcomment,['Change 261293 merged by jenkins-bot:\nT50891: Register  and  natively\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+584806,Parsoid should support  and  natively as they are not normal parser tags,"Change 261293 had a related patch set uploaded (by Arlolra):
+T50891: Register  and  natively
+
+[[https://gerrit.wikimedia.org/r/261293]]
+",task_subcomment,['Change 261293 had a related patch set uploaded (by Arlolra):\nT50891: Register  and  natively\n\n[[GERRIT_URL]]'],['GERRIT_URL']
+570976,Parsoid should support  and  natively as they are not normal parser tags,">>! In T50891#1840365, @kaldari wrote:
+> Any update on this?
+
+A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations.
+
+I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",task_subcomment,"['QUOTE\nQUOTE\n\nA generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions.', 'As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated.', 'VE and other tools can then use this to provide translation support by querying the API to manage translations.', 'I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+570478,Parsoid should support  and  natively as they are not normal parser tags,Any update on this?,task_subcomment,['Any update on this?'],['ACTION ON ISSUE']
+404559,Parsoid should support  and  natively as they are not normal parser tags,"Since  is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension).
+
+This native translate will be relatively straightforward and will not do anything special beyond recognizing the  and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext.
+
+This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",task_subcomment,"[""Since  is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension)."", 'This native translate will be relatively straightforward and will not do anything special beyond recognizing the  and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation.', 'In addition, it would also have to register a html2wt handler for serializing it back to wikitext.', 'This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does.', 'Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN']"
+404106,Parsoid should support  and  natively as they are not normal parser tags,I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for  tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.,task_subcomment,"['I had a chat with Subbu about this.', 'In the short tem (this year) we could add configurable support for  tags in parsoid.', 'That support will preserve the tags and comments when pages are edited with VE.', 'In the long term we will implement support for translatable pages without any kind of markup.', 'Marking those pages for translation would only work with VE and it needs special page translation module in VE.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'INVESTIGATION AND EXPLORATION']"
+402925,Parsoid should support  and  natively as they are not normal parser tags,"Kabhi2104 asked on #mediawiki-i18n:
+> Nemo_bis:  i had one doubt, what does normal parser tags mean ?
+
+Explained briefly from a non-technical perspective, this means that  is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[https://www.mediawiki.org/wiki/Special:Version|the list on Special:Version]].
+
+Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions|is meaningful for the parser and perhaps shouldn't be required]].
+
+More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.",task_subcomment,"['Kabhi2104 asked on #mediawiki-i18n:\nQUOTE\n\nExplained briefly from a non-technical perspective, this means that  is a ""tag"" for the Translate extension, but the parser ""doesn\'t know"" it.', 'A symptom is the absence from [[URL list on Special:Version]].', 'Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894.', ""But even in the current situation there are some limitations, especially for the newline, which [[URL meaningful for the parser and perhaps shouldn't be required]]."", ""More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.""]","['MOTIVATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+226198,Parsoid should support  and  natively as they are not normal parser tags,"To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself. I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.",task_subcomment,"[""To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself."", 'I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+226191,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to Nemo from comment #43)
+> (In reply to James Forrester from comment #42)
+> > No patch any more. :-(
+> 
+> Hmm I'm not sure that's what ""Can be re-activated if there is outlook on
+> getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible
+> way to tag such stale patches in need of TLC.
+
+No. There is no patch to review for merge. There is patch to re-*do*.",task_subcomment,"['(In reply to Nemo from comment #43)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo.', 'There is no patch to review for merge.', 'There is patch to re-*do*.']","['ACTION ON ISSUE', 'ACTION ON ISSUE', 'SOLUTION DISCUSSION']"
+226186,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to James Forrester from comment #42)
+> No patch any more. :-(
+
+Hmm I'm not sure that's what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.",task_subcomment,"['(In reply to James Forrester from comment #42)\nQUOTE\n\nHmm I\'m not sure that\'s what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.']",['SOLUTION DISCUSSION']
+226182,Parsoid should support  and  natively as they are not normal parser tags,No patch any more. :-(,task_subcomment,"['No patch any more.', ':-(']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR']"
+226178,Parsoid should support  and  natively as they are not normal parser tags,"Change 91583 abandoned by Siebrand:
+Add $wgTranslatePageTranslationUseParserHook
+
+Reason:
+Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state.
+
+https://gerrit.wikimedia.org/r/91583",task_subcomment,"['Change 91583 abandoned by Siebrand:\nAdd $wgTranslatePageTranslationUseParserHook\n\nReason:\nAbandoned as there is no progress on this patch set.', 'Can be re-activated if there is outlook on getting this in a mergable state.', 'GERRIT_URL']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+226174,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to comment #39)
+> (In reply to comment #36)
+> > Issues I have found:
+> > 
+> > * [MAJOR] Disabling edit section links does not work for headings inside
+> >  tags
+> 
+> You could try marking your output as HTML according to
+> https://www.mediawiki.org/wiki/Manual:
+> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.
+> 3F
+
+This causes (lack of) whitespace issues and breaks all lists.
+
+> I'm not sure whether that suppresses section edit links too, but worth a try
+> IMO.
+
+It doesn't.
+
+> 
+> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice
+> > fix. Above issue make this a bigger issue.
+> > * [BLOCKER] Table of contents does not include links
+> 
+> Can you check whether your headings are matched by the formatHeadings regexp?
+
+I'm assuming it processes the html I'm returning, which is:
+
    CultureCulture
    
+
+Not sure whether that matches or not.
+
+> 
+> Ideally we'd move both TOC and section edit links to JS / CSS. That is our
+> plan
+> for Parsoid output, but not going to happen over night.
+
+Any changes for interim solutions?",task_subcomment,"['(In reply to comment #39)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis causes (lack of) whitespace issues and breaks all lists.', ""QUOTE\nQUOTE\n\nIt doesn't."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI\'m assuming it processes the html I\'m returning, which is:\n
    CultureCulture
    \n\nNot sure whether that matches or not.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAny changes for interim solutions?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'MOTIVATION', 'SOLUTION USAGE']"
+226169,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to comment #36)
+> Issues I have found:
+> 
+> * [MAJOR] Disabling edit section links does not work for headings inside
+>  tags
+
+You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F
+
+I'm not sure whether that suppresses section edit links too, but worth a try IMO.
+
+> * [NORMAL] Edit section links don't work. Not a regression, but would be nice
+> fix. Above issue make this a bigger issue.
+> * [BLOCKER] Table of contents does not include links
+
+Can you check whether your headings are matched by the formatHeadings regexp?
+
+Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",task_subcomment,"[""(In reply to comment #36)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYou could try marking your output as HTML according to URL\n\nI'm not sure whether that suppresses section edit links too, but worth a try IMO."", 'QUOTE\nQUOTE\nQUOTE\n\nCan you check whether your headings are matched by the formatHeadings regexp?', ""Ideally we'd move both TOC and section edit links to JS / CSS."", 'That is our plan for Parsoid output, but not going to happen over night.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN']"
+226164,Parsoid should support  and  natively as they are not normal parser tags,Editing translatable pages via API seems to work now.,task_subcomment,['Editing translatable pages via API seems to work now.'],['SOLUTION USAGE']
+226162,Parsoid should support  and  natively as they are not normal parser tags,"Also, please test the patch if you can to see if you find any other changes in behavior.",task_subcomment,"['Also, please test the patch if you can to see if you find any other changes in behavior.']",['SOLUTION DISCUSSION']
+226159,Parsoid should support  and  natively as they are not normal parser tags,"Issues I have found:
+
+* [MAJOR] Disabling edit section links does not work for headings inside  tags
+* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue.
+* [BLOCKER] Table of contents does not include links
+* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen.
+
+Please help me solve the remaining issues.",task_subcomment,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside  tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']","['BUG REPRODUCTION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+226153,Parsoid should support  and  natively as they are not normal parser tags,"Change 91583 had a related patch set uploaded by Nikerabbit:
+Add $wgTranslatePageTranslationUseParserHook
+
+https://gerrit.wikimedia.org/r/91583",task_subcomment,['Change 91583 had a related patch set uploaded by Nikerabbit:\nAdd $wgTranslatePageTranslationUseParserHook\n\nGERRIT_URL'],['OBSERVED BUG BEHAVIOR']
+226147,Parsoid should support  and  natively as they are not normal parser tags,"Trying the parser hook solution now. I have code like:
+
+		$parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) {
+			$re = '~]+)>(.*?)~u';
+			$output = preg_replace( $re, '\2', $input );
+
+			$output = $parser->recursiveTagParse( $output, $frame );
+			$output = trim( $output );
+			return $output;
+		} );
+
+This seems to work okay on simple text, with the exception of section edit links.
+
+I'm still trying with more complex pages with templates as well extensions and our tutorial.",task_subcomment,"['Trying the parser hook solution now.', ""I have code like:\n\n\t\t$parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) {\n\t\t\t$re = '~]+)>(.*?"", "")~u';\n\t\t\t$output = preg_replace( $re, '\\2', $input );\n\n\t\t\t$output = $parser->recursiveTagParse( $output, $frame );\n\t\t\t$output = trim( $output );\n\t\t\treturn $output;\n\t\t} );\n\nThis seems to work okay on simple text, with the exception of section edit links."", ""I'm still trying with more complex pages with templates as well extensions and our tutorial.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+226141,Parsoid should support  and  natively as they are not normal parser tags,"**gmaruzz** wrote:
+
+bump",task_subcomment,['**gmaruzz** wrote:\n\nbump'],['ACTION ON ISSUE']
+226138,Parsoid should support  and  natively as they are not normal parser tags,"Niklas: So, here is what I found:
+
+https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash.
+
+https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception.
+
+I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",task_subcomment,"['Niklas: So, here is what I found:\n\nURL works and does not crash.', 'URL throws the exception.', 'I am a bit baffled why the comment in the extension content should change what hook is called.', ""I'll let you investigate from here."", 'It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+226134,Parsoid should support  and  natively as they are not normal parser tags,"Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",task_subcomment,"['Niklas: To me, it looks like an existing bug got exposed.', 'Can you provide more details?', 'Maybe full url of the API call?', 'And/or, if you hop onto #mediawiki-parsoid, we could investigate.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+226125,Parsoid should support  and  natively as they are not normal parser tags,"I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown. Does anybody have an idea why?",task_subcomment,"['I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown.', 'Does anybody have an idea why?']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+226117,Parsoid should support  and  natively as they are not normal parser tags,"To summarize:
+
+* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine.
+* This lets the translate hack work for now. At least it won't crash.
+* The translate extension will crash once we actually call the registered tag hook.
+
+So there is some time to fix this up, but we should not pretend that it is fixed right now.
+
+Can you provide more information on what stops you from using the actual tag hook?",task_subcomment,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+226108,Parsoid should support  and  natively as they are not normal parser tags,"Okay, we tested and all is good for now. You can ignore #c27 :-). 
+
+As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).",task_subcomment,"['Okay, we tested and all is good for now.', 'You can ignore #c27 :-).', 'As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).']","['SOLUTION USAGE', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+226101,Parsoid should support  and  natively as they are not normal parser tags,"Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For  and  tags found in top-level pages, since we never go through PHP parser at all, this may still not work. 
+
+Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what  and  relies on), and that will bomb.
+
+One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",task_subcomment,"['Actually, now that I wrote that, I might have misspoken about whether it will work now as well.', 'Niklas is right.', 'For  and  tags found in top-level pages, since we never go through PHP parser at all, this may still not work.', 'Parsoid will recognize the hooks because of the registration.', 'In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what  and  relies on), and that will bomb.', 'One of us (Gabriel or me) will experiment with the updated code locally and update this bug.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+226094,Parsoid should support  and  natively as they are not normal parser tags,"The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.
+
+Right now, The translate code preprocesses the page by stripping the  and  tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.
+
+If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point.
+
+So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. 
+
+I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more.
+
+Hope this summarizes where we stand now.",task_subcomment,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the  and  tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']","['SOLUTION DISCUSSION', 'FUTURE PLAN', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'FUTURE PLAN', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+226087,Parsoid should support  and  natively as they are not normal parser tags,Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.,task_subcomment,"['Misunderstanding or miscommunication about the actual requirements is not scope creep.', 'The patch which was made does not add value.', 'I changed the title to reflect the issue with my understanding of it.']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+226079,Parsoid should support  and  natively as they are not normal parser tags,"This issue appears to suffer from scope creep. The requirements of the current summary have been met. See https://translatewiki.net/wiki/Special:Version?uselang=en: Section ""Parser extension tags"" now shows "" and """,task_subcomment,"['This issue appears to suffer from scope creep.', 'The requirements of the current summary have been met.', 'See URL Section ""Parser extension tags"" now shows "" and ""']","['FUTURE PLAN', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+226073,Parsoid should support  and  natively as they are not normal parser tags,"That patch won't work well with Parsoid, see the comment in the patch set.",task_subcomment,"[""That patch won't work well with Parsoid, see the comment in the patch set.""]",['OBSERVED BUG BEHAVIOR']
+226068,Parsoid should support  and  natively as they are not normal parser tags,I don't deserve the credit for Niklas's fix. :-),task_subcomment,"[""I don't deserve the credit for Niklas's fix."", ':-)']","['CONTRIBUTION AND COMMITMENT', 'SOLUTION DISCUSSION']"
+226063,Parsoid should support  and  natively as they are not normal parser tags,"Change 83427 merged by jenkins-bot:
+Register translate and tvar to the parser
+
+https://gerrit.wikimedia.org/r/83427",task_subcomment,['Change 83427 merged by jenkins-bot:\nRegister translate and tvar to the parser\n\nGERRIT_URL'],['ACTION ON ISSUE']
+226059,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to comment #19)
+> I think I already did it yesterday.
+
+There is a comment, but now a followup question requires addresssing",task_subcomment,"['(In reply to comment #19)\nQUOTE\n\nThere is a comment, but now a followup question requires addresssing']",['INVESTIGATION AND EXPLORATION']
+226053,Parsoid should support  and  natively as they are not normal parser tags,I think I already did it yesterday.,task_subcomment,['I think I already did it yesterday.'],['OBSERVED BUG BEHAVIOR']
+226048,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to comment #17)
+> Assigning to James, hoping this may get a parsoid person to review the patch
+> that's been available for nearly a month now.
+
+Oh. We've been patiently waiting for you to merge it. :-(
+
+Will ping the team.",task_subcomment,"['(In reply to comment #17)\nQUOTE\nQUOTE\n\nOh.', ""We've been patiently waiting for you to merge it."", ':-(\n\nWill ping the team.']","['ACTION ON ISSUE', 'SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+226041,Parsoid should support  and  natively as they are not normal parser tags,"Assigning to James, hoping this may get a parsoid person to review the patch that's been available for nearly a month now.",task_subcomment,"[""Assigning to James, hoping this may get a parsoid person to review the patch that's been available for nearly a month now.""]",['ACTION ON ISSUE']
+226037,Parsoid should support  and  natively as they are not normal parser tags,"fwiw this bug has been mentioned at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_weekly_update_-_2013-09-26_.28MW_1.22wmf19.29
+
+I have also seen this problem here and there while editing at mediawiki.org. Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.",task_subcomment,"['fwiw this bug has been mentioned at URL\n\nI have also seen this problem here and there while editing at mediawiki.org.', 'Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+226033,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to comment #14)
+> In the long term yes, but wont this render VE useless on translatable pages
+> in the short them?
+
+Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE.
+
+However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.",task_subcomment,"['(In reply to comment #14)\nQUOTE\nQUOTE\n\nYes.', ""On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE."", ""However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.""]","['SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+226028,Parsoid should support  and  natively as they are not normal parser tags,"In the long term yes, but wont this render VE useless on translatable pages in the short them?",task_subcomment,"['In the long term yes, but wont this render VE useless on translatable pages in the short them?']",['SOLUTION DISCUSSION']
+226022,Parsoid should support  and  natively as they are not normal parser tags,"Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",task_subcomment,"['Niklas: If VE has to support editing for , , etc.', 'tags, Parsoid has to know about those tags.', 'Parsoid finds out about installed tags by querying mediawiki API.', 'So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+226016,Parsoid should support  and  natively as they are not normal parser tags,See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.,task_subcomment,"['See the above commit.', 'It is not thoroughly tested.', ""I still don't understand what would the benefit.""]","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+226008,Parsoid should support  and  natively as they are not normal parser tags,"Change 83427 had a related patch set uploaded by Nikerabbit:
+Register translate and tvar to the parser
+
+https://gerrit.wikimedia.org/r/83427",task_subcomment,['Change 83427 had a related patch set uploaded by Nikerabbit:\nRegister translate and tvar to the parser\n\nGERRIT_URL'],['INVESTIGATION AND EXPLORATION']
+225999,Parsoid should support  and  natively as they are not normal parser tags,Ping.,task_subcomment,['Ping.'],['OBSERVED BUG BEHAVIOR']
+225992,Parsoid should support  and  natively as they are not normal parser tags,Does someone want to try registering them and see what happens? I probably don't have time before Wikimania.,task_subcomment,"['Does someone want to try registering them and see what happens?', ""I probably don't have time before Wikimania.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+225986,Parsoid should support  and  natively as they are not normal parser tags,"I don't know. Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.",task_subcomment,"[""I don't know."", 'Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION']"
+225980,Parsoid should support  and  natively as they are not normal parser tags,@Niklas are there issues with registering them?,task_subcomment,['SCREEN_NAME are there issues with registering them?'],['OBSERVED BUG BEHAVIOR']
+225975,Parsoid should support  and  natively as they are not normal parser tags,*** Bug 52408 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 52408 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+225969,Parsoid should support  and  natively as they are not normal parser tags,"Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text.  This will also let VE support them in the future and protect them from being modified right now.
+
+Is there any other way to discover that , ,  are valid tags on the wiki, i.e. what is the mediawiki api endpoint?  So far we've been using siprop and fetching installed extension tags and use that to detect these.",task_subcomment,"['Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text.', 'This will also let VE support them in the future and protect them from being modified right now.', 'Is there any other way to discover that , ,  are valid tags on the wiki, i.e.', 'what is the mediawiki api endpoint?', ""So far we've been using siprop and fetching installed extension tags and use that to detect these.""]","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION']"
+225965,Parsoid should support  and  natively as they are not normal parser tags, and  are not a normal extension tags. Please explain why I should register them.,task_subcomment,"[' and  are not a normal extension tags.', 'Please explain why I should register them.']","['MOTIVATION', 'INVESTIGATION AND EXPLORATION']"
+225960,Parsoid should support  and  natively as they are not normal parser tags,"(In reply to comment #2)
+> Parsoid does fetch a list of registered extensions from the config and uses
+> that to wrap the block with mw:Object/Extension/ type. All
+> other unknown tags are pass through as plain text.
+
+Ah, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this. Re-filing.",task_subcomment,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nAh, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this."", 'Re-filing.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+225956,Parsoid should support  and  natively as they are not normal parser tags,"Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text.
+
+The problem is that mediawiki does not report  as an installed extension.  Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags
+
+Any idea why mw.org is not reporting  as a registered extension?",task_subcomment,"['Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type.', 'All other unknown tags are pass through as plain text.', 'The problem is that mediawiki does not report  as an installed extension.', 'Check URL\n\nAny idea why mw.org is not reporting  as a registered extension?']","['INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+225949,Parsoid should support  and  natively as they are not normal parser tags,"Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn't recognise  as an extension block; should it take the local list of registered extensions, and for ones it hasn't been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?",task_subcomment,"['Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn\'t recognise  as an extension block; should it take the local list of registered extensions, and for ones it hasn\'t been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?']",['SOLUTION DISCUSSION']
+50885,Load visualeditor modules in a closure mapping $/mw/ve to their globals,"This may introduce a really large number of scopes and have undesirable performance effects, but we need to come up with a solution nonetheless.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"['Load visualeditor modules in a closure mapping $/mw/ve to their globals\n\nThis may introduce a really large number of scopes and have undesirable performance effects, but we need to come up with a solution nonetheless.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+1236806,Load visualeditor modules in a closure mapping $/mw/ve to their globals,"In MediaWiki, we moved away from the closures (IIFEs), see {add9bd191fd4d16250b301208600854cb52f6b33} and {91f950d6b0677166134bc58eb487943a63f97b00}. So I believe this is no longer desirable.",task_subcomment,"['In MediaWiki, we moved away from the closures (IIFEs), see {add9bd191fd4d16250b301208600854cb52f6b33} and {91f950d6b0677166134bc58eb487943a63f97b00}.', 'So I believe this is no longer desirable.']","['MOTIVATION', 'SOLUTION DISCUSSION']"
+225630,Load visualeditor modules in a closure mapping $/mw/ve to their globals,"Rephrasing bug.
+
+Problems:
+
+
+* We're repeatedly referencing $/mw from global scope instead of securing the reference. This is worse for performance and for proper functioning (e.g. jQuery might be redefined at a later time causing version mismatches, this is why ResourceLoader maps $) 
+
+* We're using $ and mw directly instead of mapping jQuery and mediaWiki.
+
+* In standalone, our code executes in the global scope. This is bad.
+
+Solution:
+
+* For standalone, build the dist/ files with a closure mapping, securing and caching '$' from 'jQuery'. And for VE modules other than ve.base, it would also map 've' to 'VisualEditor' (bug 67642)
+
+* In MediaWiki, ResourceLoader already provides a closure which we'd extend to also map 've' to 'VisualEditor'.",task_subcomment,"['Rephrasing bug.', ""Problems:\n\n\n* We're repeatedly referencing $/mw from global scope instead of securing the reference."", 'This is worse for performance and for proper functioning (e.g.', ""jQuery might be redefined at a later time causing version mismatches, this is why ResourceLoader maps $) \n\n* We're using $ and mw directly instead of mapping jQuery and mediaWiki."", '* In standalone, our code executes in the global scope.', 'This is bad.', ""Solution:\n\n* For standalone, build the dist/ files with a closure mapping, securing and caching '$' from 'jQuery'."", ""And for VE modules other than ve.base, it would also map 've' to 'VisualEditor' (bug 67642)\n\n* In MediaWiki, ResourceLoader already provides a closure which we'd extend to also map 've' to 'VisualEditor'.""]","['OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION']"
+225625,Load visualeditor modules in a closure mapping $/mw/ve to their globals,"I suggest for standalone we introduce an module-intro/outro that is used to wrap around individual modules (not per file).
+
+So e.g. dist/ve.core.js would be:
+
+-- intro
+( function ( ve, $ ) {
+ -- include ve.js
+ -- include ve.A.js
+ -- include ve.B.js
+ -- include ve.C.js
+-- outro
+}( VisualEditor, jQuery ) );
+
+And in MediaWiki the same would effectively happen but on-demand by ResourceLoader (since we don't want to use a build system for MW, but instead work on the raw source files directly and have them build dynamically).
+
+See bug 48886 for details, but the end result would be:
+
+-- startup:
+register(
+ ..,
+ [ 'ext.visualEditor', 1234, ...., ['VisualEditor']
+);
+
+-- mw.loader:
+ script( $, global[propKeys..].. );
+
+-- load.php response when loading visualeditor:
+mw.loader.implement( 'ext.visualEditor.core', function ( $, ve ) {
+ -- include ve.js
+ -- include ve.A.js
+ -- include ve.B.js
+ -- include ve.C.js
+} );",task_subcomment,"['I suggest for standalone we introduce an module-intro/outro that is used to wrap around individual modules (not per file).', 'So e.g.', ""dist/ve.core.js would be:\n\n-- intro\n( function ( ve, $ ) {\n -- include ve.js\n -- include ve.A.js\n -- include ve.B.js\n -- include ve.C.js\n-- outro\n}( VisualEditor, jQuery ) );\n\nAnd in MediaWiki the same would effectively happen but on-demand by ResourceLoader (since we don't want to use a build system for MW, but instead work on the raw source files directly and have them build dynamically)."", ""See bug 48886 for details, but the end result would be:\n\n-- startup:\nregister(\n ..,\n [ 'ext.visualEditor', 1234, ...., ['VisualEditor']\n);\n\n-- mw.loader:\n script( $, global[propKeys..].. );\n\n-- load.php response when loading visualeditor:\nmw.loader.implement( 'ext.visualEditor.core', function ( $, ve ) {\n -- include ve.js\n -- include ve.A.js\n -- include ve.B.js\n -- include ve.C.js\n} );""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+225620,Load visualeditor modules in a closure mapping $/mw/ve to their globals,"For the record, inside ResourceLoader context $ is a local variable provided by the ResourceLoader built-in closure.
+
+See also bug 48886.",task_subcomment,"['For the record, inside ResourceLoader context $ is a local variable provided by the ResourceLoader built-in closure.', 'See also bug 48886.']","['INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR']"
+50844,VisualEditor: Multiple empty lines turn into uneditable elements due to mwPlaceholder,"If wikitext contains several empty lines in a row, hovering over those lines in the VisualEditor will present them as uneditable elements. Since the VisualEditor is perfectly able to create and remove empty lines, this seems unnecessary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Multiple empty lines turn into uneditable elements due to mwPlaceholder\n\nIf wikitext contains several empty lines in a row, hovering over those lines in the VisualEditor will present them as uneditable elements.', 'Since the VisualEditor is perfectly able to create and remove empty lines, this seems unnecessary.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+223313,VisualEditor: Multiple empty lines turn into uneditable elements due to mwPlaceholder,"This has been fixed (by removing the mwPlaceholder code in Parsoid, now that VisualEditor can handle these). Sorry for not responding before.",task_subcomment,"['This has been fixed (by removing the mwPlaceholder code in Parsoid, now that VisualEditor can handle these).', 'Sorry for not responding before.']","['SOLUTION DISCUSSION', 'ACTION ON ISSUE']"
+50830,VisualEditor: Invalid or non-matching tags should not be normalised in unchanged sections of the document,"In this edit the user only made the ""die -> der"" change. In addition the  was removed by the VisualEditor.
+
+http://de.wikipedia.org/w/index.php?title=Fu%C3%9Fball-Bremen-Liga_2012%2F13&diff=118880158&oldid=118873211
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+T52052
+T52050",task_description,"['VisualEditor: Invalid or non-matching tags should not be normalised in unchanged sections of the document\n\nIn this edit the user only made the ""die -> der"" change.', 'In addition the  was removed by the VisualEditor.', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nT52052\nT52050']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+1845920,VisualEditor: Invalid or non-matching tags should not be normalised in unchanged sections of the document,"Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.",task_subcomment,"['Parsoid\'s ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit.', 'Please re-open if you run into similar dirty diffs that happened within the last year or so.']","['OBSERVED BUG BEHAVIOR', 'ACTION ON ISSUE']"
+222148,VisualEditor: Invalid or non-matching tags should not be normalised in unchanged sections of the document,"OK, then it's a different issue. Created a new one for it: #50050.",task_subcomment,"[""OK, then it's a different issue."", 'Created a new one for it: #50050.']","['OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION']"
+222139,VisualEditor: Invalid or non-matching tags should not be normalised in unchanged sections of the document,"This is due to the merging of the 2  tags. Currently it fails compare custom attributes like ""style"" when attempting to merge equal annotation sequences.",task_subcomment,"['This is due to the merging of the 2  tags.', 'Currently it fails compare custom attributes like ""style"" when attempting to merge equal annotation sequences.']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+222131,VisualEditor: Invalid or non-matching tags should not be normalised in unchanged sections of the document,Other example: https://www.mediawiki.org/w/index.php?title=Git%2FConversion%2Fpywikipedia&diff=714194&oldid=713893 (not tag removal but tag property removal). The only real edit is at the bottom.,task_subcomment,"['Other example: URL (not tag removal but tag property removal).', 'The only real edit is at the bottom.']","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR']"
+50829,VisualEditor: Write test cases for ElementLinearData#getAnnotationIndexesFromOffset,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,['VisualEditor: Write test cases for ElementLinearData#getAnnotationIndexesFromOffset\n\n\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'],['INVESTIGATION AND EXPLORATION']
+50796,VisualEditor: Deleting a line break causes strange results,"Steps to Reproduce:
+
+1. Go to https://www.mediawiki.org/wiki/API:Alltransclusions
+2. Insert a blank line after the first paragraph.
+3. Use the Del key (not backspace) to delete that line.
+
+Rather than deleting the line, the first keypress (sometimes) does nothing. And then the second keypress finally gets rid of the newline, but attempting to save the page shows a diff with the newline still added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",task_description,"['VisualEditor: Deleting a line break causes strange results\n\nSteps to Reproduce:\n\n1.', 'Go to URL\n2.', 'Insert a blank line after the first paragraph.', '3.', 'Use the Del key (not backspace) to delete that line.', 'Rather than deleting the line, the first keypress (sometimes) does nothing.', 'And then the second keypress finally gets rid of the newline, but attempting to save the page shows a diff with the newline still added.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION USAGE', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+219887,VisualEditor: Deleting a line break causes strange results,This was fixed in the re-write of deletion handling in CE; sorry for not marking it as such beforehand.,task_subcomment,['This was fixed in the re-write of deletion handling in CE; sorry for not marking it as such beforehand.'],['BUG REPRODUCTION']
+219884,VisualEditor: Deleting a line break causes strange results,"Created attachment 12390
+Bug in Firefox 21
+
+The described problem is slight different for me (Firefox 21)
+
+When inserting a new line and then deleting it, the paragraph is swapped with the next one.
+
+Although both paragraphs are still present on the visual editor, the edit diff shows that the first one has been removed.
+
+**Attached**: {F10655}",task_subcomment,"['Created attachment 12390\nBug in Firefox 21\n\nThe described problem is slight different for me (Firefox 21)\n\nWhen inserting a new line and then deleting it, the paragraph is swapped with the next one.', 'Although both paragraphs are still present on the visual editor, the edit diff shows that the first one has been removed.', '**Attached**: {F10655}']","['BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+50789,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),"There are essentially two ways to create a link:
+
+#1 You enter the link's text, select it, click the link button (or CTRL-K), and choose the link target.
+
+#2 You click the link button first, enter the target and get out of the dialog, at which point the link text (identical to chosen link target) will be entered.
+
+I'm not sure which method users prefer, but it's clear that both methods should work seamlessly. However, with the current setup both methods are problematic:
+
+#1 Once the correct target has been picked (either by entering it, or by selecting from the list), it is not quite clear what the user should do next. Is the back arrow the right thing to do, or does that cancel the selection? Should I simply click outside of the dialog, or does that cancel? It turns out: if the target was selected from the list, both these actions are correct and do not cancel the choice, but if the link target was entered by hand (and not followed by Enter!), both actions do cancel the choice. The fastest way is to enter the link target and hit Enter twice. This is all fairly unintuitive.
+
+#2 With this method, the user will often have to adjust the link's text afterwards, for instance in the case of plurals or if the target article is disambiguated with parentheses. But it is not clear to the user that adjusting the link text is safe and won't create a broken link; indeed the crucial distinction between link text and link target remains obscure. (Changing a singular to a plural is especially difficult since editing links at the end is not allowed.)
+
+I have checked the workflow of entering links in LibreOffice, Gmail and Word; they are all basically the same as in the Visual Editor, with two major differences: 
+
+a) the dialog popup window has a clear OK button, and
+
+b) the dialog popup window contains separate clearly labeled boxes for the link text and the link target. 
+
+I believe both of these changes make a lot of sense.
+
+When entering the dialog from an existing link or from highlighted text, that text should automatically be entered into the link text's box, with a corresponding suggestion for the link target preselected, but both boxes should be editable independently. The link target box should have a list of further suggestions underneath. Once everything is OK, clicking the OK button or hitting Enter should create the link; clicking outside of the dialog box or hitting the back arrow should cancel the action.
+
+There is another minor issue: right now, when hovering over an existing link, the link target is displayed in a popup; when clicking on the link, a separate link symbol popup occurs which does not show the link target. The meaning of that symbol is not clear; it turns out that clicking on it will open the dialog popup, allowing to change or remove the link. Gmail solves this issue as follows: hovering over a link will not display anything, but when clicking on a link, a tiny popup appears giving the link's target and options to change or remove the link. I find that completely self-explanatory.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",task_description,"[""VisualEditor: Improvements and  behaviour changes to the link input widget (tracking)\n\nThere are essentially two ways to create a link:\n\n#1 You enter the link's text, select it, click the link button (or CTRL-K), and choose the link target."", '#2 You click the link button first, enter the target and get out of the dialog, at which point the link text (identical to chosen link target) will be entered.', ""I'm not sure which method users prefer, but it's clear that both methods should work seamlessly."", 'However, with the current setup both methods are problematic:\n\n#1 Once the correct target has been picked (either by entering it, or by selecting from the list), it is not quite clear what the user should do next.', 'Is the back arrow the right thing to do, or does that cancel the selection?', 'Should I simply click outside of the dialog, or does that cancel?', 'It turns out: if the target was selected from the list, both these actions are correct and do not cancel the choice, but if the link target was entered by hand (and not followed by Enter!', '), both actions do cancel the choice.', 'The fastest way is to enter the link target and hit Enter twice.', 'This is all fairly unintuitive.', ""#2 With this method, the user will often have to adjust the link's text afterwards, for instance in the case of plurals or if the target article is disambiguated with parentheses."", ""But it is not clear to the user that adjusting the link text is safe and won't create a broken link; indeed the crucial distinction between link text and link target remains obscure."", '(Changing a singular to a plural is especially difficult since editing links at the end is not allowed.)', 'I have checked the workflow of entering links in LibreOffice, Gmail and Word; they are all basically the same as in the Visual Editor, with two major differences: \n\na) the dialog popup window has a clear OK button, and\n\nb) the dialog popup window contains separate clearly labeled boxes for the link text and the link target.', 'I believe both of these changes make a lot of sense.', ""When entering the dialog from an existing link or from highlighted text, that text should automatically be entered into the link text's box, with a corresponding suggestion for the link target preselected, but both boxes should be editable independently."", 'The link target box should have a list of further suggestions underneath.', 'Once everything is OK, clicking the OK button or hitting Enter should create the link; clicking outside of the dialog box or hitting the back arrow should cancel the action.', 'There is another minor issue: right now, when hovering over an existing link, the link target is displayed in a popup; when clicking on the link, a separate link symbol popup occurs which does not show the link target.', 'The meaning of that symbol is not clear; it turns out that clicking on it will open the dialog popup, allowing to change or remove the link.', ""Gmail solves this issue as follows: hovering over a link will not display anything, but when clicking on a link, a tiny popup appears giving the link's target and options to change or remove the link."", 'I find that completely self-explanatory.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'BUG REPRODUCTION', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'INVESTIGATION AND EXPLORATION', 'BUG REPRODUCTION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'EXPECTED BEHAVIOR', 'SOLUTION DISCUSSION']"
+403707,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),Now tracked in #VisualEditor-MediaWiki-Links instead.,task_subcomment,['Now tracked in #VisualEditor-MediaWiki-Links instead.'],['INVESTIGATION AND EXPLORATION']
+219497,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),*** Bug 57716 has been marked as a duplicate of this bug. ***,task_subcomment,"['*** Bug 57716 has been marked as a duplicate of this bug.', '***']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+219491,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),Turning this into a tracking bug as it's a lot easier to understand that way.,task_subcomment,"[""Turning this into a tracking bug as it's a lot easier to understand that way.""]",['ACTION ON ISSUE']
+219486,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),"at en.wp Mauro Bieg comments:
+""The add-link dialog should have a clear ""OK"" and ""Cancel"" button. Right now, you have no obvious way to get rid of it and it is not clear what happens when you click somewhere else (the dialog goes away, but did it save the changes or not?) Also, what does the strange back button (<) to the left do? and are the Link-symbol and ""Hyperlink"" two buttons or a description or what (nothing happens when I click on them)? The trash symbol is good and does what you'd expect it to: remove the link.""",task_subcomment,"['at en.wp Mauro Bieg comments:\n""The add-link dialog should have a clear ""OK"" and ""Cancel"" button.', 'Right now, you have no obvious way to get rid of it and it is not clear what happens when you click somewhere else (the dialog goes away, but did it save the changes or not?)', 'Also, what does the strange back button (<) to the left do?', 'and are the Link-symbol and ""Hyperlink"" two buttons or a description or what (nothing happens when I click on them)?', 'The trash symbol is good and does what you\'d expect it to: remove the link.""']","['INVESTIGATION AND EXPLORATION', 'INVESTIGATION AND EXPLORATION', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR']"
+219479,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),"Adam Cuerden comments again on the suggestion to have separate boxes for link target and link title:
+""Yes [that would be better], but do make sure it's on the same page. Don't give one dialogue, then a second. Also, if one of the boxes is left blank, it should be auto-completed from the other box. ""
+
+For the second part of the comment they mean that if someone gives a link target (e.g. Fish) and doesn't specify any title, produce a link: [[Fish]]
+If someone gives a link title (e.g. Hedgehog) but doesn't specify a target, produce the link: [[Hedgehog]].",task_subcomment,"['Adam Cuerden comments again on the suggestion to have separate boxes for link target and link title:\n""Yes [that would be better], but do make sure it\'s on the same page.', ""Don't give one dialogue, then a second."", 'Also, if one of the boxes is left blank, it should be auto-completed from the other box. ""', 'For the second part of the comment they mean that if someone gives a link target (e.g.', ""Fish) and doesn't specify any title, produce a link: [[Fish]]\nIf someone gives a link title (e.g."", ""Hedgehog) but doesn't specify a target, produce the link: [[Hedgehog]].""]","['SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'SOLUTION DISCUSSION', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION']"
+219477,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),"English Wikipedia user comments that the current behaviour of the input widget is not intuitive at all:
+
+""I clicked the link tool while not focused on any text, to try and add a new link. I got a largely empty box with no instructions, and the next word in the article highlighted within the box.  I fiddled with it a few times, and still don't know if typing in the box A. changes the text of the link. B. allows me to select more words. C. Changes what is linked to, or D. is followed by another, nearly identical box for a secondary function""
+
+To me this is further evidence that we need two boxes: one to enter the link target and one to enter the link display text. The second box would default to the same as the link for internal links and for external links either (ideally) the page title or (less ideally but probably easier) the filename sans extension. 
+
+This would also fix Bug 50945 and Bug 51438 (if the latter is distinct from the former)",task_subcomment,"['English Wikipedia user comments that the current behaviour of the input widget is not intuitive at all:\n\n""I clicked the link tool while not focused on any text, to try and add a new link.', 'I got a largely empty box with no instructions, and the next word in the article highlighted within the box.', ""I fiddled with it a few times, and still don't know if typing in the box A. changes the text of the link."", 'B. allows me to select more words.', 'C. Changes what is linked to, or D. is followed by another, nearly identical box for a secondary function""\n\nTo me this is further evidence that we need two boxes: one to enter the link target and one to enter the link display text.', 'The second box would default to the same as the link for internal links and for external links either (ideally) the page title or (less ideally but probably easier) the filename sans extension.', 'This would also fix Bug 50945 and Bug 51438 (if the latter is distinct from the former)']","['OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'OBSERVED BUG BEHAVIOR', 'INVESTIGATION AND EXPLORATION', 'SOLUTION DISCUSSION', 'SOLUTION DISCUSSION', 'BUG REPRODUCTION']"
+219473,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),(inspector->input widget; inspector is the context menu with buttons to open a dialog or input widget),task_subcomment,['(inspector->input widget; inspector is the context menu with buttons to open a dialog or input widget)'],['OBSERVED BUG BEHAVIOR']
+219468,VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),"Alternately, once a link is selected we could have the link inspector automatically close (re: OK buttons). I'm more of a fan of OK buttons because I think auto-closes are just inviting someone to mis-click and get infuriated at the software for going away and leaving them with the wrong link.",task_subcomment,"['Alternately, once a link is selected we could have the link inspector automatically close (re: OK buttons).', ""I'm more of a fan of OK buttons because I think auto-closes are just inviting someone to mis-click and get infuriated at the software for going away and leaving them with the wrong link.""]","['SOLUTION DISCUSSION', 'SOLUTION DISCUSSION']"
+50772,"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","User can enter html tags or provide tag attributes or attribute values that Parsoid (and downstream clients) treat specially.
+
+Ex: #mwt3 for about-ids, or mw:Object/* for typeofs or